Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are guiding a project through an RFC-driven development workflow with these stages:
| # | Stage | Artifact | Command / Prompt |
|---|---|---|---|
| 0 | Document an existing codebase (instead of stages 1, 3 and 4) | PRD.md, FEATURES.md, RULES.md | /document-existing (document-existing-prompt.md) |
| 1 | Create PRD | PRD.md | /create-prd (interactive-prd-creation-prompt.md) |
| 2 | Verify PRD | PRD.md (improved) + PRD-REVIEW.md | /verify-prd (prd-comprehensive-verification-prompt.md) |
| 3 | Extract features | FEATURES.md | /extract-features (prd-to-features-prompt.md) |
| 4 | Generate rules | RULES.md | /generate-rules (prd-to-rules-prompt.md) |
| 5 | Generate RFCs | RFCs/ folder + RFCS.md | /generate-rfcs (prd-to-rfcs-prompt.md) |
| 6 | Testing strategy | TEST-STRATEGY.md | /test-strategy (testing-strategy-prompt.md) |
| 7 | Implement RFCs (each once its declared predecessors are done) | Code | /implement-rfc <id> (implementation-prompt-template.md) |
| 8 | Review each implementation | reviews/REVIEW-RFC-<id>.md | /review-rfc <id> (code-review-prompt.md) |
| 9 | Manage changes (whenever requirements move) | changes/CHANGE-REQUEST-<nnn>.md | /manage-changes (prd-change-management-prompt.md) |
| 10 | Status check (anytime) | this report | /workflow-status (workflow-status-prompt.md) |
Stage 6 comes before stage 7 deliberately: a test plan written after the code is a coverage audit, not a plan.
Inspect the current project to determine workflow progress. If trace-check.py is available -- in a scripts/ folder beside these instructions, or in the project's own scripts/ folder -- run it on the project first (python3 <path>/trace-check.py .): it checks IDs, coverage, RFC dependencies and review records mechanically, and its FAIL lines belong in your Inconsistencies section.
/implement-rfc and /review-rfc keep current, then verify it: spot-check the acceptance criteria of every RFC it marks Implemented or Reviewed against the actual code, and report any status the code does not support. Do not assume an RFC is done just because code exists, or because the column says so.reviews/ for a report per implemented RFC — an implemented RFC with no review is the most common real-world gap, and reviews are exactly what gets skipped under deadline.changes/ whose decisions are still pending?If you cannot inspect files directly, ask me to describe or paste the artifacts before reporting.
Then report:
Status table — each workflow stage with its artifact and status (Done / In progress / Missing / Stale)
Per-RFC progress — implementation and review status side by side, one row per RFC:
RFC-001 implemented ✅ reviewed ❌
RFC-002 implemented ✅ reviewed ❌
RFC-003 implemented ✅ reviewed ✅
A single "reviews done" row hides which RFCs were actually reviewed. Report them individually.
Inconsistencies — anything drifted, skipped, or contradictory, with file references
Next step — the single recommended next action, with the exact command or prompt to run
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Interview the user about a product idea and write PRD.md. Use at the start of a new project, before features, rules or RFCs exist.
The English summary is being prepared. Showing the original description.
Document an existing codebase as PRD.md, FEATURES.md and RULES.md, so new work is planned against the code as it is. Use instead of create-prd when the code already exists.
The English summary is being prepared. Showing the original description.
Turn PRD.md into FEATURES.md: permanent feature IDs, MoSCoW priorities, acceptance criteria and the PRD requirement each feature comes from.
The English summary is being prepared. Showing the original description.
Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.
The English summary is being prepared. Showing the original description.
Write RULES.md, the project standards the AI must follow, with registry-verified dependency versions and permanent rule IDs.
The English summary is being prepared. Showing the original description.
Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.
The English summary is being prepared. Showing the original description.