teamspec 3.2.0 → 4.1.0

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

@@ -0,0 +1,198 @@
+# Technical Architecture: `ta-{PRX}-{NNN}-{description}`
+
+<!--
+  ⚠️ TECHNICAL ARCHITECTURE RULES
+
+  Technical Architecture documents technical decisions and design approaches.
+
+  RULES:
+  1. Technical Architecture links to features they affect
+  2. Technical Architecture links to business decisions that triggered them
+  3. SA does NOT update Feature Canon directly - Technical Architecture informs FA
+  4. If behavior is affected, FA must review Feature Canon
+
+  NAMING PATTERN: ta-{PRX}-{NNN}-{description}.md
+  EXAMPLE: ta-ACME-001-microservices.md
+
+  TEAMSPEC RULES ENFORCED:
+  - TS-TA-001: Technical Architecture required for architecture-impacting changes
+  - TS-TA-002: Technical Architecture must link to affected features
+-->
+
+> **Template Version**: 4.0
+> **Last Updated**: 2026-01-11
+
+---
+
+**Document Owner:** SA (Solution Architect)  
+**Artifact Type:** Technical Architecture (Canonical)  
+**Lifecycle:** Permanent, versioned
+
+---
+
+## Metadata
+
+| Field | Value |
+| :--- | :--- |
+| **TA ID** | ta-{PRX}-{NNN} |
+| **Product** | {product-id} ({PRX}) |
+| **Status** | Proposed / Accepted / Deprecated / Superseded |
+| **Date** | YYYY-MM-DD |
+| **Author** | [SA Name] |
+| **Superseded By** | [ta-{PRX}-{NNN} if applicable] |
+
+---
+
+## Context
+
+> What is the problem? Why do we need to make a technical decision?
+
+[Describe the technical situation, constraints, and forces that require a decision.]
+
+---
+
+## Options Considered
+
+### Option 1: [Option Name]
+
+**Description**: [Brief description]
+
+**Pros**:
+- [Pro 1]
+- [Pro 2]
+
+**Cons**:
+- [Con 1]
+- [Con 2]
+
+### Option 2: [Option Name]
+
+**Description**: [Brief description]
+
+**Pros**:
+- [Pro 1]
+
+**Cons**:
+- [Con 1]
+
+---
+
+## Decision
+
+> We are choosing **Option X** because...
+
+[Clear statement of the decision and primary rationale]
+
+---
+
+## Consequences
+
+### Positive
+
+- [Benefit 1]
+- [Benefit 2]
+
+### Negative
+
+- [Trade-off 1]
+- [Trade-off 2]
+
+---
+
+## Related Decisions
+
+<!-- TEAMSPEC RULE: Link to business decisions that triggered this Technical Architecture -->
+
+| Decision ID | Decision Title | Relationship |
+|-------------|----------------|--------------|
+| [dec-{PRX}-{NNN}](../decisions/dec-{PRX}-{NNN}-*.md) | [Title] | Triggered by / Related to |
+
+> If this Technical Architecture was triggered by a business decision, link it here.
+
+---
+
+## Affected Features
+
+<!-- TEAMSPEC RULE: TS-TA-002 - Technical Architecture must link to features -->
+
+> ⚠️ If this decision affects user-observable behavior, FA must review Feature Canon.
+
+| Feature ID | Feature Name | Impact | Canon Review Needed? |
+|------------|--------------|--------|---------------------|
+| [f-{PRX}-{NNN}](../features/f-{PRX}-{NNN}-*.md) | [Name] | [How this affects behavior] | Yes / No |
+
+---
+
+## Behavior Impact Assessment
+
+> ⚠️ SA provides technical facts. FA translates to Feature Canon behavior.
+
+### Does this Technical Architecture affect user-observable behavior?
+
+- [ ] **No** — Internal/technical change only (no Canon update needed)
+- [ ] **Yes** — Behavior implications described below
+
+### Behavior Implications (if Yes)
+
+| Technical Decision | Behavior Implication | FA Action |
+|--------------------|---------------------|-----------|
+| [e.g., Rate limit: 100 req/min] | [e.g., System rejects excess requests] | FA adds to Canon |
+
+> **Workflow:**
+> 1. SA creates Technical Architecture with technical constraints
+> 2. Technical Architecture may imply behavior constraints
+> 3. FA incorporates constraints into Feature Canon
+> 4. FA owns the behavioral wording
+
+---
+
+## Examples of Behavior-Impacting Decisions
+
+✅ **Include in Feature Impact** (FA must review Canon):
+- Changing how errors are reported to users
+- Adding/removing functionality constraints
+- Changing performance characteristics users observe
+- Changing access control or permissions
+
+❌ **Usually no Feature Impact**:
+- Internal refactoring (no user-observable change)
+- Technology stack decisions (if behavior unchanged)
+- Database optimization (if behavior unchanged)
+
+---
+
+## Documentation Trail
+
+This Technical Architecture is referenced in Feature Canon Change Log when it affects documented behavior:
+
+> ta-{PRX}-{NNN}: [Title] — Added [feature capability / constraint]
+
+This maintains traceability between architecture and product behavior.
+
+---
+
+## Implementation Notes
+
+_Technical details for DEV team._
+
+- [Implementation note 1]
+- [Implementation note 2]
+
+---
+
+## Review & Approval
+
+| Role | Name | Status | Date |
+|------|------|--------|------|
+| SA (Author) | [Name] | ✅ | YYYY-MM-DD |
+| Tech Lead | [Name] | ⏳ | |
+| FA (if behavior affected) | [Name] | ⏳ | |
+
+---
+
+## Linter Rules Enforced
+
+| Rule | Description |
+|------|-------------|
+| TS-TA-001 | Technical Architecture required for architecture-impacting changes |
+| TS-TA-002 | Technical Architecture must link to affected features |

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

@@ -0,0 +1,131 @@
+# Technical Architecture Increment: `<tai-PRX-XXX-description>`
+
+> **ID:** tai-PRX-XXX  
+> **Product:** `<product-id>` (PRX)  
+> **Project:** `<project-id>`  
+> **Target TA Feature:** `<ta-PRX-XXX-name>`  
+> **Target Feature:** `<f-PRX-XXX-feature-name>`  
+> **Status:** draft | proposed | approved | implemented | synced
+
+---
+
+**Document Owner:** SA (Solution Architect)  
+**Artifact Type:** Technical Architecture Increment (Project)  
+**Lifecycle:** Project-scoped, merged to Product TA after approval
+
+---
+
+## Metadata
+
+| Field | Value |
+| :--- | :--- |
+| **TAI ID** | tai-PRX-XXX |
+| **Status** | Proposed / Accepted / Implemented / Synced |
+| **Date** | YYYY-MM-DD |
+| **Author** | [SA Name] |
+| **Target TA** | [ta-PRX-XXX](../../products/PRX/technical-architecture/ta-PRX-XXX-*.md) |
+| **Feature Increment** | [fi-PRX-XXX](../feature-increments/fi-PRX-XXX-*.md) |
+
+---
+
+## 1. Overview
+
+_Brief description of the technical architecture increment specific to this project._
+
+---
+
+## 2. AS-IS (Current Product TA)
+
+> _Auto-populated from Product Technical Architecture. DO NOT EDIT unless correcting errors._
+
+_Copy relevant sections from the Product TA._
+
+---
+
+## 3. TO-BE (Project Technical Architecture)
+
+### 3.1 New/Changed Architecture Elements
+
+_Describe what the project-specific architecture includes that product architecture doesn't._
+
+### 3.2 Technical Specifications
+
+_Detailed technical specifications for this increment._
+
+### 3.3 Out of Scope
+
+_Explicitly state what this increment does NOT include._
+
+---
+
+## 4. Impact Analysis
+
+### 4.1 Feature Implications
+
+| Feature | Impact Type | Description |
+|---------|-------------|-------------|
+| [f-PRX-XXX] | Modified | _What architecture changes affect this feature_ |
+
+### 4.2 Infrastructure Dependencies
+
+_Links to infrastructure or platform requirements._
+
+### 4.3 Implementation Constraints
+
+_Architecture constraints that affect DEV work._
+
+---
+
+## 5. Behavior Impact Assessment
+
+> ⚠️ Does this TAI affect user-observable behavior?
+
+### 5.1 Changes to Feature Behavior
+
+_What behavior changes result from this architecture._
+
+### 5.2 Feature Canon Updates
+
+_What sections of Feature Canon need updates based on this TAI._
+
+---
+
+## 6. Integration Notes
+
+### 6.1 Product TA Alignment
+
+_How this project TAI aligns with or extends the product TA._
+
+### 6.2 Merge Strategy
+
+_How this TAI will be merged back to Product TA after project completion._
+
+---
+
+## 7. Implementation Notes
+
+### 7.1 Development Guidelines
+
+_Key implementation guidance for the development team._
+
+### 7.2 Testing and Validation
+
+_How the architecture will be validated._
+
+---
+
+## 8. Review & Approval
+
+| Role | Name | Status | Date |
+|------|------|--------|------|
+| SA (Author) | [Name] | ✅ | YYYY-MM-DD |
+| Tech Lead | [Name] | ⏳ | |
+| FA (if behavior affected) | [Name] | ⏳ | |
+
+---
+
+## Change Log
+
+| Date | Author | Change |
+|------|--------|--------|
+| YYYY-MM-DD | @author | Initial draft |

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

@@ -0,0 +1,145 @@
+# Test Cases: `<tc-fi-PRX-XXX-description>`
+
+<!-- 
+  ⚠️ PROJECT-LEVEL TEST CASES
+  
+  Test cases for Feature Increments validate project-specific test scenarios.
+  These are created during sprint planning and refined during development.
+  
+  RULES:
+  1. Test cases reference Feature-Increment behavior
+  2. Tests can reference Feature Canon sections
+  3. Tests are specific to the project sprint
+  4. Linked to acceptance criteria
+  
+  TEAMSPEC RULES ENFORCED:
+  - TS-DOD-003: Tests are feature-increment level
+  - TS-QA-002: Tests must reference Feature Canon or Increment Canon
+-->
+
+> **Template Version**: 2.0  
+> **Last Updated**: 2026-01-07
+
+---
+
+**Document Owner:** QA (QA Engineer)  
+**Artifact Type:** Project Test Cases (Project-scoped)  
+**Lifecycle:** Project-scoped, merged to Product feature tests after approval
+
+---
+
+## Test Case Reference
+
+**Feature Increment:** [fi-PRX-XXX — Increment Name](../feature-increments/fi-PRX-XXX-*.md)  
+**Feature:** [F-XXX — Feature Name](../../products/PRX/features/F-XXX-name.md)  
+**Test Level:** Feature Increment (project-scoped)
+
+| Metadata | Value |
+| :--- | :--- |
+| **TC ID** | tc-fi-PRX-XXX |
+| **Feature Increment** | [fi-PRX-XXX](../feature-increments/fi-PRX-XXX-*.md) |
+| **Feature** | [F-XXX](../../products/PRX/features/F-XXX-name.md) |
+| **Author** | [QA Name] |
+| **Created** | YYYY-MM-DD |
+| **Last Updated** | YYYY-MM-DD |
+
+---
+
+## Test Scenarios
+
+### TC-001: [Title]
+
+- **Type**: Positive / Negative / Boundary
+- **Feature Reference**: [fi-PRX-XXX: TO-BE Behavior](../feature-increments/fi-PRX-XXX-*.md)
+- **Acceptance Criteria**: AC-1 from FI
+- **Pre-conditions**: [Setup required]
+- **Steps**:
+  1. [Action 1]
+  2. [Action 2]
+- **Expected Result**: [What should happen]
+- **Test Data**: [Data needed]
+- **Automation**: Manual / Automated
+
+### TC-002: [Title]
+
+- **Type**: Positive / Negative / Boundary
+- **Feature Reference**: [fi-PRX-XXX: TO-BE Behavior](../feature-increments/fi-PRX-XXX-*.md)
+- **Acceptance Criteria**: AC-2 from FI
+- **Pre-conditions**: [Setup required]
+- **Steps**:
+  1. [Action 1]
+  2. [Action 2]
+- **Expected Result**: [What should happen]
+- **Test Data**: [Data needed]
+- **Automation**: Manual / Automated
+
+---
+
+## Acceptance Criteria Coverage
+
+| AC ID | AC Description | Test ID | Status |
+|-------|----------------|---------|--------|
+| AC-1 | [From FI] | TC-001 | [ ] |
+| AC-2 | [From FI] | TC-002 | [ ] |
+| AC-3 | [From FI] | TC-003 | [ ] |
+
+---
+
+## Edge Case Coverage
+
+| Edge Case | Feature Behavior | Test ID | Status |
+|-----------|-----------------|---------|--------|
+| [Edge case 1] | [How it should behave] | TC-004 | [ ] |
+| [Edge case 2] | [How it should behave] | TC-005 | [ ] |
+
+---
+
+## Feature Alignment Validation
+
+Before marking tests as "Complete":
+
+- [ ] All tests reference Feature Increment or Feature Canon behavior
+- [ ] All acceptance criteria are covered
+- [ ] No tests for undocumented behavior
+- [ ] Feature-Increment is current (no pending updates)
+- [ ] Feature Canon is reviewed for conflicts
+
+---
+
+## Test Execution Results
+
+| Date | Tester | Environment | Pass | Fail | Blocked | Notes |
+|------|--------|-------------|------|------|---------|-------|
+| YYYY-MM-DD | [Name] | [Env] | {N} | {N} | {N} | |
+| YYYY-MM-DD | [Name] | [Env] | {N} | {N} | {N} | |
+
+---
+
+## Issues Logged
+
+| Issue ID | Description | Severity | Status | Owner |
+|----------|-------------|----------|--------|-------|
+| BUG-XXX | [Issue] | P1/P2/P3 | Open | [Owner] |
+
+---
+
+## Test Sign-Off
+
+This test pack validates:
+
+1. ✅ Feature-Increment acceptance criteria are met
+2. ✅ Documented behavior works correctly
+3. ✅ Edge cases are handled properly
+
+**QA Approved:** [ ] Yes  
+**QA Name:** ________________  
+**Date:** ________________  
+**Sprint:** ________________
+
+---
+
+## Change Log
+
+| Date | Author | Change |
+|------|--------|--------|
+| YYYY-MM-DD | @author | Initial test cases |

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

@@ -1,28 +1,31 @@
 # 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
+<!--
+  ⛔ DEPRECATED TEMPLATE - DO NOT USE
+
+  This template is DEPRECATED as of TeamSpec 4.0.
+
+  USE INSTEAD:
+  - tc-template.md for PROJECT test cases (tc-fi-{PRX}-{NNN}-*.md)
+  - Product regression tests use rt-f-{PRX}-{NNN}-*.md pattern
+
+  REASON: TeamSpec 4.0 uses a two-layer QA model:
+  1. Project Test Cases (tc-fi-*) → validate Feature-Increments
+  2. Product Regression Tests (rt-f-*) → long-term regression coverage
+
+  This old template doesn't follow the 4.0 naming conventions or QA model.
+
+  See: spec/4.0/registry.yml for correct artifact patterns
 -->
 
-> **Template Version**: 2.0  
+> **Template Version**: 2.0 (DEPRECATED)
 > **Last Updated**: 2026-01-07
+> **Status**: ⛔ DEPRECATED - Use tc-template.md instead
 
 ---
 
-**Document Owner:** QA (QA Engineer)  
-**Artifact Type:** Canonical (Feature-level)  
+**Document Owner:** QA (QA Engineer)
+**Artifact Type:** Canonical (Feature-level) - DEPRECATED
 **Lifecycle:** Permanent, evolves with Feature Canon
 
 ---