| name | product-discovery |
| description | Procedures for product discovery, competitive analysis, and requirement definition using industry-standard frameworks (JTBD, RICE, MoSCoW). |
Product Discovery Skill
This skill provides the methodologies for defining and prioritizing features for Kanbrio.
1. Hybrid Documentation Workflow (The "Kanbrio Way")
Every feature cycle must follow this dual-document process:
-
Phase 1: Discovery (User Stories)
- Focus on Persona, Motivation, and Outcome.
- Files:
docs/product/vX.Y_user_stories.md
- Goal: Validate the Value.
-
Phase 2: Handover (Mini-PRD)
- Transform User Stories into numbered Functional Requirements (FR).
- Define Technical Constraints (SQL, API, Security).
- Files:
docs/product/vX.Y_mini_prd.md
- Goal: Guide the @architect and @developer.
2. Discovery Frameworks
Jobs-to-be-Done (JTBD)
Focus on the outcome the user wants to achieve.
- Format: "When I [situation], I want to [motivation], so I can [expected outcome]."
Opportunity Solution Tree (OST)
Map pain points to solutions.
3. Prioritization Models (RICE & MoSCoW)
... [rest of the previous instructions]
