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>
107 lines
2.5 KiB
Markdown
107 lines
2.5 KiB
Markdown
# [Plan Title]
|
|
|
|
## Overview
|
|
- **Goal:** [One sentence describing the end state]
|
|
- **Created:** YYYY-MM-DD
|
|
- **Status:** In Progress | Complete
|
|
|
|
## Planning Guardrails
|
|
- This plan assumes design was validated before implementation planning.
|
|
- Skills are invoked via workspace discovery (`.cursor/rules/`).
|
|
- Milestones require verification + local commits + explicit approval before proceeding.
|
|
|
|
## Context
|
|
|
|
### Requirements
|
|
[Gathered requirements from user questions]
|
|
|
|
### Constraints
|
|
[Technical, business, or timeline constraints]
|
|
|
|
### Success Criteria
|
|
[How we know this is complete]
|
|
|
|
## Architecture
|
|
|
|
### Design Decisions
|
|
[Key architectural choices and rationale]
|
|
|
|
### Component Relationships
|
|
[How pieces fit together]
|
|
|
|
### Data Flow
|
|
[How data moves through the system]
|
|
|
|
## Milestones
|
|
|
|
### M1: [Name]
|
|
**Description:** [What this milestone achieves]
|
|
|
|
**Acceptance Criteria:**
|
|
- [ ] [Criterion 1]
|
|
- [ ] [Criterion 2]
|
|
|
|
**Stories:** S-101, S-102, S-103...
|
|
|
|
**Milestone Completion Rule (MANDATORY):**
|
|
- Run lint/typecheck/tests for changed files.
|
|
- Commit locally (DO NOT push).
|
|
- Stop and ask user for feedback.
|
|
- Apply feedback, re-check changed files, commit again.
|
|
- Move to next milestone only after user approval.
|
|
|
|
---
|
|
|
|
### M2: [Name]
|
|
**Description:** [What this milestone achieves]
|
|
|
|
**Acceptance Criteria:**
|
|
- [ ] [Criterion 1]
|
|
- [ ] [Criterion 2]
|
|
|
|
**Stories:** S-201, S-202, S-203...
|
|
|
|
**Milestone Completion Rule (MANDATORY):**
|
|
- Run lint/typecheck/tests for changed files.
|
|
- Commit locally (DO NOT push).
|
|
- Stop and ask user for feedback.
|
|
- Apply feedback, re-check changed files, commit again.
|
|
- Move to next milestone only after user approval.
|
|
|
|
---
|
|
|
|
## Technical Specifications
|
|
|
|
### Types & Interfaces
|
|
```typescript
|
|
// Key type definitions (or equivalent language constructs)
|
|
```
|
|
|
|
### API Contracts
|
|
```typescript
|
|
// Endpoint signatures, request/response shapes (if applicable)
|
|
```
|
|
|
|
### Constants & Enums
|
|
```typescript
|
|
// Shared constants (if applicable)
|
|
```
|
|
|
|
## Files Inventory
|
|
|
|
| File | Purpose | Milestone |
|
|
|------|---------|-----------|
|
|
| `path/to/file.ts` | [What it does] | M1 |
|
|
| `path/to/other.ts` | [What it does] | M2 |
|
|
|
|
---
|
|
|
|
## Related Plan Files
|
|
|
|
This file is part of the plan folder under `ai_plan/`:
|
|
- `original-plan.md` - Original approved plan (reference for original intent)
|
|
- `final-transcript.md` - Final planning transcript (reference for rationale/context)
|
|
- `milestone-plan.md` - This file (full specification)
|
|
- `story-tracker.md` - Status tracking (must be kept up to date)
|
|
- `continuation-runbook.md` - Resume/execution context (read first)
|