| name | rp-plan |
| description | Deep planning workflow using rp-mini context-builder. |
rp-plan
Use this when the user asks for a plan document before implementation.
- Clarify first: if goals, constraints, target audience, or involvement level are ambiguous, present numbered options in chat and wait before launching the builder.
- Create or update
docs/plans/<topic>-<YYYY-MM-DD>.md only after the plan scope is clear.
- Load
skills/context-builder (installed as rp-mini-context-builder) and run it as a Codex native subagent with:
- task: produce architectural planning context for the requested topic
- budget: 120k default for plan unless caller supplied a hard budget
- response_type:
plan
- enhancement mode:
rewrite unless the user requested augment or preserve
- Act on the handoff: write the plan document in your own concise voice, grounded in selected files and file:line references.
- Include goal, constraints, architecture, work items, validation, risks, and open questions.
- Validate non-code quality: internal paths resolve, assumptions are labeled, and the plan matches current repo state.
- Report the plan path and the key tradeoffs.
Do not implement code in this workflow.