specweave 0.6.8 → 0.7.1

package/src/templates/AGENTS.md.template

@@ -44,7 +44,7 @@ This is a **SpecWeave project** where specifications and documentation are the s
 .claude/                     # Claude Code components (if using Claude)
 ├── agents/                  # Specialized roles (PM, Architect, DevOps, etc.)
 ├── skills/                  # Capabilities (increment-planner, context-loader, etc.)
-└── commands/                # Slash commands (/inc, /do, /done)
+└── commands/                # Slash commands (/specweave:increment, /specweave:do, /specweave:done)
 
 plugins/                     # Optional plugins (extended capabilities)
 └── specweave-{name}/
@@ -212,7 +212,7 @@ cat plugins/specweave-github/commands/github-sync.md
 ### What Are Commands?
 
 Commands are **executable workflows** defined as `.md` files in `plugins/specweave/commands/`. Each file contains:
-- Command name (from filename, e.g., `inc.md` → `/inc`)
+- Command name (from filename, e.g., `specweave-increment.md` → `/specweave:increment`)
 - Complete workflow instructions
 - Parameters and usage examples
 - Step-by-step execution guide
@@ -228,15 +228,15 @@ Commands are **executable workflows** defined as `.md` files in `plugins/specwea
 ls plugins/specweave/commands/
 
 # Common output:
-# inc.md          - Plan new increment (/inc "feature")
-# do.md           - Execute implementation (/do)
-# done.md         - Close increment (/done 0001)
-# validate.md     - Validate increment (/validate 0001)
-# progress.md     - Check status (/progress)
-# sync-docs.md    - Sync living docs (/sync-docs)
-# next.md         - Smart increment transition
-# costs.md        - Display AI cost dashboard
-# translate.md    - Translate content
+# specweave-increment.md  - Plan new increment (/specweave:increment "feature")
+# specweave-do.md         - Execute implementation (/specweave:do)
+# specweave-done.md       - Close increment (/specweave:done 0001)
+# specweave-validate.md   - Validate increment (/specweave:validate 0001)
+# specweave-progress.md   - Check status (/specweave:progress)
+# specweave-sync-docs.md  - Sync living docs (/specweave:sync-docs)
+# specweave-next.md       - Smart increment transition (/specweave:next)
+# specweave-costs.md      - Display AI cost dashboard (/specweave:costs)
+# specweave-translate.md  - Translate content (/specweave:translate)
 # tdd-*.md        - TDD workflow commands
 # ... (17 commands total)
 ```
@@ -256,18 +256,18 @@ ls plugins/specweave-github/commands/
 
 ### How to Execute Commands (Step-by-Step)
 
-**When user says**: "create new increment for user auth" or "run /inc user auth"
+**When user says**: "create new increment for user auth" or "run /specweave:increment user auth"
 
 **You should**:
 
 1. **Identify the command**:
-   - Keywords match: "create increment" → `inc.md`
-   - Explicit slash: "/inc" → `inc.md`
+   - Keywords match: "create increment" → `specweave-increment.md`
+   - Explicit slash: "/specweave:increment" → `specweave-increment.md`
    - Map request to command file
 
 2. **Read the command file**:
    ```bash
-   cat plugins/specweave/commands/inc.md
+   cat plugins/specweave/commands/specweave-increment.md
    ```
 
 3. **Parse the workflow**:
@@ -287,7 +287,7 @@ ls plugins/specweave-github/commands/
    - Show created files
    - Suggest next steps
 
-### Example: Executing /inc Command
+### Example: Executing /specweave:increment Command
 
 **User says**: "create new increment for user authentication"
 
@@ -295,13 +295,13 @@ ls plugins/specweave-github/commands/
 
 ```bash
 # Step 1: Identify command
-# "create increment" → inc.md
+# "create increment" → specweave-increment.md
 
 # Step 2: Read command file
-cat plugins/specweave/commands/inc.md
+cat plugins/specweave/commands/specweave-increment.md
 ```
 
-**After reading inc.md, you learn**:
+**After reading specweave-increment.md, you learn**:
 - This is PM-led increment planning
 - Requires: feature description
 - Creates: spec.md, plan.md, tasks.md, tests.md
@@ -355,7 +355,7 @@ cat plugins/specweave/commands/inc.md
 
 ✅ Increment 0001-user-authentication ready!
 
-Next: /do 0001 (execute implementation)
+Next: /specweave:do (execute implementation)
 ```
 
 **Step 5: Confirm completion**:
@@ -371,7 +371,7 @@ Files:
 
 Next steps:
   1. Review generated files
-  2. Run: /do 0001 (execute implementation)
+  2. Run: /specweave:do (execute implementation)
 ```
 
 ### Core Command Reference
@@ -380,21 +380,21 @@ Next steps:
 
 | Command | File | Purpose | Example |
 |---------|------|---------|---------|
-| `/inc` | `inc.md` | Plan new increment | `/inc "user auth"` |
-| `/do` | `do.md` | Execute implementation | `/do 0001` |
-| `/done` | `done.md` | Close increment | `/done 0001` |
-| `/validate` | `validate.md` | Validate quality | `/validate 0001` |
-| `/progress` | `progress.md` | Check status | `/progress` |
+| `/specweave:increment` | `specweave-increment.md` | Plan new increment | `/specweave:increment "user auth"` |
+| `/specweave:do` | `specweave-do.md` | Execute implementation | `/specweave:do` |
+| `/specweave:done` | `specweave-done.md` | Close increment | `/specweave:done 0001` |
+| `/specweave:validate` | `specweave-validate.md` | Validate quality | `/specweave:validate 0001` |
+| `/specweave:progress` | `specweave-progress.md` | Check status | `/specweave:progress` |
 
 **Specialized** (use when needed):
 
 | Command | File | Purpose | Example |
 |---------|------|---------|---------|
-| `/sync-docs` | `sync-docs.md` | Sync living docs | `/sync-docs update` |
-| `/next` | `next.md` | Smart increment transition | `/next` |
-| `/costs` | `costs.md` | AI cost dashboard | `/costs 0001` |
-| `/translate` | `translate.md` | Translate content | `/translate ru` |
-| `/tdd-cycle` | `tdd-cycle.md` | TDD workflow | `/tdd-cycle` |
+| `/specweave:sync-docs` | `specweave-sync-docs.md` | Sync living docs | `/specweave:sync-docs update` |
+| `/specweave:next` | `specweave-next.md` | Smart increment transition | `/specweave:next` |
+| `/specweave:costs` | `specweave-costs.md` | AI cost dashboard | `/specweave:costs 0001` |
+| `/specweave:translate` | `specweave-translate.md` | Translate content | `/specweave:translate ru` |
+| `/specweave:tdd-cycle` | `specweave-tdd-cycle.md` | TDD workflow | `/specweave:tdd-cycle` |
 
 **Plugin Commands** (when plugins installed):
 
@@ -402,6 +402,88 @@ Next steps:
 |---------|------|---------|--------|
 | `/github:sync` | `plugins/specweave-github/commands/github-sync.md` | Sync to GitHub | specweave-github |
 | `/github:create-issue` | `plugins/specweave-github/commands/github-create-issue.md` | Create GitHub issue | specweave-github |
+| `/sync-tasks` | `commands/sync-tasks.md` | Sync tasks.md status | specweave (core) |
+
+---
+
+### 🚨 CRITICAL: Task Completion Tracking
+
+**Problem**: Commands like `/progress`, `/validate`, `/done` rely on `tasks.md` status being accurate.
+If tasks.md shows "1/24 complete" but you've actually finished 24 tasks, everything breaks!
+
+**Solution**: Update `tasks.md` after EACH task completes.
+
+#### For Claude Code Users (Automatic ✅)
+
+**Good news**: This happens automatically via `post-task-completion.sh` hook!
+
+When you complete a task (mark todo as done), the hook:
+1. ✅ Detects completion
+2. ✅ Updates corresponding task in tasks.md
+3. ✅ Recalculates progress %
+4. ✅ Syncs to GitHub issue (if enabled)
+
+**You don't need to do anything manually!**
+
+#### For Other AI Tools (Manual ⚠️)
+
+**⚠️ IMPORTANT**: After completing EACH task, manually update tasks.md:
+
+**Step-by-Step**:
+
+```bash
+# Example: You just completed T-001
+
+# 1. Open tasks.md
+vim .specweave/increments/0007-feature-name/tasks.md
+
+# 2. Find the task you completed
+#### T-001: Implement authentication service
+
+# 3. Change status from pending to completed
+**Status**: [ ] pending
+# ↓ Change to ↓
+**Status**: [x] completed
+
+# 4. Update progress counters at the top
+**Completed**: 0  # ← Increment this (0 → 1)
+**Progress**: 0%  # ← Recalculate (1/24 = 4%)
+
+# 5. Save and commit
+git add .specweave/increments/0007-feature-name/tasks.md
+git commit -m "chore: mark T-001 as complete"
+```
+
+**Why This Matters**:
+- `/progress` shows accurate completion % ✅
+- `/validate` checks pass ✅
+- `/done` can close the increment ✅
+- Team knows real status ✅
+
+**Validation Check**:
+```bash
+# Verify tasks.md is in sync
+/sync-tasks --validate
+
+# If out of sync:
+/sync-tasks  # Auto-fix from GitHub or git history
+```
+
+**Quick Reference Card** (print and keep handy):
+
+```
+┌────────────────────────────────────────────────┐
+│  AFTER EACH TASK: Update tasks.md Status      │
+├────────────────────────────────────────────────┤
+│  1. Open: .specweave/increments/XXXX/tasks.md │
+│  2. Find: #### T-XXX                           │
+│  3. Change: [ ] pending → [x] completed        │
+│  4. Update: Completed count & Progress %       │
+│  5. Commit: git commit -m "chore: mark done"   │
+└────────────────────────────────────────────────┘
+```
+
+---
 
 ### Command Execution Pattern (Template)
 
@@ -1067,6 +1149,224 @@ Only **Claude Code** has automatic hooks that remind you to update docs.
 
 ---
 
+## 🔗 External Tracker Sync (CRITICAL FOR NON-CLAUDE TOOLS)
+
+**IMPORTANT**: Claude Code has automatic hooks that sync to external trackers (GitHub Issues, Jira, Azure DevOps) after each task completion. **GitHub Copilot, Cursor, and other tools DO NOT have these hooks!**
+
+### You MUST Manually Sync to External Trackers After Every Task
+
+When you complete ANY task, you MUST sync progress to external trackers if they are enabled for the project.
+
+#### Step 1: Detect Which Trackers Are Enabled
+
+Check the current increment's `metadata.json`:
+
+```bash
+# Find current increment (latest non-backlog increment)
+CURRENT_INCREMENT=$(ls -t .specweave/increments/ 2>/dev/null | grep -v "_backlog" | head -1)
+
+# Check metadata
+cat .specweave/increments/$CURRENT_INCREMENT/metadata.json
+```
+
+**Example metadata.json**:
+```json
+{
+  "id": "0007-smart-increment-discipline",
+  "title": "Increment Management v2.0",
+  "status": "active",
+  "github": {
+    "issue": 4,
+    "url": "https://github.com/anton-abyzov/specweave/issues/4"
+  },
+  "jira": {
+    "issue": "PROJ-123",
+    "url": "https://company.atlassian.net/browse/PROJ-123"
+  },
+  "ado": {
+    "item": 456,
+    "url": "https://dev.azure.com/org/project/_workitems/edit/456"
+  }
+}
+```
+
+#### Step 2: Sync to Each Enabled Tracker
+
+**For GitHub** (if `github.issue` exists):
+
+```bash
+# Get issue number
+GITHUB_ISSUE=$(jq -r '.github.issue' .specweave/increments/$CURRENT_INCREMENT/metadata.json)
+
+# Post progress comment
+gh issue comment "$GITHUB_ISSUE" --body "Progress update: Task T-XXX completed in increment $CURRENT_INCREMENT
+
+Details:
+- Task: [Task description]
+- Status: Completed
+- Timestamp: $(date -u +"%Y-%m-%dT%H:%M:%SZ")
+
+Next: [Next task or completion status]
+"
+```
+
+**For Jira** (if `jira.issue` exists):
+
+```bash
+# Get issue key
+JIRA_ISSUE=$(jq -r '.jira.issue' .specweave/increments/$CURRENT_INCREMENT/metadata.json)
+
+# Add comment (requires jira CLI: https://github.com/ankitpokhrel/jira-cli)
+jira issue comment add "$JIRA_ISSUE" "Progress update: Task T-XXX completed
+
+Details:
+- Task: [Task description]
+- Status: Completed
+- Increment: $CURRENT_INCREMENT
+"
+
+# Update status if task is major milestone
+# jira issue move "$JIRA_ISSUE" "In Progress" / "Review" / "Done"
+```
+
+**For Azure DevOps** (if `ado.item` exists):
+
+```bash
+# Get work item ID
+ADO_ITEM=$(jq -r '.ado.item' .specweave/increments/$CURRENT_INCREMENT/metadata.json)
+
+# Add comment (requires az CLI: https://aka.ms/azure-cli)
+az boards work-item update --id "$ADO_ITEM" --discussion "Progress update: Task T-XXX completed
+
+Details:
+- Task: [Task description]
+- Status: Completed
+- Increment: $CURRENT_INCREMENT
+"
+```
+
+#### Step 3: When to Sync
+
+**After EVERY task completion**, sync to all enabled trackers:
+
+```bash
+# Example workflow after completing T-003:
+
+# 1. Mark task complete in tasks.md
+vim .specweave/increments/0007-feature/tasks.md
+# Change: - [ ] T003: Task → - [x] T003: Task ✅
+
+# 2. Update increment documentation (plan.md, etc.)
+# [See "Documentation Updates" section above]
+
+# 3. Sync to external trackers
+gh issue comment 4 --body "✅ T-003 Complete: Create test-aware-planner structure
+
+Directory structure created at plugins/specweave/agents/test-aware-planner/
+
+Next: T-004 - Write test-aware-planner AGENT.md prompt
+"
+
+# 4. Continue to next task
+```
+
+#### Step 4: Update Task Checklist in GitHub/Jira
+
+**For GitHub Issues with task checklists**:
+
+The issue body likely contains a task checklist:
+
+```markdown
+## Tasks
+- [x] T-001: Update plan.md
+- [x] T-002: Add auto-sync hook
+- [ ] T-003: Create test-aware-planner structure
+- [ ] T-004: Write AGENT.md prompt
+```
+
+**Update the checklist** after each task:
+
+```bash
+# Get current issue body
+gh issue view 4 --json body -q .body > issue-body.md
+
+# Edit the checklist (mark T-003 as done)
+vim issue-body.md
+# Change: - [ ] T-003 → - [x] T-003
+
+# Update issue
+gh issue edit 4 --body-file issue-body.md
+```
+
+**For Jira** (subtasks):
+
+If tasks are represented as subtasks:
+
+```bash
+# List subtasks
+jira issue list --parent PROJ-123
+
+# Update subtask status
+jira issue move PROJ-123-SUB1 "Done"
+```
+
+#### Step 5: Sync Increment Status Changes
+
+When increment status changes (active → paused → completed), sync that too:
+
+```bash
+# Example: Increment completed
+gh issue comment 4 --body "🎉 INCREMENT COMPLETED!
+
+All 24 tasks finished. Increment 0007-smart-increment-discipline is now complete.
+
+See completion report: .specweave/increments/0007-smart-increment-discipline/reports/COMPLETION-SUMMARY.md
+"
+
+# Close the issue
+gh issue close 4 --comment "Increment completed and merged to main branch."
+```
+
+### Why This Matters
+
+**Without external tracker sync**:
+- ❌ Stakeholders don't see progress
+- ❌ Team members work in isolation
+- ❌ No audit trail of work done
+- ❌ GitHub/Jira becomes stale and useless
+
+**With external tracker sync**:
+- ✅ Real-time visibility into progress
+- ✅ Team stays informed
+- ✅ Stakeholders can track without asking
+- ✅ Complete audit trail
+- ✅ GitHub/Jira remains the source of truth
+
+### Tools That Need Manual Sync
+
+These tools **DO NOT** have automatic external tracker sync:
+- GitHub Copilot (all versions)
+- Cursor
+- Windsurf
+- Gemini CLI
+- Generic AI tools (ChatGPT, Claude web, etc.)
+
+Only **Claude Code** has automatic hooks (via `post-task-completion.sh`) that sync to external trackers.
+
+### Summary Checklist (After Every Task)
+
+When you complete a task in non-Claude tools:
+
+1. ✅ Mark task complete in tasks.md
+2. ✅ Update living docs (see "Documentation Updates" section)
+3. ✅ **Sync to GitHub/Jira/ADO** (this section)
+4. ✅ Update RFC if applicable (if task implements architecture decision)
+5. ✅ Continue to next task
+
+**Remember**: In Claude Code, steps 3-4 happen automatically via hooks. In other tools, YOU must do them manually!
+
+---
+
 ## Security Considerations
 
 - Never commit secrets (use `.env` files, gitignored)

package/src/templates/CLAUDE.md.template

@@ -330,6 +330,29 @@ Plugins are detected and suggested during `specweave init` based on:
 
 ---
 
+## Frequently Asked Questions
+
+**New to SpecWeave?** Check out the [FAQ](https://spec-weave.com/docs/faq) for answers to common questions:
+
+### Quick Answers
+- **Why specs in two locations?** Living Docs (permanent, complete feature) vs Increment Specs (temporary, current work)
+- **When do I need living docs spec?** Major features (3+ increments), brownfield integration, or external PM tools
+- **Can I delete increment specs?** YES, after completion. Living docs specs are NEVER deleted (permanent)
+- **Which spec is source of truth?** Living docs spec (when it exists), otherwise increment spec
+
+### Key Topics Covered
+- ✅ Two-spec architecture explained
+- ✅ When to create living docs specs
+- ✅ Increment spec lifecycle
+- ✅ Brownfield documentation linking
+- ✅ External PM tool integration (Jira, ADO, GitHub)
+- ✅ Small vs large feature decisions
+- ✅ Project structure and organization
+
+**[View Complete FAQ →](https://spec-weave.com/docs/faq)**
+
+---
+
 ## Testing
 
 **Four Levels**:
@@ -351,29 +374,21 @@ Plugins are detected and suggested during `specweave init` based on:
 
 | User Says | Use Command | What It Does |
 |-----------|-------------|--------------|
-| "Let's build [feature]" | `/inc "[feature]"` | Plan new increment |
-| "Start implementing" | `/do` | Execute tasks (smart resume) |
-| "What's the status?" | `/progress` | Show task completion % |
-| "Is this ready?" | `/validate 0001` | Validate increment quality |
-| "We're done" | `/done 0001` | Close increment |
+| "Let's build [feature]" | `/specweave:increment "[feature]"` | Plan new increment |
+| "Start implementing" | `/specweave:do` | Execute tasks (smart resume) |
+| "What's the status?" | `/specweave:progress` | Show task completion % |
+| "Is this ready?" | `/specweave:validate 0001` | Validate increment quality |
+| "We're done" | `/specweave:done 0001` | Close increment |
 
 **Plugin Commands** (when installed):
 | "Sync to GitHub" | `/specweave:github:sync` | Export to GitHub issues |
 | "Sync to Jira" | `/specweave:jira:sync` | Export to Jira |
 
-### Command Aliases
-
-- `/inc` = `/specweave inc` = `/specweave:inc`
-- `/do` = `/specweave do` = `/specweave:do`
-- `/validate` = `/specweave validate` = `/specweave:validate`
-- `/done` = `/specweave done` = `/specweave:done`
-- `/progress` = `/specweave progress` = `/specweave:progress`
-
 ---
 
 ## Key SpecWeave Principles
 
-1. **Specification-First**: Always start with `/inc` to create specs before coding
+1. **Specification-First**: Always start with `/specweave:increment` to create specs before coding
 2. **Documentation = Source of Truth**: Specs guide implementation, not the reverse
 3. **Incremental**: Work in small, measurable increments
 4. **Validated**: Every increment validated before closure
@@ -394,19 +409,19 @@ Plugins are detected and suggested during `specweave init` based on:
 
 **Create your first feature**:
 ```bash
-/inc "your feature description"
+/specweave:increment "your feature description"
 ```
 
 **Typical Workflow**:
-1. `/inc "feature"` → SpecWeave creates specs
+1. `/specweave:increment "feature"` → SpecWeave creates specs
 2. Review specs (spec.md, plan.md, tasks.md)
-3. `/do` → Claude implements the code
-4. `/progress` → Check status anytime
-5. `/validate 0001` → Validate quality (optional)
-6. `/done 0001` → Close when complete
+3. `/specweave:do` → Claude implements the code
+4. `/specweave:progress` → Check status anytime
+5. `/specweave:validate 0001` → Validate quality (optional)
+6. `/specweave:done 0001` → Close when complete
 
 **Remember**:
-- Type `/inc` first, THEN implement
+- Type `/specweave:increment` first, THEN implement
 - Keep root clean (use increment folders)
 - All agents/skills activate automatically
 

package/src/templates/COMPLETION-REPORT.template.md

@@ -0,0 +1,128 @@
+# Increment {{ID}}: {{TITLE}}
+
+**Status**: {{STATUS}}
+**Type**: {{TYPE}}
+**Created**: {{CREATED_DATE}}
+**Completed**: {{COMPLETED_DATE}}
+
+---
+
+## Original Scope (Planned)
+
+### User Stories
+
+{{ORIGINAL_USER_STORIES}}
+
+### Tasks
+
+{{ORIGINAL_TASKS}}
+
+**Estimated Effort**: {{ESTIMATED_HOURS}} hours
+
+---
+
+## Scope Evolution (Living Updates)
+
+_This section is updated during the increment whenever scope changes occur._
+
+{{#SCOPE_CHANGES}}
+### {{CHANGE_DATE}}: {{CHANGE_TITLE}}
+
+**Changed**: {{WHAT_CHANGED}}
+**Reason**: {{WHY_CHANGED}}
+**Impact**: {{IMPACT_HOURS}} hours ({{IMPACT_DIRECTION}})
+**Decision**: {{WHO_APPROVED}}
+**Documentation**: {{DOCUMENTATION_LINKS}}
+
+---
+{{/SCOPE_CHANGES}}
+
+{{#IF_NO_CHANGES}}
+_No scope changes during this increment._
+{{/IF_NO_CHANGES}}
+
+---
+
+## Final Delivery
+
+### Completed User Stories
+
+{{COMPLETED_USER_STORIES}}
+
+### Deferred User Stories
+
+{{DEFERRED_USER_STORIES}}
+
+### Added User Stories
+
+{{ADDED_USER_STORIES}}
+
+**Delivered**: {{DELIVERED_COUNT}} user stories ({{PLANNED_COUNT}} originally planned, {{ADDED_COUNT}} added, {{DEFERRED_COUNT}} deferred)
+**Actual Effort**: {{ACTUAL_HOURS}} hours (vs {{ESTIMATED_HOURS}} estimated)
+
+---
+
+## What Changed and Why
+
+### Deferrals
+
+{{#DEFERRALS}}
+- **{{DEFERRED_ITEM}}**: {{DEFERRAL_REASON}}
+  - Business value: {{BUSINESS_VALUE_ASSESSMENT}}
+  - Can be added later: {{CAN_ADD_LATER}}
+{{/DEFERRALS}}
+
+### Additions
+
+{{#ADDITIONS}}
+- **{{ADDED_ITEM}}**: {{ADDITION_REASON}}
+  - Stakeholder: {{STAKEHOLDER}}
+  - Scope approved by: {{APPROVER}}
+{{/ADDITIONS}}
+
+### Technical Pivots
+
+{{#TECHNICAL_PIVOTS}}
+- **{{PIVOT_DESCRIPTION}}**: {{PIVOT_DECISION}}
+  - Documented in: {{ADR_LINK}}
+  - Impact: {{PIVOT_IMPACT}}
+{{/TECHNICAL_PIVOTS}}
+
+---
+
+## Lessons Learned
+
+{{#LESSONS}}
+1. **{{LESSON_TITLE}}**: {{LESSON_DESCRIPTION}}
+{{/LESSONS}}
+
+---
+
+## Metrics
+
+- **Velocity**: {{ACTUAL_HOURS}} hours / {{DAYS_TAKEN}} days = {{HOURS_PER_DAY}} hours/day
+- **Scope creep**: {{SCOPE_CREEP_ANALYSIS}}
+- **Test coverage**: {{TEST_COVERAGE}}% (target: 80%)
+- **Defects found**: {{DEFECTS_COUNT}} ({{CRITICAL_COUNT}} critical, {{MINOR_COUNT}} minor)
+
+---
+
+## Related Documentation
+
+{{#RELATED_DOCS}}
+- {{DOC_TYPE}}: [{{DOC_TITLE}}]({{DOC_LINK}})
+{{/RELATED_DOCS}}
+
+---
+
+**Report Version**: v{{REPORT_VERSION}} (updated {{UPDATE_COUNT}} times during increment)
+**Last Updated**: {{LAST_UPDATED}}
+**Updated By**: {{UPDATED_BY}}
+
+---
+
+## Update History
+
+{{#UPDATE_HISTORY}}
+- v{{VERSION}}: {{UPDATE_DATE}} - {{UPDATE_DESCRIPTION}}
+{{/UPDATE_HISTORY}}