Menu
Convert a user task into an execution-ready implementation plan with assumptions, risks, files likely to change, validation steps, rollback notes, and approval readiness. Use during Plan Mode.
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
Keep code changes bound to an approved plan, avoid unrelated refactors, respect off-limits files, and summarize changed files. Use during Execute Mode.
Review implementation against an approved plan and return PASS, PARTIAL PASS, or FAIL with missing requirements, unexpected changes, risks, and test/build status. Use during Validator Mode.
Inspect project structure, frameworks, package managers, entry points, configs, and architecture before implementation planning. Use when planning requires understanding an unfamiliar codebase.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Generate safe git status, diff summaries, changed file summaries, and commit message suggestions without committing or pushing. Use after execution or validation.
Find and respect project rules such as AGENTS.md, CLAUDE.md, README.md, .cursor/rules, .factory/rules, .pi, and .env.example before planning or execution.
| name | implementation-planning |
| description | Convert a user task into an execution-ready implementation plan with assumptions, risks, files likely to change, validation steps, rollback notes, and approval readiness. Use during Plan Mode. |
Produce concrete plans only. Ask follow-up questions when required. Include task summary, assumptions, files likely to change, allowed new file locations, off-limits files, implementation steps, risks, validation steps, rollback notes, and readiness status. Do not plan arbitrary repository-root files unless the exact root path is approved and justified; otherwise route new artifacts to conventional project directories.
Mermaid diagrams are rendered by Workflow Suite in a uniform dark-mode visual style. For user-facing workflows, export/share paths, request lifecycles, architecture, data flow, multi-step sequences, state transitions, dependencies, validation flow, or implementation phases, include a meaningful Mermaid diagram plus concise prose unless the user requested prose only or the response is trivial. Use concise labels and the right diagram type; do not hardcode random style/classDef/light-theme overrides unless the user explicitly asks.
.env contents.Use this skill as in-process guidance for the current model. Use a sub-agent only when the task benefits from an isolated context window, parallel read-only research, forced preflight, or independent validation. Do not use both this skill and a same-purpose agent for the same narrow job unless the workflow or user explicitly requires it.