CodingText outputGuided
4 Agents to Spec, Build, Break, and Fix a Feature
Four agents take turns: write the spec, build it, try to break it, then fix it. Why it matters: fewer half-done features.
Scanned · no issuesReady to use
Prompt
Run a 4-agent feature pipeline.
Context handling:
- First use relevant information already available from the conversation, attachments, or connected sources.
- Do not ask me to repeat details you already have.
- If a required detail is missing, ask one short follow-up.
- State important assumptions. Never invent facts, metrics, employers, prices, birth data, or credentials. Use [NEEDED] when something is missing.
Feature request:
{{feature}}
Repo / stack notes:
{{stack}}
Agents in order:
1) SPEC — acceptance criteria, non-goals, edge cases
2) BUILD — implementation plan or code sketch
3) BREAK — tests, failure cases, security holes
4) FIX — patches for what BREAK found
End with: DONE checklist + remaining risks. Do not invent APIs that don't exist in the stack notes.Create your final prompt
Add your context and generate
Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.
What to build
Stack / repo
What to expect
Example output
A clear structured answer you can act on.
Example context
Example input
Paste your details into the variables.
Coding workflow prompts
More in this series
- Incident Commander Kit
- Create a Minimal Bug-Reproduction Plan
- Convert Requirements into Acceptance Tests
- Plan a Safe Dependency Upgrade
- Generate SQL with a Validation Plan
- Turn My Workflow Into a Cursor Skill
- Agent Report Card (Pass/Fail Tests)
- Generate API Test Cases from a Contract
- Review an Architecture Diagram for Risks
- REST API Design — ChatGPT Prompt
- GitHub Actions CI Pipeline — ChatGPT Prompt
- Debugging Root Cause Analysis — ChatGPT Prompt
Keep exploring
Discussion
Comments (0)
Sign in to leave a comment.
Loading comments…