@torus-engineering/tas-kit 1.13.0 → 2.1.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@torus-engineering/tas-kit",
-  "version": "1.13.0",
-  "description": "Turbo AI-first toolkit for modern agentic SDLC teams.",
+  "version": "2.1.0",
+  "description": "TAS Kit - Turbo Agentic SDLC toolkit for modern AI-first software teams.",
   "type": "module",
   "bin": {
     "tas-kit": "bin/cli.js"

package/.tas/README.md

@@ -1,334 +0,0 @@
-# TAS Kit
-
-Turbo AI-first toolkit for modern agentic SDLC teams.
-
----
-
-## Purpose
-
-TAS Kit helps software development teams:
-- **Standardize SDLC process** with clear artifacts (PRD, SAD, ADR, Epic, Feature, Story)
-- **Optimize token usage** through Context Layer — invest in design phase, save in code phase
-- **Support multiple workflows**: from solo developer to full team with PE/SE/DSE roles
-- **Automate** with Hybrid and Autonomous agents operating 24/7
-
----
-
-## Design Philosophy
-
-### Spec-Driven Development
-All code starts from spec. Story.md is "context digest" that has absorbed all information from PRD, SAD, ADR, Feature. Each implementation session only needs to read CLAUDE.md + Story.md — no need to reload all artifacts.
-
-### Human-Led, AI-Powered
-- **Human-led**: Architecture decisions, design approval, code review
-- **AI-assisted**: Draft creation, implementation per spec, test execution, bug detection
-
-### Dual Mode Operation
-- **Hybrid Mode**: Developer and AI work together in session
-- **Autonomous Mode**: AI automatically develops 24/7, reports results when done
-
-### Lightweight & Context-Aware
-- Each skill < 3KB, total kit < 50KB
-- Context Layer: invest tokens in design phase to save many times in code phase
-- When coding: MUST start new session (don't reuse old session that loaded PRD/SAD to avoid Window Context bloat)
-
-### Role-Based & Template-Driven
-- 3 roles: PE (Product Engineer), SE (Software Engineer), DSE (DevOps Engineer)
-- Separate templates for PRD, SAD, ADR, Epic, Feature, Story per team standards
-- Flow configurable via `tas.yaml` file
-
-### Azure DevOps Compatible
-- Markdown output compatible with Azure DevOps Wiki
-- Mermaid diagrams don't use `()` characters (avoid conflict with ADO syntax)
-
----
-
-## SDLC Workflow
-
-:::mermaid
-graph TD
-    subgraph Phase1["Phase 1: Discovery"]
-        PRD["/tas-prd"]
-        SAD["/tas-sad"]
-        ADR["/tas-adr"]
-        DESIGN["/tas-design"]
-        PRD -->|Product Engineer| PRD_ARTIFACT["PRD.md"]
-        PRD_ARTIFACT -->|Software Engineer| SAD
-        PRD_ARTIFACT -->|Software Engineer| ADR
-        SAD --> SAD_ARTIFACT["SAD.md"]
-        ADR --> ADR_ARTIFACT["ADR-XXX.md"]
-        PRD_ARTIFACT -->|Product Engineer| DESIGN
-        DESIGN --> DESIGN_ARTIFACT["design-spec.md"]
-    end
-
-    subgraph Phase2["Phase 2: Planning"]
-        EPIC["/tas-epic"]
-        FEATURE["/tas-feature"]
-        STORY["/tas-story"]
-        PRD_ARTIFACT -->|Product Engineer| EPIC
-        EPIC --> EPIC_ARTIFACT["Epic-XXX/"]
-        EPIC_ARTIFACT -->|Product Engineer| FEATURE
-        FEATURE --> FEATURE_ARTIFACT["Feature-XXX/"]
-        SAD_ARTIFACT --> FEATURE
-        DESIGN_ARTIFACT --> FEATURE
-        FEATURE_ARTIFACT -->|Product Engineer| STORY
-        STORY --> STORY_ARTIFACT["Story-XXX.md"]
-    end
-
-    subgraph Phase3["Phase 3: Implementation"]
-        PLAN["/tas-plan"]
-        DEV["/tas-dev"]
-        FIX["/tas-fix"]
-        APItest["/tas-apitest"]
-        E2E["/tas-e2e"]
-        FUNCTEST_WEB["/tas-functest-web"]
-        FUNCTEST_MOBILE["/tas-functest-mobile"]
-        E2E_WEB["/tas-e2e-web"]
-        E2E_MOBILE["/tas-e2e-mobile"]
-        BUG["/tas-bug"]
-        REVIEW["/tas-review"]
-        FUNctest["/tas-functest"]
-        STORY_ARTIFACT -->|Software Engineer| PLAN
-        PLAN --> STORY_ARTIFACT
-        STORY_ARTIFACT -->|AI Agent| DEV
-        DEV --> CODE["Source Code"]
-        CODE -->|Bug found| FIX
-        FIX --> CODE
-        CODE -->|Software Engineer| REVIEW
-        REVIEW --> REVIEW_ARTIFACT["Code Review Report"]
-        STORY_ARTIFACT -->|Software Engineer| APItest
-        APItest --> APITEST_ARTIFACT["API Testing Script"]
-        FUNCTEST_ARTIFACT -->|Product Engineer| E2E
-        E2E --> E2E_ARTIFACT["E2E Test Scenarios"]
-        FUNCTEST_ARTIFACT -->|Software Engineer| FUNCTEST_WEB
-        FUNCTEST_WEB --> FUNCTEST_WEB_ARTIFACT["Functional Test Web Script"]
-        FUNCTEST_ARTIFACT -->|Software Engineer| FUNCTEST_MOBILE
-        FUNCTEST_MOBILE --> FUNCTEST_MOBILE_ARTIFACT["Functional Test Mobile Script"]
-        FUNCTEST_ARTIFACT -->|Product Engineer| E2E_WEB
-        E2E_WEB --> E2E_WEB_ARTIFACT["E2E Web Test Script"]
-        FUNCTEST_ARTIFACT -->|Product Engineer| E2E_MOBILE
-        E2E_MOBILE --> E2E_MOBILE_ARTIFACT["E2E Mobile Test Script"]
-        CODE -->|Bug found| BUG
-        BUG --> BUG_ARTIFACT["Bug Report"]
-        FEATURE_ARTIFACT -->|Product Engineer| FUNctest
-        FUNctest --> FUNCTEST_ARTIFACT["Functional-Testing-Spec-FeatureXXX.md"]
-    end
-
-    subgraph Phase4["Phase 4: Quality & Deploy"]
-        SECURITY["/tas-security"]
-        PIPELINE["Pipeline / CLI"]
-        CODE -->|DevOps Engineer| SECURITY
-        SECURITY --> SECURITY_ARTIFACT["Security Report"]
-        APITEST_ARTIFACT -->|Product Engineer| PIPELINE
-        FUNCTEST_WEB_ARTIFACT --> PIPELINE
-        FUNCTEST_MOBILE_ARTIFACT --> PIPELINE
-        E2E_WEB_ARTIFACT --> PIPELINE
-        E2E_MOBILE_ARTIFACT --> PIPELINE
-        PIPELINE --> TEST_REPORT["Test Report"]
-        SECURITY_ARTIFACT -->|DevOps Engineer| DEPLOY["Production"]
-        TEST_REPORT --> DEPLOY
-    end
-
-    STATUS["/tas-status"] -.->|Track| PRD_ARTIFACT
-    STATUS -.->|Track| SAD_ARTIFACT
-    STATUS -.->|Track| STORY_ARTIFACT
-    STATUS -.->|Track| DEPLOY
-
-    style PRD_ARTIFACT fill:#e1f5ff
-    style SAD_ARTIFACT fill:#fff4e1
-    style DESIGN_ARTIFACT fill:#f3e5f5
-    style STORY_ARTIFACT fill:#e8f5e9
-    style CODE fill:#f3e5f5
-    style TEST_REPORT fill:#c8e6c9
-    style DEPLOY fill:#c8e6c9
-:::
-
-### Phase Summary
-
-| Phase | Role | Commands | Artifacts |
-|-------|------|----------|-----------|
-| **Phase 1: Discovery** | PE, SE | `/tas-prd`, `/tas-sad`, `/tas-adr`, `/tas-design` | PRD.md, SAD.md, ADR-XXX.md, design-spec.md |
-| **Phase 2: Planning** | SE | `/tas-epic`, `/tas-feature`, `/tas-story`, `/tas-functest` | Epic-XXX/, Feature-XXX/, Story-XXX.md, Functional-Testing-Spec-FeatureXXX.md |
-| **Phase 3: Implementation** | PE, SE, AI | `/tas-plan`, `/tas-dev`, `/tas-fix`, `/tas-apitest`, `/tas-e2e`, `/tas-functest-web`, `/tas-functest-mobile`, `/tas-e2e-web`, `/tas-e2e-mobile`, `/tas-bug`, `/tas-review` | Plan.md, Source Code, API Testing Script, E2E Test Scenarios, Functional Test Scripts, Bug Report, Code Review Report |
-| **Phase 4: Quality & Deploy** | PE, DSE | `/tas-security`, Pipeline/CLI | Security Report, Test Report, Production |
-
-### Phase Details
-
-#### Phase 1: Discovery
-- **PE**: Create PRD with `/tas-prd`, create design-spec with `/tas-design`
-- **SE**: Create SAD with `/tas-sad`, create ADR with `/tas-adr`
-
-#### Phase 2: Planning
-- **PE**: Breakdown Epic with `/tas-epic`, Feature with `/tas-feature`, Story with `/tas-story`
-
-#### Phase 3: Implementation
-- **SE**: Create Plan with `/tas-plan`, Implement with `/tas-dev`, Fix bug with `/tas-fix`
-- **SE**: Review code with `/tas-review`
-- **PE**: Create Functional Testing Spec with `/tas-functest`
-- **SE**: Create API Testing Script with `/tas-apitest`
-- **PE**: Create E2E Test Scenarios with `/tas-e2e`
-- **SE**: Create Functional Test Scripts with `/tas-functest-web`, `/tas-functest-mobile`
-- **PE**: Create E2E Test Scripts with `/tas-e2e-web`, `/tas-e2e-mobile`
-- **PE**: Create Bug Report with `/tas-bug`
-
-#### Phase 4: Quality & Deploy
-- **DSE**: Security Review with `/tas-security`
-- **PE**: Run Pipeline/CLI to execute Automation Tests
-- **DSE**: Deploy to Production
-
----
-
-## Quick Start
-
-```bash
-npx @torus-engineering/tas-kit install
-```
-
-### Options
-
-```bash
-npx @torus-engineering/tas-kit install --directory /path/to/my-project
-npx @torus-engineering/tas-kit install --yes    # skip confirmation prompts
-```
-
----
-
-## Important Setup
-
-### CLAUDE.md
-
-Most important configuration file — Claude reads this file first in every session.
-
-**Structure:**
-```markdown
-# Project Name
-
-## Tech Stack
-- Backend: .NET / Node.js / Python
-- Frontend: React / Next.js
-- Database: PostgreSQL / MySQL
-- Infrastructure: AWS / Azure
-
-## Conventions
-- Coding standards
-- Architecture patterns
-- Testing requirements
-```
-
-### tas.yaml
-
-Controls TAS Kit flow per project.
-
-**Structure:**
-```yaml
-project:
-  name: "My Project"
-  team: "Team Name"
-
-azure_devops:
-  enabled: true
-  organization: "org"
-  project: "project"
-
-flow:
-  mode: "greenfield"  # or "brownfield"
-  use_tdd: true
-  auto_review: true
-```
-
-### project-status.yaml
-
-Project status index — automatically updated after each artifact change.
-
-**Structure:**
-```yaml
-last_updated: 2025-01-15
-
-artifacts:
-  prd:
-    file: docs/prd.md
-    status: Approved
-    version: "1.0"
-
-epics:
-  Epic-001:
-    status: Active
-    features:
-      Feature-001:
-        stories:
-          Story-001:
-            status: In Progress
-```
-
-### .env
-
-Environment variables for Azure DevOps integration.
-
-```bash
-AZURE_DEVOPS_PAT=your_pat_here
-AZURE_DEVOPS_ORG=your_org
-AZURE_DEVOPS_PROJECT=your_project
-```
-
----
-
-## What gets installed
-
-```
-.claude/
-  commands/   22 slash commands (/tas-*, /ado-*)
-  skills/     3 auto-invoked skills
-  agents/     29 specialized subagents
-.tas/
-  templates/  Markdown templates (PRD, SAD, ADR, Epic, Feature, Story...)
-  rules/      Coding standards + workflow rules (code-review, story-done, security...)
-  tools/      ADO integration script (tas-ado.py)
-CLAUDE.md     Project context template (edit this for your project)
-tas.yaml      Flow configuration template (edit this for your project)
-.env.example  Environment variable template
-```
-
----
-
-## Commands Reference
-
-| Command | Description | Role |
-|---------|-------------|------|
-| `/tas-init` | Initialize TAS for new project | All |
-| `/tas-status` | Display current project status | All |
-| `/tas-prd` | Create/update Product Requirements Document | PE |
-| `/tas-sad` | Create/update Solution Architecture Document | SE |
-| `/tas-adr` | Create Architecture Decision Record | SE |
-| `/tas-design` | Create Design Specification | SE |
-| `/tas-epic` | Create/update Epic | SE |
-| `/tas-feature` | Create/update Feature | SE |
-| `/tas-story` | Create/update Story | SE |
-| `/tas-functest` | Create Functional Testing Specification | SE |
-| `/tas-spec` | Lightweight spec (solo / prototype) | SE |
-| `/tas-plan` | Create technical implementation plan | SE |
-| `/tas-dev` | Implement story (agentic) | AI |
-| `/tas-fix` | Quick fix without full story flow | SE |
-| `/tas-apitest` | Create API Testing Script automatically | SE |
-| `/tas-e2e` | Create E2E Test Scenarios | PE |
-| `/tas-functest-web` | Create Functional Test Script for Web | SE |
-| `/tas-functest-mobile` | Create Functional Test Script for Mobile | SE |
-| `/tas-e2e-web` | Create E2E Test Script for Web | PE |
-| `/tas-e2e-mobile` | Create E2E Test Script for Mobile | PE |
-| `/tas-bug` | Create Bug Report | PE |
-| `/tas-review` | Code Review with checklist | SE |
-| `/tas-brainstorm` | Brainstorm solutions | All |
-| `/tas-security` | Security Review | DSE |
-| `/ado-*` | Azure DevOps integration | All |
-
----
-
-## Requirements
-
-- Node.js 18+
-- [Claude Code](https://claude.ai/code)
-
----
-
-## Documentation
-
-See `.tas/README.md` after install for detailed documentation.

package/.tas/commands/tas-epic.md

@@ -1,35 +0,0 @@
-# /tas-epic $ARGUMENTS
-
-Role: PE - Product Engineer
-Create or update Epic document.
-
-## Prerequisite
-- docs/prd.md must exist
-
-## Actions
-1. Need context from root/tas.yaml and docs/prd.md
-2. Need context from .tas/templates/Epic.md
-3. Determine mode based on $ARGUMENTS:
-
-### CREATE mode ($ARGUMENTS is new Epic description, or no $ARGUMENTS):
-4. If no $ARGUMENTS, ask user for Epic description.
-5. Read project.code from root/tas.yaml. Scan docs/epics/ to determine sequence number.
-6. Create directory docs/epics/{code}-Epic-{NNN}-{slug}/
-7. Create file docs/epics/{code}-Epic-{NNN}-{slug}/{code}-Epic-{NNN}-{slug}.md
-8. Update `project-status.yaml` per `.tas/rules/common/project-status.md` — add entry to `epics`.
-
-### UPDATE mode ($ARGUMENTS is Epic ID, e.g., "Epic-001"):
-4. Find directory docs/epics/{code}-Epic-001-*/
-5. Need context from current Epic file
-6. Ask user what needs changing (update scope, add feature, change status...)
-7. Update file, add changelog
-8. Update `project-status.yaml` per `.tas/rules/common/project-status.md` — update `epics.{EPIC_ID}.status`.
-
-## Principles
-- Each Epic maps to one business capability in PRD
-- Epic does NOT contain technical details, only business value
-- Effort estimation at T-shirt size level: S/M/L/XL
-
-## Final Step — Token Log
-
-Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to working Epic file.

package/.tas/commands/tas-story.md

@@ -1,91 +0,0 @@
-# /tas-story $ARGUMENTS
-
-Role: PE - Product Engineer
-Create or update User Story document.
-
-**Scope:** Business logic, user experience, acceptance criteria, test cases.
-**Out of scope:** Technical implementation, files to modify, database schema — that's `/tas-plan`'s job.
-
-## Always / Ask / Never
-
-| | Action |
-|---|---|
-| **Always** | Write AC in Given/When/Then format |
-| **Always** | Set `plan_status: pending` for new Story |
-| **Ask** | When Story > 8h — suggest splitting |
-| **Never** | Read SAD, ADR — technical is `/tas-plan`'s job |
-
-## Prerequisite
-- At least one Feature must exist
-
-## Actions
-
-### CREATE mode ($ARGUMENTS is new Story description, or no $ARGUMENTS)
-
-**Step 1 — Identify Feature**
-- Read `project.code` from root/`tas.yaml`
-- Prioritize in order:
-  1. If `$ARGUMENTS` contains Feature ID → use it
-  2. If context has `parent_id` → use it
-  3. Ask user: "Which Feature does this Story belong to?" — no directory scan
-
-**Step 2 — Gather business context**
-- Read identified Feature file (get business context, scope, existing Stories list)
-- Read PRD (if exists) — only business requirements, user goals
-
-**Step 3 — Determine Story ID**
-- Read Stories section in Feature file → determine next index from that list
-- DO NOT scan directory
-
-**Step 4 — Draft Story with user**
-
-Discuss to fill in:
-
-a) **User Story**: "As a [role], I want [goal], so that [benefit]"
-
-b) **Business Requirements** (if any): specific business rules, stakeholder constraints
-
-c) **Design Notes** (if any): UI/UX specs, mockup links, flow diagrams
-
-d) **Prerequisites** (if any): other Stories that must be done first
-
-e) **Acceptance Criteria**: each AC is a clear Given/When/Then scenario
-
-**Step 5 — Test Case Prompting**
-
-After AC confirmed, ask more:
-- "Besides happy path, any edge cases to test?" (empty input, boundary values, concurrent)
-- "Any negative cases to cover?" (unauthorized, invalid data, timeout, not found)
-- "Any external dependencies to mock when testing?" (external APIs, database state)
-
-Write all to `## Unit Test Cases` section.
-
-**Step 6 — Create file**
-- Read `.tas/templates/Story.md` for format
-- Create `docs/epics/{code}-Epic-{NNN}-{slug}/{code}-Feature-{NNN}-{slug}/{code}-Story-{NNN}-{slug}.md`
-- Frontmatter: `plan_status: pending`, `plan_date:` left empty
-
-**Step 7 — Update project-status.yaml**
-Per `.tas/rules/common/project-status.md` — add entry to `epics.{EPIC_ID}.features.{FEATURE_ID}.stories`.
-
-**Step 8 — Notify next step**
-> "Story created. Before SE starts coding, run `/tas-plan {Story-ID}` for technical planning."
-
----
-
-### UPDATE mode ($ARGUMENTS is Story ID, e.g., "Story-005")
-
-1. Find file via glob `docs/epics/**/{code}-Story-{ID}-*.md`
-2. Read current Story file
-3. Ask user what needs changing (update AC, change status, add test cases, fix business rule...)
-4. Update file, add entry to Changelog
-5. Update `project-status.yaml` per `.tas/rules/common/project-status.md`.
-
-## Principles
-- Story must be small enough to complete in **4-8 hours**; if larger → split into multiple Stories
-- Story file = **product artifact**: describes *what* and *why*, not *how*
-- Story status: New → Committed → In Progress → Deploy Test → Verify Test → Deploy Stag → Verify Stag → Deploy Prod → Verify Prod → Done
-
-## Final Step — Token Log
-
-Follow `.tas/rules/common/token-logging.md`: write AI Usage Log to working Story file.

package/.tas/rules/common/story-done.md

@@ -1,30 +0,0 @@
-# Definition of Done
-
-Workflow gate used by `/tas-dev` Step 5 — verify each item before marking Story complete.
-
-## Code
-
-- [ ] Code implemented per acceptance criteria
-- [ ] Follows conventions in CLAUDE.md
-- [ ] Each public method has doc comment (XML doc / JSDoc / docstring)
-
-## Testing
-
-- [ ] Unit tests pass (happy path + edge cases + negative cases)
-- [ ] No regression on existing tests
-
-## Review
-
-- [ ] Code review passed (per `.tas/rules/common/code-review.md`)
-- [ ] If `auto_review = true`, passed automated review
-
-## Documentation
-
-- [ ] Technical notes in Story updated
-- [ ] If API changes, corresponding docs updated
-
-## Status
-
-- [ ] Story status updated in Story file
-- [ ] `project-status.yaml` updated
-- [ ] Commit message follows correct format

package/.tas/templates/Epic.md

@@ -1,46 +0,0 @@
----
-ado_id:
-ado_type: Epic
-ado_title: "{Title}"
-ado_state: New
-ado_assigned_to:
-ado_created:
-last_ado_sync:
----
-# Epic-{NNN}: {Title}
-
-> **Status:** New | Pending | In Design | In Progress | In Monitoring | In Closing | Done | Removed
-> **Owner:** {PE name}
-> **Created:** {Date}
-> **PRD Reference:** {link to PRD section}
-
-## Business Value
-{Business value description}
-
-## Scope
-### In Scope
-- Item 1
-- Item 2
-
-### Out of Scope
-- Item 1
-
-## Acceptance Criteria (High-level)
-- [ ] Criteria 1
-- [ ] Criteria 2
-
-## Features
-| ID | Feature | Priority | Estimate |
-|----|---------|----------|----------|
-| Feature-001 | {name} | Must | M |
-| Feature-002 | {name} | Should | L |
-
-## Dependencies
-- {dependency 1}
-
-## Risks
-- {risk 1}
-
-## Changelog
-| Date | Changes | Author |
-|------|---------|--------|

package/.tas/templates/Story.md

@@ -1,90 +0,0 @@
----
-ado_id:
-ado_type: User Story
-ado_title: "{Title}"
-ado_state: New
-ado_assigned_to:
-ado_created:
-last_ado_sync:
-parent_ado_id:
-plan_status: pending
-plan_date:
----
-# Story-{NNN}: {Title}
-
-> **Status:** New | Committed | In Progress | Deploy Test | Verify Test | Deploy Stag | Verify Stag | Deploy Prod | Verify Prod | Done
-> **Feature:** Feature-{NNN}
-> **Assigned to:** {SE name}
-> **Estimate:** {S/M/L}
-> **Created:** {Date}
-
-## User Story
-As a {role}, I want {goal}, so that {benefit}.
-
----
-## Business Requirements (if any)
-*(Special business requirements, business rules, constraints from stakeholders — add only when needed)*
-
----
-## Design Notes (if any)
-*(UI/UX specs, mockup links, design decisions, flow diagrams — add only when needed)*
-
----
-## Prerequisites (if any)
-*(Dependencies from other Stories or required conditions — add only when needed)*
-
----
-## Acceptance Criteria
-
-### AC-1: {title}
-- **Given** {precondition}
-- **When** {action}
-- **Then** {expected result}
-- **Functional Tests**: *(fill FT IDs after running `/tas-functest` — e.g.: `{PROJECT}_E{EPIC}_F{FEATURE}_S{STORY}_FT_001_H`, `FT_002_N`)*
-
-### AC-2: {title}
-- **Given** {precondition}
-- **When** {action}
-- **Then** {expected result}
-- **Functional Tests**: *(fill FT IDs after running `/tas-functest`)*
-
----
-## Unit Test Cases
-*(PE designs happy path + edge cases + negative cases. SE implements in code.)*
-
-### Happy Path
-| ID | AC Ref | Description | Input | Expected Output |
-|----|--------|-------------|-------|-----------------|
-| UT-1 | AC-1 | {description} | {input} | {expected} |
-
-### Edge Cases
-| ID | AC Ref | Description | Input | Expected Output |
-|----|--------|-------------|-------|-----------------|
-| UT-E1 | AC-1 | {description} | {input} | {expected} |
-
-### Negative Cases
-| ID | AC Ref | Description | Input | Expected Output |
-|----|--------|-------------|-------|-----------------|
-| UT-N1 | AC-1 | {description} | {input} | {expected} |
-
-### Dependencies to Mock
-- {external API, database state, third-party service...}
-
----
-<!-- ═══════════════════════════════════════════════════════════════════
-     TECHNICAL PLAN — generated by /tas-plan, do not edit manually
-     ═══════════════════════════════════════════════════════════════════ -->
-
----
-## Definition of Done
-- [ ] Technical plan completed (`/tas-plan`)
-- [ ] Code implemented
-- [ ] Unit tests pass
-- [ ] Code review passed
-- [ ] Acceptance criteria verified
-- [ ] No regression
-- [ ] Documentation updated (if needed)
-
-## Changelog
-| Date | Changes | Author |
-|------|---------|--------|