@curdx/flow 2.2.4 → 2.3.0

package/agents/flow-researcher.md

@@ -5,28 +5,15 @@ memory: project
 model: sonnet
 effort: high
 maxTurns: 40
+color: blue
 tools: [Read, Write, WebSearch, WebFetch, Grep, Glob, Bash]
 ---
 
-<output-discipline>
-**CRITICAL: Extreme concision required to prevent context overflow.**
-
-Your output must follow these rules:
-1. **Write first, explain never**: Your FIRST action must be calling the Write tool with the full research.md content. Do NOT paste content as assistant text.
-2. **No previews**: Do NOT preview the research findings in your response. The file itself is the deliverable.
-3. **Minimal status updates**: Use bullets, not prose. One-line updates only.
-4. **Final output**: After Write succeeds, output EXACTLY 3 lines:
-   - Line 1: "✓ research.md generated"
-   - Line 2: "Recommendations: N"
-   - Line 3: "Next: /curdx-flow:spec --phase=requirements"
-5. **No explanations**: Do NOT explain what you found, why you recommend it, or what the research contains. The file speaks for itself.
-
-**Violation of these rules = task failure.**
-</output-discipline>
-
 # Flow Researcher — Research Analysis Agent
 
 @${CLAUDE_PLUGIN_ROOT}/agent-preamble/preamble.md
+@${CLAUDE_PLUGIN_ROOT}/knowledge/artifact-output-discipline.md
+@${CLAUDE_PLUGIN_ROOT}/knowledge/artifact-summary-contracts.md
 
 ## Your Responsibilities
 
@@ -152,24 +139,10 @@ If any answer is "no", redo it before writing.
 
 ## Output to User
 
-When done, give the user a brief:
-
-```
-✓ Research complete: .flow/specs/<name>/research.md
-
-Key findings:
-  - Finding 1
-  - Finding 2
-  - Finding 3
-
-Recommended direction: Solution X (rationale)
-
-Open questions (please answer before entering requirements phase):
-  1. Q1
-  2. Q2
-
-Next step: /curdx-flow:spec --phase=requirements
-```
+Follow `${CLAUDE_PLUGIN_ROOT}/knowledge/artifact-output-discipline.md`.
+After `Write` succeeds, emit the `research.md` contract from
+`${CLAUDE_PLUGIN_ROOT}/knowledge/artifact-summary-contracts.md` and nothing
+else.
 
 ## Research discipline (stop-condition, not length-target)
 
@@ -188,14 +161,5 @@ Self-check before `Write`: for every paragraph, ask "does this change a reader's
 
 ---
 
-<bookend>
-**Restated critical rules (output discipline):**
-
-1. Write first, explain never. Your FIRST action = Write tool call with full file content.
-2. No previews. Do NOT paste content in your response.
-3. Minimal status. Bullets only, one line each.
-4. Fixed output. Exactly 3-5 lines (see output template in frontmatter).
-5. No explanations. Do NOT explain what you produced. The file is the deliverable.
-
-**Violation of these rules = task failure.**
-</bookend>
+The file is the deliverable. Do not add previews, rationale summaries, or open
+question lists to chat output.

package/agents/flow-reviewer.md

@@ -5,6 +5,7 @@ memory: project
 model: sonnet
 effort: high
 maxTurns: 40
+color: purple
 tools: [Read, Grep, Glob, Bash]
 ---
 

package/agents/flow-security-auditor.md

@@ -5,6 +5,7 @@ memory: project
 model: opus
 effort: high
 maxTurns: 40
+color: red
 tools: [Read, AskUserQuestion, Grep, Glob, Bash, WebSearch]
 ---
 

package/agents/flow-triage-analyst.md

@@ -5,6 +5,7 @@ memory: project
 model: opus
 effort: high
 maxTurns: 40
+color: orange
 tools: [Read, Write, AskUserQuestion, WebSearch, Grep, Glob, Bash]
 ---
 

package/agents/flow-ui-researcher.md

@@ -5,6 +5,7 @@ memory: project
 model: sonnet
 effort: medium
 maxTurns: 25
+color: blue
 tools: [Read, Write, WebSearch, WebFetch, Grep, Glob, Bash]
 ---
 

package/agents/flow-ux-designer.md

@@ -6,6 +6,7 @@ memory: project
 model: sonnet
 effort: medium
 maxTurns: 25
+color: pink
 tools: [Read, Write, AskUserQuestion, Bash, WebSearch, Skill]
 ---
 

package/agents/flow-verifier.md

@@ -5,6 +5,7 @@ memory: project
 model: sonnet
 effort: high
 maxTurns: 30
+color: yellow
 tools: [Read, Grep, Glob, Bash, Monitor]
 ---
 

package/cli/install-companions.js

@@ -1,14 +1,14 @@
 /**
- * Re-export barrel preserving the pre-Stage-7 import surface. New callers
- * should import directly from the concern-specific modules below instead
- * of going through this barrel. Kept in place so existing imports in
- * cli/install.js and cli/install-workflow.js keep working unchanged.
+ * Re-export barrel preserving the stable import surface. New callers should
+ * import directly from the concern-specific modules below instead of going
+ * through this barrel. Kept in place so existing imports in cli/install.js
+ * and cli/install-workflow.js keep working unchanged.
  *
- * Concern split (see docs/refactor-plan.md Stage 7):
- *   install-required-plugins.js   — required Claude Code companion plugins
- *   install-bundled-mcps.js       — user-level MCP registration
+ * Concern split:
+ *   install-required-plugins.js    — required Claude Code companion plugins
+ *   install-bundled-mcps.js        — user-level MCP registration
  *   install-recommended-plugins.js — optional recommended plugins
- *   install-context7-config.js    — context7 API-key prompt (private to required)
+ *   install-context7-config.js     — context7 API-key prompt (private to required)
  */
 
 export {

package/cli/install-next-steps.js

@@ -5,7 +5,9 @@ export function printNextSteps() {
   const cliCmd = cliOnPath ? "curdx-flow" : "npx @curdx/flow";
 
   console.log(`\n${color.bold(`${color.green("✓")} Install complete`)}\n`);
-  console.log(`${color.bold("Restart Claude Code")} so the plugin registers all its commands and hooks.\n`);
+  console.log(
+    `${color.bold("Restart Claude Code")} so the plugin registers its commands, hooks, default main-thread agent, and background monitor.\n`
+  );
   console.log(`${color.bold("Next steps")}:\n`);
   console.log(`  ${color.dim("# Verify health")}`);
   console.log(`  ${cliCmd} doctor\n`);

package/cli/lib/doctor-claude-settings.js

@@ -73,6 +73,7 @@ const CURDX_FLOW_AGENT_TYPES = [
   "flow-debugger",
   "flow-edge-hunter",
   "flow-executor",
+  "flow-orchestrator",
   "flow-planner",
   "flow-product-designer",
   "flow-qa-engineer",

package/cli/lib/doctor-report.js

@@ -158,7 +158,7 @@ export function buildDoctorReport({
         "warn",
         `claude CLI            ${claudeVersionValue} below recommended ${MIN_CLAUDE_VERSION}`,
         [
-          "curdx-flow uses modern Claude Code plugin dependency resolution and plugin bin/ PATH support",
+          "curdx-flow uses modern Claude Code plugin dependency resolution, plugin bin/PATH support, plugin-level main-agent routing, and monitor surfaces",
           "run: claude update",
         ]
       );

package/gates/coverage-audit-gate.md

@@ -7,8 +7,6 @@ depends_on: []
 
 # Coverage Audit Gate — Multi-Source Coverage Audit
 
-> Derived from get-shit-done's "Multi-Source Coverage Audit".
->
 > Rule: every claim in the spec must be covered by implementation/tests. Uncovered = missed = future bug.
 
 ---
@@ -181,4 +179,4 @@ Fix recommendations:
 
 ---
 
-_Source: get-shit-done's multi-source coverage audit._
+_Source: CurDX-Flow multi-source coverage audit contract._

package/gates/tdd-gate.md

@@ -8,8 +8,6 @@ depends_on: []
 # TDD Gate — Red/Green/Yellow Cycle Enforcement
 
 > **Iron rule**: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.
->
-> Source: superpowers' test-driven-development skill.
 
 ---
 
@@ -182,7 +180,3 @@ Compliant: 4
 Fix recommendations:
   T2: add test test(auth): red - password hashing, verify it fails, then redo GREEN
 ```
-
----
-
-_Source: superpowers' test-driven-development skill._

package/gates/verification-gate.md

@@ -7,7 +7,7 @@ depends_on: []
 
 # Verification Gate — Verification Required Before Completion
 
-> **Always enabled**. No evidence = no completion. This is the Superpowers "Verification Before Completion" iron rule.
+> **Always enabled**. No evidence = no completion. Verification must be based on observed proof, not claimed completion.
 
 ---
 
@@ -177,7 +177,3 @@ Warnings: 1
 Fix recommendations:
   V1: dispatch flow-executor to run tests, add evidence to the commit message body
 ```
-
----
-
-_Source: superpowers' verification-before-completion skill. CurdX-Flow turns it into a gate._

package/hooks/scripts/common.sh

@@ -4,6 +4,13 @@ has_python3() {
   command -v python3 >/dev/null 2>&1
 }
 
+env_flag_enabled() {
+  case "$(printf '%s' "${1:-}" | tr '[:upper:]' '[:lower:]')" in
+    1|true|yes|on) return 0 ;;
+    *) return 1 ;;
+  esac
+}
+
 json_escape() {
   local value="${1:-}"
 

package/hooks/scripts/session-start.sh

@@ -26,7 +26,7 @@ mkdir -p "$DATA_DIR" 2>/dev/null || true
 LAST_CHECK=""
 [ -f "$MARKER" ] && LAST_CHECK="$(cat "$MARKER" 2>/dev/null)"
 
-if [ "$LAST_CHECK" != "$TODAY" ]; then
+if env_flag_enabled "${CLAUDE_PLUGIN_OPTION_DAILY_DEPENDENCY_CHECK:-1}" && [ "$LAST_CHECK" != "$TODAY" ]; then
   MISSING=()
 
   # Skip if `claude` CLI is not on PATH

package/hooks/scripts/stop-watcher.sh

@@ -26,6 +26,10 @@ allow_stop() {
   exit 0
 }
 
+autonomous_blocking_enabled() {
+  env_flag_enabled "${CLAUDE_PLUGIN_OPTION_AUTONOMOUS_BLOCKING:-1}"
+}
+
 # ---------- helper: block and inject continuation ----------
 block_continue() {
   local reason="$1"
@@ -83,6 +87,10 @@ EOF
 [ "$STRATEGY" != "stop-hook" ] && allow_stop
 [ "$PHASE" != "execute" ] && allow_stop
 
+if ! autonomous_blocking_enabled; then
+  allow_stop
+fi
+
 # ---------- 5. Check hook input + completion signal in transcript ----------
 # Claude Code passes transcript path via stdin as JSON: {"transcript_path": "/path/..."}
 # We read stdin to detect ALL_TASKS_COMPLETE or TASK_FAILED

package/knowledge/artifact-output-discipline.md

@@ -0,0 +1,24 @@
+# Artifact Output Discipline
+
+Use this discipline for artifact-producing agents that write canonical files
+such as `research.md`, `requirements.md`, `design.md`, `tasks.md`, or
+`codebase-index.md`.
+
+## Core Rules
+
+1. Write the artifact first. The first substantive action should be the `Write`
+   tool call for the final file content.
+2. Do not preview or paraphrase the artifact inline. The file is the
+   deliverable.
+3. Keep status updates minimal: short bullets or fixed summary lines only.
+4. End with the exact compact output contract defined by the agent-specific
+   section. No extra explanation before or after it.
+5. If something blocks the write, report the blocker directly instead of
+   emitting a fake success summary.
+
+## Why
+
+- Prevents context waste from duplicating the artifact in chat
+- Makes the written file the canonical output surface
+- Keeps artifact-producing subagents consistent across research, product,
+  architecture, planning, and brownfield mapping

package/knowledge/artifact-summary-contracts.md

@@ -0,0 +1,50 @@
+# Artifact Summary Contracts
+
+Use these compact summary contracts after an artifact lands successfully. Pair
+them with `artifact-output-discipline.md`: write first, no preview, then emit
+the exact contract below and stop.
+
+## research.md
+
+```text
+✓ research.md generated
+Recommendations: N
+Next: /curdx-flow:spec --phase=requirements
+```
+
+## requirements.md
+
+```text
+✓ requirements.md generated
+User stories: N
+Functional requirements: N
+Next: /curdx-flow:spec --phase=design
+```
+
+## design.md
+
+```text
+✓ design.md generated
+Architecture decisions: N
+Components: N
+Next: /curdx-flow:spec --phase=tasks
+```
+
+## tasks.md
+
+```text
+✓ tasks.md generated
+Total tasks: N
+Coverage audit: PASS
+Phases: 1-5
+Next: /curdx-flow:implement
+```
+
+## codebase-index.md
+
+```text
+✓ codebase-index.md generated
+Modules: N
+Entry points: N
+Next: /curdx-flow:start <feature-name>
+```

package/knowledge/claude-code-runtime-contracts.md

@@ -72,11 +72,23 @@ Guarded artifact targets:
 ## Plugin Settings
 
 - Claude Code plugin-root `settings.json` currently supports only `agent` and `subagentStatusLine`.
-- CurDX-Flow ships only `subagentStatusLine`, pointing at `${CLAUDE_PLUGIN_ROOT}/hooks/scripts/subagent-statusline.sh`.
+- CurDX-Flow ships both:
+  - `agent: "flow-orchestrator"` to route the main thread through the CurDX-Flow coordinator by default.
+  - `subagentStatusLine`, pointing at `${CLAUDE_PLUGIN_ROOT}/hooks/scripts/subagent-statusline.sh`.
 - The status-line script must fail open on malformed input or missing `python3`; UI decoration must never break agent execution.
 - Plugin-root references must never traverse outside the plugin directory. Installed marketplace plugins run from Claude Code's plugin cache, so parent-directory references are invalid even if they work in a development checkout.
 - If adding plugin settings, update `schemas/plugin-settings.schema.json`, `test/plugin-structure-contract.test.js`, `test/pack-tarball-smoke.test.js`, and `scripts/validate-plugin-contracts.mjs` in the same change.
 
+## Plugin Monitors and User Config
+
+- CurDX-Flow ships a plugin monitor at `${CLAUDE_PLUGIN_ROOT}/monitors/monitors.json` to surface `.flow` state changes back into the active Claude session.
+- Monitors run only when the Claude `Monitor` tool is available, and only in interactive CLI sessions.
+- CurDX-Flow `userConfig` values are exported to plugin subprocesses as `CLAUDE_PLUGIN_OPTION_<KEY>`.
+- Current runtime knobs:
+  - `autonomous_blocking`: lets users disable stop-hook continuation without editing plugin files.
+  - `daily_dependency_check`: silences or enables the once-per-day recommended-plugin reminder.
+  - `monitor_interval_seconds`: controls plugin monitor polling cadence.
+
 ## Plugin Dependency Constraints
 
 - Official dependency version constraints require upstream plugin release tags in the `{plugin-name}--v{version}` format.

package/knowledge/execution-strategies.md

@@ -76,7 +76,7 @@ main agent
 - ✓ Quality-first (every task must be high-quality, avoid context pollution)
 - ✓ Moderate task size (2-15 minutes)
 - ✓ Tasks relatively independent, no complex shared context needed
-- ✓ Superpowers style
+- ✓ Stable per-task quality matters more than dispatch overhead
 
 ### Advantages
 - Each subagent uses at most ~30% context → stable quality
@@ -127,7 +127,7 @@ Safety invariant: `ALL_TASKS_COMPLETE` is advisory, not authoritative. If `tasks
 - ✓ Long task chains (20+)
 - ✓ Unattended execution (overnight automation)
 - ✓ You don't want to trigger each step manually
-- ✓ smart-ralph style
+- ✓ Long-running sequential work with checkpointed continuation
 
 ### Advantages
 - Truly autonomous execution — the user can walk away
@@ -169,7 +169,7 @@ main agent
 - ✓ Many `[P]` markers in tasks.md
 - ✓ Tasks are independent (different files, different components)
 - ✓ Time-pressured (parallelism is faster)
-- ✓ get-shit-done style
+- ✓ Parallel-safe delivery work
 
 ### Advantages
 - Wall-clock time greatly reduced (N parallel tasks at once)
@@ -298,4 +298,6 @@ Claude Code checkpoints plus `.flow/specs/<name>/.progress.md` are the current r
 
 ---
 
-_Adapted from smart-ralph (stop-hook), superpowers (subagent), get-shit-done (wave)._
+This document defines CurDX-Flow's shipped strategy semantics: stop-hook for
+checkpointed continuation, subagent for serial isolated execution, and wave for
+parallel batches.

package/knowledge/poc-first-workflow.md

@@ -114,7 +114,7 @@ Commit: `refactor(scope): yellow - <what was cleaned up>`
 ### Pitfalls
 - **Code first, tests after** → not TDD, this is post-hoc testing. Easily misses edge cases.
 - **Tests only cover happy path** → no error handling coverage; the common cause of production issues.
-- **Too much mocking** → tests disconnected from real behavior. See Superpowers' "integration tests hit real DB" lesson.
+- **Too much mocking** → tests disconnected from real behavior. Keep primary evidence anchored to real integrations at system boundaries.
 
 ---
 
@@ -211,7 +211,7 @@ Feature is verified, reviewed, and ready for a human PR/release decision.
 
 ## Relationship to the TDD Iron Rule
 
-**TDD iron rule inherited from Superpowers**: "NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST"
+**TDD iron rule**: "NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST"
 
 **POC-First's compromise**: Phase 1 allows skipping tests because the purpose of POC is to validate the idea, not to deliver.
 
@@ -221,7 +221,3 @@ Feature is verified, reviewed, and ready for a human PR/release decision.
 - Newly added **production code**: must be covered by Phase 3 TDD loop
 
 The two don't conflict: POC is not production code; production code starts at Phase 2.
-
----
-
-_Adapted from smart-ralph's POC-First workflow, extended with superpowers' TDD discipline._

package/knowledge/spec-driven-development.md

@@ -178,7 +178,3 @@ The two complement each other:
 - Agents `mcp__claude_mem__search` the history before starting research
 - What gets written into research.md is filtered, retention-worthy conclusions
 - Subsequent sessions: claude-mem auto-injects recent context; spec files provide the structured overview
-
----
-
-_Adapted from smart-ralph's spec engine, extended with get-shit-done's multi-source audit._

package/knowledge/systematic-debugging.md

@@ -1,7 +1,5 @@
 # Systematic Debugging — 4-Stage Methodology
 
-> Inherited from superpowers' systematic-debugging skill.
->
 > Agents reference this via `@${CLAUDE_PLUGIN_ROOT}/knowledge/systematic-debugging.md`.
 
 ---
@@ -378,7 +376,3 @@ The value of systematic debugging:
 Unsystematic → fixes fast but fragile → bitten again by the same bug
 Systematic  → fixes slow but thorough → solved once, never looked back
 ```
-
----
-
-_Source: superpowers' systematic-debugging skill._

package/knowledge/two-stage-review.md

@@ -1,6 +1,6 @@
 # Two-Stage Review — Two-Stage Code Review
 
-> CurdX-Flow version of Superpowers' code review skill.
+> CurDX-Flow runtime contract for two-stage review.
 >
 > Agents reference this via `@${CLAUDE_PLUGIN_ROOT}/knowledge/two-stage-review.md`.
 
@@ -129,6 +129,12 @@ Stage 2 applies all enabled Gates (from `.flow/config.json`):
 - Each applicable edge-case category addressed (N/A noted for the rest)?
 - Gap list has priorities?
 
+#### 2.8 (enterprise) DevEx review (devex-gate)
+
+- Are naming, comments, and structure maintainable for the next engineer?
+- Is setup, typing, and test ergonomics acceptable without tribal knowledge?
+- Does the developer loop stay fast enough to keep future changes safe?
+
 ### Stage 2 verdict
 
 - **EXCELLENT**: all enabled Gates pass, adversarial review clean or only low-severity findings
@@ -232,7 +238,7 @@ Some reviewers list 50 minor improvements — the user can't process.
      ↓                     ↓
      ↓              review-report.md
      ↓
-(optional) /curdx-flow:review --adversarial --edge-case
+(optional) /curdx-flow:review --adversarial --edge-case --devex
                     ↓
                     adversarial-review.md
                     edge-cases.md
@@ -241,7 +247,3 @@ Ready for human PR/release handoff with verification + review evidence
 ```
 
 Verify is "did we implement the right thing", Review is "is the implementation good", Audit is "what else could be better". CurdX-Flow currently stops at evidence-backed handoff; do not reference non-existent ship/land commands.
-
----
-
-_Source: superpowers' code-review two-stage design, extended with CurdX-Flow's Gate system._

package/knowledge/wave-execution.md

@@ -399,4 +399,5 @@ As in "Case 3" above. Solutions:
 
 ---
 
-_Source: get-shit-done's wave execution. CurdX-Flow turns it from a concept into executable logic._
+_Source: CurDX-Flow wave execution contract. This file defines the executable
+parallel-delivery rules used by the plugin runtime._

package/monitors/monitors.json

@@ -0,0 +1,8 @@
+[
+  {
+    "name": "flow-state",
+    "description": "Watch CurDX-Flow .flow state changes and notify Claude when the active spec, phase, or remaining tasks change.",
+    "command": "${CLAUDE_PLUGIN_ROOT}/monitors/scripts/flow-state-monitor.sh",
+    "when": "always"
+  }
+]

package/monitors/scripts/flow-state-monitor.sh

@@ -0,0 +1,99 @@
+#!/usr/bin/env bash
+
+set -u
+
+interval="${CLAUDE_PLUGIN_OPTION_MONITOR_INTERVAL_SECONDS:-8}"
+case "$interval" in
+  ''|*[!0-9]*)
+    interval=8
+    ;;
+esac
+if [ "$interval" -lt 3 ] 2>/dev/null; then
+  interval=3
+fi
+
+build_snapshot() {
+  if [ ! -d ".flow" ]; then
+    return 0
+  fi
+
+  local active=""
+  active="$(cat .flow/.active-spec 2>/dev/null || true)"
+  [ -z "$active" ] && return 0
+
+  local spec_dir=".flow/specs/$active"
+  [ ! -d "$spec_dir" ] && return 0
+
+  local state_file="$spec_dir/.state.json"
+  local tasks_file="$spec_dir/tasks.md"
+
+  python3 - "$active" "$state_file" "$tasks_file" <<'PY' 2>/dev/null
+import json
+import os
+import re
+import sys
+
+active, state_file, tasks_file = sys.argv[1:4]
+
+phase = "unknown"
+strategy = "unknown"
+task_index = 0
+total_tasks = 0
+failed_attempts = 0
+global_iteration = 0
+
+if os.path.exists(state_file):
+    try:
+        state = json.load(open(state_file, "r", encoding="utf-8"))
+        phase = state.get("phase") or phase
+        strategy = state.get("strategy") or strategy
+        execute_state = state.get("execute_state") or {}
+        task_index = execute_state.get("task_index") or 0
+        total_tasks = execute_state.get("total_tasks") or 0
+        failed_attempts = execute_state.get("failed_attempts") or 0
+        global_iteration = execute_state.get("global_iteration") or 0
+    except Exception:
+        phase = "invalid-state"
+
+unchecked = 0
+if os.path.exists(tasks_file):
+    try:
+        text = open(tasks_file, "r", encoding="utf-8").read()
+        unchecked = len(re.findall(r"^- \[ \] \*\*[0-9]+(\.[0-9]+|\.VF|\.X(\+[0-9]+)?)*\*\*", text, re.M))
+    except Exception:
+        unchecked = -1
+
+parts = [
+    f"CurDX-Flow monitor: spec={active}",
+    f"phase={phase}",
+    f"strategy={strategy}",
+]
+
+if total_tasks > 0:
+    parts.append(f"tasks={task_index}/{total_tasks}")
+parts.append(f"unchecked={unchecked}")
+
+if failed_attempts > 0:
+    parts.append(f"failed_attempts={failed_attempts}")
+if global_iteration > 0:
+    parts.append(f"loop={global_iteration}")
+
+print(" ".join(parts))
+PY
+}
+
+last_snapshot=""
+
+while true; do
+  snapshot="$(build_snapshot)"
+  if [ -n "$snapshot" ] && [ "$snapshot" != "$last_snapshot" ]; then
+    printf '%s\n' "$snapshot"
+    last_snapshot="$snapshot"
+  fi
+
+  if [ "${CURDX_FLOW_MONITOR_ONCE:-0}" = "1" ]; then
+    exit 0
+  fi
+
+  sleep "$interval"
+done

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@curdx/flow",
-  "version": "2.2.4",
-  "description": "CLI installer for CurdX-Flow — AI engineering workflow meta-framework for Claude Code",
+  "version": "2.3.0",
+  "description": "Skill-first discipline layer and CLI installer for Claude Code",
   "type": "module",
   "bin": {
     "curdx-flow": "bin/curdx-flow.js"
@@ -19,6 +19,7 @@
     "gates/",
     "hooks/",
     "knowledge/",
+    "monitors/",
     "agent-preamble/",
     "output-styles/",
     "templates/",

package/schemas/agent-frontmatter.schema.json

@@ -54,6 +54,10 @@
     "isolation": {
       "type": "string",
       "enum": ["worktree"]
+    },
+    "color": {
+      "type": "string",
+      "enum": ["red", "blue", "green", "yellow", "purple", "orange", "pink", "cyan"]
     }
   }
 }