create-sdd-project 0.9.6 → 0.9.8

package/lib/config.js

@@ -103,6 +103,12 @@ const TEMPLATE_AGENTS = [
   'qa-engineer.md',
 ];
 
+// Template-provided command files (for upgrade: detect custom commands)
+const TEMPLATE_COMMANDS = [
+  'review-plan.md',
+  'context-prompt.md',
+];
+
 module.exports = {
   DEFAULTS,
   PROJECT_TYPES,
@@ -114,4 +120,5 @@ module.exports = {
   FRONTEND_AGENTS,
   BACKEND_AGENTS,
   TEMPLATE_AGENTS,
+  TEMPLATE_COMMANDS,
 };

package/lib/upgrade-generator.js

@@ -7,6 +7,7 @@ const {
   FRONTEND_AGENTS,
   BACKEND_AGENTS,
   TEMPLATE_AGENTS,
+  TEMPLATE_COMMANDS,
 } = require('./config');
 const { adaptAgentContentForProjectType } = require('./adapt-agents');
 const {
@@ -110,7 +111,7 @@ function collectCustomAgents(dest) {
 }
 
 /**
- * Find custom command files (not .gitkeep).
+ * Find custom command files (not .gitkeep, not template-owned).
  * Returns array of { relativePath, content } objects.
  */
 function collectCustomCommands(dest) {
@@ -120,6 +121,7 @@ function collectCustomCommands(dest) {
   const files = fs.readdirSync(commandsDir);
   for (const file of files) {
     if (file === '.gitkeep') continue;
+    if (TEMPLATE_COMMANDS.includes(file)) continue;
     customs.push({
       relativePath: path.join('.claude', 'commands', file),
       content: fs.readFileSync(path.join(commandsDir, file), 'utf8'),
@@ -239,14 +241,12 @@ function generateUpgrade(config) {
         const srcSub = path.join(templateToolDir, sub);
         const destSub = path.join(base, sub);
         if (fs.existsSync(srcSub)) {
-          // For .claude/commands, merge: copy new template files without overwriting user's custom commands
+          // For .claude/commands, merge: overwrite SDD template commands, preserve user's custom commands
           if (dir === '.claude' && sub === 'commands') {
             fs.mkdirSync(destSub, { recursive: true });
             for (const file of fs.readdirSync(srcSub)) {
-              const destFile = path.join(destSub, file);
-              if (!fs.existsSync(destFile)) {
-                fs.cpSync(path.join(srcSub, file), destFile);
-              }
+              // Always overwrite template-owned files (they may have been updated)
+              fs.cpSync(path.join(srcSub, file), path.join(destSub, file));
             }
           } else {
             fs.cpSync(srcSub, destSub, { recursive: true });

package/package.json

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

package/template/.claude/commands/context-prompt.md

@@ -0,0 +1,44 @@
+Generate a complete context recovery prompt to paste after /compact or at the start of a new session.
+
+## What to include
+
+The prompt must contain EVERYTHING needed for a new session (or post-compact) to continue work without information loss:
+
+1. **Project state**: current branch, last commit, working tree status, SDD version
+2. **Workflow**: SDD development workflow, autonomy level, branching strategy
+3. **Active feature**: current step in the 6-step workflow, what has been done, what remains
+4. **Epics and progress**: table with status of each epic
+5. **Backlog**: pending features with priorities and dependencies
+6. **Infrastructure**: key modules, endpoints, schemas, with exact file paths
+7. **Tests**: total count, files, lint/build/tsc status
+8. **Key files to read**: list of files the new session must read first
+9. **Next action**: the specific next thing to do, with context
+10. **User notes**: any decisions or constraints communicated by the user
+
+### Workflow Recovery (CRITICAL)
+
+This section prevents the agent from losing track of the development process after /compact:
+
+11. **Current workflow step**: Which of the 6 steps (Spec, Setup, Plan, Implement, Finalize, Review) is active
+12. **Pending checkpoints**: Which approvals remain (Spec, Ticket, Plan, Commit, Merge)
+13. **Merge checklist reminder**: If at Step 5 or later, explicitly state: "Before requesting merge approval, you MUST read `references/merge-checklist.md` and execute ALL actions (0-8). Fill the `## Merge Checklist Evidence` table in the ticket with real evidence for each action."
+14. **Step order reminder**: "After commit+PR, run code-review-specialist and qa-engineer (Step 5), then execute merge-checklist actions. Do NOT request merge approval without completing the checklist."
+
+## How to generate
+
+- Read `docs/project_notes/product-tracker.md` (Active Session + Features tables + Completion Log)
+- Read `docs/project_notes/decisions.md` (recent ADRs)
+- Read `docs/project_notes/key_facts.md` (stack, components)
+- Read the current ticket in `docs/tickets/` if a feature is active
+- Run `git log --oneline -5` and `git status` for current state
+- Read `.sdd-version` for SDD DevFlow version
+
+## Output format
+
+Structured markdown with tables, ready to paste directly as the first message of a new session. The prompt should be self-contained — the receiving agent should not need to ask clarifying questions.
+
+## Context
+
+- Users work remotely with long sessions — interruptions are costly
+- After /review-plan + plan approval, context is typically at 50%+ usage, making /compact necessary before implementation
+- The workflow recovery section is essential: without it, the agent may skip merge checklist actions after /compact

package/template/.gemini/commands/context-prompt-instructions.md

@@ -0,0 +1,46 @@
+## Context Prompt — Instructions
+
+Generate a complete context recovery prompt to paste after compaction or at the start of a new session.
+
+### What to include
+
+The prompt must contain EVERYTHING needed for a new session (or post-compact) to continue work without information loss:
+
+1. **Project state**: current branch, last commit, working tree status, SDD version
+2. **Workflow**: SDD development workflow, autonomy level, branching strategy
+3. **Active feature**: current step in the 6-step workflow, what has been done, what remains
+4. **Epics and progress**: table with status of each epic
+5. **Backlog**: pending features with priorities and dependencies
+6. **Infrastructure**: key modules, endpoints, schemas, with exact file paths
+7. **Tests**: total count, files, lint/build/tsc status
+8. **Key files to read**: list of files the new session must read first
+9. **Next action**: the specific next thing to do, with context
+10. **User notes**: any decisions or constraints communicated by the user
+
+#### Workflow Recovery (CRITICAL)
+
+This section prevents the agent from losing track of the development process after compaction:
+
+11. **Current workflow step**: Which of the 6 steps (Spec, Setup, Plan, Implement, Finalize, Review) is active
+12. **Pending checkpoints**: Which approvals remain (Spec, Ticket, Plan, Commit, Merge)
+13. **Merge checklist reminder**: If at Step 5 or later, explicitly state: "Before requesting merge approval, you MUST read `references/merge-checklist.md` and execute ALL actions (0-8). Fill the `## Merge Checklist Evidence` table in the ticket with real evidence for each action."
+14. **Step order reminder**: "After commit+PR, run code-review-specialist and qa-engineer (Step 5), then execute merge-checklist actions. Do NOT request merge approval without completing the checklist."
+
+### How to generate
+
+- Read `docs/project_notes/product-tracker.md` (Active Session + Features tables + Completion Log)
+- Read `docs/project_notes/decisions.md` (recent ADRs)
+- Read `docs/project_notes/key_facts.md` (stack, components)
+- Read the current ticket in `docs/tickets/` if a feature is active
+- Run `git log --oneline -5` and `git status` for current state
+- Read `.sdd-version` for SDD DevFlow version
+
+### Output format
+
+Structured markdown with tables, ready to paste directly as the first message of a new session. The prompt should be self-contained — the receiving agent should not need to ask clarifying questions.
+
+### Context
+
+- Users work remotely with long sessions — interruptions are costly
+- After plan review + plan approval, context is typically at 50%+ usage, making compaction necessary before implementation
+- The workflow recovery section is essential: without it, the agent may skip merge checklist actions after compaction

package/template/.gemini/commands/context-prompt.toml

@@ -0,0 +1,2 @@
+description = "Generate a complete context recovery prompt to paste after compaction or at the start of a new session"
+prompt = "Read the file .gemini/commands/context-prompt-instructions.md and follow the instructions to generate a context recovery prompt."