Home
← Back to templates
Multi-Role Development Pipeline
Programming
Get design, implementation, review and optimization in one connected pass.
Role: You are simulating four roles in sequence: Architect, Engineer, Reviewer, Optimizer. Context: Task: build a rate limiter middleware for an Express API Task: Architect designs, Engineer implements, Reviewer critically checks, Optimizer improves based on the review. Constraints: Each role genuinely builds on the previous — Reviewer references specific code, Optimizer addresses what Reviewer flagged. Output Format: Design -> implementation -> feedback -> final version.
Expected output
A design, then real implementation code, then a review that references specific lines of that actual code (not generic feedback), and a final optimized version that specifically addresses what the review flagged.
Usage tips
- Check that the Reviewer step genuinely references specific code, not generic advice — if it reads generic, ask it to be more specific to the actual implementation.
- Use this for a self-contained task small enough to go through all 4 roles in one pass, not a whole feature.
Try it
Fill in the placeholders below and see the compiled prompt update live.
What do you want done?
- 57
- Words
- 438
- Characters
- 0/1
- Placeholders filled
- 1 min
- Reading time
Quality score11
- Completeness0
- Clarity0
- Context0
- Specificity0
- Constraints0
- Format0
- Output0
- Constraints note100
- Success criteria0
- Scope focus100
- Verification step0
- Negative example0
- Confidence0
- Placeholder syntax100
- Markdown structure0
Suggestions
- Fill in the remaining placeholders.
- Expand your answers — a few words each isn't enough detail for the model to work with.
- Add background context so the model understands the situation.
Role: You are simulating four roles in sequence: Architect, Engineer, Reviewer, Optimizer.
Context: Task: {{TASK}}
Task: Architect designs, Engineer implements, Reviewer critically checks, Optimizer improves based on the review.
Constraints: Each role genuinely builds on the previous — Reviewer references specific code, Optimizer addresses what Reviewer flagged.
Output Format: Design -> implementation -> feedback -> final version.
AI Assistant