declare-cc 0.5.9 → 0.6.0

package/bin/declare.js

@@ -0,0 +1,16 @@
+#!/usr/bin/env node
+'use strict';
+
+const path = require('path');
+const fs = require('fs');
+
+const bundlePath = path.resolve(__dirname, '../dist/declare-tools.cjs');
+
+if (!fs.existsSync(bundlePath)) {
+  console.error('[declare] Bundle not found: ' + bundlePath);
+  console.error('[declare] Run `npm run build` in the declare-cc package directory.');
+  process.exit(1);
+}
+
+// Forward argv as-is — declare-tools.cjs reads process.argv
+require(bundlePath);

package/commands/declare/complete-milestone.md

@@ -144,7 +144,7 @@ Locate or create a `## Current State` section. Update it to reflect the complete
 **Version shipped:** vX.Y (YYYY-MM-DD)
 **Milestones completed:** [N] ([M-01, M-02, ...])
 **Known gaps:** [list incomplete milestones, or "None"]
-**Next step:** Run /declare:new-milestone to start vX.Z cycle
+**Next step:** Run /declare:new-cycle to start vX.Z cycle
 ```
 
 If the section already exists, update it in place. If it does not exist, append it after the last section.
@@ -197,7 +197,7 @@ git commit -m "chore: archive vX.Y milestone snapshot
 
 Next: Start the next milestone cycle.
 
-Run /declare:new-milestone
+Run /declare:new-cycle
 ```
 
 **Error handling:**
@@ -212,4 +212,4 @@ Run /declare:new-milestone
 - Archive is a snapshot, not a destructive operation — FUTURE.md and MILESTONES.md remain in place.
 - PROJECT.md is the persistent memory across versions — always update it.
 - Git tag marks the historical release point for the snapshot.
-- This command archives only — use /declare:new-milestone to reset for the next cycle.
+- This command archives only — use /declare:new-cycle to reset for the next cycle.

package/commands/declare/execute.md

@@ -126,7 +126,7 @@ Spawning [count] agent(s)...
 
 **3c. Spawn executor agents in parallel using the Task tool:**
 
-For each action in the wave, spawn a Task with instructions like:
+For each action in the wave, spawn a Task with `model: "opus"` and instructions like:
 
 ```
 Execute the plan at [outputPath].

package/commands/declare/{new-milestone.md → new-cycle.md}

@@ -1,5 +1,5 @@
 ---
-description: Start a new Declare milestone cycle — archive declarations, reset FUTURE.md and MILESTONES.md, preserve PROJECT.md and STATE.md
+description: Start a new Declare cycle — archive current declarations to FUTURE-ARCHIVE.md, reset FUTURE.md and MILESTONES.md, preserve PROJECT.md and STATE.md
 allowed-tools:
   - Read
   - Write

package/commands/declare/plan.md

@@ -77,6 +77,7 @@ Display: `Running /declare:discuss [M-XX]...`
 
 Spawn a Task agent:
 - subagent_type: `general-purpose`
+- model: `opus`
 - description: `Discuss M-XX implementation decisions`
 - prompt:
   ```
@@ -123,7 +124,7 @@ Also read the milestone's PLAN.md (at `milestoneFolderPath/PLAN.md`) for action
 
 **Step 6: Spawn declare-planner.**
 
-Spawn a Task agent using `agents/declare-planner.md` with the following prompt:
+Spawn a Task agent using `agents/declare-planner.md` with `model: "opus"` and the following prompt:
 
 ```
 Plan milestone ${MILESTONE} actions.
@@ -150,7 +151,7 @@ Wait for the planner to complete.
 
 **Step 7: Spawn declare-plan-checker.**
 
-After planner completes, spawn a Task agent using `agents/declare-plan-checker.md` with the following prompt:
+After planner completes, spawn a Task agent using `agents/declare-plan-checker.md` with `model: "haiku"` and the following prompt:
 
 ```
 Verify EXEC-PLAN files for milestone ${MILESTONE}.
@@ -183,7 +184,7 @@ If **ISSUES FOUND**: proceed to Step 9 (revision loop).
 
 Track revision count. If revision count >= 3, skip to Step 9 with a warning.
 
-Spawn declare-planner again in revision mode:
+Spawn declare-planner again in revision mode with `model: "opus"`:
 
 ```
 Revise EXEC-PLAN files for milestone ${MILESTONE} based on checker feedback.
@@ -283,6 +284,7 @@ After displaying the summary, reload the graph and check for milestones that sti
   For each wave, spawn one Task agent per milestone **in the same response** so they execute in parallel:
 
   Subagent type: `gsd-executor`
+  model: `opus`
   Prompt per milestone:
   ```
   Execute milestone [M-XX] "[title]" for the Declare project.

package/commands/declare/progress.md

@@ -89,11 +89,11 @@ Evaluate project state and present the appropriate option(s):
 
 **Route C — All milestones for active declarations complete:**
 - "All milestones for the current declaration wave are complete."
-- Offer: "Run `/declare:complete-milestone` or plan the next milestone with `/declare:new-milestone`"
+- Offer: "Run `/declare:complete-milestone` or plan the next milestone with `/declare:new-cycle`"
 
 **Route D — No active milestone:**
 - "No active milestone found."
-- Offer: "Run `/declare:new-milestone` to plan the next milestone, or `/declare:status` to review the full graph"
+- Offer: "Run `/declare:new-cycle` to plan the next milestone, or `/declare:status` to review the full graph"
 
 **Route E — No declarations exist:**
 - "No declarations found. Start by defining what you want to be true."

package/commands/declare/research.md

@@ -62,9 +62,9 @@ Spawning 4 researchers: STACK, FEATURES, ARCHITECTURE, PITFALLS...
 
 Spawn all 4 Task agents in the same response so they run in parallel. Each agent researches a specific domain.
 
-For each researcher, the prompt follows this pattern (fill in milestone-specific context):
+For each researcher, the prompt follows this pattern (fill in milestone-specific context). Each researcher Task is spawned with `model: "sonnet"`.
 
-**STACK researcher:**
+**STACK researcher** (model: `sonnet`):
 
 ```
 First, read agents/declare-researcher.md for your role and instructions.
@@ -91,7 +91,7 @@ Do NOT commit — the synthesizer will commit everything together.
 </output>
 ```
 
-**FEATURES researcher:**
+**FEATURES researcher** (model: `sonnet`):
 
 ```
 First, read agents/declare-researcher.md for your role and instructions.
@@ -118,7 +118,7 @@ Do NOT commit — the synthesizer will commit everything together.
 </output>
 ```
 
-**ARCHITECTURE researcher:**
+**ARCHITECTURE researcher** (model: `sonnet`):
 
 ```
 First, read agents/declare-researcher.md for your role and instructions.
@@ -145,7 +145,7 @@ Do NOT commit — the synthesizer will commit everything together.
 </output>
 ```
 
-**PITFALLS researcher:**
+**PITFALLS researcher** (model: `sonnet`):
 
 ```
 First, read agents/declare-researcher.md for your role and instructions.
@@ -191,7 +191,7 @@ Spawning synthesizer...
 
 If any researcher returned `## RESEARCH BLOCKED`, surface the blocker to the user before spawning the synthesizer. Ask whether to continue with partial research or abort.
 
-**Step 7: Spawn declare-research-synthesizer.**
+**Step 7: Spawn declare-research-synthesizer** (model: `sonnet`).
 
 ```
 First, read agents/declare-research-synthesizer.md for your role and instructions.

package/commands/declare/resume.md

@@ -118,7 +118,7 @@ Evaluate the current project state and present the most relevant next step:
 
 **Route D — No active milestone:**
 - "No active milestone found."
-- Offer: "`/declare:new-milestone` to plan next milestone" or "`/declare:status` to review graph"
+- Offer: "`/declare:new-cycle` to plan next milestone" or "`/declare:status` to review graph"
 
 **Route E — No project initialized:**
 - "Project not initialized."

package/commands/declare/verify.md

@@ -51,6 +51,7 @@ node dist/declare-tools.cjs commit "test(${MILESTONE_ID}): complete UAT - ${PASS
 **On gaps found — spawn parallel declare-debugger agents (one per gap):**
 
 For each gap in the UAT Gaps section, spawn a declare-debugger agent with:
+- `model: "opus"`
 - `symptoms_prefilled: true` (skip symptom gathering)
 - `goal: find_root_cause_only` (diagnose but don't fix)
 - Pre-filled symptoms from the gap's test_id, expected, and actual fields