What problem does it solve? Teams often jump into technical design before clearly defining what the business actually needs, leading to rework and misaligned solutions. This Skill structures a conversation that captures a business capability — purpose, stakeholders, triggers, outputs, rules, and success criteria — in purely business terms, producing a reviewable markdown document before any technical design begins. ## Core Features & Use Cases - Six-dimension elicitation: Walks through purpose, stakeholders, triggers and inputs, outputs, business rules, and success criteria, probing vague answers and mirroring back understanding. - Technical drift redirection: Detects when answers drift into implementation details (APIs, databases, frameworks) and redirects to business-level framing while parking technical ideas as open questions. - Hugo/Docsy-ready output: Produces a markdown document from a template with stable heading anchors and Docsy frontmatter, saved under docs/content/capabilities/ and validated via a local Hugo preview. - Use Case: A product manager says "help me define a capability for customer onboarding." The Skill asks focused questions one or two at a time, redirects any technical tangents, and delivers a complete capability document with open questions flagged for stakeholder review. ## Quick Start Ask the assistant to help you define a business capability for a specific business function, such as "help me define the refund processing capability for our store."
