Feature Plan Execution Assistant

Feature Plan Execution Assistant

Help me work through a feature plan one task at a time.

Step 1: Gather Context

Ask me for:

• Feature name (kebab-case, e.g., user-authentication)
• Brief feature/branch description
• Relevant planning doc path (default docs/ai/planning/feature-{name}.md)
• Any supporting design/implementation docs (design, requirements, implementation)
• Current branch and latest diff summary (git status -sb, git diff --stat)

Step 2: Load the Plan

• Request the planning doc contents or offer commands like:

  cat docs/ai/planning/feature-<name>.md
  

• Parse sections that represent task lists (look for headings + checkboxes [ ], [x]).
• Build an ordered queue of tasks grouped by section (e.g., Foundation, Core Features, Testing).

Step 3: Present Task Queue

Show an overview:

### Task Queue: <Feature Name>
1. [status] Section • Task title
2. ...

Status legend: todo, in-progress, done, blocked (based on checkbox/notes if present).

Step 4: Interactive Task Execution

For each task in order:

1. Display the section/context, full bullet text, and any existing notes.
2. Suggest relevant docs to reference (requirements/design/implementation).
3. Ask: "Plan for this task?" Offer to outline sub-steps using the design doc.
4. Prompt to mark status (done, in-progress, blocked, skipped) and capture short notes/next steps.
5. Encourage code/document edits inside Cursor; offer commands/snippets when useful.
6. If blocked, record blocker info and move task to the end or into a "Blocked" list.

Step 5: Update Planning Doc

After each status change, generate a Markdown snippet the user can paste back into the planning doc, e.g.:

- [x] Task: Implement auth service (Notes: finished POST /auth/login, tests added)

Remind the user to keep the source doc updated.

Step 6: Check for Newly Discovered Work

After each section, ask if new tasks were discovered. If yes, capture them in a "New Work" list with status todo and include in the summary.

Step 7: Session Summary

Produce a summary table:

### Execution Summary
- Completed: (list)
- In Progress: (list + owners/next steps)
- Blocked: (list + blockers)
- Skipped / Deferred: (list + rationale)
- New Tasks: (list)

Step 8: Next Actions

Remind the user to:

• Update docs/ai/planning/feature-{name}.md with the new statuses
• Sync related docs (requirements/design/implementation/testing) if decisions changed
• Run /check-implementation to validate changes against design docs
• Run /writing-test to produce unit/integration tests targeting 100% coverage
• Run /update-planning to reconcile the planning doc with the latest status
• Run /code-review when ready for final review
• Run test suites relevant to completed tasks

Let me know when you're ready to start executing the plan. Provide the feature name and planning doc first.