writing-plans

Use when reviewer flags candidate; reproduce it first.

Use when facing repeated corrections, discovering recurring failure patterns, or needing a systematic way to compound learning across sessions.

Use before recovery or post-merge reconciliation plans.

Ultra-compressed response mode.

Lead every factual claim with evidence.

Multi-phase feasibility gatekeeping before building solutions.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.

Use when executing implementation plans with independent tasks in the current session

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…

No description from the publisher yet.