Menu
Use when producing implementable technical plans with task breakdown and verification matrix. After context gathering, before implementation.
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
Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.
Use when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.
Use when designing UI, choosing colors, typography, spacing, creating visual hierarchy, or making design decisions. Based on Refactoring UI by Wathan & Schoger.
Use when someone needs a plain-language explanation of how an existing feature or edge case behaves in the codebase. Triggers - non-technical stakeholder asks how something works, need code-informed functional explanation, need to understand rules or edge cases without implementation planning.
Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.
Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.
| name | technical-planning |
| description | Use when producing implementable technical plans with task breakdown and verification matrix. After context gathering, before implementation. |
Produce a precise, implementable technical plan. Do NOT write implementation code.
{ide-folder}/{outputFolder}/tech/vision/...){ide-folder}/{outputFolder}/product/prd/{epicNumber}-EPIC-{epicName}/US-{usName}-{usNumber}.md){ide-folder}/{outputFolder}/task/.../technical-context.md){ide-folder}/{outputFolder}/task/{epicNumber}-EPIC-{epicName}/US-{usName}-{usNumber}/technical-plan.md
Epic ID: EPIC-{epicNumber}
User Story ID: US-{usNumber}
Document: Technical Plan
Status: Draft | Ready
Owner: AI Architect (Plan)
Last Updated: (ISO timestamp)
Inputs: (list exact paths)
| # | Section | Content |
|---|---|---|
| 1 | Scope & Non-Scope | AC-* addressed, explicitly not done |
| 2 | Proposed design | Components, boundary rules, key flows |
| 3 | Contracts & interfaces | Types, signatures, APIs, error semantics |
| 3.1 | Data Transformation Layer | MANDATORY for calculation stories - raw→normalized mapping table |
| 4 | Data & multi-tenancy | Tenant scoping, migration/rollback |
| 5 | Security constraints | AuthN/Z, input validation, sensitive data, rate limiting |
| 6 | Observability | Logging, metrics, failure modes, tracking events |
| 7 | Task breakdown | PR-sized tasks with TASK-* IDs |
| 8 | Verification Matrix | MANDATORY - AC-* → tests/checks mapping |
| 9 | Software Engineer Brief | Step-by-step order, DoD checklist, commands |
| 10 | Open questions | If blocking, list with defaults |
- `TASK-01` Title
- Description
- Files/packages impacted
- AC covered (`AC-*`)
- Notes/pitfalls
Every AC-* must have at least one verification:
assertNeverpackagePriceCents over priceCents/sync-issue after writing