teamspec 3.2.0

package/teamspec-core/profiles/platform-team.yml

@@ -0,0 +1,104 @@
+# Platform Team Profile
+
+> **Version:** 2.0  
+> **Applies To:** Platform teams, infrastructure teams, API teams, DevOps
+
+This profile emphasizes API contracts, SLAs, and cross-team coordination.
+
+---
+
+## Profile Characteristics
+
+| Aspect | Configuration |
+|--------|---------------|
+| Governance Level | Moderate |
+| Sign-off Required | For breaking changes |
+| Audit Trail | Optional |
+| Change Control Board | No |
+| Documentation | API-focused |
+
+---
+
+## Additional Checkpoints
+
+### Definition of Ready Additions
+
+| Check | Enforcement |
+|-------|-------------|
+| API contract defined (if applicable) | Required |
+| Consumer impact assessed | Required |
+| SLA implications documented | Required |
+| Backward compatibility checked | Required |
+
+### Definition of Done Additions
+
+| Check | Enforcement |
+|-------|-------------|
+| API documentation updated | Required |
+| Consumer teams notified | Required |
+| Runbook updated (if operational) | Required |
+| Monitoring/alerting configured | Required |
+
+---
+
+## Required Artifacts
+
+Platform stories SHOULD include:
+
+1. **API Impact Section**
+   ```markdown
+   ## API Impact
+   
+   | Endpoint | Change Type | Breaking? |
+   |----------|-------------|-----------|
+   ```
+
+2. **Consumer Impact Section**
+   ```markdown
+   ## Consumer Impact
+   
+   - **Affected Teams:** [Team A, Team B]
+   - **Migration Required:** [Yes/No]
+   - **Deprecation Timeline:** [Date]
+   ```
+
+3. **SLA Considerations**
+   ```markdown
+   ## SLA Considerations
+   
+   - **Availability Impact:** [None/Minor/Major]
+   - **Performance Impact:** [None/Minor/Major]
+   - **Monitoring:** [Dashboard link]
+   ```
+
+---
+
+## Breaking Change Process
+
+For breaking changes:
+
+1. **Announce** — Notify consumers 2 sprints ahead
+2. **Document** — Create migration guide
+3. **Support** — Provide backward compatibility period
+4. **Deprecate** — Follow deprecation timeline
+
+---
+
+## Feature Canon Emphasis
+
+For platform teams, Feature Canon should include:
+
+1. **API contracts** (OpenAPI specs, etc.)
+2. **SLA definitions**
+3. **Consumer documentation**
+4. **Operational runbooks**
+
+---
+
+## Cross-Team Coordination
+
+| Artifact | Purpose |
+|----------|---------|
+| API Changelog | Track all API changes |
+| Consumer Registry | Know who uses what |
+| Deprecation Log | Track deprecation timelines |

package/teamspec-core/profiles/regulated.yml

@@ -0,0 +1,97 @@
+# Regulated Industry Profile
+
+> **Version:** 2.0  
+> **Applies To:** Banking, Healthcare, Government, Insurance
+
+This profile adds compliance-focused governance overlays to TeamSpec.
+
+---
+
+## Profile Characteristics
+
+| Aspect | Configuration |
+|--------|---------------|
+| Governance Level | Strict |
+| Sign-off Required | Yes |
+| Audit Trail | Yes |
+| Change Control Board | Yes |
+| Documentation | Comprehensive |
+
+---
+
+## Additional Checkpoints
+
+### Definition of Ready Additions
+
+| Check | Enforcement |
+|-------|-------------|
+| Risk assessment completed | Required |
+| Compliance impact documented | Required |
+| Data classification reviewed | Required |
+| Security review scheduled (if applicable) | Required |
+
+### Definition of Done Additions
+
+| Check | Enforcement |
+|-------|-------------|
+| Compliance sign-off obtained | Required |
+| Audit log entries verified | Required |
+| Release notes drafted | Required |
+| Rollback plan documented | Required |
+
+---
+
+## Required Artifacts
+
+Stories in regulated environments MUST include:
+
+1. **Risk Assessment Section**
+   ```markdown
+   ## Risk Assessment
+   
+   | Risk | Impact | Mitigation |
+   |------|--------|------------|
+   ```
+
+2. **Compliance Impact Section**
+   ```markdown
+   ## Compliance Impact
+   
+   - **Affected Regulations:** [SOX/PCI-DSS/HIPAA/etc.]
+   - **Data Classification:** [Public/Internal/Confidential/Restricted]
+   - **Audit Requirements:** [Yes/No]
+   ```
+
+---
+
+## Approval Gates
+
+| Gate | Approver | When |
+|------|----------|------|
+| Story Creation | BA + Compliance | Before backlog |
+| Sprint Entry | SM + Risk Officer | Sprint planning |
+| Release | CCB | Before deployment |
+
+---
+
+## Recommended Compliance Frameworks
+
+- SOX (Sarbanes-Oxley)
+- PCI-DSS (Payment Card Industry)
+- HIPAA (Health Insurance Portability)
+- GDPR (General Data Protection)
+- SOC2 (Service Organization Control)
+- ISO27001 (Information Security)
+- FedRAMP (Federal Risk and Authorization)
+- POPIA (Protection of Personal Information Act)
+
+---
+
+## Feature Canon Requirements
+
+For regulated environments, Feature Canon MUST include:
+
+1. **Compliance section** in feature files
+2. **Data handling documentation** 
+3. **Audit trail** of all changes
+4. **Version history** with approvers

package/teamspec-core/profiles/startup.yml

@@ -0,0 +1,85 @@
+# Startup / MVP Profile
+
+> **Version:** 2.0  
+> **Applies To:** Startups, MVP development, rapid prototyping
+
+This profile reduces documentation overhead while maintaining Feature Canon integrity.
+
+---
+
+## Profile Characteristics
+
+| Aspect | Configuration |
+|--------|---------------|
+| Governance Level | Minimal |
+| Sign-off Required | No |
+| Audit Trail | No |
+| Change Control Board | No |
+| Documentation | Lean |
+
+---
+
+## Adjusted Checkpoints
+
+### Definition of Ready Simplifications
+
+| Standard Check | Startup Adjustment |
+|----------------|-------------------|
+| Full dev plan required | Task list sufficient |
+| Formal risk assessment | Quick risk note OK |
+| Multiple approvers | Single FA approval |
+
+### Definition of Done Simplifications
+
+| Standard Check | Startup Adjustment |
+|----------------|-------------------|
+| Comprehensive test coverage | Critical path tests OK |
+| Formal code review | Pair programming counts |
+| Full documentation update | README update sufficient |
+
+---
+
+## Feature Canon (Still Required!)
+
+Even in startup mode, Feature Canon is mandatory:
+
+| Aspect | Requirement |
+|--------|-------------|
+| Feature files | Required (can be minimal) |
+| Story-feature links | Required |
+| Delta format | Recommended |
+| Story Ledger | Simplified OK |
+
+> ⚠️ **Feature Canon is NOT optional.** It prevents knowledge loss as the team scales.
+
+---
+
+## Recommended Practices
+
+1. **Time-box documentation** — 15 min max per story
+2. **Living docs** — Update as you code, not after
+3. **Lightweight ADRs** — One-pager decisions
+4. **Skip sprints** — Use Kanban if velocity matters more than planning
+
+---
+
+## When to Graduate
+
+Consider moving to `enterprise` or `regulated` profile when:
+
+- Team grows beyond 5 people
+- First paying customer
+- External audit required
+- Series A funding
+- Compliance requirements emerge
+
+---
+
+## Anti-Patterns to Avoid
+
+| Anti-Pattern | Why It's Bad |
+|--------------|--------------|
+| No Feature Canon | "We'll document later" = never |
+| No story tracking | Can't measure velocity |
+| Skipping tests entirely | Technical debt explodes |
+| One giant feature file | Unmaintainable |

package/teamspec-core/teamspec.yml

@@ -0,0 +1,69 @@
+# TeamSpec Configuration
+# Version: 2.0.0
+
+version: "2.0"
+name: "TeamSpec Feature Canon Operating Model"
+
+# Core principles
+principles:
+  - Feature Canon is the source of truth for system behavior
+  - Stories describe deltas (changes), not full behavior
+  - Structural artifacts require explicit creation commands
+  - Each role has clear ownership boundaries
+
+# Folder structure reference
+structure:
+  teamspec_root: ".teamspec"
+  project_root: "projects/{project-id}"
+  
+  folders:
+    features: "projects/{project-id}/features"
+    stories: "projects/{project-id}/stories"
+    adr: "projects/{project-id}/adr"
+    decisions: "projects/{project-id}/decisions"
+    dev_plans: "projects/{project-id}/dev-plans"
+    qa: "projects/{project-id}/qa"
+    sprints: "projects/{project-id}/sprints"
+    epics: "projects/{project-id}/epics"
+
+# Role definitions
+roles:
+  BA:
+    name: "Business Analyst"
+    owns:
+      - "Problem/goal definition"
+      - "Business value and scope"
+      - "Feature Canon: Purpose & Scope section"
+  FA:
+    name: "Functional Analyst"
+    owns:
+      - "Functional specifications"
+      - "Story slicing"
+      - "Feature Canon: Behavior section"
+      - "Feature Canon: Change Log"
+  SA:
+    name: "Solution Architect"
+    owns:
+      - "Technical design"
+      - "Architecture decisions (ADRs)"
+  DEV:
+    name: "Developer"
+    owns:
+      - "Implementation"
+      - "Development plans"
+  QA:
+    name: "Quality Assurance"
+    owns:
+      - "Test cases (feature-level)"
+      - "Bug reports"
+      - "UAT packs"
+  SM:
+    name: "Scrum Master"
+    owns:
+      - "Sprint management"
+      - "Process facilitation"
+  DES:
+    name: "Designer"
+    owns:
+      - "UI/UX design"
+      - "Design system"

package/teamspec-core/templates/README.md

@@ -0,0 +1,211 @@
+# TeamSpec 2.0 Templates
+
+> **Version:** 2.0  
+> **Last Updated:** 2026-01-07  
+> **Purpose:** Aligned templates for Feature Canon operating model
+
+---
+
+## Overview
+
+These templates are designed for the TeamSpec 2.0 Feature Canon operating model. Each template:
+
+1. **Identifies its owner** — Which role creates/maintains it
+2. **States its artifact type** — Source of Truth, Execution, Planning, or Operational
+3. **Enforces linter rules** — Which TS-* rules apply
+4. **Links to Feature Canon** — How it relates to the canonical source of truth
+
+---
+
+## Template Index
+
+### Source of Truth Templates
+
+These templates create **canonical artifacts** — the authoritative source of truth.
+
+| Template | Owner | Linter Rules | Purpose |
+|----------|-------|--------------|---------|
+| [feature-template.md](feature-template.md) | BA/FA | TS-FEAT-* | Feature Canon entries |
+| [decision-log-template.md](decision-log-template.md) | BA | TS-DEC-* | Business decisions |
+| [adr-template.md](adr-template.md) | SA | TS-ADR-* | Architecture decisions |
+
+### Execution Templates
+
+These templates create **execution artifacts** — deltas to the source of truth.
+
+| Template | Owner | Linter Rules | Purpose |
+|----------|-------|--------------|---------|
+| [story-template.md](story-template.md) | FA | TS-STORY-* | User stories (deltas) |
+| [testcases-template.md](testcases-template.md) | QA | TS-QA-* | Feature-level test cases |
+| [bug-report-template.md](bug-report-template.md) | QA | TS-QA-002 | Bug reports with classification |
+| [uat-pack-template.md](uat-pack-template.md) | QA | TS-UAT-* | User acceptance testing |
+
+### Planning Templates
+
+These templates create **planning artifacts** — become historical after Canon is established.
+
+| Template | Owner | Lifecycle | Purpose |
+|----------|-------|-----------|---------|
+| [business-analysis-template.md](business-analysis-template.md) | BA | Historical | Business analysis |
+| [functional-spec-template.md](functional-spec-template.md) | FA | Transitional | Functional elaboration |
+| [storymap-template.md](storymap-template.md) | FA | Historical | Story mapping workshops |
+| [refinement-notes-template.md](refinement-notes-template.md) | FA | Historical | Refinement session notes |
+
+### Operational Templates
+
+These templates create **operational artifacts** — sprint and process management.
+
+| Template | Owner | Lifecycle | Purpose |
+|----------|-------|-----------|---------|
+| [sprint-template.md](sprint-template.md) | SM | Sprint-bound | Sprint management |
+| [sprint-goal-template.md](sprint-goal-template.md) | SM | Sprint-bound | Sprint goal and commitment |
+| [active-sprint-template.md](active-sprint-template.md) | SM | Living | Current sprint status |
+| [sprints-index-template.md](sprints-index-template.md) | SM | Living | Sprint history index |
+
+---
+
+## Artifact Lifecycle
+
+```
+Planning Artifacts          Source of Truth          Execution Artifacts
+─────────────────          ──────────────────        ────────────────────
+BA Doc ─────────────────▶  Feature Canon  ◀─────────  Stories (deltas)
+Functional Spec ────────▶  Decision Log   ◀─────────  Bug Reports
+Story Map ──────────────▶  ADRs           ◀─────────  Test Cases
+
+      (Historical)           (Canonical)             (Sprint-bound)
+```
+
+---
+
+## Key Alignment Features
+
+### 1. Delta Enforcement (Stories)
+
+Stories use Before/After format and MUST link to features:
+
+```markdown
+### Before (current behavior)
+Reference: F-XXX, Section: [section]
+
+### After (new behavior)
+[ONLY the delta - what changes]
+```
+
+### 2. FA Acceptance Gate (Stories)
+
+Stories require FA approval before Ready for Development:
+
+```markdown
+## FA Acceptance Gate
+
+| Check | Status | FA Initials |
+|-------|--------|-------------|
+| Story describes delta only | [ ] | |
+| Feature link is correct | [ ] | |
+```
+
+### 3. Bug Classification (Bugs)
+
+Bugs must be classified into exactly one category:
+
+- **Implementation Defect** — Code doesn't match Canon
+- **Feature Canon Wrong** — Canon doesn't match intent
+- **Undocumented Behavior** — Neither covers the case
+
+### 4. Feature-Level Testing (Test Cases)
+
+Tests validate Feature Canon, not individual stories:
+
+```markdown
+**Feature:** [F-XXX](../../features/F-XXX-name.md)
+**Test Level:** Feature (not Story)
+```
+
+### 5. Scope Freeze (Sprints)
+
+After sprint commitment, scope changes require decision log:
+
+```markdown
+## Scope Freeze Notice
+
+**Sprint Committed:** [ ] Yes / [ ] No
+> ⚠️ After commitment, any scope change requires Decision Log entry.
+```
+
+### 6. Canon Sync Verification (Sprints)
+
+Before sprint close, verify Canon is updated:
+
+```markdown
+## Canon Sync Verification
+
+| Story | Impact Type | Canon Updated? | FA Verified |
+|-------|-------------|----------------|-------------|
+```
+
+---
+
+## Template Ownership by Role
+
+| Role | Templates Owned |
+|------|-----------------|
+| **BA** | business-analysis, decision-log, feature (Purpose/Scope) |
+| **FA** | story, functional-spec, storymap, refinement-notes, feature (Behavior) |
+| **SA** | adr |
+| **DEV** | — (uses dev-plans, not templated here) |
+| **QA** | testcases, bug-report, uat-pack |
+| **SM** | sprint, sprint-goal, active-sprint, sprints-index |
+
+---
+
+## Linter Rules Reference
+
+| Rule | Applies To | Description |
+|------|------------|-------------|
+| TS-STORY-001 | Stories | Feature link required |
+| TS-STORY-002 | Stories | Delta-only format |
+| TS-STORY-003 | Stories | ACs testable |
+| TS-STORY-004 | Stories | Sprint assignment by SM only |
+| TS-STORY-005 | Stories | DoR complete |
+| TS-FEAT-001 | Features | Feature must exist before stories |
+| TS-FEAT-002 | Features | All sections required |
+| TS-FEAT-003 | Features | Feature ID unique |
+| TS-DEC-001 | Decisions | Must link to features |
+| TS-ADR-001 | ADRs | Required for architecture changes |
+| TS-ADR-002 | ADRs | Must link to features |
+| TS-QA-001 | Tests | Must reference Feature Canon |
+| TS-QA-002 | Bugs | Classification required |
+| TS-DOD-001 | All | Canon sync before Done |
+| TS-DOD-002 | Tests | Tests are feature-level |
+| TS-DEVPLAN-001 | Sprints | Dev plan before implementation |
+
+---
+
+## Usage
+
+### Creating New Artifacts
+
+1. Copy the appropriate template
+2. Fill in all required sections
+3. Ensure links to Feature Canon are correct
+4. Verify linter rules pass
+
+### Template Customization
+
+These templates can be customized per project, but:
+
+- **DO NOT** remove linter rule sections
+- **DO NOT** remove ownership markers
+- **DO NOT** remove Feature Canon links
+- **DO** add project-specific sections as needed
+
+---
+
+## Related Documentation
+
+- [agents/README.md](../agents/README.md) — Agent prompts
+- [roles/ROLES_AND_RESPONSIBILITIES.md](../roles/ROLES_AND_RESPONSIBILITIES.md) — Role definitions
+- [roles/WORKFLOW.md](../roles/WORKFLOW.md) — Workflow phases
+- [roles/LINTER_RULES_SPECIFICATION.md](../roles/LINTER_RULES_SPECIFICATION.md) — Linter rules
+- [roles/TEMPLATE_ALIGNMENT_REQUIREMENTS.md](../roles/TEMPLATE_ALIGNMENT_REQUIREMENTS.md) — Alignment spec

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

@@ -0,0 +1,98 @@
+# Active Sprint
+
+> **Living Document**: This file always reflects the current active sprint.
+
+> **Template Version**: 2.0  
+> **Last Updated**: 2026-01-07
+
+---
+
+**Document Owner:** SM (Scrum Master)  
+**Artifact Type:** Operational (Living)  
+**Location:** `sprints/active-sprint.md`
+
+---
+
+## Current Sprint
+
+**Sprint {N}**: [{Sprint Goal Title}](sprint-{N}/sprint-goal.md)
+
+| Field | Value |
+|-------|-------|
+| **Status** | 🟢 Active |
+| **Start** | {YYYY-MM-DD} |
+| **End** | {YYYY-MM-DD} |
+| **Days Remaining** | {N} |
+
+---
+
+## Sprint Goal
+
+> {One-sentence sprint goal}
+
+---
+
+## Progress Summary
+
+| Metric | Value |
+|--------|-------|
+| **Total Points** | {N} |
+| **Completed** | {N} |
+| **Remaining** | {N} |
+| **Progress** | {N}% |
+
+```
+[████████░░░░░░░░░░░░] 40%
+```
+
+---
+
+## Story Status
+
+| Story | Title | Points | Dev Plan | Status |
+|-------|-------|--------|----------|--------|
+| S-XXX | {Title} | {N} | [Plan](../dev-plans/story-XXX-tasks.md) | 🟢 Done |
+| S-XXX | {Title} | {N} | [Plan](../dev-plans/story-XXX-tasks.md) | 🟡 In Progress |
+| S-XXX | {Title} | {N} | [Plan](../dev-plans/story-XXX-tasks.md) | ⚪ Not Started |
+
+**Status Legend**: 🟢 Done | 🟡 In Progress | ⚪ Not Started | 🔴 Blocked
+
+---
+
+## Canon Sync Status
+
+> ⚠️ Stories with behavior changes must have Feature Canon updated before Done.
+
+| Story | Impact Type | Canon Synced? |
+|-------|-------------|---------------|
+| S-XXX | Adds Behavior | [ ] |
+| S-XXX | Changes Behavior | [ ] |
+
+---
+
+## Blockers
+
+| Story | Blocker | Days Blocked | Escalated To |
+|-------|---------|--------------|--------------|
+| _None_ | | | |
+
+---
+
+## Quick Links
+
+- [Sprint Goal Details](sprint-{N}/sprint-goal.md)
+- [Definition of Ready](../.teamspec/definitions/definition-of-ready.md)
+- [Definition of Done](../.teamspec/definitions/definition-of-done.md)
+- [Feature Canon](../features/)
+
+---
+
+## Sprint History
+
+| Sprint | Goal | Velocity | Status |
+|--------|------|----------|--------|
+| [Sprint {N-1}](sprint-{N-1}/sprint-goal.md) | {Goal} | {N} pts | ✅ Closed |
+
+---
+
+_Last updated: {YYYY-MM-DD HH:MM}_