cclaw-cli 0.51.30 → 1.0.0

package/dist/content/status-command.js

@@ -45,7 +45,7 @@ a read-only command.
 
 ## Algorithm
 
-1. Read \`${flowPath}\`. If missing → report **BLOCKED: flow state absent** and suggest \`cclaw init\`.
+1. Read \`${flowPath}\`. If missing → report **BLOCKED: flow state absent** and suggest \`npx cclaw-cli init\`.
 2. Read \`${delegationPath}\`. Missing → treat all mandatory delegations as pending.
 3. Render **time in stage** as \`(unknown)\` unless visible conversation or
    artifact handoff context gives a timestamp.
@@ -81,7 +81,7 @@ a read-only command.
     - If current stage has unmet gates -> \`/cc\` to resume.
     - If a mandatory delegation is missing evidence -> dispatch the worker/reviewer or waive with rationale; do not advance silently.
     - If a TDD blocker taxonomy code is present (\`NO_SOURCE_CONTEXT\`, \`NO_TEST_SURFACE\`, \`NO_IMPLEMENTABLE_SLICE\`, \`RED_NOT_EXPRESSIBLE\`, \`NO_VCS_MODE\`) -> name the blocker and the rewind/config route.
-    - If review is blocked by critical findings -> show \`cclaw internal rewind tdd "review_blocked_by_critical <finding-ids>"\` plus the later \`cclaw internal rewind --ack tdd\`.
+    - If review is blocked by critical findings -> show \`npx cclaw-cli internal rewind tdd "review_blocked_by_critical <finding-ids>"\` plus the later \`npx cclaw-cli internal rewind --ack tdd\`.
     - If closeout substate is non-idle -> \`/cc\` to continue the chain.
     - If current stage is complete -> \`/cc\` to advance (or report "Flow complete" if terminal).
 
@@ -89,7 +89,7 @@ a read-only command.
 
 - Keep output compact (≤ 40 lines) — status, not narrative.
 - Start with the same operator rows as \`/cc\` when possible:
-  \`Current\`, \`Stage\`, \`Progress\`, \`Gates\`, \`Delegations\`, \`Risks\`, \`Blocked by\`, \`Next\`, \`Evidence needed\`. Use labels like \`gate: tdd_green_full_suite\`, \`delegation proof: reviewer evidenceRefs\`, and \`closeout: compound_review\` instead of raw JSON tone.
+  \`Current\`, \`Stage\`, \`Progress\`, \`Gates\`, \`Delegations\`, \`Risks\`, \`Blocked by\`, \`Next\`, \`Evidence needed\`. Use labels like \`gate: tdd_green_full_suite\`, \`delegation proof: reviewer evidenceRefs\`, and \`closeout: post_ship_review\` instead of raw JSON tone.
 - When blocked, include a plain-English action block:
   \`Current: <stage or closeout substate>\`; \`Blocked by: <gate/delegation/blocker code>\`; \`Next: <exact command or managed remediation>\`; \`Evidence needed: <artifact/test/review/delegation evidence>\`.
 - Report counts, not full artifact contents. Include active subagent count from \`${subagentsPath()}\` and proof gaps from \`${delegationEventsPath()}\` when present. Convert gate/delegation state into human labels: \`passed\`, \`blocked\`, \`missing proof\`, \`waived with reason\`, \`stale\`, \`ready to advance\`, or the closeout substate label.
@@ -98,12 +98,12 @@ a read-only command.
 
 ## Anti-patterns
 
-- Rebuilding trace-matrix or running doctor from \`/cc-view status\` — those belong to dedicated tools.
+- Re-running heavy artifact workflows from \`/cc-view status\` — status is read-only and should not trigger sync or mutation paths.
 - Treating absence of delegation log as "all delegations complete".
 - Collapsing \`◎ missing-evidence\` into \`✓ completed\` — role-switch gaps must stay
   visible so the stage cannot advance silently.
 - Omitting the closeout row when \`shipSubstate !== "idle"\`; it is the only signal
-  that tells the user why \`/cc\` is about to run retro/compound/archive.
+  that tells the user why \`/cc\` is about to run post-ship closeout/archive.
 - Mutating state to "clean up" during a status check.
 `;
 }

package/dist/content/subagent-context-skills.js

@@ -112,11 +112,166 @@ Use after the default reviewer/security-reviewer passes when repo signals identi
 - Keep the default general reviewer pass intact; this is additive context, not a replacement.
 `;
 }
+function criticMultiPerspectiveSkill() {
+    return `${skillFrontmatter("critic-multi-perspective", "Multi-perspective critic protocol with pre-commitment predictions and realist checks.")}# Critic Multi-Perspective Pass
+
+Use with the \`critic\` delegation in \`brainstorm\`, \`scope\`, and \`design\`.
+
+## Required Output
+
+- Before investigation, emit \`predictions[]\` with explicit hypotheses.
+- Analyze through context-aware angles:
+  - plan/spec/scope: executor, stakeholder, skeptic
+  - design/code: security, operator, new-hire
+- Include a dedicated gap analysis (what is missing, not only what is wrong).
+- Move low-confidence concerns (<=4/10) into \`openQuestions[]\`.
+- For every critical/major concern, include a \`realistCheckResults[]\` verdict.
+- End with \`predictionsValidated[]\` mapping each prediction to confirmed/disproven.
+
+## Guardrails
+
+- Do not block solely on low-confidence concerns.
+- Suppress or downgrade implausible critical findings during realist checks.
+- Escalate to adversarial mode when reviewers disagree, confidence is low, or trust boundaries are involved.
+`;
+}
+function documentCoherencePassSkill() {
+    return `${skillFrontmatter("document-coherence-pass", "Consistency-focused pass for cross-section coherence in spec/plan/design documents.")}# Document Coherence Pass
+
+Use with \`coherence-reviewer\` on spec/plan/design artifacts.
+
+## Required Output
+
+- List contradictions between sections and where they occur.
+- Flag terminology drift where one concept is named inconsistently.
+- Flag broken internal references, forward references, and dependency narrative mismatches.
+- Return calibrated findings with concrete anchors and one-line corrections.
+
+## Guardrails
+
+- Do not score overall quality; focus on consistency and coherence only.
+- Do not invent contradictions without citation to concrete sections/lines.
+`;
+}
+function documentScopeGuardSkill() {
+    return `${skillFrontmatter("document-scope-guard", "Complexity and minimum-change guardrail for scope/plan/design documents.")}# Document Scope Guard
+
+Use with \`scope-guardian-reviewer\` when expansion pressure or abstraction creep is likely.
+
+## Required Output
+
+- Surface where existing solutions can be reused instead of adding new abstractions.
+- Identify minimum-change alternative when current proposal is broader than needed.
+- Call out complexity smells (speculative generic utilities, framework-ahead-of-need structures).
+- Return calibrated findings with explicit impact on scope boundaries.
+
+## Guardrails
+
+- Challenge unnecessary breadth, but do not silently shrink required user outcomes.
+- Tie every scope reduction recommendation to a concrete cost/risk rationale.
+`;
+}
+function documentFeasibilityPassSkill() {
+    return `${skillFrontmatter("document-feasibility-pass", "Feasibility validation for runtime/resource/dependency assumptions in plan/design artifacts.")}# Document Feasibility Pass
+
+Use with \`feasibility-reviewer\` on plan/design docs that rely on runtime or operational assumptions.
+
+## Required Output
+
+- Enumerate resource/time/runtime assumptions and whether they are validated.
+- Flag external dependency availability or reliability risks.
+- Flag rollout assumptions that are not backed by operational evidence.
+- Return PASS/PASS_WITH_GAPS/FAIL/BLOCKED rationale grounded in cited assumptions.
+
+## Guardrails
+
+- Focus on practical viability; do not redesign architecture unless feasibility is blocked.
+- Distinguish unknowns that need evidence from hard blockers that require rework.
+`;
+}
+function reviewPerfLensSkill() {
+    return `${skillFrontmatter("review-perf-lens", "Optional deep performance lens for large or high-risk review surfaces.")}# Review Performance Lens
+
+Use as an optional follow-up lens when the default reviewer pass flags non-trivial performance risk.
+
+## Required Output
+
+- Hot-path or algorithmic-risk summary with touched files.
+- Potential regressions and estimated blast radius.
+- Clear NO_IMPACT or FOUND_<n> result with evidence.
+
+## Guardrails
+
+- Run only when justified by diff scope or explicit trigger.
+- Do not replace the mandatory reviewer pass; this lens is additive.
+`;
+}
+function reviewCompatLensSkill() {
+    return `${skillFrontmatter("review-compat-lens", "Optional compatibility lens for high-risk API/config/schema changes.")}# Review Compatibility Lens
+
+Use as an optional follow-up lens when contracts, config, persistence schema, or generated clients might break consumers.
+
+## Required Output
+
+- Surface inventory: APIs/config/schema/CLI/client contracts touched.
+- Compatibility risk assessment (backward, forward, migration path).
+- Clear NO_IMPACT or FOUND_<n> result with evidence.
+
+## Guardrails
+
+- Focus on externally observable contracts and migration safety.
+- Do not duplicate baseline reviewer findings verbatim.
+`;
+}
+function reviewObservabilityLensSkill() {
+    return `${skillFrontmatter("review-observability-lens", "Optional observability lens for diagnosability and rollback safety.")}# Review Observability Lens
+
+Use as an optional follow-up lens when failure diagnosis, telemetry, or operational rollback confidence is at risk.
+
+## Required Output
+
+- Signals checked: logs, metrics, traces, alerts, debug handles.
+- Gaps that could block diagnosis or rollback during incidents.
+- Clear NO_IMPACT or FOUND_<n> result with evidence.
+
+## Guardrails
+
+- Escalate only diagnosis-impacting gaps; avoid style-only telemetry suggestions.
+- Keep scope tied to touched code paths and rollout-critical behavior.
+`;
+}
+function architectCrossStageVerificationSkill() {
+    return `${skillFrontmatter("architect-cross-stage-verification", "Cross-stage cohesion verification before ship finalization.")}# Architect Cross-Stage Verification
+
+Use with the \`architect\` delegation in the \`ship\` stage.
+
+## Required Output
+
+- Read scope/design/spec/plan/review artifacts plus shipped diff/code surfaces.
+- Validate that locked decisions and acceptance mappings still match shipped behavior.
+- Flag drift between intended architecture and implemented boundaries.
+- Return exactly one status token: \`CROSS_STAGE_VERIFIED\`, \`DRIFT_DETECTED\`, or \`BLOCKED\`.
+- Provide evidence refs for every drift claim and identify the smallest corrective route.
+
+## Guardrails
+
+- Do not defer unresolved drift to post-ship follow-up without explicit waiver.
+- If evidence is insufficient to verify cohesion, return \`BLOCKED\` with missing inputs.
+`;
+}
 export const SUBAGENT_CONTEXT_SKILLS = {
     "tdd-cycle-evidence": tddCycleEvidenceSkill(),
     "review-spec-pass": reviewSpecPassSkill(),
     "security-audit": securityAuditSkill(),
     "adversarial-review": adversarialReviewSkill(),
     "receiving-code-review": receivingCodeReviewSkill(),
-    "stack-aware-review": stackAwareReviewSkill()
+    "stack-aware-review": stackAwareReviewSkill(),
+    "critic-multi-perspective": criticMultiPerspectiveSkill(),
+    "document-coherence-pass": documentCoherencePassSkill(),
+    "document-scope-guard": documentScopeGuardSkill(),
+    "document-feasibility-pass": documentFeasibilityPassSkill(),
+    "review-perf-lens": reviewPerfLensSkill(),
+    "review-compat-lens": reviewCompatLensSkill(),
+    "review-observability-lens": reviewObservabilityLensSkill(),
+    "architect-cross-stage-verification": architectCrossStageVerificationSkill()
 };

package/dist/content/subagents.d.ts

@@ -1,8 +1,3 @@
 export declare function subagentDrivenDevSkill(): string;
 export declare function parallelAgentsSkill(): string;
-/**
- * Returns markdown fragments augmenting each specialist persona with Task tool
- * delegation guidance. Combine with the existing `body` field from `core-agents.ts`.
- */
-export declare function enhancedAgentBody(agentName: string): string;
 export declare function subagentsAgentsMdBlock(): string;

package/dist/content/subagents.js

@@ -5,25 +5,6 @@ import { conversationLanguagePolicyMarkdown } from "./language-policy.js";
  * specialist payloads. Cclaw materializes static instructions — this module does not
  * execute orchestration logic at install time beyond string assembly.
  */
-const SUBAGENT_AGENT_NAMES = [
-    "researcher",
-    "architect",
-    "spec-validator",
-    "slice-implementer",
-    "performance-reviewer",
-    "compatibility-reviewer",
-    "observability-reviewer",
-    "release-reviewer",
-    "planner",
-    "product-manager",
-    "critic",
-    "reviewer",
-    "security-reviewer",
-    "test-author",
-    "doc-updater",
-    "implementer",
-    "fixer"
-];
 const MARKDOWN_CODE_FENCE = "```";
 function formatAgentList(agents) {
     return agents.length > 0 ? agents.join(", ") : "none";
@@ -94,10 +75,10 @@ can enforce phase-appropriate write boundaries. Use separate workers only when t
 
 | Harness | Fallback | Delegation tool | Structured ask | Capability source |
 |---|---|---|---|---|
-| Claude | \`native\` | Task (named subagent_type) | AskUserQuestion | \`npx cclaw-cli doctor\` |
-| Cursor | \`generic-dispatch\` | Task (generic subagent_type: explore/generalPurpose/…) | AskQuestion | \`npx cclaw-cli doctor\` |
-| OpenCode | \`native\` | generated \`.opencode/agents/<agent>.md\` subagents via Task / \`@agent\` mention | \`question\` (permission-gated; \`permission.question: "allow"\`) | \`npx cclaw-cli doctor\` |
-| Codex | \`native\` | generated \`.codex/agents/<agent>.toml\` custom agents via native parallel subagent spawning | \`request_user_input\` (experimental; Plan / Collaboration mode) | \`npx cclaw-cli doctor\` |
+| Claude | \`native\` | Task (named subagent_type) | AskUserQuestion | \`npx cclaw-cli sync\` |
+| Cursor | \`generic-dispatch\` | Task (generic subagent_type: explore/generalPurpose/…) | AskQuestion | \`npx cclaw-cli sync\` |
+| OpenCode | \`native\` | generated \`.opencode/agents/<agent>.md\` subagents via Task / \`@agent\` mention | \`question\` (permission-gated; \`permission.question: "allow"\`) | \`npx cclaw-cli sync\` |
+| Codex | \`native\` | generated \`.codex/agents/<agent>.toml\` custom agents via native parallel subagent spawning | \`request_user_input\` (experimental; Plan / Collaboration mode) | \`npx cclaw-cli sync\` |
 
 **Dispatch rules driven by \`subagentFallback\`:**
 
@@ -143,10 +124,10 @@ Concrete per-stage rules so the controller does not have to guess which tier fit
 
 | Stage | Deep slot | Balanced slot(s) | Fast fan-out | Trigger to escalate |
 |---|---|---|---|---|
-| brainstorm | planner (only if ambiguity spans >1 module) | product-manager / critic when product value or premise is uncertain | run in-thread research playbooks | promote to \`balanced\` critic if the do-nothing path may beat the idea |
-| scope | planner (always) | product-manager / critic when mode changes user value or boundaries are soft | run \`research/git-history.md\` in-thread when churn is high | promote to \`balanced\` critic if scope mode is disputed |
+| brainstorm | planner (only if ambiguity spans >1 module) | product-discovery / critic when product value or premise is uncertain | run in-thread research playbooks | promote to \`balanced\` critic if the do-nothing path may beat the idea |
+| scope | planner (always) | product-discovery / critic when mode changes value, trajectory, or boundaries | run \`research/git-history.md\` in-thread when churn is high | promote to \`balanced\` critic if scope mode is disputed |
 | design | planner (always) | critic, security-reviewer, test-author when alternatives/trust/testability apply | run \`research/framework-docs-lookup.md\` + \`research/best-practices-lookup.md\` in-thread | escalate one specialist to \`deep\` only if a failure mode is Critical-severity |
-| spec | — | reviewer (if spec > 200 lines or multiple ACs) | — | escalate to \`deep\` only for spec ↔ design contradictions |
+| spec | — | spec-validator / spec-document-reviewer / reviewer (for long or high-risk specs) | — | escalate to \`deep\` only for spec ↔ design contradictions |
 | plan | planner (solo, always) | — | — | never fan out at plan stage; one owner for dependency graph |
 | tdd | — | ${formatAgentList(stageSummary("tdd").primaryAgents)} (per slice, carrying RED/GREEN/REFACTOR evidence) · reviewer (slice-local only when sliceReview triggers) | doc-updater (API surface changes) | escalate to \`deep\` only when a RED test cannot be expressed (design leak) |
 | review | — | ${formatAgentList(stageSummary("review").mandatoryAgents)} (both mandatory) | doc-updater for release-note drift checks | escalate a \`balanced\` reviewer to \`deep\` only when two reviewers disagree on severity |
@@ -174,6 +155,7 @@ Borrow the good part of Team/Ruflo-style orchestration without adding a swarm ru
 - **No parallel writes to adjacent surfaces.** If tasks may touch the same module, serialize them.
 - **Checkpoint before synthesis.** Each agent returns status, files inspected/changed, evidence, and blockers before the parent acts.
 - **Consensus is for hard calls only.** Use two reviewers when severity or architecture is disputed; otherwise one evidence-backed reviewer is enough.
+- **Multi-wave persistence uses the executing-waves skill.** For 2+ wave efforts, maintain \`.cclaw/wave-plans/\` and run carry-forward drift audits in brainstorm.
 
 ## Parallelization Decision Gate
 
@@ -404,6 +386,8 @@ ${conversationLanguagePolicyMarkdown()}
 
 Implementation that touches shared source trees must remain **sequential** unless you have proven disjoint filesystem ownership (rare) and an explicit merge protocol.
 
+When explicit bounded TDD fan-out is approved with parallel \`slice-implementer\` lanes, author \`.cclaw/artifacts/cohesion-contract.md\` + \`.json\` before launch and run \`integration-overseer\` after fan-in.
+
 ## When to Use
 
 - **Independent investigations** (perf vs correctness vs dependency hygiene) with separated code neighborhoods.
@@ -427,11 +411,13 @@ Implementation that touches shared source trees must remain **sequential** unles
 ## Dispatch Protocol
 
 1. **Identify independent problem domains** (no file overlap; no shared mutable working assumptions).
-2. **Craft one prompt per domain** with **full context pasted** — same HARD-GATE as SDD: no “go read X to learn why.”
-3. **Launch ALL agents in a single controller message** (multiple Task tool calls) so they start with comparable timelines.
-4. **Wait for all to return** before synthesis (avoid incremental confirmation bias).
-5. **Reconcile results:** deduplicate findings, merge overlaps, and **conflict-check** contradictions explicitly.
-6. **Run the full test suite after any code changes** — parallel analysis may propose edits; verification stays mandatory.
+2. **Author cohesion contract first** whenever fan-out touches shared interfaces or bounded parallel \`slice-implementer\` lanes.
+3. **Craft one prompt per domain** with **full context pasted** — same HARD-GATE as SDD: no “go read X to learn why.”
+4. **Launch ALL agents in a single controller message** (multiple Task tool calls) so they start with comparable timelines.
+5. **Wait for all to return** before synthesis (avoid incremental confirmation bias).
+6. **Run integration-overseer after fan-in** to verify touchpoints, boundary types, invariants, and integration-test outcomes.
+7. **Reconcile results:** deduplicate findings, merge overlaps, and **conflict-check** contradictions explicitly.
+8. **Run the full test suite after any code changes** — parallel analysis may propose edits; verification stays mandatory.
 
 ## Review Army Pattern (gstack)
 
@@ -642,6 +628,30 @@ Required output:
 - TESTABILITY_MAP: concrete test level and command/manual evidence per AC
 ${MARKDOWN_CODE_FENCE}
 
+`;
+}
+function specDocumentReviewerEnhancedBody() {
+    return `
+
+## Task Tool Delegation
+
+Use this payload for final spec-document quality checks before plan handoff:
+
+${MARKDOWN_CODE_FENCE}
+You are a spec-document-reviewer subagent.
+
+SPEC_ARTIFACT: {04-spec excerpt or full body}
+UPSTREAM_CONTEXT: {scope/design refs used by the spec}
+
+Required output:
+- DOCUMENT_VERDICT: PASS | PASS_WITH_GAPS | FAIL | BLOCKED
+- COMPLETENESS_CHECK: missing required sections or weakly populated rows
+- CONSISTENCY_CHECK: contradictions across ACs, assumptions, mapping, and approval
+- CLARITY_CHECK: ambiguity/placeholders/two-way wording to rewrite
+- SCOPE_FIT_CHECK: whether the artifact still maps to one coherent subsystem/plan slice
+- PATCH_RECOMMENDATIONS: minimal edits to make the spec plan-ready
+${MARKDOWN_CODE_FENCE}
+
 `;
 }
 function sliceImplementerEnhancedBody() {
@@ -808,6 +818,30 @@ Required output:
 - SCOPE_HANDOFF: one recommendation for hold/selective/expand/reduce
 ${MARKDOWN_CODE_FENCE}
 
+`;
+}
+function productStrategistEnhancedBody() {
+    return `
+
+## Task Tool Delegation
+
+Use this payload for expansion-mode scope strategy checks:
+
+${MARKDOWN_CODE_FENCE}
+You are a product-strategist subagent.
+
+SCOPE_MODE: {SCOPE EXPANSION|SELECTIVE EXPANSION}
+DECISION_CONTEXT: {scope contract excerpt + constraints + approved brainstorm direction}
+DEPTH: {standard|deep}
+
+Required output:
+- VISION_DELTA: 10x trajectory vs hold-scope baseline
+- EXPANSION_PROPOSALS: 2-3 concrete proposals with add/defer/skip recommendation
+- UPSIDE_AND_RISK: strategic upside, reversibility, and principal downside per proposal
+- TRAJECTORY_FIT: whether current architecture trajectory can absorb accepted expansions
+- FINAL_RECOMMENDATION: smallest high-leverage expansion set to lock now
+${MARKDOWN_CODE_FENCE}
+
 `;
 }
 function criticEnhancedBody() {
@@ -959,56 +993,6 @@ ${MARKDOWN_CODE_FENCE}
 
 `;
 }
-/**
- * Returns markdown fragments augmenting each specialist persona with Task tool
- * delegation guidance. Combine with the existing `body` field from `core-agents.ts`.
- */
-export function enhancedAgentBody(agentName) {
-    switch (agentName) {
-        case "researcher":
-            return researcherEnhancedBody();
-        case "architect":
-            return architectEnhancedBody();
-        case "spec-validator":
-            return specValidatorEnhancedBody();
-        case "slice-implementer":
-            return sliceImplementerEnhancedBody();
-        case "performance-reviewer":
-            return performanceReviewerEnhancedBody();
-        case "compatibility-reviewer":
-            return compatibilityReviewerEnhancedBody();
-        case "observability-reviewer":
-            return observabilityReviewerEnhancedBody();
-        case "release-reviewer":
-            return releaseReviewerEnhancedBody();
-        case "planner":
-            return plannerEnhancedBody();
-        case "product-manager":
-            return productManagerEnhancedBody();
-        case "critic":
-            return criticEnhancedBody();
-        case "reviewer":
-            return reviewerEnhancedBody();
-        case "security-reviewer":
-            return securityReviewerEnhancedBody();
-        case "test-author":
-            return testAuthorEnhancedBody();
-        case "doc-updater":
-            return docUpdaterEnhancedBody();
-        case "implementer":
-            return implementerEnhancedBody();
-        case "fixer":
-            return fixerEnhancedBody();
-        default:
-            return `
-
-## Task Tool Delegation
-
-_No enhanced Task template is defined for agent \`${agentName}\`._
-
-`;
-    }
-}
 export function subagentsAgentsMdBlock() {
     return `### Subagent Orchestration
 

package/dist/content/templates.d.ts

@@ -1,4 +1,4 @@
 export declare const ARTIFACT_TEMPLATES: Record<string, string>;
 export declare const RULEBOOK_MARKDOWN = "# Cclaw Rulebook\n\n## MUST_ALWAYS\n- Follow flow order: brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship\n- Require explicit user confirmation after plan before TDD\n- Keep evidence artifacts in `.cclaw/artifacts/`\n- Enforce RED before GREEN in TDD\n- Run two-layer review (spec_compliance and code_quality) before ship\n- Validate all inputs before processing \u2014 never trust external data without sanitization\n- Prefer immutable data patterns and pure functions where the language supports them\n- Follow existing repo conventions, patterns, and directory structure \u2014 match the codebase\n- Verify claims with fresh evidence: \"tests pass\" requires running tests in this message\n- Use conventional commits: `type(scope): description` (feat, fix, refactor, test, docs, chore)\n\n## MUST_NEVER\n- Skip RED phase and jump directly to GREEN in TDD\n- Ship with critical review findings\n- Start implementation during /brainstorm\n- Modify generated cclaw files manually when CLI can regenerate them\n- Commit `.cclaw/` or generated shim files\n- Expose secrets, tokens, API keys, or absolute system paths in agent output\n- Duplicate existing functionality without explicit justification \u2014 search before building\n- Bypass security checks, linting hooks, or type checking to \"move faster\"\n- Claim success (\"Done,\" \"All good,\" \"Tests pass\") without running verification in this message\n- Make changes outside the blast radius of the current task without user consent\n\n## DELEGATION\nWhen a task requires specialist knowledge (security audit, performance profiling, database review),\ndelegate to a specialized agent or skill if the harness supports it. The primary agent should:\n1. Identify the specialist domain\n2. Provide focused context (relevant files, the specific concern)\n3. Evaluate the specialist output before acting on it \u2014 do not blindly apply recommendations\n";
-export declare const CURSOR_WORKFLOW_RULE_MDC = "---\ndescription: cclaw workflow guardrails for Cursor agent sessions\nglobs:\n  - \"**/*\"\nalwaysApply: true\n---\n\n<!-- cclaw-managed-cursor-workflow-rule -->\n\n# Cclaw Workflow Guardrails\n\n## Activation Rule\n\nBefore responding to coding work:\n1. Read `.cclaw/state/flow-state.json`.\n2. Start with `/cc` or continue with `/cc`.\n3. If no software-stage flow applies, respond normally.\n\n## Stage Order\n\n`brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship`\n\nTrack-specific skips are allowed only when `flow-state.track` + `skippedStages` explicitly say so.\n\n## Task Classification\n\n| Class | Route |\n|---|---|\n| non-trivial software work | `/cc <idea>` |\n| trivial software fix | `/cc <idea>` (quick track) |\n| bugfix with repro | `/cc <idea>` and enforce RED-first in tdd |\n| pure question / non-software | direct answer (no stage flow) |\n\n## Command Surface\n\n- `/cc` = entry and resume.\n- `/cc` = only progression path.\n- Knowledge capture and recall use the `learnings` skill when requested.\n\n## Verification Discipline\n\n- No completion claim without fresh command evidence in this turn.\n- Do not mark gates passed from memory.\n- Keep evidence in `.cclaw/artifacts/`; archive via `npx cclaw-cli archive`.\n\n## Delegation And Approvals\n\n- Machine-only checks in design/plan/tdd/review/ship should auto-dispatch when tooling supports it.\n- Ask for user input only at explicit approval gates (scope mode, plan approval, challenge resolution, ship finalization).\n- If harness capabilities are partial, record waiver reasons in delegation logs.\n\n## Routing Source Of Truth\n\n- Primary router: `.cclaw/skills/using-cclaw/SKILL.md`.\n- Stage behavior: current stage skill plus `.cclaw/state/flow-state.json`.\n- Preamble budget: keep role/status announcements brief and avoid repeating\n  them unless the stage or role changes.\n";
+export declare const CURSOR_WORKFLOW_RULE_MDC = "---\ndescription: cclaw workflow guardrails for Cursor agent sessions\nglobs:\n  - \"**/*\"\nalwaysApply: true\n---\n\n<!-- cclaw-managed-cursor-workflow-rule -->\n\n# Cclaw Workflow Guardrails\n\n## Activation Rule\n\nBefore responding to coding work:\n1. Read `.cclaw/state/flow-state.json`.\n2. Start with `/cc` or continue with `/cc`.\n3. If no software-stage flow applies, respond normally.\n\n## Stage Order\n\n`brainstorm -> scope -> design -> spec -> plan -> tdd -> review -> ship`\n\nTrack-specific skips are allowed only when `flow-state.track` + `skippedStages` explicitly say so.\n\n## Task Classification\n\n| Class | Route |\n|---|---|\n| non-trivial software work | `/cc <idea>` |\n| trivial software fix | `/cc <idea>` (quick track) |\n| bugfix with repro | `/cc <idea>` and enforce RED-first in tdd |\n| pure question / non-software | direct answer (no stage flow) |\n\n## Command Surface\n\n- `/cc` = entry and resume.\n- `/cc` = only progression path.\n- Knowledge capture and recall use the `learnings` skill when requested.\n\n## Verification Discipline\n\n- No completion claim without fresh command evidence in this turn.\n- Do not mark gates passed from memory.\n- Keep evidence in `.cclaw/artifacts/`; archive through closeout via `/cc` or cancel early via `node .cclaw/hooks/cancel-run.mjs`.\n\n## Delegation And Approvals\n\n- Machine-only checks in design/plan/tdd/review/ship should auto-dispatch when tooling supports it.\n- Ask for user input only at explicit approval gates (scope mode, plan approval, challenge resolution, ship finalization).\n- If harness capabilities are partial, record waiver reasons in delegation logs.\n\n## Routing Source Of Truth\n\n- Primary router: `.cclaw/skills/using-cclaw/SKILL.md`.\n- Stage behavior: current stage skill plus `.cclaw/state/flow-state.json`.\n- Preamble budget: keep role/status announcements brief and avoid repeating\n  them unless the stage or role changes.\n";
 export declare function buildRulesJson(): Record<string, unknown>;