What problem does it solve? Turning a feature request or spec into an executable, reviewable implementation plan is error-prone: tasks get oversized, requirements get dropped, and QA policy is applied inconsistently. This Skill enforces a disciplined planning protocol that produces phased, traceable plans with locked QA and execution profiles. ## Core Features & Use Cases - Profile-driven planning: Supports strict and balanced planning profiles that control spec requirements, clarification depth, and QA gate defaults. - Four-stage clarification funnel: Inventories uncertainties, classifies them, consults a critic sounding board, and surfaces only genuine user decisions with always-surface protections for scope, security, and destructive behavior. - QA gate and execution profile bootstrap: Persists eleven QA gates (reviewer, test_engineer, drift_check, councils, mutation testing, and more) plus parallel-coder, commit-frequency, and auto-proceed settings bound to the exact plan identity. - Traceability enforcement: Maps every FR-### and MUST/SHALL SC-### from the effective spec to plan tasks, flagging coverage gaps and gold-plating before critic review. - Use Case: A team lead asks the architect to plan a payment-integration feature; the Skill checks spec status, runs the clarification funnel, drafts phased tasks with granularity rules, persists QA gates, and hands the plan to a critic gate before execution. ## Quick Start Ask the architect to plan the implementation of your feature, for example: "Plan the implementation of the payment integration feature from the current spec."
