@edupia-tutor/spec-driven-docs 0.14.0

package/skills/discovery/SKILL.tmpl

@@ -0,0 +1,147 @@
+---
+description: Guides product discovery for a new feature through structured Q&A. Trigger when: "/define-product", "khám phá tính năng", "define new feature", "start new feature", "product discovery", "tôi muốn build tính năng mới", "let's define a feature", "begin feature discovery".
+---
+
+# /define-product — Feature Discovery (9-Phase Q&A)
+
+Lead the user through 9 structured checkpoints to fully define a new feature before writing any code. Each phase ends with a summary and confirmation before proceeding.
+
+## Pre-check
+
+{{include:steps/context-loader.md}}
+
+If `.agent/project-context.yaml` does not exist, ask for basic context upfront: "What domain does this feature belong to? Who are the main user types in your system?"
+
+## Phase 1 — Problem & Goal
+**CHECKPOINT 1/9**
+
+Ask:
+1. What problem does this feature solve? What pain point are users experiencing?
+2. Who is the primary user (persona/role)?
+3. What is the desired outcome?
+
+Summarize → confirm → proceed.
+
+## Phase 2 — User Flow
+**CHECKPOINT 2/9**
+
+Ask the user to describe the end-to-end flow from the user's perspective:
+- Trigger: what initiates this flow?
+- Steps: what does the user do?
+- End state: what does the user see/have?
+
+Confirm flow is complete before proceeding.
+
+## Phase 3 — Use Case List
+**CHECKPOINT 3/9**
+
+Derive use cases from the flow. Present as:
+```
+{DOMAIN}-UC1: {Use Case Name}
+{DOMAIN}-UC2: {Use Case Name}
+```
+
+Ask: "Does this cover everything? Any missing use cases?"
+
+## Phase 4 — Business Rules
+**CHECKPOINT 4/9**
+
+For each use case, identify constraints:
+- Validation rules (what inputs are required/invalid?)
+- Business logic rules (what calculations/decisions happen?)
+- State rules (what must be true before this UC runs?)
+
+Format:
+```
+BR-{N}: {Rule description} → applies to UC{N}
+```
+
+## Phase 5 — Acceptance Criteria
+**CHECKPOINT 5/9**
+
+For each use case, define measurable acceptance criteria:
+```
+AC-UC{N}-{M}: Given {context}, when {action}, then {expected result}
+```
+
+## Phase 6 — Edge Cases
+**CHECKPOINT 6/9**
+
+Explore failure scenarios:
+- What if required data is missing?
+- What if concurrent requests happen?
+- What if an upstream dependency fails?
+- What are the boundary conditions?
+
+## Phase 7 — Scope Boundary
+**CHECKPOINT 7/9**
+
+Explicitly define what is OUT of scope for this feature iteration. This prevents scope creep.
+
+Format:
+```
+OUT OF SCOPE:
+- {thing}: deferred to {reason/future phase}
+```
+
+## Phase 8 — Cross-Service / Cross-Module Dependencies
+**CHECKPOINT 8/9**
+
+Identify dependencies on other modules or services:
+- What data does this feature need from other services?
+- What events/callbacks does it produce?
+- What APIs must it call?
+
+## Phase 9 — Validation & Summary
+**CHECKPOINT 9/9**
+
+Produce final summary:
+```
+Feature: {name}
+Domain: {domain}
+Primary Persona: {role}
+Use Cases: {N} (list)
+Business Rules: {N}
+Dependencies: {list}
+Estimated Complexity: Low / Medium / High
+```
+
+Ask: "Approved? Or any changes needed?"
+
+## Output
+
+On approval, write file: `specs/product-definition/{feature-slug}.md`
+
+```markdown
+# Product Definition — {Feature Name}
+
+**Date**: {date}
+**Domain**: {domain}
+**Status**: draft
+
+## Problem Statement
+{from Phase 1}
+
+## User Flow
+{from Phase 2}
+
+## Use Cases
+| UC-ID | Name | Priority |
+|-------|------|----------|
+| {DOMAIN}-UC1 | {name} | High |
+
+## Business Rules
+| BR-ID | Rule | Applies To |
+|-------|------|-----------|
+
+## Acceptance Criteria
+{from Phase 5}
+
+## Out of Scope
+{from Phase 7}
+
+## Cross-Service Dependencies
+{from Phase 8}
+```
+
+{{include:steps/report-footer.md}}