devflow-kit 3.11.0 → 3.12.0

package/src/assets/commands/bug-analysis.mds

@@ -1,5 +1,5 @@
 ---
-description: Proactive bug finding with static and semantic analysis — hunts real bugs in changed code before merge
+description: Proactive bug finding in changed code before merge, with static and semantic analysis
 output-dir: dist/commands
 ---
 @import { knowledge_load } from "./_partials/_knowledge.mds"
@@ -9,8 +9,6 @@ output-dir: dist/commands
 @import "./_partials/_settings.mds" as settings
 # Bug Analysis Command
 
-Run a proactive bug analysis on the current branch: static analysis tools and parallel semantic analyzers, synthesized into one bug report.
-
 ## Usage
 
 `/bug-analysis [--full] [--no-static]`: `--full` ignores incremental state; `--no-static` skips static analysis.
@@ -224,9 +222,7 @@ Pick the focus analyzers from `CHANGED_FILES` (Step 2b; do not re-run `git diff`
 **Requires:** DIFF_RANGE, ANALYSIS_DIR, ACTIVE_FOCUSES, STATIC_FINDINGS, ACCEPTANCE_RULES, PLAN_CONTEXT, FEATURE_KNOWLEDGE
 <!-- curation:end -->
 
-Spawn ALL active Debug agents **in a single message** (parallel, NOT background):
-
-For each active focus, spawn:
+Spawn one Debug agent for each active focus, all in a single message (parallel, not background):
 ```
 Agent(subagent_type="Debug", run_in_background=false):
 "Analyze focusing on {focus}.
@@ -313,7 +309,7 @@ Seven phases: Phase 1 to Phase 7.
 |------|----------|
 | Rebase invalidates `.last-analysis-head` SHA | `git cat-file -t` check fails → fallback to full diff |
 | Zero changed files in DIFF_RANGE with exit 0 | Stop: "No changes to analyze." |
-| `--full` flag | Bypass incremental detection (Step 2a), run full diff from base |
+| `--full` flag | Step 2a takes the full-range path |
 | A scanner did not run or did not complete | Name the tool and why in `STATIC_FINDINGS`, not `(none)`; a tool that did not complete keeps the marker |
 
 ## Resolve Compatibility

package/src/assets/commands/code-review.mds

@@ -1,5 +1,5 @@
 ---
-description: Comprehensive branch review using specialized sub-agents for PR readiness
+description: Branch review by specialized agents for PR readiness
 output-dir: dist/commands
 ---
 @import { knowledge_load } from "./_partials/_knowledge.mds"
@@ -18,12 +18,7 @@ Run a comprehensive code review of the current branch by spawning parallel revie
 
 ## Usage
 
-```
-/code-review           (review current branch — or all worktrees if multiple found)
-/code-review #42       (review specific PR)
-/code-review --full    (force full-branch review, ignore previous review state)
-/code-review --path /path/to/worktree  (review a specific worktree only)
-```
+`/code-review` (the current branch, or every reviewable worktree), `/code-review #42` (one PR), `--full` (ignore the previous review state), `--path <worktree>` (one worktree only).
 
 ## Phases
 
@@ -306,7 +301,7 @@ The core, database, dependencies, documentation and compliance focuses, and ever
 
 {{decisions_load()}}
 <!-- curation:on -->
-This produces a compact index of active ADR/PF entries. Pass `DECISIONS_CONTEXT` to all Review agents as one shared slice, cut over the diff's files. Review agents use `devflow:apply-decisions` to Read full entry bodies on demand.
+Pass `DECISIONS_CONTEXT` to all Review agents as one shared slice, cut over the diff's files.
 
 <!-- curation:end -->
 {{knowledge_load()}}
@@ -354,11 +349,9 @@ Spawn Review agents **in a single message**, one per focus in REVIEW_FOCUS_LIST
 | documentation | conditional | devflow:documentation | diff.patch |
 | compliance | diff-driven | devflow:compliance | diff.patch |
 
-Review agent count: `code` runs 8 core +1-12 at `full`, up to 2 fewer at `standard`, 3-4 at lean; a reduced class or a mix runs 2-6.
-
 {{compliance_focus_inject()}}
 
-Each Review agent invocation (all in one message, **NOT background**):
+Each Review agent invocation:
 ```
 Agent(subagent_type="Review", run_in_background=false):
 "Review focusing on {focus}. Load the pattern skill via the Skill tool: Skill(skill="devflow:{focus}").
@@ -455,35 +448,21 @@ Per worktree, after successful completion:
 
 ```
 /code-review
-│
 <!-- compliance:on -->
 ├─ Phase 0: Worktree Discovery & Pre-flight, Steps 0a-0f (Git agent per worktree, parallel)
 <!-- compliance:off -->
 ├─ Phase 0: Worktree Discovery & Pre-flight, Steps 0a-0e (Git agent per worktree, parallel)
 <!-- compliance:end -->
 │  ├─ Step 0b: Resolve the compliance lens and gate level
-│
-├─ Per worktree (SEQUENTIAL):
-│  │
-│  ├─ Phase 1: Analyze changed files
-│  │  ├─ Classify the diff (paths.txt → DIFF_CLASS)
-│  │  ├─ Choose the focuses
-│  │  └─ Write diff.patch and diff-{focus}.patch
-│  │
-│  ├─ Phase 2: Reviews (PARALLEL within worktree), one per REVIEW_FOCUS_LIST focus
-│  │  ├─ code: core (diff.patch), language (diff-{focus}.patch), conditional
-│  │  └─ docs-only / tests-only / lockfile-only: the reduced set (diff.patch)
-│  │
+└─ Per worktree (SEQUENTIAL):
+   ├─ Phase 1: Classify the diff, choose the focuses, write diff.patch and diff-{focus}.patch
+   ├─ Phase 2: Reviews (PARALLEL): code, or docs-only / tests-only / lockfile-only (the reduced set)
 <!-- compliance:on -->
-│  ├─ Phase 3: Synthesis → Review Comment (SEQUENTIAL within worktree)
-│  │  ├─ Step 3a: Synthesize agent (mode: review, writes review-summary.md)
-│  │  └─ Step 3b: Git agent (post-review-summary)
+   ├─ Phase 3: Synthesize agent, then Git agent (post-review-summary)
 <!-- compliance:off -->
-│  ├─ Phase 3: Synthesis → Review Summary (SEQUENTIAL within worktree)
-│  │  └─ Step 3a: Synthesize agent (mode: review, writes review-summary.md)
+   ├─ Phase 3: Synthesize agent (writes review-summary.md)
 <!-- compliance:end -->
-│  │
-│  └─ Phase 4: Write .last-review-head + display results
+   └─ Phase 4: Write .last-review-head + display results
 ```
 
 ## Edge Cases
@@ -492,7 +471,7 @@ Per worktree, after successful completion:
 |------|----------|
 | `--full` in multi-worktree mode | Applies to all worktrees (global modifier). It sets the diff range, never the gate level |
 <!-- compliance:on -->
-| Review comment already posted | Git agent matches its own marker on the `{cycle, timestamp}` pair → skip silently (D7) |
+| Review comment already posted | Git agent skips it (D7) |
 <!-- compliance:end -->
 | Docs-only diff | Its Step 1.1 set, narrowed by level |
 | Tests-only diff | Its Step 1.1 set, narrowed by level |
@@ -516,4 +495,4 @@ Per worktree, after successful completion:
 2. **Parallel, not background** - Multiple agents in one message, but `run_in_background=false` so phases complete before proceeding
 3. **Git agent for git work** - All git operations go through Git agent, except the exceptions named in Principle 1; its writes print nothing
 4. **Honest reporting** - Display agent outputs directly
-5. **Incremental by default** - Only review new changes unless `--full` specified
+5. **Fewest turns** - Send calls that need no output of each other in one message: the Step 0a listing with the Step 0b-ii script; at `standard` or `lean`, the Step 1.2b directory print with the Step 1.1 listing, and its Read with the `paths.txt` Read; the Phase 1b git calls, each under its own condition, with the Step 1.3 writes

package/src/assets/commands/debug.mds

@@ -1,5 +1,5 @@
 ---
-description: Debug issues using competing hypothesis investigation with parallel agents
+description: Debug issues with parallel agents on competing hypotheses
 output-dir: dist/commands
 ---
 @import { knowledge_writeback } from "./_partials/_knowledge.mds"
@@ -9,8 +9,6 @@ output-dir: dist/commands
 @import "./_partials/_compliance.mds" as compliance
 # Debug Command
 
-Investigate bugs by spawning parallel agents, each pursuing a different hypothesis. Evidence is aggregated and synthesized to identify the root cause.
-
 ## Usage
 
 ```
@@ -27,10 +25,7 @@ What follows `/debug` is bound once, here. Every later step names it `COMMAND_IN
 $ARGUMENTS
 </command-input>
 
-`COMMAND_INPUT` is one of:
-- Bug description: "login fails after session timeout"
-- Issue reference: "#42"
-- Empty: use conversation context
+An empty `COMMAND_INPUT` means: use the conversation context.
 
 ## Phases
 
@@ -57,7 +52,7 @@ Phase 7 passes `COMPLIANCE_DIRECTIVE` to the Code agent that implements the fix,
 The orchestrator uses `DECISIONS_CONTEXT` locally when generating hypotheses (Phase 2) — prior pitfalls and decisions can suggest specific root causes to investigate. Follow `devflow:apply-decisions` to Read full entry bodies on demand. **Do NOT pass `DECISIONS_CONTEXT` to Explore investigators** — decisions context stays in the orchestrator; investigators examine code directly.
 
 <!-- curation:end -->
-**No up-front feature knowledge load** — debug investigation workers read code directly to avoid confirmation bias. Feature knowledge is only written back at the end if the investigation surfaced durable, cross-cutting knowledge.
+**No up-front feature knowledge load** — debug investigation workers read code directly to avoid confirmation bias. Write back only if the investigation found durable, cross-cutting knowledge.
 
 ### Phase 2: Context Gathering
 
@@ -222,47 +217,11 @@ Ask user via AskUserQuestion: "Want me to implement this fix?"
 
 {{knowledge_writeback()}}
 
-## Architecture
-
-```
-/debug (orchestrator)
-│
-<!-- curation:on -->
-├─ Phase 1: Load Decisions Index (Orchestrator-Local)
-<!-- curation:off -->
-├─ Phase 1: Resolve Settings
-<!-- curation:end -->
-│  └─ No up-front feature knowledge load (avoids confirmation bias in investigators)
-│
-├─ Phase 2: Context gathering
-│  └─ Git agent (fetch issue, if #N provided)
-│
-├─ Phase 3: Parallel investigation
-│  └─ 3-5 Explore agents, one per hypothesis (single message)
-│
-├─ Phase 4: Converge
-│  └─ Validate confirmed hypotheses, unify partials, or generate second-round
-│
-├─ Phase 5: Synthesize
-│  └─ Synthesize agent aggregates and compares findings
-│
-├─ Phase 6: Root cause report with confidence level
-│
-├─ Phase 7: Offer Fix
-│  └─ AskUserQuestion → Code agent (fix) + Polish agent, or done
-│
-└─ Feature Knowledge Write-Back (Conditional)
-   └─ Knowledge agent (if investigation surfaced durable cross-cutting knowledge)
-```
-
 ## Principles
 
 1. **Competing hypotheses** - Never investigate a single theory; always have alternatives
-2. **Parallel execution** - All investigators run simultaneously for speed
-3. **Evidence-based** - Every claim requires file:line references
-4. **Honest uncertainty** - If no hypothesis survives, report that clearly
-5. **Convergence validation** - Confirmed hypotheses get additional validation to prevent confirmation bias
-6. **No pre-loaded knowledge in sub-agents** - Investigators read code fresh to avoid confirmation bias; feature knowledge write-back happens only after investigation completes
+2. **Evidence-based** - Every claim requires file:line references
+3. **Honest uncertainty** - If no hypothesis survives, report that clearly
 
 ## Error Handling
 
@@ -270,4 +229,3 @@ Ask user via AskUserQuestion: "Want me to implement this fix?"
 - If all hypotheses are disproved: report "No root cause identified" with investigation summary
 - If an investigator errors: continue with remaining results, note the gap
 - If convergence validation contradicts the original confirmation: downgrade confidence and report contradicting evidence
-- If user declines fix: done — report stands as documentation