teamspec 3.2.0 → 4.1.0

package/teamspec-core/templates/sprint-template.md

@@ -1,22 +1,24 @@
 # Sprint {N}
 
-<!-- 
+<!--
   ⚠️ SPRINT ≠ SCOPE DEFINITION
-  
+
   This sprint is a TIME-BOXED execution snapshot.
-  
+
   RULES:
   1. Sprint does not define scope (Features do)
-  2. Sprint does not change priority (BA does)
+  2. Sprint does not change priority (PO does)
   3. Only SM can modify sprint contents
   4. Scope changes require explicit Decision Log entry
-  
+
   After sprint commitment, scope changes must be logged in /decisions/
+
+  LOCATION: projects/{project-id}/sprints/sprint-{N}/
 -->
 
-> **Template Version**: 2.0  
-> **Last Updated**: 2026-01-07  
-> **Location**: `sprints/sprint-{N}/sprint-goal.md`
+> **Template Version**: 4.0
+> **Last Updated**: 2026-01-11
+> **Location**: `projects/{project-id}/sprints/sprint-{N}/sprint-goal.md`
 
 ---
 
@@ -60,8 +62,8 @@
 
 > ⚠️ After commitment, any scope change requires:
 > 1. SM to facilitate discussion
-> 2. BA to approve scope change
-> 3. Decision logged in /decisions/DEC-XXX.md
+> 2. PO to approve scope change
+> 3. Decision logged in /decisions/dec-{PRX}-{NNN}.md
 > 4. Story removed/added with explicit note
 
 ---
@@ -72,7 +74,7 @@
 
 | Story ID | Title | Points | Dev Plan | Owner | Status |
 |----------|-------|--------|----------|-------|--------|
-| [S-XXX](../../stories/ready-for-development/S-XXX-*.md) | {Title} | {N} | [Plan](../../dev-plans/story-XXX-tasks.md) | @dev | ⚪ Not Started |
+| [s-e{EEE}-{SSS}](../stories/in-progress/s-e{EEE}-{SSS}-*.md) | {Title} | {N} | [dp-e{EEE}-s{SSS}](../dev-plans/dp-e{EEE}-s{SSS}-*.md) | @dev | ⚪ Not Started |
 
 > ⚠️ All committed stories must have a Dev Plan before implementation starts.
 
@@ -125,11 +127,11 @@
 
 ## Canon Sync Verification
 
-> ⚠️ Before sprint close, verify Feature Canon is updated for all behavior-changing stories.
+> ⚠️ Before sprint close, verify Feature-Increments TO-BE sections are complete for all behavior-changing stories.
 
-| Story | Impact Type | Canon Updated? | FA Verified |
-|-------|-------------|----------------|-------------|
-| S-XXX | Adds/Changes | [ ] | [ ] |
+| Story | FI | Impact Type | FI TO-BE Complete? | FA Verified |
+|-------|-----|-------------|-------------------|-------------|
+| s-e{EEE}-{SSS} | fi-{PRX}-{NNN} | Adds/Changes | [ ] | [ ] |
 
 ---
 

package/teamspec-core/templates/story-template-v4.md

@@ -0,0 +1,202 @@
+# Story: `s-eXXX-YYY-description`
+
+<!-- 
+  ⚠️ TEAMSPEC 4.0 STORY TEMPLATE
+  
+  Stories in 4.0 are linked to Epics via filename.
+  Filename pattern: s-eXXX-YYY-description.md
+  
+  RULES:
+  - Story filename MUST include Epic ID (eXXX)
+  - YYY is the story sequence within the Epic
+  - Stories describe DELTAS, not full behavior
+  
+  TEAMSPEC RULES ENFORCED:
+  - TS-STORY-006: Story must link to Epic (via filename)
+  - TS-STORY-007: Linked Epic must exist
+  - TS-STORY-002: Delta-only format required
+  - TS-STORY-003: Acceptance Criteria required
+-->
+
+> **Template Version**: 4.0  
+> **Last Updated**: 2026-01-10
+
+---
+
+## Metadata
+
+| Field | Value |
+|-------|-------|
+| **Story ID** | s-eXXX-YYY |
+| **Epic** | epic-PRX-XXX |
+| **Status** | Backlog |
+| **Estimate** | [Points] |
+| **Author** | [FA Name] |
+| **Sprint** | — |
+
+**Document Owner:** FA (Functional Analyst)  
+**Artifact Type:** Execution (Delta to Feature Canon)  
+**Lifecycle:** Sprint-bound, archived after completion
+
+> ⚠️ **Stories start in Backlog.** Only the Scrum Master can assign stories to a sprint.
+
+---
+
+## User Story
+
+**As a** [Persona],  
+**I want** [Action],  
+**So that** [Benefit].
+
+---
+
+## Linked Epic
+
+> ⚠️ **MANDATORY**: Epic link is embedded in filename (eXXX).  
+> **TEAMSPEC RULE:** TS-STORY-006 - Epic link required (via filename)
+
+| Epic ID | Epic Name | Product |
+|---------|-----------|---------|
+| [epic-PRX-XXX](../epics/epic-PRX-XXX-description.md) | [Epic Name] | [Product Name] (PRX) |
+
+---
+
+## Linked Feature-Increment
+
+> Recommended: Link to the Feature-Increment this story implements.
+
+| FI ID | Description |
+|-------|-------------|
+| [fi-PRX-XXX](../feature-increments/fi-PRX-XXX-description.md) | [Brief description] |
+
+---
+
+## Feature Impact
+
+> Describe what this story CHANGES relative to current documented behavior.  
+> **Do NOT restate full feature behavior here.**
+
+<!-- TEAMSPEC RULE: TS-STORY-002 requires Before/After (AS-IS/TO-BE) format -->
+
+### Impact Type
+
+- [ ] **Adds Behavior** — New capability not currently in the feature
+- [ ] **Changes Behavior** — Modifies existing documented behavior
+- [ ] **Fixes Defect** — Restores behavior to match documentation (no feature update needed)
+- [ ] **Technical Only** — Refactor/performance with no user-observable change
+
+### AS-IS (current behavior)
+
+<!-- 
+  Describe the CURRENT behavior as documented in Product Feature Canon.
+  Reference: f-PRX-XXX, Section: [section name]
+  
+  Example: "Currently, users must log in with email/password (f-DIT-001, Main Flow Step 1)"
+-->
+
+**Reference:** f-PRX-XXX, Section: [section]
+
+[Brief description of current behavior per Feature Canon]
+
+### TO-BE (new behavior)
+
+<!-- 
+  Describe ONLY what changes.
+  This becomes the new behavior in Feature Canon after completion.
+  
+  Example: "Users can also log in with Google OAuth"
+-->
+
+[ONLY the delta - what changes]
+
+> ⚠️ **FEATURE CANON RULE**  
+> If this story adds or changes behavior, the Feature-Increment TO-BE must be complete  
+> and Canon sync must happen before project closure.  
+> See: TS-DOD-003 - Product sync after deployment
+
+---
+
+## Sprint Assignment
+
+<!-- TEAMSPEC RULE: TS-STORY-004 - Only SM can assign sprint -->
+
+**Sprint:** —  
+**Assigned By:** ________________  
+**Role:** SM  
+**Date:** ________________
+
+> ⚠️ Only the Scrum Master (SM) can assign this story to a sprint.
+
+---
+
+## Acceptance Criteria (AC)
+
+> ⚠️ **MANDATORY**: AC must be present and testable.  
+> **TEAMSPEC RULE:** TS-STORY-003 - AC required
+
+### Scenario 1: [Happy Path]
+
+- **Given** [Context]
+- **When** [Action]
+- **Then** [Result]
+
+### Scenario 2: [Edge Case]
+
+- **Given** ...
+- **When** ...
+- **Then** ...
+
+---
+
+## Technical Notes
+
+- **API**: [Endpoint]
+- **DB**: [Table/Schema]
+- **TAI**: [tai-PRX-XXX if applicable]
+
+---
+
+## UX & Copy
+
+- [Figma Link]
+- Error Messages: [List specific messages]
+
+---
+
+## DoR Checklist (Feature Alignment)
+
+- [ ] Linked to Epic (via filename s-eXXX-YYY)
+- [ ] Linked Epic exists in epics folder
+- [ ] Linked Feature-Increment exists (if applicable)
+- [ ] Story describes DELTA only, not full behavior
+- [ ] Feature impact type is marked
+- [ ] ACs map to feature behavior / business rules
+
+## DoR Checklist (Standard)
+
+- [ ] AC Defined (Gherkin or checklist)
+- [ ] UX Attached (or "No UI required")
+- [ ] Dependencies Clear
+- [ ] Estimated
+- [ ] Small enough for one sprint
+
+## DoD Checklist
+
+- [ ] Code Complete
+- [ ] Tests Passed
+- [ ] Feature-Increment TO-BE complete (if behavior changed)
+- [ ] FA Accepted
+- [ ] Story marked Done in backlog
+
+---
+
+## Linter Rules Enforced
+
+| Rule | Description | Status |
+|------|-------------|--------|
+| TS-STORY-006 | Epic link required (via filename) | Checked on save |
+| TS-STORY-007 | Linked Epic must exist | Checked on save |
+| TS-STORY-002 | Delta-only format (AS-IS/TO-BE) | Checked on save |
+| TS-STORY-003 | ACs testable | Checked on Ready |
+| TS-STORY-004 | Sprint assignment by SM only | Checked on assignment |
+| TS-STORY-005 | DoR complete | Checked on Ready |

package/teamspec-core/templates/story-template.md

@@ -1,24 +1,25 @@
-# S-XXX: [Title]
+# Story: `s-eXXX-YYY-description`
 
-<!-- TEAMSPEC RULE: TS-STORY-002 -->
 <!-- 
-  ⚠️ STORIES ARE DELTAS, NOT DOCUMENTATION
+  ⚠️ TEAMSPEC 4.0 STORY TEMPLATE
   
-  This story describes a CHANGE to the Feature Canon.
+  Stories in 4.0 are linked to Epics via filename.
+  Filename pattern: s-eXXX-YYY-description.md
   
-  DO NOT:
-  - Restate full feature behavior
-  - Include complete specifications
-  - Document end-to-end flows
+  RULES:
+  - Story filename MUST include Epic ID (eXXX)
+  - YYY is the story sequence within the Epic
+  - Stories describe DELTAS, not full behavior
   
-  DO:
-  - Reference Feature Canon (F-XXX) for current behavior
-  - Describe only what changes (Before → After)
-  - Link to Feature Canon rules (BR-XXX)
+  TEAMSPEC RULES ENFORCED:
+  - TS-STORY-006: Story must link to Epic (via filename)
+  - TS-STORY-007: Linked Epic must exist
+  - TS-STORY-002: Delta-only format required
+  - TS-STORY-003: Acceptance Criteria required
 -->
 
-> **Template Version**: 2.0  
-> **Last Updated**: 2026-01-07
+> **Template Version**: 4.0  
+> **Last Updated**: 2026-01-10
 
 ---
 
@@ -26,7 +27,8 @@
 
 | Field | Value |
 |-------|-------|
-| **Story ID** | S-XXX |
+| **Story ID** | s-eXXX-YYY |
+| **Epic** | epic-PRX-XXX |
 | **Status** | Backlog |
 | **Estimate** | [Points] |
 | **Author** | [FA Name] |
@@ -48,34 +50,24 @@
 
 ---
 
-## Linked Project
-
-> ⚠️ **MANDATORY**: Link to the project this story belongs to.
-
-| Project ID | Name |
-|------------|------|
-| [PROJECT-ID](../project.yml) | [Project Name] |
-
----
-
 ## Linked Epic
 
-> Recommended: Link to the parent epic.
+> ⚠️ **MANDATORY**: Epic link is embedded in filename (eXXX).  
+> **TEAMSPEC RULE:** TS-STORY-006 - Epic link required (via filename)
 
-| Epic ID | Epic Name |
-|---------|-----------|
-| [EPIC-XXX](../epics/EPIC-XXX.md) | [Epic Name] |
+| Epic ID | Epic Name | Product |
+|---------|-----------|---------|
+| [epic-PRX-XXX](../epics/epic-PRX-XXX-description.md) | [Epic Name] | [Product Name] (PRX) |
 
 ---
 
-## Linked Feature
+## Linked Feature-Increment
 
-> ⚠️ **MANDATORY**: Every story must link to at least one feature.  
-> **TEAMSPEC RULE:** TS-STORY-001 - Feature link required
+> Recommended: Link to the Feature-Increment this story implements.
 
-| Feature ID | Feature Name |
-|------------|--------------|
-| [F-XXX](../features/F-XXX-feature-name.md) | [Feature Name] |
+| FI ID | Description |
+|-------|-------------|
+| [fi-PRX-XXX](../feature-increments/fi-PRX-XXX-description.md) | [Brief description] |
 
 ---
 
@@ -84,7 +76,7 @@
 > Describe what this story CHANGES relative to current documented behavior.  
 > **Do NOT restate full feature behavior here.**
 
-<!-- TEAMSPEC RULE: TS-STORY-002 requires Before/After format -->
+<!-- TEAMSPEC RULE: TS-STORY-002 requires Before/After (AS-IS/TO-BE) format -->
 
 ### Impact Type
 
@@ -93,20 +85,20 @@
 - [ ] **Fixes Defect** — Restores behavior to match documentation (no feature update needed)
 - [ ] **Technical Only** — Refactor/performance with no user-observable change
 
-### Before (current behavior)
+### AS-IS (current behavior)
 
 <!-- 
-  Describe the CURRENT behavior as documented in Feature Canon.
-  Reference: F-XXX, Section: [section name]
+  Describe the CURRENT behavior as documented in Product Feature Canon.
+  Reference: f-PRX-XXX, Section: [section name]
   
-  Example: "Currently, users must log in with email/password (F-001, Main Flow Step 1)"
+  Example: "Currently, users must log in with email/password (f-DIT-001, Main Flow Step 1)"
 -->
 
-**Reference:** F-XXX, Section: [section]
+**Reference:** f-PRX-XXX, Section: [section]
 
 [Brief description of current behavior per Feature Canon]
 
-### After (new behavior)
+### TO-BE (new behavior)
 
 <!-- 
   Describe ONLY what changes.
@@ -118,8 +110,9 @@
 [ONLY the delta - what changes]
 
 > ⚠️ **FEATURE CANON RULE**  
-> If this story adds or changes behavior, the Feature Canon MUST be updated before this story can be marked Done.  
-> See: Definition of Done - TS-DOD-001
+> If this story adds or changes behavior, the Feature-Increment TO-BE must be complete  
+> and Canon sync must happen before project closure.  
+> See: TS-DOD-003 - Product sync after deployment
 
 ---
 
@@ -136,33 +129,16 @@
 
 ---
 
-## Decision References
-
-_Business decisions that drove this story's existence or scope._
-
-> **When Required**: If this story has "Adds Behavior" or "Changes Behavior" impact, it MUST either:
->
-> - Reference at least one DEC ID, OR
-> - Explicitly check "No new business decision required" below
-
-| Decision ID | Summary | Impact on This Story |
-|-------------|---------|----------------------|
-| [DEC-XXX](../decisions/DEC-XXX-*.md) | [One-line summary] | [Why this story exists / what changed] |
-
-- [ ] **No new business decision required** (for stories without scope/behavior decisions)
-
----
-
 ## Acceptance Criteria (AC)
 
-> AC must map to Feature Canon behavior. Reference feature business rules where applicable.
+> ⚠️ **MANDATORY**: AC must be present and testable.  
+> **TEAMSPEC RULE:** TS-STORY-003 - AC required
 
 ### Scenario 1: [Happy Path]
 
 - **Given** [Context]
 - **When** [Action]
 - **Then** [Result]
-- **Feature Rule**: [BR-XXX if applicable]
 
 ### Scenario 2: [Edge Case]
 
@@ -176,7 +152,7 @@ _Business decisions that drove this story's existence or scope._
 
 - **API**: [Endpoint]
 - **DB**: [Table/Schema]
-- **ADR**: [ADR-XXX if applicable]
+- **TAI**: [tai-PRX-XXX if applicable]
 
 ---
 
@@ -187,31 +163,14 @@ _Business decisions that drove this story's existence or scope._
 
 ---
 
-## FA Acceptance Gate
-
-> This story must be reviewed by FA before moving to Ready for Development.
-
-| Check | Status | FA Initials |
-|-------|--------|-------------|
-| Story describes delta only | [ ] | |
-| Feature link is correct | [ ] | |
-| ACs reference Feature Canon | [ ] | |
-| No full behavior restatement | [ ] | |
-
-**FA Approved:** [ ] Yes  
-**FA Name:** ________________  
-**Date:** ________________
-
----
-
 ## DoR Checklist (Feature Alignment)
 
-- [ ] Linked to one or more Feature IDs
-- [ ] Feature file(s) exist and are current
+- [ ] Linked to Epic (via filename s-eXXX-YYY)
+- [ ] Linked Epic exists in epics folder
+- [ ] Linked Feature-Increment exists (if applicable)
 - [ ] Story describes DELTA only, not full behavior
 - [ ] Feature impact type is marked
 - [ ] ACs map to feature behavior / business rules
-- [ ] Open questions tracked at feature level (not here)
 
 ## DoR Checklist (Standard)
 
@@ -225,10 +184,9 @@ _Business decisions that drove this story's existence or scope._
 
 - [ ] Code Complete
 - [ ] Tests Passed
-- [ ] **Feature Canon updated** (if behavior changed) — TS-DOD-001
-- [ ] Feature Change Log entry added
-- [ ] Story Ledger updated
+- [ ] Feature-Increment TO-BE complete (if behavior changed)
 - [ ] FA Accepted
+- [ ] Story marked Done in backlog
 
 ---
 
@@ -236,9 +194,9 @@ _Business decisions that drove this story's existence or scope._
 
 | Rule | Description | Status |
 |------|-------------|--------|
-| TS-STORY-001 | Feature link required | Checked on save |
-| TS-STORY-002 | Delta-only format | Checked on save |
+| TS-STORY-006 | Epic link required (via filename) | Checked on save |
+| TS-STORY-007 | Linked Epic must exist | Checked on save |
+| TS-STORY-002 | Delta-only format (AS-IS/TO-BE) | Checked on save |
 | TS-STORY-003 | ACs testable | Checked on Ready |
 | TS-STORY-004 | Sprint assignment by SM only | Checked on assignment |
 | TS-STORY-005 | DoR complete | Checked on Ready |
-| TS-DOD-001 | Canon sync | Checked on Done |