create-sdd-project 0.2.2 → 0.3.0

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.

package/template/.claude/skills/development-workflow/references/sprint-init-template.md

@@ -1,82 +0,0 @@
-# Sprint Initialization Template
-
-Use this template when running `init sprint N`.
-
-## How to Initialize
-
-1. Copy template below to `docs/project_notes/sprint-{N}-tracker.md`
-2. Read the sprint section from your project plan — extract goal, backend tasks (B*.*), frontend tasks (F*.*)
-3. Set dates (start + 2 weeks)
-4. Use `start task B0.1` to begin
-
----
-
-## Template
-
-```markdown
-# Sprint {N}: {Sprint Title}
-
-**Period:** YYYY-MM-DD to YYYY-MM-DD
-**Goal:** {Sprint goal}
-**Progress:** 0/{total} tasks (0%)
-
----
-
-## Active Session
-
-> **Read this section first** when starting a new session or after context compaction.
-
-**Last Updated:** —
-
-| Field | Value |
-|-------|-------|
-| **Current Task** | None |
-| **Step** | — |
-| **Branch** | — |
-| **Complexity** | — |
-| **Ticket** | — |
-
-**Context:** _No active work._
-
-**Next Actions:**
-1. —
-
-**Open Questions:** _None._
-
-**Auto-Approved Decisions (this session):**
-
-| Step | Decision | Rationale |
-|------|----------|-----------|
-| — | — | — |
-
----
-
-## Tasks
-
-### Backend
-
-| # | Task | Status | Notes |
-|---|------|--------|-------|
-{backend_tasks}
-
-### Frontend
-
-| # | Task | Status | Notes |
-|---|------|--------|-------|
-{frontend_tasks}
-
-**Status Legend:** ⬚ Pending | 🔄 In Progress | ✅ Complete | ⏸️ Blocked | ❌ Cancelled
-
----
-
-## Completion Log
-
-| Date | Task | Commit | Notes |
-|------|------|--------|-------|
-
----
-
-## Sprint Notes
-
-_Key learnings, issues, or observations._
-```

package/template/.gemini/commands/init-sprint.toml

@@ -1,2 +0,0 @@
-description = "Initialize a new sprint tracker (e.g., /init-sprint 1)"
-prompt = "Initialize sprint {{args}}. Follow the sprint initialization template in .gemini/skills/development-workflow/references/sprint-init-template.md"

package/template/.gemini/skills/development-workflow/references/sprint-init-template.md

@@ -1,82 +0,0 @@
-# Sprint Initialization Template
-
-Use this template when running `init sprint N`.
-
-## How to Initialize
-
-1. Copy template below to `docs/project_notes/sprint-{N}-tracker.md`
-2. Read the sprint section from your project plan — extract goal, backend tasks (B*.*), frontend tasks (F*.*)
-3. Set dates (start + 2 weeks)
-4. Use `start task B0.1` to begin
-
----
-
-## Template
-
-```markdown
-# Sprint {N}: {Sprint Title}
-
-**Period:** YYYY-MM-DD to YYYY-MM-DD
-**Goal:** {Sprint goal}
-**Progress:** 0/{total} tasks (0%)
-
----
-
-## Active Session
-
-> **Read this section first** when starting a new session or after context compaction.
-
-**Last Updated:** —
-
-| Field | Value |
-|-------|-------|
-| **Current Task** | None |
-| **Step** | — |
-| **Branch** | — |
-| **Complexity** | — |
-| **Ticket** | — |
-
-**Context:** _No active work._
-
-**Next Actions:**
-1. —
-
-**Open Questions:** _None._
-
-**Auto-Approved Decisions (this session):**
-
-| Step | Decision | Rationale |
-|------|----------|-----------|
-| — | — | — |
-
----
-
-## Tasks
-
-### Backend
-
-| # | Task | Status | Notes |
-|---|------|--------|-------|
-{backend_tasks}
-
-### Frontend
-
-| # | Task | Status | Notes |
-|---|------|--------|-------|
-{frontend_tasks}
-
-**Status Legend:** ⬚ Pending | 🔄 In Progress | ✅ Complete | ⏸️ Blocked | ❌ Cancelled
-
----
-
-## Completion Log
-
-| Date | Task | Commit | Notes |
-|------|------|--------|-------|
-
----
-
-## Sprint Notes
-
-_Key learnings, issues, or observations._
-```

package/template/docs/project_notes/sprint-0-tracker.md

@@ -1,66 +0,0 @@
-# Sprint 0 Tracker
-
-**Period:** [YYYY-MM-DD] to [YYYY-MM-DD]
-**Goal:** Project setup and infrastructure
-**Progress:** 0/0 tasks (0%)
-
----
-
-## Active Session
-
-> **Read this section first** when starting a new session or after context compaction. Provides instant context recovery.
-
-**Last Updated:** —
-
-| Field | Value |
-|-------|-------|
-| **Current Task** | None |
-| **Step** | — |
-| **Branch** | — |
-| **Complexity** | — |
-| **Ticket** | — |
-
-**Context:** _No active work._
-
-**Next Actions:**
-1. —
-
-**Open Questions:** _None._
-
-**Auto-Approved Decisions (this session):**
-
-| Step | Decision | Rationale |
-|------|----------|-----------|
-| — | — | — |
-
----
-
-## Tasks
-
-### Backend
-
-| # | Task | Status | Notes |
-|---|------|--------|-------|
-| B0.1 | [Task description] | ⬚ | |
-
-### Frontend
-
-| # | Task | Status | Notes |
-|---|------|--------|-------|
-| F0.1 | [Task description] | ⬚ | |
-
-**Status Legend:** ⬚ Pending | 🔄 In Progress | ✅ Complete | ⏸️ Blocked | ❌ Cancelled
-
----
-
-## Completion Log
-
-| Date | Task | Commit | Notes |
-|------|------|--------|-------|
-| | | | |
-
----
-
-## Sprint Notes
-
-- Sprint initialized. Replace tasks above with your actual Sprint 0 backlog.