Cursor rule
Phase 1 - restate the task, surface unknowns, define testable success criteria, and classify complexity before any code.
Cursor rule
Phase 1 - restate the task, surface unknowns, define testable success criteria, and classify complexity before any code.
Cursor rule
Phase 2 - gather real context. Read before editing, verify every API/symbol/path exists, never guess signatures.
Cursor rule
Phase 3 - design the approach with at least one alternative, state trade-offs, and enumerate edge cases and error paths before coding.
Cursor rule
Phase 4 - implement the chosen design as a minimal, incremental diff with no scope creep and no fake completions.
Cursor rule
Phase 5 - adversarial self-critique. Assume bugs exist and actively try to break your own implementation before running it.
Cursor rule
Phase 6 - hard verification gate. Run typecheck, lint, and tests; paste real output; never claim success without evidence.
Cursor rule
Phase 7 - bounded retry loop. Diagnose root cause before re-editing; re-plan or escalate at iteration 3; stop and surface a blocker at iteration 5.
Cursor rule
When and how to spawn a readonly critic subagent for a fresh perspective, and how to fold its findings back into the pipeline.
Cursor rule
Entry point for the disciplined reasoning pipeline. Invoke to make a cheap model plan, implement, self-critique, and verify with hard no-premature-done gates.
Cursor rule
Project-specific adapter — inject your commands, docs, and security gates into the generic pipeline phases.
Cursor rule
Cross-cutting protocol - offload durable state to a per-task memory file to virtually expand the context window and prevent decision drift.