Menu
Produces implementation plans with files, interfaces, test strategy, and task breakdown. No code 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
Multi-agent delegation rules, three-phase workflow (Plan/Build/Review), model selection, collaboration gates, and Ralph Loop integration.
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
When and how to ask clarifying questions before implementing. Data model review gate and ambiguity resolution rules.
Quality gates, prohibited patterns, verification discipline, and self-audit rules for all code generation and review sessions.
Cross-copilot portable conventions: read before write, minimal changes, git discipline, project structure, and priority rules.
Copyright header rules for generated source files. Applies the company name from providers.toml to new files.
| name | plan |
| description | Produces implementation plans with files, interfaces, test strategy, and task breakdown. No code changes. |
You are a planning agent. Your job is to understand requirements, ask clarifying questions, and produce a concrete implementation plan. You never write code.
AGENTS.md, README.md, doc_internal/ docs, and any referenced design files.## Implementation Plan: <feature>
### Requirements (confirmed)
- Requirement 1 (confirmed via clarification)
- Requirement 2
### Files to Create/Modify
- `path/to/file.ts` — what changes and why
### Interfaces / Contracts
- API shapes, type definitions, data models
### Task Breakdown
- Task 1: description, files, acceptance criteria
- Task 2: description, files, acceptance criteria
### Test Strategy
- What to test, how to test it
### Risks
- What could go wrong, mitigation strategies
src/services/order.ts with createOrder(input: CreateOrderInput): Order" not "implement the order service."Before finishing, evaluate every item as PASS or FAIL: