create-sdd-project 0.2.4 → 0.3.0

package/template/.claude/skills/project-memory/SKILL.md

@@ -7,7 +7,7 @@ description: "Set up and maintain a structured project memory system in docs/pro
 
 ## Overview
 
-Maintain institutional knowledge for projects by establishing a structured memory system in `docs/project_notes/`. This skill sets up three key memory files (bugs, decisions, key facts) plus sprint trackers, and configures the main AI instruction file to automatically reference and maintain them.
+Maintain institutional knowledge for projects by establishing a structured memory system in `docs/project_notes/`. This skill sets up three key memory files (bugs, decisions, key facts) plus the product tracker, and configures the main AI instruction file to automatically reference and maintain them.
 
 ## When to Use This Skill
 
@@ -32,14 +32,14 @@ docs/
     ├── bugs.md              # Bug log with solutions
     ├── decisions.md         # Architectural Decision Records
     ├── key_facts.md         # Project configuration and constants
-    └── sprint-X-tracker.md  # Sprint progress, active task, completion log
+    └── product-tracker.md   # Feature backlog, active session, completion log
 ```
 
 **Initial file content:** Copy templates from the `references/` directory in this skill:
 - Use `references/bugs_template.md` for initial `bugs.md`
 - Use `references/decisions_template.md` for initial `decisions.md`
 - Use `references/key_facts_template.md` for initial `key_facts.md`
-- Sprint tracker is created using the development-workflow skill
+- Product tracker is created using the development-workflow skill
 
 ### 2. Configure AI Instruction File - Memory-Aware Behavior
 
@@ -51,7 +51,7 @@ Add or update a "Project Memory System" section in the project's main AI instruc
 This project maintains institutional knowledge in `docs/project_notes/`.
 
 ### Memory Files
-- **sprint-X-tracker.md** - Sprint progress, active task, completion log
+- **product-tracker.md** - Feature backlog, active session, completion log
 - **bugs.md** - Bug log with dates, solutions, and prevention notes
 - **decisions.md** - Architectural Decision Records (ADRs)
 - **key_facts.md** - Project configuration, ports, important URLs
@@ -68,7 +68,7 @@ This project maintains institutional knowledge in `docs/project_notes/`.
 - Check `docs/project_notes/key_facts.md`
 
 **When completing work:**
-- Update sprint tracker and add to Completion Log
+- Update product tracker and add to Completion Log
 ```
 
 ### 3. Searching Memory Files
@@ -116,7 +116,7 @@ When encountering problems or making decisions, proactively search memory files:
 
 - User is responsible for manual cleanup
 - Remove very old bug entries (6+ months) that are no longer relevant
-- Archive old sprint trackers
+- Review and clean up completed features in product tracker
 - Keep all decisions (they provide historical context)
 - Update key_facts.md when project configuration changes
 
@@ -126,7 +126,7 @@ When encountering problems or making decisions, proactively search memory files:
 - **references/decisions_template.md** - ADR format with examples
 - **references/key_facts_template.md** - Key facts organization with examples
 
-Sprint trackers are created using the development-workflow skill.
+Product tracker is created using the development-workflow skill.
 
 ## Tips for Effective Memory Management
 
@@ -138,7 +138,7 @@ Sprint trackers are created using the development-workflow skill.
 
 ## Integration with Other Skills
 
-- **development-workflow**: Updates sprint tracker and memory files during task execution
+- **development-workflow**: Updates product tracker and memory files during task execution
 - **bug-workflow**: Documents bugs and solutions in bugs.md
 
 ## Success Criteria
@@ -146,7 +146,7 @@ Sprint trackers are created using the development-workflow skill.
 This skill is successfully deployed when:
 
 - `docs/project_notes/` directory exists with memory files
-- Sprint tracker exists for active sprint
+- Product tracker exists with feature backlog
 - AI instruction file includes "Project Memory System" section
 - Memory files follow template format
 - AI assistant checks memory files before proposing changes

package/template/.gemini/agents/backend-developer.md

@@ -28,4 +28,4 @@ Implement the task following the Implementation Plan in the ticket. Use strict T
 - ALWAYS use explicit types (no `any`)
 - ALWAYS handle errors with domain error classes
 - NEVER modify code outside the scope of the current ticket
-- ALWAYS verify implementation matches the approved spec. If deviation needed, document in sprint tracker's Active Session and ask for approval
+- ALWAYS verify implementation matches the approved spec. If deviation needed, document in product tracker's Active Session and ask for approval

package/template/.gemini/agents/frontend-developer.md

@@ -28,4 +28,4 @@ Implement the task following the Implementation Plan in the ticket. Use strict T
 - ALWAYS use `'use client'` for components with hooks
 - ALWAYS handle loading and error states
 - NEVER modify code outside the scope of the current ticket
-- ALWAYS verify implementation matches the approved spec. If deviation needed, document in sprint tracker's Active Session and ask for approval
+- ALWAYS verify implementation matches the approved spec. If deviation needed, document in product tracker's Active Session and ask for approval

package/template/.gemini/commands/add-feature.toml

@@ -0,0 +1,2 @@
+description = "Add a new feature to the product tracker (e.g., /add-feature User authentication)"
+prompt = "Add feature '{{args}}' to the product tracker. Follow the add-feature template in .gemini/skills/development-workflow/references/add-feature-template.md"

package/template/.gemini/commands/next-task.toml

@@ -1,2 +1,2 @@
-description = "Start the next pending task in the current sprint"
-prompt = "Read the sprint tracker in docs/project_notes/ and start the next pending task. Follow the development-workflow skill in .gemini/skills/development-workflow/SKILL.md"
+description = "Start the next pending feature from the product tracker"
+prompt = "Read the product tracker in docs/project_notes/ and start the next pending feature. Follow the development-workflow skill in .gemini/skills/development-workflow/SKILL.md"

package/template/.gemini/commands/show-progress.toml

@@ -1,2 +1,2 @@
-description = "Show current sprint progress and active task status"
-prompt = "Read the sprint tracker in docs/project_notes/ and show: current sprint progress (% complete), active task and step, and list of pending tasks."
+description = "Show current progress and active feature status"
+prompt = "Read the product tracker in docs/project_notes/ and show: current progress (features done vs total), active feature and step, and list of pending features."

package/template/.gemini/commands/start-task.toml

@@ -1,2 +1,2 @@
-description = "Start working on a specific task (e.g., /start-task B0.1)"
+description = "Start working on a specific feature (e.g., /start-task F001)"
 prompt = "Start task {{args}}. Follow the development-workflow skill in .gemini/skills/development-workflow/SKILL.md"

package/template/.gemini/skills/bug-workflow/SKILL.md

@@ -23,7 +23,7 @@ description: "Handles bug discovery, triage, investigation, and resolution. Invo
 |----------|----------|------|
 | Critical | Immediate (<1h) | **C: Hotfix** — Confirm → Branch from main → Minimal fix → Test → Deploy → Document → Post-mortem |
 | High | Same day | **B: Standard** — Triage → Branch → Investigate → Fix (TDD) → Validate → Document → PR |
-| Medium | Within sprint | **A: Quick** — Triage → Investigate → Fix → Test → Document → Commit |
+| Medium | Within cycle | **A: Quick** — Triage → Investigate → Fix → Test → Document → Commit |
 | Low | Backlog | **A: Quick** or escalate to backlog |
 
 **Escalate to `development-workflow`** when: >1 day work, architectural changes needed, or significant refactoring required.
@@ -60,7 +60,7 @@ Find root cause, not symptoms. Techniques: git bisect, layer isolation (Frontend
 
 ## Step 5: Validate
 
-Follow `production-code-validator` instructions in `.gemini/agents/`. Ensure no debug code, proper error handling.
+Run `production-code-validator`. Ensure no debug code, proper error handling.
 
 ## Step 6: Document in bugs.md
 
@@ -78,7 +78,7 @@ Follow `production-code-validator` instructions in `.gemini/agents/`. Ensure no
 
 ## Step 7: Commit/PR
 
-**Commit format:** `fix(<area>): <description>` + body (bug, root cause, fix)
+**Commit format:** `fix(<area>): <description>` + body (bug, root cause, fix) + `Co-Authored-By: Claude <noreply@anthropic.com>`
 
 **Hotfix PR:** `--base main` always. After merge in GitFlow: merge main back to develop. Tag: `vX.Y.Z+1`.
 
@@ -99,7 +99,7 @@ Follow `production-code-validator` instructions in `.gemini/agents/`. Ensure no
 
 | File | When |
 |------|------|
-| `sprint-X-tracker.md` | Bug being worked on (Active Session) |
+| `product-tracker.md` | Bug being worked on (Active Session) |
 | `bugs.md` | Always |
 | `decisions.md` | If architectural decision made |
 

package/template/.gemini/skills/development-workflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: development-workflow
-description: "Orchestrates the complete development workflow for each task. Invoke with: 'start task B0.1', 'show sprint progress', 'next task', or 'init sprint N'."
+description: "Orchestrates the complete development workflow for each feature. Invoke with: 'start task F001', 'show progress', 'next task', or 'add feature'."
 ---
 
 # Development Workflow Skill
@@ -8,7 +8,7 @@ description: "Orchestrates the complete development workflow for each task. Invo
 ## Quick Reference
 
 0. **Spec** — `spec-creator` drafts/updates specs → SPEC APPROVAL (Std/Cplx)
-1. **Setup** — Branch, ticket, sprint tracker → TICKET APPROVAL (Std/Cplx)
+1. **Setup** — Branch, ticket, product tracker → TICKET APPROVAL (Std/Cplx)
 2. **Plan** — Planner agent writes implementation plan → PLAN APPROVAL (Std/Cplx)
 3. **Implement** — Developer agent, TDD, real-time spec sync
 4. **Finalize** — Tests/lint/build, `production-code-validator` → COMMIT APPROVAL
@@ -19,19 +19,19 @@ description: "Orchestrates the complete development workflow for each task. Invo
 
 ## Commands
 
-- `start task B0.1` — Begin working on a specific task
-- `next task` — Start the next pending task in current sprint
-- `show sprint progress` — View sprint completion status
-- `init sprint N` — Initialize a new sprint tracker
+- `start task F001` — Begin working on a specific feature
+- `next task` — Start the next pending feature from product tracker
+- `show progress` — View feature completion status
+- `add feature "description"` — Add a new feature to the product tracker
 
 ---
 
 ## On Skill Start
 
-1. Read the sprint tracker (`docs/project_notes/sprint-X-tracker.md`) → **Active Session** section for context recovery
+1. Read the product tracker (`docs/project_notes/product-tracker.md`) → **Active Session** section for context recovery
 2. Read `GEMINI.md` → **Autonomy Level**
 3. Read `docs/project_notes/key_facts.md` → **Branching Strategy**
-4. If resuming an active task → continue from the step recorded in the tracker's Active Session
+4. If resuming an active feature → continue from the step recorded in the tracker's Active Session
 
 ---
 
@@ -47,7 +47,7 @@ Read the **Autonomy Level** from `GEMINI.md`.
 | Commit Approval (Step 4) | Required | Auto | Auto | Auto |
 | Merge Approval (Step 5) | Required | Required | Required | Auto |
 
-- **Auto** = proceed without asking; log in sprint tracker → "Auto-Approved Decisions" table
+- **Auto** = proceed without asking; log in product tracker → "Auto-Approved Decisions" table
 - **Required** = ask user explicitly; do NOT continue without approval
 - **Quality gates always run** regardless of level (tests, lint, build, validators)
 
@@ -83,11 +83,11 @@ Ask user to classify complexity before starting. See `references/complexity-guid
 
 See `references/branching-strategy.md` for details.
 
-1. Verify sprint tracker exists, no active task, dependencies met
-2. Create feature branch: `feature/sprint<N>-<task-id>-<short-description>`
+1. Verify product tracker exists, no active feature, dependencies met
+2. Create feature branch: `feature/<feature-id>-<short-description>`
 3. **Std/Cplx:** Generate ticket from `references/ticket-template.md` → fill `## Spec` section
 4. **Complex:** Also review `decisions.md` for related ADRs
-5. Update sprint tracker → Active Session: task, step `1/6 (Setup)`, branch, complexity
+5. Update product tracker → Active Session: feature, step `1/6 (Setup)`, branch, complexity
 
 **→ CHECKPOINT: Ticket Approval** (Std/Cplx only — Simple skips to Step 3)
 
@@ -95,7 +95,7 @@ See `references/branching-strategy.md` for details.
 
 ## Step 2: Plan (Standard/Complex only)
 
-1. Follow the planner agent instructions (`backend-planner` for B*.*, `frontend-planner` for F*.*) in `.gemini/agents/`
+1. Follow the planner agent instructions (`backend-planner` for backend features, `frontend-planner` for frontend features) in `.gemini/agents/`
 2. Write Implementation Plan into ticket's `## Implementation Plan`
 3. Update tracker: step `2/6 (Plan)`
 
@@ -115,7 +115,7 @@ See `references/branching-strategy.md` for details.
 - UI components → `docs/specs/ui-components.md` (MANDATORY)
 - Env variables → `.env.example` | ADRs → `decisions.md`
 
-**Spec deviation** → document in sprint tracker Active Session and ask for approval.
+**Spec deviation** → document in product tracker Active Session and ask for approval.
 
 Update tracker: step `3/6 (Implement)`, context summary.
 
@@ -154,7 +154,7 @@ Update tracker: step `5/6 (Review)`
 ## Step 6: Complete
 
 1. Delete feature branch (local + remote)
-2. Update sprint tracker: task → Completed, add to Completion Log, update progress %
+2. Update product tracker: feature → done, add to Completion Log, update progress
 3. Record bugs in `bugs.md`, decisions in `decisions.md`
 4. Clear Active Session → "No active work"
 
@@ -179,18 +179,18 @@ Agent instructions are in `.gemini/agents/`. Read the relevant agent file when e
 - `references/ticket-template.md` — Ticket format
 - `references/pr-template.md` — PR template
 - `references/branching-strategy.md` — Branching guide
-- `references/sprint-init-template.md` — New sprint initialization
+- `references/add-feature-template.md` — Add feature to tracker
 - `references/complexity-guide.md` — Complexity classification
 - `references/workflow-example.md` — Full worked example
 - `references/failure-handling.md` — Recovery & rollbacks
 
 ## Constraints
 
-- **One task at a time** — never start a new task before completing current
+- **One feature at a time** — never start a new feature before completing current
 - **TDD mandatory** — all code needs tests
 - **Type safety** — fully typed, no `any`
 - **English only** — all technical artifacts
 - **Memory first** — check `project_notes/` before changes
-- **Sprint tracker** — keep Active Session updated at every step
+- **Product tracker** — keep Active Session updated at every step
 - **Correct agents** — Backend → `backend-planner` + `backend-developer`, Frontend → `frontend-planner` + `frontend-developer`
 - **Correct base branch** — check `key_facts.md` before creating branches

package/template/.gemini/skills/development-workflow/references/add-feature-template.md

@@ -0,0 +1,16 @@
+# Add Feature Template
+
+Use this template when running `add feature "description"`.
+
+## How to Add a Feature
+
+1. Read the product tracker (`docs/project_notes/product-tracker.md`)
+2. Determine the next feature ID (F001, F002, ...)
+3. Add a row to the Features table
+4. Use `start task F001` to begin working on it
+
+## Feature ID Convention
+
+- **Format:** F001, F002, F003... (sequential)
+- **Type:** backend, frontend, fullstack, infra
+- **Branch:** `feature/<id>-<short-desc>` (e.g., `feature/F001-external-api`)

package/template/.gemini/skills/development-workflow/references/branching-strategy.md

@@ -11,7 +11,7 @@ main ────●────●────●────●────●
           \  /      \  /
            \/        \/
         feature/   feature/
-        B1.1       B1.2
+        F001       F002
                          tag: v0.1.0
 ```
 

package/template/.gemini/skills/development-workflow/references/complexity-guide.md

@@ -19,23 +19,23 @@ Before starting any task, ask the user to classify its complexity using **contex
 
 ## Examples
 
-**Example 1 - Task might be already done:**
+**Example 1 - Feature might overlap with existing work:**
 ```
-What complexity level for B1.5 (Implement refresh token rotation)?
+What complexity level for F003 (Implement refresh token rotation)?
 
 1. Simple (Recommended)
-   Verify existing implementation in B1.3, add tests if missing
+   Verify existing implementation in F001, add tests if missing
 
 2. Standard
    Add additional rotation logic or edge cases
 
-3. Skip B1.5
-   Already done in B1.3, move to B1.6 (auth controller)
+3. Skip F003
+   Already done in F001, move to F004 (auth controller)
 ```
 
 **Example 2 - Standard new feature:**
 ```
-What complexity level for B1.4 (Create auth middleware)?
+What complexity level for F002 (Create auth middleware)?
 
 1. Simple
    Straightforward middleware, minimal logic

package/template/.gemini/skills/development-workflow/references/failure-handling.md

@@ -68,14 +68,14 @@
 
 **Recovery:**
 1. **Identify** the blocking task/resource
-2. **Document** the block in sprint tracker "Active Task" section
+2. **Document** the block in product tracker "Active Session" section
 3. **Options:**
    - Wait for blocker to resolve
    - Switch to different task
    - Create mock/stub to continue
 
-**Update sprint tracker:**
-- Change task status to Blocked
+**Update product tracker:**
+- Change feature status to Blocked
 
 ---
 

package/template/.gemini/skills/development-workflow/references/pr-template.md

@@ -14,10 +14,10 @@ gh pr create --base main --title "<type>(<scope>): <description>" --body "$(cat
 
 [One paragraph: what this PR does and why]
 
-## Task Reference
+## Feature Reference
 
-- **Task:** [B0.1] | **Sprint:** [0]
-- **Ticket:** [docs/tickets/task-id.md]
+- **Feature:** [F001]
+- **Ticket:** [docs/tickets/feature-id.md]
 
 ## Changes
 

package/template/.gemini/skills/development-workflow/references/ticket-template.md

@@ -1,7 +1,7 @@
-# [TASK-ID]: [Task Title]
+# [FEATURE-ID]: [Feature Title]
 
-**Sprint:** [N] | **Type:** [Backend/Frontend]-[Feature/Bugfix/Refactor] | **Priority:** [High/Medium/Low]
-**Status:** In Progress | **Branch:** feature/sprint[N]-[TASK-ID]-[short-description]
+**Feature:** [ID] | **Type:** [Backend/Frontend/Fullstack]-[Feature/Bugfix/Refactor] | **Priority:** [High/Medium/Low]
+**Status:** In Progress | **Branch:** feature/[FEATURE-ID]-[short-description]
 **Created:** [YYYY-MM-DD] | **Dependencies:** [List or "None"]
 
 ---

package/template/.gemini/skills/development-workflow/references/workflow-example.md

@@ -1,8 +1,8 @@
-# Workflow Example: Task B0.1 (Simple, L2 Trusted, github-flow)
+# Workflow Example: Feature F001 (Simple, L2 Trusted, github-flow)
 
 ## On Skill Start
 
-1. Read sprint tracker → Active Session → No active task
+1. Read product tracker → Active Session → No active feature
 2. `CLAUDE.md` → Autonomy Level 2 (Trusted)
 3. `key_facts.md` → branching: github-flow (base: `main`)
 
@@ -12,10 +12,10 @@
 
 ```bash
 git checkout main && git pull
-git checkout -b feature/sprint0-B0.1-express-setup
+git checkout -b feature/F001-express-setup
 ```
 
-Update sprint tracker → Active Session: B0.1, step `1/6`, branch, complexity: Simple.
+Update product tracker → Active Session: F001, step `1/6`, branch, complexity: Simple.
 
 ## Step 2: Plan — Skipped (Simple task)
 
@@ -72,7 +72,7 @@ git commit -m "feat(backend): initialize Express + TypeScript project
 ## Step 5: Review
 
 ```bash
-git push -u origin feature/sprint0-B0.1-express-setup
+git push -u origin feature/F001-express-setup
 gh pr create --base main --title "feat(backend): initialize Express + TypeScript project" --body "..."
 gh pr merge --squash
 ```
@@ -81,7 +81,7 @@ gh pr merge --squash
 
 ```bash
 git checkout main && git pull
-git branch -d feature/sprint0-B0.1-express-setup
+git branch -d feature/F001-express-setup
 ```
 
-Update sprint tracker: B0.1 → Completed, add to Completion Log, clear Active Session.
+Update product tracker: F001 → done, add to Completion Log, clear Active Session.

package/template/.gemini/skills/project-memory/SKILL.md

@@ -7,7 +7,7 @@ description: "Set up and maintain a structured project memory system in docs/pro
 
 ## Overview
 
-Maintain institutional knowledge for projects by establishing a structured memory system in `docs/project_notes/`. This skill sets up three key memory files (bugs, decisions, key facts) plus sprint trackers, and ensures the AI assistant automatically references and maintains them.
+Maintain institutional knowledge for projects by establishing a structured memory system in `docs/project_notes/`. This skill sets up three key memory files (bugs, decisions, key facts) plus the product tracker, and ensures the AI assistant automatically references and maintains them.
 
 ## When to Use This Skill
 
@@ -32,14 +32,14 @@ docs/
     ├── bugs.md              # Bug log with solutions
     ├── decisions.md         # Architectural Decision Records
     ├── key_facts.md         # Project configuration and constants
-    └── sprint-X-tracker.md  # Sprint progress, active task, completion log
+    └── product-tracker.md   # Feature backlog, active session, completion log
 ```
 
 **Initial file content:** Copy templates from the `references/` directory in this skill:
 - Use `references/bugs_template.md` for initial `bugs.md`
 - Use `references/decisions_template.md` for initial `decisions.md`
 - Use `references/key_facts_template.md` for initial `key_facts.md`
-- Sprint tracker is created using the development-workflow skill
+- Product tracker is created using the development-workflow skill
 
 ### 2. Memory-Aware Behavior
 
@@ -55,7 +55,7 @@ The following protocols should be followed at all times:
 - Check `docs/project_notes/key_facts.md`
 
 **When completing work:**
-- Update sprint tracker and add to Completion Log
+- Update product tracker and add to Completion Log
 
 ### 3. Searching Memory Files
 
@@ -102,7 +102,7 @@ When encountering problems or making decisions, proactively search memory files:
 
 - User is responsible for manual cleanup
 - Remove very old bug entries (6+ months) that are no longer relevant
-- Archive old sprint trackers
+- Review and clean up completed features in product tracker
 - Keep all decisions (they provide historical context)
 - Update key_facts.md when project configuration changes
 
@@ -112,7 +112,7 @@ When encountering problems or making decisions, proactively search memory files:
 - **references/decisions_template.md** - ADR format with examples
 - **references/key_facts_template.md** - Key facts organization with examples
 
-Sprint trackers are created using the development-workflow skill.
+Product tracker is created using the development-workflow skill.
 
 ## Tips for Effective Memory Management
 
@@ -124,7 +124,7 @@ Sprint trackers are created using the development-workflow skill.
 
 ## Integration with Other Skills
 
-- **development-workflow**: Updates sprint tracker and memory files during task execution
+- **development-workflow**: Updates product tracker and memory files during task execution
 - **bug-workflow**: Documents bugs and solutions in bugs.md
 
 ## Success Criteria
@@ -132,6 +132,6 @@ Sprint trackers are created using the development-workflow skill.
 This skill is successfully deployed when:
 
 - `docs/project_notes/` directory exists with memory files
-- Sprint tracker exists for active sprint
+- Product tracker exists with feature backlog
 - Memory files follow template format
 - AI assistant checks memory files before proposing changes

package/template/AGENTS.md

@@ -27,7 +27,7 @@ project/
 
 Institutional knowledge lives in `docs/project_notes/`:
 
-- **sprint-X-tracker.md** — Sprint progress, **Active Session** (current task, next actions, open questions), completion log
+- **product-tracker.md** — Feature backlog, **Active Session** (current feature, next actions, open questions), completion log
 - **bugs.md** — Bug log with solutions and prevention notes
 - **decisions.md** — Architectural Decision Records (ADRs)
 - **key_facts.md** — Project configuration, ports, URLs, branching strategy
@@ -36,8 +36,8 @@ Institutional knowledge lives in `docs/project_notes/`:
 
 After context loss, new session, or context compaction — BEFORE continuing work:
 
-1. **Read sprint tracker** (`docs/project_notes/sprint-X-tracker.md`) → **Active Session** section
-2. If there is an active task → read the referenced ticket in `docs/tickets/`
+1. **Read product tracker** (`docs/project_notes/product-tracker.md`) → **Active Session** section
+2. If there is an active feature → read the referenced ticket in `docs/tickets/`
 3. Respect the configured autonomy level — do NOT skip checkpoints
 
 ## Anti-Patterns (Avoid)
@@ -48,14 +48,14 @@ After context loss, new session, or context compaction — BEFORE continuing wor
 - Creating files when existing ones can be extended
 - Adding features not explicitly requested
 - Committing without updating ticket acceptance criteria
-- Forgetting to update sprint tracker's Active Session after step changes
+- Forgetting to update product tracker's Active Session after step changes
 
 ## Automated Hooks (Claude Code)
 
 The project includes pre-configured hooks in `.claude/settings.json`:
 
 - **Quick Scan** (`SubagentStop`): After `backend-developer` or `frontend-developer` finishes, a fast grep-based scan (~2s, no additional API calls) checks for `console.log`, `debugger`, `TODO/FIXME`, hardcoded secrets, and localhost references. Critical issues block; warnings are non-blocking (full review happens in Step 5).
-- **Compaction Recovery** (`SessionStart → compact`): After context compaction, injects a reminder to read the sprint tracker Active Session for context recovery.
+- **Compaction Recovery** (`SessionStart → compact`): After context compaction, injects a reminder to read the product tracker Active Session for context recovery.
 
 Personal notification hooks (macOS/Linux) are in `.claude/settings.local.json` — see that file for examples.
 

package/template/CLAUDE.md

@@ -12,8 +12,8 @@
 
 After context compaction or new session — BEFORE continuing work:
 
-1. Read sprint tracker (`docs/project_notes/sprint-X-tracker.md`) → **Active Session**
-2. If active task → read referenced ticket in `docs/tickets/`
+1. Read product tracker (`docs/project_notes/product-tracker.md`) → **Active Session**
+2. If active feature → read referenced ticket in `docs/tickets/`
 3. Read the active skill file (`.claude/skills/*/SKILL.md`)
 4. Do NOT proceed past any checkpoint without user confirmation (respect autonomy level)
 5. If Active Session shows a pending checkpoint, ask before continuing

package/template/ai-specs/specs/base-standards.mdc

@@ -31,7 +31,7 @@ These conventions adapt per-project via `<!-- CONFIG: -->` comments in `CLAUDE.m
 
 ```
 0. SPEC      → spec-creator drafts/updates specs        → SPEC APPROVAL (Std/Cplx)
-1. SETUP     → Branch, ticket, sprint tracker            → TICKET APPROVAL (Std/Cplx)
+1. SETUP     → Branch, ticket, product tracker            → TICKET APPROVAL (Std/Cplx)
 2. PLAN      → Planner agent creates implementation plan → PLAN APPROVAL (Std/Cplx)
 3. IMPLEMENT → Developer agent, TDD, real-time spec sync
 4. FINALIZE  → Tests/lint/build, production-validator    → COMMIT APPROVAL
@@ -67,12 +67,12 @@ Quality gates (tests, lint, build, validators) **always run** regardless of leve
 | Commit Approval | Required | Auto | Auto | Auto |
 | Merge Approval | Required | Required | Required | Auto |
 
-- **L1 Full Control**: First sprint or learning SDD — human approves every step.
+- **L1 Full Control**: New project or learning SDD — human approves every step.
 - **L2 Trusted**: Comfortable with SDD — AI handles routine, human reviews plans and merges.
 - **L3 Autopilot**: Battle-tested workflow — human only reviews PRs before merge.
-- **L4 Full Auto**: Full automation — human reviews at sprint boundaries only.
+- **L4 Full Auto**: Full automation — human reviews completed features only.
 
-**Auto** = proceed without asking; log in sprint tracker → "Auto-Approved Decisions" table.
+**Auto** = proceed without asking; log in product tracker → "Auto-Approved Decisions" table.
 
 ## 4. Agent Roles
 
@@ -121,11 +121,11 @@ All agents MUST follow: **Acknowledge** → **Execute** → **Explain** → **Ga
 
 ## 8. Project Memory Protocols
 
-- Starting a session or after compaction → read sprint tracker's **Active Session** first
+- Starting a session or after compaction → read product tracker's **Active Session** first
 - Before architectural changes → check `decisions.md`
 - When encountering bugs → search `bugs.md`
 - When looking up config → check `key_facts.md`
-- After every step change → update sprint tracker's Active Session
+- After every step change → update product tracker's Active Session
 
 ## 9. Git Conventions
 
@@ -139,7 +139,7 @@ All agents MUST follow: **Acknowledge** → **Execute** → **Explain** → **Ga
 | Branch | Base | Merges to |
 |--------|------|-----------|
 | `main` | — | — (always deployable) |
-| `feature/sprint<N>-<task-id>-<desc>` | main | main (PR) |
+| `feature/<feature-id>-<desc>` | main | main (PR) |
 | `bugfix/<area>-<desc>` | main | main (PR) |
 | `hotfix/<desc>` | main | main (fast-track PR) |
 
@@ -149,7 +149,7 @@ All agents MUST follow: **Acknowledge** → **Execute** → **Explain** → **Ga
 |--------|------|-----------|
 | `main` | — | — (releases only) |
 | `develop` | main | — (integration) |
-| `feature/sprint<N>-<task-id>-<desc>` | develop | develop (PR) |
+| `feature/<feature-id>-<desc>` | develop | develop (PR) |
 | `release/<version>` | develop | main + develop |
 | `hotfix/<desc>` | main | main + develop |
 

package/template/docs/project_notes/product-tracker.md

@@ -0,0 +1,56 @@
+# Product Tracker
+
+> Feature backlog and progress tracking. Each feature follows the SDD workflow (Steps 0-6).
+
+---
+
+## Active Session
+
+> **Read this section first** when starting a new session or after context compaction. Provides instant context recovery.
+
+**Last Updated:** —
+
+| Field | Value |
+|-------|-------|
+| **Current Feature** | None |
+| **Step** | — |
+| **Branch** | — |
+| **Complexity** | — |
+| **Ticket** | — |
+
+**Context:** _No active work._
+
+**Next Actions:**
+1. —
+
+**Open Questions:** _None._
+
+**Auto-Approved Decisions (this session):**
+
+| Step | Decision | Rationale |
+|------|----------|-----------|
+| — | — | — |
+
+---
+
+## Features
+
+| ID | Feature | Type | Status | Step | Notes |
+|----|---------|------|--------|------|-------|
+| F001 | [Feature description] | backend | pending | — | |
+
+**Status Legend:** pending | in-progress | done | blocked | cancelled
+
+---
+
+## Completion Log
+
+| Date | Feature | Commit/PR | Notes |
+|------|---------|-----------|-------|
+| | | | |
+
+---
+
+## Notes
+
+- Tracker initialized. Use `add feature "description"` to add features.