Menu
Plan phase of the workflow chain. Uses Opus to design an implementation strategy. Use when the user wants to create a detailed plan before executing changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | st-plan |
| description | Plan phase of the workflow chain. Uses Opus to design an implementation strategy. Use when the user wants to create a detailed plan before executing changes. |
Design the implementation strategy for the user's task.
steop state set-phase plan --mode plan
Launch the architect agent (steop:architect, Opus, read-only tools).
Note: When invoked from
st-flowwith FLOW MODE, produce the blueprint and return it immediately without asking for approval. The instructions below describe standalone behavior.
Provide the agent with all available context from prior research (if any) plus the user's task description.
Prefer the simpler of two equivalent designs. If the Research Summary flagged an area that YAGNI would skip, skip it unless the Task Brief's Success criteria require it. Don't design for hypothetical future requirements not stated in the brief.
The planning agent should produce:
<chosen> chosen over <alternative> because <reason>.step → verify: format where helpful.After the agent completes, present the plan to the user and ask for approval or adjustments before proceeding to execution.
Clarify phase of the workflow chain. Uses Opus to analyze the user's request, resolve ambiguities, define scope, and produce a clear task brief before research begins.
Execute phase of the workflow chain. Uses Haiku (simple), Sonnet (standard), or Opus (complex) to implement code changes according to a plan. Use when the user has an approved plan ready to execute.
Flow workflow chain that runs clarify → [research] → plan → execute → validate end-to-end without stopping. Pauses only on genuine ambiguity or circuit-breaker conditions.
Research phase of the workflow chain. Uses Haiku (simple) or Sonnet (standard) to research the codebase and gather context for a task. Use when the user wants to investigate code before planning.
Validate phase of the workflow chain. Uses Sonnet to review and validate implementation changes. Use when the user wants to validate that code changes are correct and complete.
Compressed 3-phase fast-feedback workflow chain (clarify → execute → validate) with cap-3 parallel executors, no retry loop, fail-fast. For prototypes, spikes, and quick refactors.