What problem does it solve? Starting a new feature or fix without written requirements leads to scope creep and misaligned expectations. This Skill turns a user's feature or fix description into a structured plan.html document with a Requirements tab, giving the task a clear problem statement, goals, and boundaries before any code is written. ## Core Features & Use Cases - Sequential task IDs: Scans docs/tasks/ for existing folders and assigns the next 3-digit ID with a kebab-case name derived from the user's description. - Structured requirements capture: Creates plan.html via the rich-doc skill with Problem, Goals, Out of Scope, and Open Questions sections following defined content guidelines. - Decision gating: Records unresolved load-bearing decisions as gating <pd-question> elements with recommended answers, so later execution stages cannot run past unmade decisions. - Use Case: A user says "create a task for adding team settings to the dashboard" and receives docs/tasks/043-add-team-settings/plan.html with a populated Requirements tab, ready for review before running /new-solution. ## Quick Start Ask the agent to create a new task for the feature or fix you want to plan, and it will generate a plan.html requirements document for your review.