create-sdd-project 0.2.4 → 0.3.0

package/README.md

@@ -36,8 +36,8 @@ Scans your project, detects your stack and architecture, and installs SDD files
 Open in your AI coding tool and run:
 
 ```
-init sprint 0
-start task B0.1
+add feature "your first feature"
+start task F001
 ```
 
 The workflow skill guides you through each step with checkpoints based on your autonomy level.
@@ -55,7 +55,7 @@ SDD DevFlow combines three proven practices:
 ### Why use SDD DevFlow?
 
 - **AI agents work better with structure.** Without guardrails, AI coding assistants produce inconsistent results. SDD provides the methodology, standards, and workflow that make AI output predictable and high-quality.
-- **Institutional memory across sessions.** Sprint trackers, bug logs, and decision records survive context compaction and session boundaries.
+- **Institutional memory across sessions.** Product tracker, bug logs, and decision records survive context compaction and session boundaries.
 - **Scales from solo to team.** Start at L1 (full control) while learning, scale to L4 (full auto) for repetitive tasks.
 - **Works with your stack.** Not opinionated about frameworks — detects and adapts to Express, Fastify, NestJS, Next.js, Nuxt, Vue, Angular, and many more.
 
@@ -79,7 +79,7 @@ SDD DevFlow combines three proven practices:
 
 | Skill | Trigger | What it does |
 |-------|---------|-------------|
-| `development-workflow` | `start task B0.1`, `next task`, `init sprint N` | Orchestrates the complete 7-step workflow |
+| `development-workflow` | `start task F001`, `next task`, `add feature` | Orchestrates the complete 7-step workflow |
 | `bug-workflow` | `report bug`, `fix bug`, `hotfix needed` | Bug triage, investigation, and resolution |
 | `project-memory` | `set up project memory`, `log a bug fix` | Maintains institutional knowledge |
 
@@ -87,7 +87,7 @@ SDD DevFlow combines three proven practices:
 
 ```
 0. SPEC      → spec-creator drafts specs        → Spec Approval
-1. SETUP     → Branch, ticket, sprint tracker    → Ticket Approval
+1. SETUP     → Branch, ticket, product tracker    → Ticket Approval
 2. PLAN      → Planner creates implementation plan → Plan Approval
 3. IMPLEMENT → Developer agent, TDD
 4. FINALIZE  → Tests/lint/build, validator       → Commit Approval
@@ -104,7 +104,7 @@ SDD DevFlow combines three proven practices:
 
 | Level | Name | Human Checkpoints | Best For |
 |-------|------|-------------------|----------|
-| L1 | Full Control | All 5 | First sprint, learning SDD |
+| L1 | Full Control | All 5 | First feature, learning SDD |
 | L2 | Trusted | Plan + Merge | Normal development **(default)** |
 | L3 | Autopilot | Merge only | Well-defined, repetitive tasks |
 | L4 | Full Auto | None (CI/CD gates only) | Bulk simple tasks |
@@ -115,7 +115,7 @@ Quality gates (tests, lint, build, validators) **always run** regardless of leve
 
 Tracks institutional knowledge across sessions in `docs/project_notes/`:
 
-- **sprint-X-tracker.md** — Sprint progress + Active Session (context recovery after compaction)
+- **product-tracker.md** — Feature backlog + Active Session (context recovery after compaction)
 - **bugs.md** — Bug log with solutions and prevention notes
 - **decisions.md** — Architectural Decision Records (ADRs)
 - **key_facts.md** — Project configuration, ports, URLs, branching strategy
@@ -123,7 +123,7 @@ Tracks institutional knowledge across sessions in `docs/project_notes/`:
 ### Automated Hooks (Claude Code)
 
 - **Quick Scan** — After developer agents finish, a fast grep-based scan (~2s, no API calls) checks for debug code, secrets, and TODOs
-- **Compaction Recovery** — After context compaction, injects a reminder to read the sprint tracker for context recovery
+- **Compaction Recovery** — After context compaction, injects a reminder to read the product tracker for context recovery
 
 ### Multi-Tool Support
 
@@ -189,7 +189,7 @@ project/
 │
 └── docs/
     ├── project_notes/                   # Project memory
-    │   ├── sprint-0-tracker.md
+    │   ├── product-tracker.md
     │   ├── key_facts.md
     │   ├── bugs.md
     │   └── decisions.md
@@ -237,7 +237,7 @@ Then look for `<!-- CONFIG: ... -->` comments in the files to customize.
 ## Roadmap
 
 - **Agent Teams**: Parallel execution of independent tasks (waiting for Claude Code Agent Teams to stabilize)
-- **PM Agent + L5 Autonomous**: AI-driven sprint orchestration with human review at sprint boundaries
+- **PM Agent + L5 Autonomous**: AI-driven feature orchestration with human review at milestone boundaries
 - **Retrofit Testing**: Automated test generation for existing projects with low coverage
 
 ## License

package/lib/config.js

@@ -78,7 +78,7 @@ const AI_TOOLS = [
 ];
 
 const AUTONOMY_LEVELS = [
-  { level: 1, name: 'Full Control', desc: 'Human approves every checkpoint (first sprint, learning SDD)' },
+  { level: 1, name: 'Full Control', desc: 'Human approves every checkpoint (first feature, learning SDD)' },
   { level: 2, name: 'Trusted', desc: 'Human reviews plans + merges only (normal development)', default: true },
   { level: 3, name: 'Autopilot', desc: 'Human only approves merges (well-defined, repetitive tasks)' },
   { level: 4, name: 'Full Auto', desc: 'No human checkpoints, CI/CD gates only (bulk simple tasks)' },

package/lib/generator.js

@@ -41,11 +41,7 @@ function generate(config) {
   step(`Setting branching: ${config.branching}`);
   updateBranching(dest, config);
 
-  // 6. Set sprint dates
-  step('Setting sprint dates to today');
-  updateSprintDates(dest);
-
-  // 7. Remove agents/specs based on project type
+  // 6. Remove agents/specs based on project type
   if (config.projectType === 'backend') {
     step('Removing frontend agents (backend only)');
     removeFrontendFiles(dest, config);
@@ -54,7 +50,7 @@ function generate(config) {
     removeBackendFiles(dest, config);
   }
 
-  // 8. Remove AI tool config if single tool selected
+  // 7. Remove AI tool config if single tool selected
   if (config.aiTools === 'claude') {
     step('Removing Gemini config (Claude only)');
     fs.rmSync(path.join(dest, '.gemini'), { recursive: true, force: true });
@@ -76,7 +72,7 @@ function generate(config) {
   console.log(`\nDone! Next steps:`);
   console.log(`  cd ${path.relative(process.cwd(), dest)}`);
   console.log(`  git init && git add -A && git commit -m "chore: initialize SDD DevFlow project"`);
-  console.log(`  # Open in your AI coding tool and run: init sprint 0\n`);
+  console.log(`  # Open in your AI coding tool and run: add feature "your first feature"\n`);
 }
 
 // --- Helpers ---
@@ -230,19 +226,6 @@ function updateBranching(dest, config) {
   // Nothing else to update — branching is read from key_facts.md at runtime
 }
 
-function updateSprintDates(dest) {
-  const file = path.join(dest, 'docs', 'project_notes', 'sprint-0-tracker.md');
-  const today = new Date().toISOString().split('T')[0];
-  // Calculate 2-week sprint end
-  const endDate = new Date();
-  endDate.setDate(endDate.getDate() + 14);
-  const end = endDate.toISOString().split('T')[0];
-
-  replaceInFile(file, [
-    [/\[YYYY-MM-DD\] to \[YYYY-MM-DD\]/, `${today} to ${end}`],
-  ]);
-}
-
 function removeFrontendFiles(dest, config) {
   // Remove frontend agents
   for (const agent of FRONTEND_AGENTS) {
@@ -262,11 +245,7 @@ function removeFrontendFiles(dest, config) {
     ['├── frontend/    ← Frontend (has its own package.json)\n', ''],
   ]);
 
-  // Remove frontend tasks from sprint tracker
-  const trackerFile = path.join(dest, 'docs', 'project_notes', 'sprint-0-tracker.md');
-  replaceInFile(trackerFile, [
-    [/\n### Frontend\n\n\|.*\n\|.*\n\|.*\n/, '\n'],
-  ]);
+  // Product tracker already defaults to backend — no change needed
 }
 
 function removeBackendFiles(dest, config) {
@@ -288,10 +267,10 @@ function removeBackendFiles(dest, config) {
     ['├── backend/     ← Backend (has its own package.json)\n', ''],
   ]);
 
-  // Remove backend tasks from sprint tracker
-  const trackerFile = path.join(dest, 'docs', 'project_notes', 'sprint-0-tracker.md');
+  // Update product tracker default feature type to frontend
+  const trackerFile = path.join(dest, 'docs', 'project_notes', 'product-tracker.md');
   replaceInFile(trackerFile, [
-    [/\n### Backend\n\n\|.*\n\|.*\n\|.*\n/, '\n'],
+    ['| backend | pending', '| frontend | pending'],
   ]);
 }
 

package/lib/init-generator.js

@@ -72,7 +72,7 @@ function generateInit(config) {
   }
 
   // 3. Copy and configure docs/
-  step('Creating docs/project_notes/ (sprint tracker, memory)');
+  step('Creating docs/project_notes/ (product tracker, memory)');
   ensureDir(path.join(dest, 'docs', 'project_notes'));
   ensureDir(path.join(dest, 'docs', 'specs'));
   ensureDir(path.join(dest, 'docs', 'tickets'));
@@ -99,14 +99,14 @@ function generateInit(config) {
     skipped
   );
 
-  // sprint-0-tracker.md — configure dates and add retrofit tasks
-  const trackerPath = path.join(dest, 'docs', 'project_notes', 'sprint-0-tracker.md');
+  // product-tracker.md — configure and add retrofit tasks
+  const trackerPath = path.join(dest, 'docs', 'project_notes', 'product-tracker.md');
   if (!fs.existsSync(trackerPath)) {
-    const template = fs.readFileSync(path.join(templateDir, 'docs', 'project_notes', 'sprint-0-tracker.md'), 'utf8');
-    const configured = configureSprintTracker(template, scan);
+    const template = fs.readFileSync(path.join(templateDir, 'docs', 'project_notes', 'product-tracker.md'), 'utf8');
+    const configured = configureProductTracker(template, scan);
     fs.writeFileSync(trackerPath, configured, 'utf8');
   } else {
-    skipped.push('docs/project_notes/sprint-0-tracker.md');
+    skipped.push('docs/project_notes/product-tracker.md');
   }
 
   // docs/specs/
@@ -195,7 +195,7 @@ function generateInit(config) {
 
   // Show review notes
   console.log('');
-  console.log('  ⚠ REVIEW BEFORE YOUR FIRST SPRINT:');
+  console.log('  ⚠ REVIEW BEFORE YOUR FIRST FEATURE:');
   if (config.projectType !== 'frontend') {
     console.log('    - ai-specs/specs/backend-standards.mdc  — Architecture section adapted from scan');
   }
@@ -214,7 +214,7 @@ function generateInit(config) {
     } else {
       console.log(`  📝 Test coverage appears low (${fileCount} test files found).`);
     }
-    console.log('     Consider starting Sprint 0 with retrofit testing tasks.');
+    console.log('     Consider adding retrofit testing as your first feature.');
   }
 
   // Prisma schema note
@@ -226,7 +226,7 @@ function generateInit(config) {
   // Done
   console.log(`\nDone! Next steps:`);
   console.log(`  git add -A && git commit -m "chore: add SDD DevFlow to existing project"`);
-  console.log(`  # Open in your AI coding tool and run: init sprint 0\n`);
+  console.log(`  # Open in your AI coding tool and run: add feature "your first feature"\n`);
 }
 
 // --- Helpers ---
@@ -646,40 +646,29 @@ function configureKeyFacts(template, config, scan) {
   return content;
 }
 
-// --- Sprint Tracker Configuration ---
+// --- Product Tracker Configuration ---
 
-function configureSprintTracker(template, scan) {
+function configureProductTracker(template, scan) {
   let content = template;
 
-  // Set dates
-  const today = new Date().toISOString().split('T')[0];
-  const endDate = new Date();
-  endDate.setDate(endDate.getDate() + 14);
-  const end = endDate.toISOString().split('T')[0];
-  content = content.replace(/\[YYYY-MM-DD\] to \[YYYY-MM-DD\]/, `${today} to ${end}`);
+  // Determine default feature type based on detected stack
+  const featureType = !scan.backend.detected && scan.frontend.detected
+    ? 'frontend'
+    : scan.backend.detected && scan.frontend.detected
+      ? 'fullstack'
+      : 'backend';
 
-  // Remove irrelevant task tables based on detected stack
-  if (!scan.frontend.detected) {
-    content = content.replace(
-      /\n### Frontend\n\n\| # \| Task \| Status \| Notes \|\n\|---\|------\|--------\|-------\|\n\| F0\.1 \| \[Task description\] \| ⬚ \| \|\n/,
-      ''
-    );
-  }
-  if (!scan.backend.detected) {
-    content = content.replace(
-      /\n### Backend\n\n\| # \| Task \| Status \| Notes \|\n\|---\|------\|--------\|-------\|\n\| B0\.1 \| \[Task description\] \| ⬚ \| \|\n/,
-      ''
-    );
+  // Update default feature type in the placeholder row
+  if (featureType !== 'backend') {
+    content = content.replace('| backend | pending', `| ${featureType} | pending`);
   }
 
-  // Add retrofit testing tasks if coverage is low
+  // Add retrofit testing as first feature if coverage is low
   if (scan.tests.estimatedCoverage === 'none' || scan.tests.estimatedCoverage === 'low') {
-    const retrofitSection = `\n### Retrofit Testing (recommended)\n\n| # | Task | Status | Notes |\n|---|------|--------|-------|\n| R0.1 | Audit existing test coverage | ⬚ | |\n| R0.2 | Add missing unit tests for critical paths | ⬚ | |\n| R0.3 | Set up CI test pipeline | ⬚ | |\n`;
-
-    // Insert before Status Legend
+    // Use regex to match the F001 placeholder row resiliently (handles column changes)
     content = content.replace(
-      '**Status Legend:**',
-      `${retrofitSection}\n**Status Legend:**`
+      /\| F001 \|[^\n]*\n/,
+      `| F001 | Retrofit: audit and improve test coverage | ${featureType} | pending | — | Recommended — low test coverage detected |\n| F002 | [Feature description] | ${featureType} | pending | — | |\n`
     );
   }
 

package/lib/init-wizard.js

@@ -220,7 +220,7 @@ async function runInitWizard(scanResult) {
 
     console.log('\n  Files to be created:');
     console.log('    ai-specs/specs/          (4 files — standards adapted to your stack)');
-    console.log('    docs/project_notes/      (4 files — sprint tracker, memory)');
+    console.log('    docs/project_notes/      (4 files — product tracker, memory)');
     console.log('    docs/specs/              (API spec, UI components)');
     console.log('    docs/tickets/            (.gitkeep)');
     if (config.aiTools !== 'gemini') {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-sdd-project",
-  "version": "0.2.4",
+  "version": "0.3.0",
   "description": "Create a new SDD DevFlow project with AI-assisted development workflow",
   "bin": {
     "create-sdd-project": "bin/cli.js"

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

@@ -57,4 +57,4 @@ Follow the DDD layer order from the plan:
 - **ALWAYS** run `npm test` after each TDD cycle to verify
 - **NEVER** skip tests for "simple" code
 - **NEVER** modify code outside the scope of the current ticket
-- **ALWAYS** verify implementation matches the approved spec. If a deviation is needed, document it in the sprint tracker's Active Session and ask for approval
+- **ALWAYS** verify implementation matches the approved spec. If a deviation is needed, document it in the product tracker's Active Session and ask for approval

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

@@ -65,4 +65,4 @@ Follow the logical order from the plan:
 - **ALWAYS** run `npm test` after each TDD cycle to verify
 - **NEVER** skip tests for "simple" components
 - **NEVER** modify code outside the scope of the current ticket
-- **ALWAYS** verify implementation matches the approved spec. If a deviation is needed, document it in the sprint tracker's Active Session and ask for approval
+- **ALWAYS** verify implementation matches the approved spec. If a deviation is needed, document it in the product tracker's Active Session and ask for approval

package/template/.claude/settings.json

@@ -19,7 +19,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "echo '{\"additionalContext\": \"Context was compacted. BEFORE doing anything else: read the sprint tracker Active Session section (docs/project_notes/sprint-*-tracker.md) for context recovery. Follow the Session Recovery protocol in CLAUDE.md.\"}'",
+            "command": "echo '{\"additionalContext\": \"Context was compacted. BEFORE doing anything else: read the product tracker Active Session section (docs/project_notes/product-tracker.md) for context recovery. Follow the Session Recovery protocol in CLAUDE.md.\"}'",
             "statusMessage": "Injecting recovery context..."
           }
         ]

package/template/.claude/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.
@@ -99,7 +99,7 @@ Run `production-code-validator`. Ensure no debug code, proper error handling.
 
 | 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/.claude/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 `CLAUDE.md` section 2 → **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 `CLAUDE.md` section 2.
 | 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. Use Task tool with planner agent (`backend-planner` for B*.*, `frontend-planner` for F*.*)
+1. Use Task tool with planner agent (`backend-planner` for backend features, `frontend-planner` for frontend features)
 2. Agent writes 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"
 
@@ -177,18 +177,18 @@ Update tracker: step `5/6 (Review)`
 - `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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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/.claude/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.