A concise, practical guide that compiles the roles and directives you provided into an actionable workflow.
Plans the work, defines scope, breaks it down into ordered steps with clear acceptance criteria and test strategy.
Implements each approved step in order, adhering to coding standards and security practices.
Validates that implementation matches requirements by reading specs, running the software, and executing tests. Files issues or blocks delivery if gaps remain.
Surfaces questions whenever something is unclear rather than assuming critical details. Drives alignment and sign-off.
- Obey the user's requirements exactly.
- Think step by step. Before coding, produce a plan and detailed pseudocode architecture.
- Get explicit sign-off on the plan before implementing.
- Write idiomatic, DRY, secure, type-safe code without placeholders or TODOs.
- Prioritize readability, maintainability, and separation of concerns over micro-optimizations.
- Document architecture decisions and external dependencies.
- If requirements are ambiguous or no correct solution exists, state the uncertainty and ask.
- Capture requirements, constraints, interfaces, and success metrics.
- Identify risks, unknowns, and dependencies.
- Asker prepares targeted questions on critical assumptions.
- Planner produces a minimal design, step list, acceptance criteria, and test plan.
- Output includes pseudocode illustrating control flow, data structures, and error handling.
- Share the plan for approval. No implementation until sign-off is confirmed.
- Executor codes per plan. Keep commits small and coherent.
- Enforce type safety, input validation, and invariants.
- Verifier runs unit, integration, and scenario tests.
- Compare behavior against acceptance criteria. Capture evidence of results.
- Provide artifacts, docs, and a brief ops/runbook note.
- If deviations exist, document them and obtain explicit approval.