track-milestone

Track Milestone Skill

When to use this Skill

Activate when the user:

• Mentions creating, updating, or checking milestones
• Uses keywords: "milestone", "deadline", "deliverable", "release", "target", "due date"
• Wants to track major project achievements
• References project timeline or roadmap
• Needs to manage milestone dependencies
• Wants to see progress toward goals

Workflow

Phase 1: Context Discovery & Intent Recognition

Objective: Understand project structure and user's specific milestone intent.

Steps:

1. Locate project RULE.md and milestones.yaml:

   ls RULE.md milestones.yaml
   

2. Read both files:

   • RULE.md: Project methodology, milestone tracking preferences
   • milestones.yaml: Existing milestones and structure

3. Detect user intent:

   • Create milestone: "create milestone", "add milestone", "new milestone"
   • Update milestone: "update milestone", "milestone progress", "mark complete"
   • Check status: "milestone status", "show milestones", "timeline"
   • Manage dependencies: "milestone depends on", "blocking milestone"

4. Route to appropriate workflow:

   • Create → Workflow A
   • Update → Workflow B
   • Status → Workflow C
   • Dependencies → Workflow D

Workflow A: Create Milestone

Objective: Add a new milestone to the project timeline.

Steps:

1. Gather milestone details:

   Name:

   Milestone name?
   Example: "Beta Release", "MVP Launch", "Security Audit Complete"
   

   Description:

   Brief description of what this milestone represents?
   

   Target date:

   Target completion date? (YYYY-MM-DD or relative like "end of Q2")
   

   Deliverables:

   What needs to be delivered for this milestone?
   - Deliverable 1
   - Deliverable 2
   

   Owner (optional):

   Who's responsible for this milestone? (@name or "Team")
   

   Dependencies (optional):

   Does this milestone depend on any other milestones?
   Example: "After Alpha Release" or "After milestones 1 and 2"