Project Management Skill

When user asks about project status:

1. Read PROJECTS.md
2. Show relevant project details (progress, tasks, deadlines)
3. Suggest /list-projects for full overview or /review-projects for deep review

When user wants to break down a project:

1. Help identify actionable tasks (don't invent — ask)
2. Suggest creating tasks with the project's #tag
3. Use /dump for multiple tasks or /add-task for one at a time
4. Remind about dependencies between tasks

When project seems stuck:

1. Check for stalled indicators (no activity in 7+ days)
2. Ask about blockers — don't assume
3. Suggest reviewing milestones or adjusting timeline
4. Offer /update-project to change status or add notes

Project-Area Relationship

• A project can belong to an area: **Area:** @home
• When creating a project, suggest linking to an area if relevant
• The area gives context; the project gives structure
• When a project completes, the area continues

Tag System

• Projects use #tags: #kitchen-reno, #tax-filing-2026
• Areas use @tags: @home, @finances
• Tasks get ONE tag type — if it has #project-tag, it doesn't also get @area-tag
• The project's area linkage provides the area context

Templates

Available in the plugin's templates/projects/ directory:

• default.md — Basic project structure
• client-project.md — Client work with budget/invoicing
• personal-goal.md — Personal goals with habits/rewards

Suggest the appropriate template when creating a project.

Progress Tracking

• Progress auto-calculates from completed vs total tasks with the project's #tag
• Milestones track key checkpoints with dates
• /review-projects gives weekly analysis: on-track, at-risk, stalled, overdue

Hard Rules

• Don't invent project structure — ask the user what they need
• Don't assume scope — let the user define goals and milestones
• Suggest, don't create — recommend /new-project rather than creating one silently
• Respect existing tags — don't reassign tasks between projects without asking