declare-cc 1.0.7 → 2.0.0

package/commands/declare/reapply-patches.md

@@ -1,178 +0,0 @@
----
-description: Review and reapply locally-modified declare-cc files after an update
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-
-<purpose>
-After a declare-cc update wipes and reinstalls .claude/commands/declare/ files, this command lets you review each locally-modified file that was backed up, preview what changed, and selectively merge your modifications into the new installed version.
-</purpose>
-
-<process>
-
-## Step 1: Detect backed-up patches
-
-Read the backup metadata file (repo-relative):
-
-```bash
-cat .planning/declare-local-patches/backup-meta.json 2>/dev/null
-```
-
-**If the file does not exist or the directory is empty:**
-```
-No local patches found. Nothing to reapply.
-
-Local patches are saved automatically when you run /declare:update
-and locally-modified files are detected before the update runs.
-```
-Exit.
-
-Parse the JSON. It contains:
-- `from_version`: the version that was installed when the backup was made
-- `backup_date`: ISO timestamp of the backup
-- `files`: array of `{ path, backup_name }` entries
-
-## Step 2: Show patch summary
-
-Read the current installed version:
-
-```bash
-node dist/declare-tools.cjs help
-```
-
-Parse the version field.
-
-Display:
-
-```
-## Local Patches to Reapply
-
-**Backed up from:** v{from_version}
-**Backed up on:**   {backup_date}
-**Current version:** v{current_version}
-**Files backed up:** {count}
-
-| # | File | Status |
-|---|------|--------|
-| 1 | {path} | Pending |
-| 2 | {path} | Pending |
-```
-
-## Step 3: Process each file
-
-Iterate over each entry in `files`.
-
-### 3a. Read both versions
-
-Read the backed-up (user's modified) copy:
-
-```bash
-cat ".planning/declare-local-patches/{backup_name}"
-```
-
-Read the current installed copy:
-
-```bash
-cat "{path}"
-```
-
-### 3b. Compare
-
-If the two files are identical: report `Skipped (already upstream)` and continue to the next file.
-
-If they differ: proceed to 3c.
-
-### 3c. Show diff preview and ask
-
-Display a diff preview. Describe the key differences in plain language (do not dump raw diff output). For example:
-
-```
---- Diff preview: {path} ---
-
-Your backed-up version adds/changes:
-- [describe what the user's version has that the new version does not, in plain language]
-
-The new installed version adds/changes:
-- [describe what the new upstream version has that the backup does not]
-```
-
-Use AskUserQuestion:
-- Question: "What would you like to do with .claude/commands/declare/{filename}?"
-- Options:
-  - "Keep my version (overwrite installed file with backup)"
-  - "Keep new version (discard backup for this file)"
-  - "Merge manually (I will edit the file after this command)"
-
-**If user chooses "Keep my version":**
-- Write the backed-up content to `{path}`.
-- Report: `Reapplied — your version is active`.
-
-**If user chooses "Keep new version":**
-- Do not modify `{path}`.
-- Report: `Kept new version — backup preserved in .planning/declare-local-patches/`.
-
-**If user chooses "Merge manually":**
-- Do not modify `{path}`.
-- Display:
-  ```
-  Backed-up copy: .planning/declare-local-patches/{backup_name}
-  Installed copy: {path}
-  Edit {path} manually, using the backup as reference.
-  ```
-- Report: `Deferred — manual merge required`.
-
-## Step 4: Update status table
-
-After processing all files, display the final status table:
-
-```
-## Reapply Complete
-
-| # | File | Result |
-|---|------|--------|
-| 1 | {path} | Reapplied |
-| 2 | {path} | Skipped (already upstream) |
-| 3 | {path} | Kept new version |
-| 4 | {path} | Deferred (manual merge) |
-
-{reapplied_count} file(s) reapplied. {skipped_count} skipped. {deferred_count} deferred.
-```
-
-## Step 5: Cleanup option
-
-Ask:
-
-Use AskUserQuestion:
-- Question: "What would you like to do with the backup files in .planning/declare-local-patches/?"
-- Options:
-  - "Keep backups (preserve for reference)"
-  - "Remove backups (clean up patch directory)"
-
-**If user chooses "Remove backups":**
-
-```bash
-rm -rf .planning/declare-local-patches
-```
-
-Display: `Backup directory removed.`
-
-**If user chooses "Keep backups":**
-Display: `Backups preserved at .planning/declare-local-patches/`
-
-</process>
-
-<success_criteria>
-- [ ] backup-meta.json located and parsed
-- [ ] Version comparison shown (backed-up from vs current)
-- [ ] Each file diff previewed in plain language
-- [ ] User confirms action per file (keep mine / keep new / manual)
-- [ ] Chosen versions written correctly
-- [ ] Final status table shown
-- [ ] Cleanup option offered
-</success_criteria>

package/commands/declare/research.md

@@ -1,267 +0,0 @@
----
-description: Research how to implement a milestone (spawns 4 parallel researchers, then synthesizes)
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - Task
-argument-hint: "[M-XX]"
----
-
-Research how to implement a milestone by spawning 4 parallel researcher agents (stack, features, architecture, pitfalls) then synthesizing their findings into a unified RESEARCH.md.
-
-**Step 1: Load graph and validate milestone.**
-
-```bash
-node dist/declare-tools.cjs load-graph
-```
-
-Parse the JSON output. If it contains an `error` field, tell the user to run `/declare:init` first and stop.
-
-If `$ARGUMENTS` contains a milestone ID (e.g., `M-02`), use it directly. Otherwise, list all pending milestones and ask the user to specify one.
-
-Extract from the graph the milestone's `title`, `goal`, and which declaration IDs it `realizes` (e.g., `D-01`). If the milestone is not found, tell the user and stop.
-
-Note the milestone slug by converting the milestone title to lowercase with hyphens (e.g., "Milestone research pipeline" → "milestone-research-pipeline"). The milestone folder path is `.planning/milestones/M-XX-slug/`.
-
-**Step 2: Check for existing research.**
-
-```bash
-ls .planning/milestones/M-XX-slug/RESEARCH.md 2>/dev/null
-```
-
-If RESEARCH.md already exists:
-- Display: "RESEARCH.md already exists for M-XX. Options: 1) Re-research (overwrite), 2) View existing, 3) Cancel"
-- Wait for user choice before continuing.
-
-If it does not exist, continue.
-
-**Step 3: Check for existing CONTEXT.md.**
-
-```bash
-ls .planning/milestones/M-XX-slug/CONTEXT.md 2>/dev/null
-```
-
-If CONTEXT.md exists, it contains user decisions that constrain research. Load it and pass it to all researcher agents.
-
-**Step 4: Display research banner.**
-
-```
-## Researching: M-XX — [milestoneTitle]
-
-**Declares:** [declaration IDs and statements]
-**Goal:** [milestone goal or title]
-**Mode:** Parallel research (4 agents → synthesizer)
-
-Spawning 4 researchers: STACK, FEATURES, ARCHITECTURE, PITFALLS...
-```
-
-**Step 5: Spawn 4 parallel declare-researcher agents.**
-
-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). Each researcher Task is spawned with `model: "sonnet"`.
-
-**STACK researcher** (model: `sonnet`):
-
-```
-First, read agents/declare-researcher.md for your role and instructions.
-
-<research_domain>STACK</research_domain>
-
-<objective>
-Research the standard technology stack for implementing milestone M-XX: [milestoneTitle]
-
-Investigate: What libraries, frameworks, and tools form the standard stack for this domain? What versions are current? What are the "blessed" combinations experts use?
-</objective>
-
-<milestone_context>
-Milestone: M-XX — [milestoneTitle]
-Goal: [milestoneGoal]
-Realizes: [declarationIds and statements]
-[contextMdContent if exists]
-</milestone_context>
-
-<output>
-Write your findings to: .planning/milestones/M-XX-slug/STACK.md
-Use the RESEARCH.md structure from your instructions but title it "STACK Research".
-Do NOT commit — the synthesizer will commit everything together.
-</output>
-```
-
-**FEATURES researcher** (model: `sonnet`):
-
-```
-First, read agents/declare-researcher.md for your role and instructions.
-
-<research_domain>FEATURES</research_domain>
-
-<objective>
-Research the features and capabilities required to implement milestone M-XX: [milestoneTitle]
-
-Investigate: What capabilities are table stakes (must-have)? What are differentiators? What should be deferred to later milestones? What do users/implementers actually need?
-</objective>
-
-<milestone_context>
-Milestone: M-XX — [milestoneTitle]
-Goal: [milestoneGoal]
-Realizes: [declarationIds and statements]
-[contextMdContent if exists]
-</milestone_context>
-
-<output>
-Write your findings to: .planning/milestones/M-XX-slug/FEATURES.md
-Use the RESEARCH.md structure from your instructions but title it "FEATURES Research".
-Do NOT commit — the synthesizer will commit everything together.
-</output>
-```
-
-**ARCHITECTURE researcher** (model: `sonnet`):
-
-```
-First, read agents/declare-researcher.md for your role and instructions.
-
-<research_domain>ARCHITECTURE</research_domain>
-
-<objective>
-Research the architecture patterns for implementing milestone M-XX: [milestoneTitle]
-
-Investigate: What are the standard component structures? What data flows are typical? What design patterns do experts use? What project organization works best?
-</objective>
-
-<milestone_context>
-Milestone: M-XX — [milestoneTitle]
-Goal: [milestoneGoal]
-Realizes: [declarationIds and statements]
-[contextMdContent if exists]
-</milestone_context>
-
-<output>
-Write your findings to: .planning/milestones/M-XX-slug/ARCHITECTURE.md
-Use the RESEARCH.md structure from your instructions but title it "ARCHITECTURE Research".
-Do NOT commit — the synthesizer will commit everything together.
-</output>
-```
-
-**PITFALLS researcher** (model: `sonnet`):
-
-```
-First, read agents/declare-researcher.md for your role and instructions.
-
-<research_domain>PITFALLS</research_domain>
-
-<objective>
-Research common pitfalls and failure modes when implementing milestone M-XX: [milestoneTitle]
-
-Investigate: What do beginners get wrong? What causes rewrites? What performance, security, or correctness traps exist? What should never be hand-rolled?
-</objective>
-
-<milestone_context>
-Milestone: M-XX — [milestoneTitle]
-Goal: [milestoneGoal]
-Realizes: [declarationIds and statements]
-[contextMdContent if exists]
-</milestone_context>
-
-<output>
-Write your findings to: .planning/milestones/M-XX-slug/PITFALLS.md
-Use the RESEARCH.md structure from your instructions but title it "PITFALLS Research".
-Do NOT commit — the synthesizer will commit everything together.
-</output>
-```
-
-Use one Task tool call per researcher. Spawn all 4 in the same response.
-
-**Step 6: After all 4 researchers complete, display interim summary.**
-
-```
-### Research Phase Complete
-
-| Domain | Status | Key Finding |
-|--------|--------|-------------|
-| STACK | Done | [brief summary from agent return] |
-| FEATURES | Done | [brief summary from agent return] |
-| ARCHITECTURE | Done | [brief summary from agent return] |
-| PITFALLS | Done | [brief summary from agent return] |
-
-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** (model: `sonnet`).
-
-```
-First, read agents/declare-research-synthesizer.md for your role and instructions.
-
-<objective>
-Synthesize the 4 research files for milestone M-XX: [milestoneTitle] into a unified RESEARCH.md.
-</objective>
-
-<milestone_context>
-Milestone: M-XX — [milestoneTitle]
-Goal: [milestoneGoal]
-Realizes: [declarationIds and statements]
-Milestone folder: .planning/milestones/M-XX-slug/
-</milestone_context>
-
-<research_files>
-- .planning/milestones/M-XX-slug/STACK.md
-- .planning/milestones/M-XX-slug/FEATURES.md
-- .planning/milestones/M-XX-slug/ARCHITECTURE.md
-- .planning/milestones/M-XX-slug/PITFALLS.md
-</research_files>
-
-<output>
-Write synthesized output to: .planning/milestones/M-XX-slug/RESEARCH.md
-Commit all research files (the 4 domain files + RESEARCH.md) together:
-  node dist/declare-tools.cjs commit "docs(M-XX): complete milestone research" --files .planning/milestones/M-XX-slug/
-</output>
-```
-
-Use one Task tool call for the synthesizer.
-
-**Step 8: Present results.**
-
-After the synthesizer returns `## SYNTHESIS COMPLETE`:
-
-```
-## Research Complete: M-XX — [milestoneTitle]
-
-**Files created:**
-- .planning/milestones/M-XX-slug/STACK.md
-- .planning/milestones/M-XX-slug/FEATURES.md
-- .planning/milestones/M-XX-slug/ARCHITECTURE.md
-- .planning/milestones/M-XX-slug/PITFALLS.md
-- .planning/milestones/M-XX-slug/RESEARCH.md
-
-**Overall confidence:** [from synthesizer]
-
-### Key Findings
-[3-5 bullets from synthesizer executive summary]
-
-### Planning Implications
-[Suggested action groups from synthesizer]
-
-**Next step:** Run `/declare:actions M-XX` to derive action plans informed by this research.
-```
-
-**Error handling:**
-
-- If `load-graph` returns an error: stop and ask user to run `/declare:init`.
-- If the milestone folder does not exist: run `mkdir -p .planning/milestones/M-XX-slug/` before spawning researchers.
-- If a researcher agent fails: log the failure, continue with the other 3 researchers, then inform the synthesizer about the missing file.
-- If synthesis is blocked: display the synthesizer's `## SYNTHESIS BLOCKED` message and ask the user how to proceed.
-- If RESEARCH.md already exists and user chose to re-research: the synthesizer will overwrite it.
-
-**Key patterns:**
-
-- 4 parallel researchers run concurrently for speed (stack, features, architecture, pitfalls).
-- Researchers write domain files but do NOT commit.
-- Synthesizer reads all 4 files, writes RESEARCH.md, and commits everything in one shot.
-- Research informs `/declare:actions` planning — always suggest it as next step.
-- CONTEXT.md (from `/declare:discuss`) constrains research when present.
-- Milestone folder path follows `.planning/milestones/M-XX-slug/` convention.
-- Use repo-relative paths in all file references and agent prompts.

package/commands/declare/resume.md

@@ -1,146 +0,0 @@
----
-name: declare:resume
-description: Restore full project context from a previous session and route to the next action
-allowed-tools:
-  - Read
-  - Bash
-  - Glob
-  - Grep
----
-
-Restore project context from a previous session and route to the appropriate next action.
-
-**Step 1: Check for handoff file.**
-
-Check whether `.continue-here.md` exists at the project root:
-
-```bash
-ls .continue-here.md 2>/dev/null && echo "found" || echo "not found"
-```
-
-**Step 2a: If `.continue-here.md` exists — restore from handoff.**
-
-Read `.continue-here.md`.
-
-Display its contents in a clean, structured format:
-
-```
-## Resuming from Saved Context
-
-**Paused at:** [Paused timestamp from file]
-**Position:** [Position from file]
-
-### Active Milestone
-
-[Active milestone details from file]
-
-### Remaining Actions
-
-[Remaining actions list from file]
-
-### Decisions Made Last Session
-
-[Decisions from file]
-
-### Blockers
-
-[Blockers from file]
-```
-
-Then run `load-graph` to get fresh action statuses (actions may have changed since the pause):
-
-```bash
-node dist/declare-tools.cjs load-graph
-```
-
-If graph loads successfully, cross-reference: if any actions listed as PENDING in `.continue-here.md` are now DONE in the graph, note that:
-
-```
-Note: Since pausing, [A-XX] has been completed.
-```
-
-Proceed to Step 3 (routing).
-
-**Step 2b: If `.continue-here.md` does not exist — load from STATE.md.**
-
-Run:
-
-```bash
-node dist/declare-tools.cjs get-state
-```
-
-```bash
-node dist/declare-tools.cjs load-graph
-```
-
-If `get-state` returns an error (STATE.md not found):
-
-```
-No project state found. Run /declare:new-project to initialize.
-```
-
-Then stop.
-
-Display the state context:
-
-```
-## Resuming from STATE.md
-
-**Current Position:** [currentPosition]
-**Last Activity:** [most recent session history entry, if any]
-
-### Recent Work
-
-[recentWork from STATE.md]
-
-### Decisions
-
-[decisions from STATE.md, or "(none recorded)"]
-```
-
-Proceed to Step 3 (routing).
-
-**Step 3: Route to next action.**
-
-Evaluate the current project state and present the most relevant next step:
-
-**Route A — Pending actions on active milestone:**
-- "Ready to continue [M-XX] — [N] actions remaining."
-- Offer: "`/declare:execute [M-XX]` to continue"
-
-**Route B — Active milestone fully complete, not yet verified:**
-- "[M-XX] has all actions done but is not yet verified."
-- Offer: "`/declare:verify [M-XX]` to verify milestone truth"
-
-**Route C — Blocker recorded:**
-- "A blocker was recorded: [blocker text]"
-- Offer options: "Resolve it manually, then run `/declare:execute [M-XX]`" or "`/declare:status` to review the graph"
-
-**Route D — No active milestone:**
-- "No active milestone found."
-- Offer: "`/declare:new-cycle` to plan next milestone" or "`/declare:status` to review graph"
-
-**Route E — No project initialized:**
-- "Project not initialized."
-- Offer: "`/declare:new-project` to initialize"
-
-Present the route as a clear, single recommendation with an alternative if applicable.
-
-**Step 4: Record session resumption.**
-
-```bash
-node dist/declare-tools.cjs record-session --stopped-at "Resumed — [currentPosition]"
-```
-
-Do not display the output of this command.
-
-**Step 5: Clean up handoff file (if used).**
-
-If `.continue-here.md` was used in Step 2a and routing shows work is continuing normally, offer:
-
-```
-The .continue-here.md handoff file can be removed once you are fully resumed.
-Run: git rm .continue-here.md && git commit -m "chore: resume work — remove handoff file"
-```
-
-Do not remove it automatically — leave that to the user.

package/commands/declare/set-profile.md

@@ -1,66 +0,0 @@
----
-description: Switch model profile for Declare agents (quality/balanced/budget)
-argument-hint: <profile>
-allowed-tools:
-  - Read
-  - Bash
----
-
-Switch the model profile used by Declare agents. Controls which Claude model each agent uses, balancing output quality vs token spend.
-
-**Step 1: Validate the profile argument.**
-
-Parse `$ARGUMENTS` to extract the profile name. It must be one of: `quality`, `balanced`, `budget`.
-
-If the argument is missing or invalid, display the usage error and the profile table below, then stop.
-
-```
-Usage: /declare:set-profile <profile>
-
-Profiles:
-  quality   — claude-opus-4-5 for all agents
-  balanced  — claude-sonnet-4-5 for execution, claude-opus-4-5 for planning
-  budget    — claude-haiku-3-5 for execution, claude-sonnet-4-5 for planning
-```
-
-**Step 2: Read current profile.**
-
-```bash
-node dist/declare-tools.cjs config-get model_profile
-```
-
-Extract the current value (default "quality" if key not found).
-
-**Step 3: Apply the new profile.**
-
-```bash
-node dist/declare-tools.cjs config-set --key model_profile --value <profile>
-```
-
-If the command fails, display the error and stop.
-
-**Step 4: Display confirmation.**
-
-Show a confirmation with the model table:
-
-```
-Profile switched: [old] → [new]
-
-Model assignments for "[new]" profile:
-
-  Agent         Model
-  ───────────────────────────────────────────────
-  Planner       [planner model]
-  Plan-checker  [plan-checker model]
-  Executor      [executor model]
-  Verifier      [verifier model]
-  Researcher    [researcher model]
-
-Use /declare:settings to configure additional workflow options.
-```
-
-Model assignments by profile:
-
-- **quality**: all agents use `claude-opus-4-5`
-- **balanced**: planner=`claude-opus-4-5`, plan-checker=`claude-opus-4-5`, executor=`claude-sonnet-4-5`, verifier=`claude-sonnet-4-5`, researcher=`claude-opus-4-5`
-- **budget**: planner=`claude-sonnet-4-5`, plan-checker=`claude-sonnet-4-5`, executor=`claude-haiku-3-5`, verifier=`claude-haiku-3-5`, researcher=`claude-sonnet-4-5`