@edupia-tutor/spec-driven-docs 0.14.0

package/commands/define-product.tmpl

@@ -0,0 +1,158 @@
+# /define-product — Feature Discovery (8-Phase Q&A)
+
+## Gate
+{{include:steps/gate.md}}
+
+*Note: For this command, there is no input file to resolve in Step 1. Skip to Step 2 (context load) and then ask: **"Ticket ID and feature name? (e.g., LOYAL-29 Loyalty Points)"***
+
+## Context
+{{include:steps/context-loader.md}}
+
+---
+
+## Phase 0 — Knowledge Sync *(AI fills automatically, no PO input needed)*
+
+AI scans the project and writes:
+
+- **Related Entities** — list entities from existing PRDs/domain-knowledge that relate to this feature.
+- **Related Modules** — list affected modules/services.
+- **Existing Rules / Logic** — rules from existing PRDs that this feature must respect.
+- **Terminology Normalization** — map any terms found in PO input to canonical terms from business-dictionary.md.
+
+```
+| Term in PO input | Canonical term (business-dictionary) |
+|------------------|--------------------------------------|
+| {original}       | {canonical}                          |
+```
+
+Store this terminology map in the output product-definition file under a `## Terminology Map` section — `/generate-prd` will reference it during its Terminology Rules step to ensure consistency.
+
+---
+
+## Phase 1 — Feature Definition *(CHECKPOINT 1)*
+
+Ask in order, one at a time:
+
+1. **Context**: Background / reason why this feature is needed?
+2. **Problem**: Specific problem to solve?
+3. **Goal**: What objective does this feature achieve?
+4. **Actors**: Who are the users? (list roles, mark Primary/Secondary)
+5. **Scope**: What does this feature do? (one function per line — only what is in this ticket)
+6. **User Story**: Confirm in format:
+   ```
+   As a {User role}
+   I want to {User goal}
+   So that {Business value}
+   ```
+
+Summarize → confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 2 — User Flow Definition *(CHECKPOINT 2)*
+
+Ask:
+1. **Entry Point**: Where does the user start interacting with this feature?
+2. **Flow Steps**: Describe each step (use table):
+   ```
+   | Step | Action (user) | Screen / State | Notes |
+   ```
+3. **Exit Point**: What is the final result when the flow completes?
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 3 — Clarification Log *(CHECKPOINT 3)*
+
+Based on Phases 1-2, AI identifies gaps and asks follow-up questions. Continue rounds until no Unresolved Items remain.
+
+```
+### Round {N}
+| # | Category       | Question   | PO Answer  |
+|---|----------------|------------|------------|
+| 1 | Context/Flow/Logic | {question} | {answer} |
+```
+
+**BLOCK**: If Unresolved Items remain → MUST NOT proceed to Phase 4.
+
+### Unresolved Items
+- {item — or "None"}
+
+When all Unresolved Items are resolved → write `✅ CHECKPOINT 3: No Unresolved Items` → proceed to Phase 4.
+
+---
+
+## Phase 4 — Business Rules *(CHECKPOINT 4)*
+
+Derive from Phases 1-3. Each BR = one rule (WHAT the system must/must not do):
+
+```
+| Rule ID | Action / Trigger    | Rule                          | Condition           |
+|---------|---------------------|-------------------------------|---------------------|
+| BR-1    | {action from flow}  | System MUST/MUST NOT...       | {applicable condition} |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 5 — Business Logic *(CHECKPOINT 5)*
+
+Map each BR to HOW the system executes it:
+
+```
+| Rule ID | System Behavior                       | Data State Change   | UI Behavior             | Error Handling         |
+|---------|---------------------------------------|---------------------|-------------------------|------------------------|
+| BR-1    | {how system processes when triggers}  | {what data changes} | {enable/disable/show...}| {error message/action} |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 6 — Acceptance Criteria *(CHECKPOINT 6)*
+
+Derive from BRs + User Story. Each AC must be testable (clear pass/fail):
+
+```
+| AC ID | Description             | Expected Behavior         | Derived from |
+|-------|-------------------------|---------------------------|--------------|
+| AC-1  | {criterion description} | {what system should do}   | BR-{N}       |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 7 — Validation Report
+
+Generate coverage matrix automatically:
+
+```
+| Flow Action | Has Rule? | Has Logic? | Has AC? | Status  |
+|-------------|-----------|------------|---------|---------|
+| {Action 1}  | ✅/❌     | ✅/❌      | ✅/❌   | OK/GAP  |
+```
+
+- **Conflicts Detected**: list any conflicting rules, or "None".
+- **Missing Items**: list gaps, or "None".
+
+If any GAP found → alert PO and resolve before marking completed.
+
+---
+
+## Output
+
+Write `{paths.product_definitions_dir}/{TICKET-ID}-{slug}.md` following `templates/product-definition.template.md`.
+
+Fill all sections with data gathered across phases.
+Set `Status: completed` when Phase 7 passes with no GAPs.
+
+{{include:steps/report-footer.md}}
+
+```
+/define-product Complete ✅
+File: {paths.product_definitions_dir}/{TICKET-ID}-{slug}.md
+Next: /generate-prd {paths.product_definitions_dir}/{TICKET-ID}-{slug}.md
+```