What problem does it solve? Turning a feature idea or requirements document into an actionable, reviewable technical plan is error-prone: plans often miss file paths, test scenarios, dependencies, or design context, forcing implementers to improvise. This Skill produces a durable implementation plan that serves as the single source of truth for downstream task slicing and autonomous execution. ## Core Features & Use Cases - Requirements-driven planning: Locates and reuses upstream requirements docs (per-feature brainstorms, project-wide PRDs, or inline request requirements) with traceability back to the source. - Research-backed decisions: Runs parallel research agents over the codebase, institutional knowledge, and optionally external best practices before structuring the plan. - Phased Implementation Units: Breaks work into atomic units grouped into numbered phases with dependencies, exact file paths, delegate subagents, skills, and typed test scenarios ([Unit], [E2E], [Manual]). - Design context for UI work: Integrates Figma MCP fetching (design context, variables, screenshots) into a per-feature SPEC.md and checks for a project DESIGN.md token source. - Use Case: After brainstorming a new profile screen feature, run the planner to produce a dated plan file in docs/plans/ with phases for data layer, UI screens, and E2E tests, ready for the autopilot workflow to execute. ## Quick Start Ask the assistant to create a technical implementation plan for your feature, optionally pointing to an existing requirements document in docs/brainstorms/.
