What problem does it solve? Complex features and multi-file changes often fail because implementation starts before the architecture is thought through. This Skill produces a structured implementation plan—covering requirements, technology research, existing patterns, trade-offs, and phased steps—so coding proceeds without guesswork. ## Core Features & Use Cases - Six-phase planning workflow: Fetches the GitHub issue, researches current library versions and best practices, explores existing architecture, evaluates alternative approaches, and breaks work into independently testable phases. - Structured plan output: Produces a standardized plan document with architecture decisions, file structure, per-phase file changes, verification steps, risks, and open questions for user approval. - Convention enforcement: Loads project rules (code quality, ripple effects, composition patterns, docs-MCP usage) so plans align with the Nexus design system codebase. - Use Case: A developer is assigned a GitHub issue to add a new component variant across the React and Tailwind packages. The Skill researches the current Radix UI and CVA patterns, maps affected files, and returns a phased plan the coordinator presents for approval before any code is written. ## Quick Start Ask the agent to create an implementation plan for GitHub issue 42 before writing any code.
