~aod-build

Implementation Checkpoint Skill

Purpose

Automatically generate standardized checkpoint reports that document implementation progress at strategic milestones. Each report includes completed tasks, remaining work, technical achievements, knowledge base entries, quality metrics, and resume instructions.

When to Use

Create a checkpoint at:

1. Complete phase finish - All tasks in a phase marked complete
2. User story completion - Entire user story implemented and tested
3. Critical milestone - Core functionality ready (e.g., MVP core)
4. Before pausing - Stopping for review, testing, or user feedback
5. After architect review - Major approval/sign-off received

How to Use

Quick Usage

# Navigate to skill directory
cd .claude/skills/~aod-build

# Generate checkpoint (interactive prompts will follow)
python scripts/generate_checkpoint.py \
  --tasks-file ../../specs/{feature-id}/tasks.md \
  --output-dir ../../specs/{feature-id} \
  --description "{Phase-Description}"

Step-by-Step Process

1. Analyze completion status

   # Script automatically:
   # - Reads tasks.md
   # - Counts [X] completed vs [ ] pending
   # - Calculates progress percentage
   # - Identifies completed phases
   # - Determines task range
   

2. Provide context when prompted

   Key achievements (3-5 bullet points):
   > - Achievement 1
   > - Achievement 2
   > - Achievement 3
   
   Knowledge base entries captured (count or 'none'):
   > 2
   
   [For each KB entry, provide: Title, Problem, Solution]
   

3. Review generated report

   # Output: CHECKPOINT-{NN}_{Description}_{TaskRange}.md
   # Location: specs/{feature-id}/
   

4. Verify index updated

   # Check: CHECKPOINTS_README.md includes new checkpoint
   

Checkpoint Naming Convention

Format: CHECKPOINT-{NN}_{Phase-Description}_{TaskRange}.md

Components:

• {NN}: Sequential checkpoint number (01, 02, 03...) - auto-detected
• {Phase-Description}: Milestone name (e.g., "Phase1-2-Complete", "US1-Complete")
• {TaskRange}: Task IDs covered (e.g., "T001-T030")