business-concept

# Business Concept ## Purpose Turn a raw business idea — however vague or detailed — into a complete business concept document. This is the foundational artifact that every downstream technical document reads from. Without it, every architecture decision, every requirement, and every design choice is built on assumptions. **This skill focuses on the BUSINESS, not the technology.** It answers: what problem is being solved, for whom, why it matters, and what constraints shape the solution space. ## Input **Works best with:** A description of the project idea, in the user's own words, at any level of polish. **Also valuable:** Anything the user already knows about the market, competitors, or constraints. **Do not require a polished brief before starting.** Extracting the details is this skill's first job. ## Key Concepts ### Business Concept vs Project Plan | Aspect | Business Concept (this skill) | Project Plan (`project-plan`) | |:---|:---|:---| | **Focus** | The IDEA — what and why | The DELIVERY — how and when | | **Questions** | What problem? For whom? Why now? | What scope? What milestones? Who owns what? | | **Output** | Problem statement, users, value prop, constraints | WBS, RACI, timeline, risk register | | **Timing** | Phase 0 — before any technical work | Phase 1 — after the concept is clear | ### Standing Constraint Questions These questions establish project-wide constraints that affect every downstream document. Ask them once, early, and record the answ...