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.
/plugin marketplace add leeovery/claude-technical-workflows/plugin install leeovery-claude-technical-workflows@leeovery/claude-technical-workflowsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/formal-planning.mdreferences/output-backlog-md.mdreferences/output-beads.mdreferences/output-formats.mdreferences/output-linear.mdreferences/output-local-markdown.mdAct 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).
You're at step 4. Create the plan. Don't jump to implementation.
Plans are built exclusively from the 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.
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
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.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.