# Issues Management System
## Directory Structure
- `/issues` - Root directory for all issues
- First level: Milestone folders (e.g., `m001-InitProject`)
- Second level: Issue files within each milestone
## Issue Types and Naming
Issue files follow the naming pattern: `{id}-{type}-{description}.md`
- `{id}`: Globally unique identifier across all issues
- `{type}`: One of the following:
- `story` - User story describing complete user value
- `feat` - New feature implementation
- `fix` - Bug fix
- `test` - Test implementation
- `{description}`: Brief kebab-case description
## Issue States
Tasks and issues can have the following states:
- `[ ]` - Not started
- `[x]` - Completed
- `[-]` - In progress
- `[*]` - Skipped
- `[!]` - Abandoned
## Templates
Two types of issue templates are available in `/issues/templates/`:
1. `story.md` - For user stories
2. `issue.md` - For features, fixes, and tests
## File Modification Rules
- Only modify task/issue states in existing files
- Do not alter other content without creating a new issue
- Always update Status History when changing states
First Time Repository
Use local issues file deal with Cursor and Vscode
unknown
Created: 1/8/2025
Updated: 1/23/2025
All Repositories (1)
Use local issues file deal with Cursor and Vscode