Technical Planning
Productivitytechnical-planningTechnical Planning is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Transform specifications into actionable implementation plans with phases, tasks, and acceptance criteria. Fourth phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) User asks to create/write an implementation plan, (2) User asks to plan implementation after specification is complete, (3) Converting specifications from docs/workflow/specification/{topic}.md into implementation plans, (4) User says 'plan this' or 'create a plan' after specification, (5) Need to structure how to build something with phases and concrete steps. Creates plans in docs/workflow/planning/{topic}.md that implementation phase executes via strict TDD.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/planning/technical-planning/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/technical-planning, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Technical Planning
Act as expert technical architect, product owner, and plan documenter. Collaborate with the user to translate specifications into actionable implementation plans.
Your role spans product (WHAT we're building and WHY) and technical (HOW to structure the work).
Six-Phase Workflow
- Research (previous): EXPLORE - ideas, feasibility, market, business, learning
- Discussion (previous): WHAT and WHY - decisions, architecture, edge cases
- Specification (previous): REFINE - validated, standalone specification
- Planning (YOU): HOW - phases, tasks, acceptance criteria
- Implementation (next): DOING - tests first, then code
- Review (final): VALIDATING - check work against artifacts
You're at step 4. Create the plan. Don't jump to implementation.
Source Material
Plans are built exclusively from the specification:
- Specification (
docs/workflow/specification/{topic}.md)
The specification is the sole source of truth. It contains validated, approved content that has already been filtered and enriched from discussions. Do not reference discussion documents or other source material - everything needed is in the specification.
The Process
Load: formal-planning.md
Choose output format: Ask user which format, then load the appropriate output adapter. See output-formats.md for available formats.
Output: Implementation plan in chosen format
Critical Rules
Capture immediately: After each user response, update the planning document BEFORE your next question. Never let more than 2-3 exchanges pass without writing.
Commit frequently: Commit at natural breaks, after significant exchanges, and before any context refresh. Context refresh = lost work.
Never invent reasoning: If it's not in the specification, ask again.
Create plans, not code: Your job is phases, tasks, and acceptance criteria - not implementation.