Plan first
Always run @plan_feature.md before coding so agents and humans align on scope.
Core templates
| Prompt | Purpose | When to run | Works with |
|---|---|---|---|
@create_brief.md | Capture north star, stakeholders, risks | Project kickoff or when goals change | Claude, Gemini, Codex, OpenCode, Cursor |
@plan_feature.md | Generate concise engineering plan and file list | Before any implementation | All tools |
@code_review.md | Validate implementation versus plan | Before merging or shipping | All tools |
@write_docs.md | Produce final documentation bundle | After finishing feature or bug fix | All tools |
Prompt files in the toolkit
prompts/create_brief.md– summarises goals, stakeholders, risks, and success criteria for a project or epic.prompts/plan_feature.md– outlines phases, file changes, acceptance checks, and test notes before coding.prompts/code_review.md– compares implementation against the agreed plan, flagging regressions and missing coverage.prompts/write_docs.md– stitches together plan, review, and execution notes into a final documentation package.prompts/README.md– instructions for storing and referencing prompts across Claude, Gemini, Codex, OpenCode, and Cursor.
Copy these into .claude/prompts/ (or equivalent) and keep the originals version-controlled so your team can customise safely.
Usage tips
Link prompts
Include the prompt output in session updates so context persists across tools.
Customize copies
Keep the originals untouched and clone them per project for extra checks or compliance language.
Advanced workflows
| Scenario | Recommended order |
|---|---|
| Large feature | @create_brief → @plan_feature → run specialist agents → @code_review → @write_docs |
| Bug fix | @plan_feature (bug mode) → agents → @code_review |
| Documentation only | @create_brief → @write_docs |