What problem does it solve? Turning a feature request into an actionable implementation plan is where scope creep and ambiguity most often creep in. This Skill produces structured, step-by-step implementation plans that trace every task back to the original request, so developers can execute without guessing. ## Core Features & Use Cases - Scope-Disciplined Planning: Works from a Scope Brief or the user's own words, keeping adjacent improvements in a separate out-of-scope list instead of inflating the plan. - Structured Plan Output: Generates plans with architecture, technology stack, phased task breakdowns, testing strategy, risk assessment, and success criteria. - Boundary Escalation: Stops and flags when the request implies materially more work than stated, delivering the in-scope plan plus the cheapest path forward. - Use Case: Given a GitHub issue describing a new API endpoint, produce a phased plan with per-task files, dependencies, and tests that any developer on the team can implement directly. ## Quick Start Ask the planner skill to create an implementation plan for the feature described in this requirements document, following the conventions in the repository's AGENTS.md.