What problem does it solve? Turning a vague feature idea or user request into a document an engineer can estimate and a stakeholder can argue with is slow and inconsistent. This Skill produces a structured feature spec with measurable goals, reasoned non-goals, prioritized requirements, and falsifiable success metrics, so scope debates happen on paper instead of in sprint planning. ## Core Features & Use Cases - Structured spec generation: Produces eight fixed sections — Problem Statement, Goals, Non-Goals, User Stories, P0/P1/P2 Requirements, Success Metrics, Open Questions, and Timeline — following a stable output template. - P0 challenge protocol: Runs three questions on every must-have requirement and demotes anything that is not genuinely blocking, regulatory, or journey-breaking. - Artifact-first intake: Reads upstream discovery artifacts (problem statement, persona, Lean UX canvas, story map) before asking questions, so the spec cites discovery instead of rewriting it. - Use Case: A product manager has a validated problem statement and Lean UX canvas for a card-dispute feature. The Skill collapses those artifacts into a spec, demotes two of six proposed P0s, flags an estimated baseline as needing instrumentation, and routes a regulatory wording question to legal as blocking. ## Quick Start Ask the assistant to write a spec for your feature idea, pointing it at any existing problem statement, persona, or Lean UX canvas files so it can pre-fill the document.
