Files
ai-coding-skills/skills/create-plan/cursor/templates/story-tracker.md
Stefano Fiorini d2970b06bd feat(create-plan): add iterative cross-model plan review and Cursor variant
Add a configurable reviewer phase to all create-plan variants (claude-code,
codex, opencode) that sends the plan to a second CLI/model for iterative
feedback (max 5 rounds). Supported reviewer CLIs: codex, claude, cursor.

Add new Cursor Agent CLI variant with full skill, templates, and
workspace-discovery-based prerequisites (.cursor/rules/).

Update README and docs/CREATE-PLAN.md with Cursor install/verify,
reviewer CLI requirements, and supported reviewer CLIs table.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 13:58:11 -06:00

1.9 KiB

Story Tracker: [Plan Title]

Progress Summary

  • Current Milestone: M1
  • Stories Complete: 0/N
  • Milestones Approved: 0/M
  • Last Updated: YYYY-MM-DD

Tracking Guardrails

  • Update status immediately when work starts (in-dev) and when work completes (completed).
  • Require explicit user approval at each milestone boundary before continuing.
  • Do not push until all milestones are approved and permission is explicitly granted.
  • Keep this file and milestone-plan.md synchronized.

Milestones

M1: [Name]

Story Description Status Notes
S-101 [Brief description] pending
S-102 [Brief description] pending
S-103 [Brief description] pending

Approval Status: pending


M2: [Name]

Story Description Status Notes
S-201 [Brief description] pending
S-202 [Brief description] pending
S-203 [Brief description] pending

Approval Status: pending


Status Legend

Status Meaning
pending Not started
in-dev Currently being worked on
completed Done - include commit hash in Notes
deferred Postponed - include reason in Notes

Update Instructions (MANDATORY)

Before starting any story:

  1. Mark story as in-dev
  2. Update "Last Updated"

After completing any story:

  1. Mark story as completed
  2. Add local commit hash to Notes
  3. Update "Stories Complete" and "Last Updated"

At milestone boundary:

  1. Run lint/typecheck/tests for changed files
  2. Commit (no push)
  3. Request feedback
  4. Apply feedback, re-check changed files, commit again
  5. Mark milestone Approval Status: approved only after user confirms
  6. Continue only after approval

After all milestones approved:

  • Ask permission to push and then mark plan completed.