teamspec 3.2.0

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

@@ -0,0 +1,244 @@
+# S-XXX: [Title]
+
+<!-- TEAMSPEC RULE: TS-STORY-002 -->
+<!-- 
+  ⚠️ STORIES ARE DELTAS, NOT DOCUMENTATION
+  
+  This story describes a CHANGE to the Feature Canon.
+  
+  DO NOT:
+  - Restate full feature behavior
+  - Include complete specifications
+  - Document end-to-end flows
+  
+  DO:
+  - Reference Feature Canon (F-XXX) for current behavior
+  - Describe only what changes (Before → After)
+  - Link to Feature Canon rules (BR-XXX)
+-->
+
+> **Template Version**: 2.0  
+> **Last Updated**: 2026-01-07
+
+---
+
+## Metadata
+
+| Field | Value |
+|-------|-------|
+| **Story ID** | S-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 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.
+
+| Epic ID | Epic Name |
+|---------|-----------|
+| [EPIC-XXX](../epics/EPIC-XXX.md) | [Epic Name] |
+
+---
+
+## Linked Feature
+
+> ⚠️ **MANDATORY**: Every story must link to at least one feature.  
+> **TEAMSPEC RULE:** TS-STORY-001 - Feature link required
+
+| Feature ID | Feature Name |
+|------------|--------------|
+| [F-XXX](../features/F-XXX-feature-name.md) | [Feature Name] |
+
+---
+
+## 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 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
+
+### Before (current behavior)
+
+<!-- 
+  Describe the CURRENT behavior as documented in Feature Canon.
+  Reference: F-XXX, Section: [section name]
+  
+  Example: "Currently, users must log in with email/password (F-001, Main Flow Step 1)"
+-->
+
+**Reference:** F-XXX, Section: [section]
+
+[Brief description of current behavior per Feature Canon]
+
+### After (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 Canon MUST be updated before this story can be marked Done.  
+> See: Definition of Done - TS-DOD-001
+
+---
+
+## 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.
+
+---
+
+## 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.
+
+### Scenario 1: [Happy Path]
+
+- **Given** [Context]
+- **When** [Action]
+- **Then** [Result]
+- **Feature Rule**: [BR-XXX if applicable]
+
+### Scenario 2: [Edge Case]
+
+- **Given** ...
+- **When** ...
+- **Then** ...
+
+---
+
+## Technical Notes
+
+- **API**: [Endpoint]
+- **DB**: [Table/Schema]
+- **ADR**: [ADR-XXX if applicable]
+
+---
+
+## UX & Copy
+
+- [Figma Link]
+- Error Messages: [List specific messages]
+
+---
+
+## 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
+- [ ] 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)
+
+- [ ] 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 Canon updated** (if behavior changed) — TS-DOD-001
+- [ ] Feature Change Log entry added
+- [ ] Story Ledger updated
+- [ ] FA Accepted
+
+---
+
+## Linter Rules Enforced
+
+| Rule | Description | Status |
+|------|-------------|--------|
+| TS-STORY-001 | Feature link required | Checked on save |
+| TS-STORY-002 | Delta-only format | 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 |

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

@@ -0,0 +1,204 @@
+---
+epic_id: "[EPIC-ID]"
+epic_name: "[Epic Name]"
+goal: "[One-sentence business goal]"
+personas:
+  - "[Persona 1]"
+  - "[Persona 2]"
+constraints:
+  - "[Constraint 1]"
+  - "[Constraint 2]"
+backbone_activities:
+  - "[Activity 1]"
+  - "[Activity 2]"
+  - "[Activity 3]"
+steps:
+  "[Activity 1]":
+    - "[Step 1.1]"
+    - "[Step 1.2]"
+  "[Activity 2]":
+    - "[Step 2.1]"
+    - "[Step 2.2]"
+feature_slices:
+  - name: "[Feature Slice 1]"
+    priority: "MVP"
+    goal: "[What this slice delivers]"
+    related_steps:
+      - "[Activity: Step]"
+  - name: "[Feature Slice 2]"
+    priority: "Next"
+    goal: "[What this slice delivers]"
+    related_steps:
+      - "[Activity: Step]"
+story_candidates:
+  - title: "[Story 1 title]"
+    slice: "[Feature Slice 1]"
+    feature_ids: ["F-XXX"]
+    notes: "[Implementation notes]"
+    risks: "[Known risks]"
+  - title: "[Story 2 title]"
+    slice: "[Feature Slice 1]"
+    feature_ids: ["F-XXX"]
+    notes: "[Implementation notes]"
+    risks: "[Known risks]"
+---
+
+# Story Map: [Epic Name]
+
+<!-- 
+  ⚠️ STORY MAP RULES
+  
+  Story maps help visualize user journeys and slice features.
+  
+  RULES:
+  1. Story candidates must link to Feature IDs
+  2. Features must exist in Canon before stories are created
+  3. This is a planning artifact, not source of truth
+-->
+
+> **Template Version**: 2.0  
+> **Last Updated**: 2026-01-07
+
+---
+
+**Document Owner:** FA (Functional Analyst)  
+**Artifact Type:** Planning (Workshop Output)  
+**Lifecycle:** Historical after stories created
+
+---
+
+**Epic ID**: [EPIC-ID]  
+**Created**: YYYY-MM-DD  
+**Facilitator**: [Name/Role]  
+**Participants**: [BA, FA, ARCH, DEV, QA names]
+
+---
+
+## Epic Overview
+
+### Goal
+
+[One-sentence statement of business value]
+
+### Personas
+
+| Persona | Description | Key Needs |
+|---------|-------------|-----------|
+| [Persona 1] | [Brief description] | [What they need] |
+| [Persona 2] | [Brief description] | [What they need] |
+
+### Constraints
+
+- **Technical**: [Stack, platform, integrations]
+- **Compliance**: [GDPR, SOX, etc.]
+- **Timeline**: [MVP deadline, launch date]
+- **Resources**: [Team size, skills]
+
+### Success Metrics
+
+| Metric | Target |
+|--------|--------|
+| [KPI 1] | [Target] |
+| [KPI 2] | [Target] |
+
+---
+
+## Story Map Visualization
+
+### Backbone (Activities)
+
+```
+┌─────────────┬─────────────┬─────────────┬─────────────┐
+│  Activity 1 │  Activity 2 │  Activity 3 │  Activity 4 │
+└─────────────┴─────────────┴─────────────┴─────────────┘
+```
+
+---
+
+## User Steps by Activity
+
+### Activity 1: [Activity Name]
+
+**User Steps**:
+1. [Step 1.1]
+2. [Step 1.2]
+3. [Step 1.3]
+
+**Edge Cases**:
+- [Edge case 1]
+- [Edge case 2]
+
+### Activity 2: [Activity Name]
+
+**User Steps**:
+1. [Step 2.1]
+2. [Step 2.2]
+
+**Edge Cases**:
+- [Edge case 1]
+
+---
+
+## Feature Slices
+
+| Slice | Priority | Goal | Features | Stories |
+|-------|----------|------|----------|---------|
+| [Slice 1] | MVP | [What it delivers] | F-XXX | S-001, S-002 |
+| [Slice 2] | Next | [What it delivers] | F-YYY | S-003 |
+| [Slice 3] | Later | [What it delivers] | F-ZZZ | TBD |
+
+---
+
+## Story Candidates
+
+> ⚠️ All story candidates must link to Feature IDs.
+> Features must exist in Canon before stories are created.
+
+| Title | Slice | Feature(s) | Impact | Notes | Risks |
+|-------|-------|------------|--------|-------|-------|
+| [Story 1] | MVP | F-XXX | Adds | [Notes] | [Risks] |
+| [Story 2] | MVP | F-XXX | Adds | [Notes] | [Risks] |
+| [Story 3] | Next | F-YYY | Adds | [Notes] | [Risks] |
+
+---
+
+## Feature Canon Alignment
+
+> Verify features exist before creating stories.
+
+| Feature ID | Feature Name | Status | Stories Mapped |
+|------------|--------------|--------|----------------|
+| F-XXX | [Name] | Active / To Create | S-001, S-002 |
+| F-YYY | [Name] | Active / To Create | S-003 |
+
+**Features to Create**:
+- [ ] F-XXX: [Feature Name] — Owner: BA
+- [ ] F-YYY: [Feature Name] — Owner: BA
+
+---
+
+## Dependencies
+
+```mermaid
+graph LR
+    S1[Story 1] --> S2[Story 2]
+    S2 --> S3[Story 3]
+    S1 --> S4[Story 4]
+```
+
+---
+
+## Risks & Mitigations
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|------------|--------|------------|
+| [Risk 1] | High/Med/Low | High/Med/Low | [Mitigation] |
+
+---
+
+## Next Steps
+
+- [ ] BA to create missing Feature files
+- [ ] FA to create stories from candidates
+- [ ] Link stories to features
+- [ ] Refine stories in backlog

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

@@ -0,0 +1,147 @@
+# Test Cases: [Feature Name]
+
+<!-- 
+  ⚠️ TESTS ARE FEATURE-LEVEL, NOT STORY-LEVEL
+  
+  Test cases validate Feature Canon behavior, not individual stories.
+  
+  RULES:
+  1. Tests reference Feature Canon sections
+  2. Tests are canonical (survive story completion)
+  3. If behavior doesn't match Canon, classify the issue
+  4. Do not create story-specific test cases
+  
+  TEAMSPEC RULES ENFORCED:
+  - TS-DOD-002: Tests are feature-level
+  - TS-QA-001: Tests must reference Feature Canon
+-->
+
+> **Template Version**: 2.0  
+> **Last Updated**: 2026-01-07
+
+---
+
+**Document Owner:** QA (QA Engineer)  
+**Artifact Type:** Canonical (Feature-level)  
+**Lifecycle:** Permanent, evolves with Feature Canon
+
+---
+
+## Test Case Reference
+
+**Feature:** [F-XXX — Feature Name](../../features/F-XXX-name.md)  
+**Test Level:** Feature (not Story)
+
+| Metadata | Value |
+| :--- | :--- |
+| **Feature** | [F-XXX](../../features/F-XXX-name.md) – [Feature Name] |
+| **Author** | [QA Name] |
+| **Created** | YYYY-MM-DD |
+| **Last Updated** | YYYY-MM-DD |
+
+<!-- TEAMSPEC RULE: TS-DOD-002 - Tests are feature-level -->
+
+> ⚠️ Test cases are canonical and feature-level.
+> Do not create story-specific test cases.
+> Test against Feature Canon, not individual stories.
+
+---
+
+## Test Scenarios
+
+### TC-001: [Title]
+
+- **Type**: Positive / Negative / Boundary
+- **Feature Reference**: F-XXX: Current Behavior > [Section]
+- **Business Rule**: BR-XXX-001 (if applicable)
+- **Pre-conditions**: [Setup required]
+- **Steps**:
+  1. [Action 1]
+  2. [Action 2]
+- **Expected Result**: [What should happen]
+- **Canon Alignment**: ✓ Matches Feature Canon documented behavior
+
+### TC-002: [Title]
+
+- **Type**: Positive / Negative / Boundary
+- **Feature Reference**: F-XXX: Current Behavior > [Section]
+- **Business Rule**: BR-XXX-002 (if applicable)
+- **Pre-conditions**: [Setup required]
+- **Steps**:
+  1. [Action 1]
+  2. [Action 2]
+- **Expected Result**: [What should happen]
+- **Canon Alignment**: ✓ Matches Feature Canon documented behavior
+
+---
+
+## Edge Case Coverage
+
+| Edge Case | Feature Canon Section | Test ID | Status |
+|-----------|----------------------|---------|--------|
+| [Edge case 1] | F-XXX: Edge Cases | TC-003 | [ ] |
+| [Edge case 2] | F-XXX: Edge Cases | TC-004 | [ ] |
+
+---
+
+## Business Rule Validation
+
+| Rule ID | Rule Description | Test ID | Status |
+|---------|------------------|---------|--------|
+| BR-XXX-001 | [Rule description] | TC-001 | [ ] |
+| BR-XXX-002 | [Rule description] | TC-002 | [ ] |
+
+---
+
+## Feature Alignment Validation
+
+Before marking tests as "Complete":
+
+- [ ] All tests reference Feature Canon behavior
+- [ ] No tests for undocumented behavior
+- [ ] If behavior doesn't match Feature Canon, flagged for investigation
+- [ ] Feature file is current (no ⚠️ pending updates)
+- [ ] Business rules (BR-XXX) are all tested
+
+---
+
+## Post-Test Documentation Check
+
+After testing is complete:
+
+- [ ] If behavior matches Feature Canon: ✅ Pass
+- [ ] If behavior doesn't match Feature Canon:
+  - [ ] Is Feature Canon wrong? Flag for FA sync.
+  - [ ] Is implementation wrong? File bug for DEV.
+  - [ ] Is this undocumented behavior? Alert FA immediately.
+
+---
+
+## Test Execution Log
+
+| Date | Tester | Environment | Pass | Fail | Blocked | Notes |
+|------|--------|-------------|------|------|---------|-------|
+| YYYY-MM-DD | [Name] | [Env] | {N} | {N} | {N} | |
+
+---
+
+## Sign-Off
+
+This test pack is evidence that:
+
+1. ✅ Documented behavior works correctly
+2. ✅ No undocumented behavior was introduced
+3. ✅ Feature Canon is accurate and complete
+
+**QA Approved:** [ ] Yes  
+**QA Name:** ________________  
+**Date:** ________________
+
+---
+
+## Linter Rules Enforced
+
+| Rule | Description |
+|------|-------------|
+| TS-QA-001 | Tests must reference Feature Canon |
+| TS-DOD-002 | Tests are feature-level, not story-level |