context-engineering-workflows

Use when starting the RPI flow and you want to deeply understand a question, system, or feature by reading the codebase before planning.

Use when starting the RPI flow and you want to deeply understand a question, system, or feature by reading the codebase before planning.

Use when starting a new deep-work task. Decomposes a task description into objective research questions that avoid premature solutioning. Phase 1 of the deep-work pipeline.

Use when you have research questions from deep-work Phase 1. Objectively investigates the codebase to answer pasted questions without access to the original task description.

Use when deep-work Phase 2 research is complete. Combines research findings with the original task to explore design options, evaluate tradeoffs, and make decisions interactively.

Use when deep-work Phase 3 design decisions are complete. Maps chosen decisions to concrete file changes organized into implementable phases.

Use when deep-work Phase 4 structure outline is complete. Expands the outline into a detailed implementation plan with exact file paths, code patterns, tests, and validation commands.

Use when deep-work Phase 5 plan is complete. Executes the implementation plan by dispatching a fresh subagent per task with two-stage review (spec compliance → code quality).

Use when you have a plan from /rpi-plan and want to execute it. Dispatches a fresh subagent per task with two-stage review (spec compliance → code quality), then runs a baked-in end-of-implementation audit that re-runs success criteria, checks the diff against the plan, and dispatches /quick-review across the SHA range.

Use after /rpi-research when you want an interactive, gated plan-creation flow. Interactive: presents understanding, design options, phase outline, then draft — each gated on user approval.

Use when starting a new deep-work task. Decomposes a task description into objective research questions that avoid premature solutioning. Phase 1 of the deep-work pipeline.

Use when you have research questions from deep-work Phase 1. Objectively investigates the codebase to answer pasted questions without access to the original task description.

Use when deep-work Phase 2 research is complete. Combines research findings with the original task to explore design options, evaluate tradeoffs, and make decisions interactively.

Use when deep-work Phase 3 design decisions are complete. Maps chosen decisions to concrete file changes organized into implementable phases.

Use when deep-work Phase 4 structure outline is complete. Expands the outline into a detailed implementation plan with exact file paths, code patterns, tests, and validation commands.

Use when deep-work Phase 5 plan is complete. Executes the implementation plan by dispatching a fresh subagent per task with two-stage review (spec compliance → code quality).

Use when you have a plan from /rpi-plan and want to execute it. Dispatches a fresh subagent per task with two-stage review (spec compliance → code quality), then runs a baked-in end-of-implementation audit that re-runs success criteria, checks the diff against the plan, and dispatches /quick-review across the SHA range.

Use after /rpi-research when you want an interactive, gated plan-creation flow. Interactive: presents understanding, design options, phase outline, then draft — each gated on user approval.