catalyst-os 1.1.1 → 1.3.0

package/.claude/commands/primer-spec.md

@@ -2,6 +2,20 @@
 
 Quickly load spec context into a fresh conversation.
 
+## Pre-computed Context
+
+```bash
+# Git state
+echo "=== BRANCH ===" && git branch --show-current
+echo "=== STATUS ===" && git status --short
+echo "=== RECENT COMMITS ===" && git log --oneline -5
+
+# Spec files
+echo "=== TASKS.MD ===" && cat .catalyst/specs/*$ARGUMENTS*/tasks.md 2>/dev/null || echo "No tasks.md for: $ARGUMENTS"
+echo "=== SPEC FRONTMATTER ===" && head -30 .catalyst/specs/*$ARGUMENTS*/spec.md 2>/dev/null || echo "No spec.md"
+echo "=== RESEARCH ===" && head -30 .catalyst/specs/*$ARGUMENTS*/research.md 2>/dev/null || echo "No research.md"
+```
+
 ---
 
 ## Purpose
@@ -26,22 +40,18 @@ When you start a new conversation (context was full), use this command to:
 
 ## What To Do
 
-### Step 1: Read Spec Files
+### Step 1: Use Pre-computed Context
 
-Read these files from `.catalyst/specs/{slug}/`:
+The bash blocks above already loaded tasks.md, spec frontmatter, research, and git state. Use this data directly — do NOT re-read these files unless you need more detail beyond what was loaded.
 
-```
-1. spec.md      → What is this feature? Requirements?
-2. tasks.md     → What's done? What's pending? What's in progress?
-3. research.md  → (if exists) Any key technical decisions?
-```
+### Step 2: Read Full Files Only If Needed
 
-### Step 2: Check Git State
+If the pre-computed context was truncated, read the full file:
 
-```bash
-git branch --show-current    # What branch are we on?
-git status --short           # Any uncommitted changes?
-git log --oneline -3         # Recent commits?
+```
+1. tasks.md     → What's done? What's pending? What's in progress?
+2. spec.md      → What is this feature? Requirements?
+3. research.md  → (if exists) Any key technical decisions?
 ```
 
 ### Step 3: Output Brief Summary
@@ -146,7 +156,7 @@ Ready to continue. What would you like to work on?
 |-----------|---------|
 | Context full, need to continue building | `/primer-spec` |
 | Want to add improvement mid-build | `/iterate-spec` |
-| Need full validation | `/validate-spec` |
+| Need full validation | `/review-spec` |
 | Check status without loading context | `/status-spec` |
 
 ---

package/.claude/commands/review-spec.md

@@ -0,0 +1,29 @@
+# /review-spec
+
+Run validation checks and code simplification on a completed implementation.
+
+## Usage
+
+```
+/review-spec @2025-11-29-stripe-integration
+```
+
+## Pre-computed Context
+
+```bash
+# Build state for validation
+echo "=== BRANCH ===" && git branch --show-current
+echo "=== STATUS ===" && git status --short
+echo "=== TASKS.MD PROGRESS ===" && grep -A 5 "## Progress" .catalyst/specs/*$ARGUMENTS*/tasks.md 2>/dev/null || echo "No tasks.md"
+echo "=== SPEC STATUS ===" && head -20 .catalyst/specs/*$ARGUMENTS*/spec.md 2>/dev/null || echo "No spec.md"
+echo "=== DIFF STAT VS BASE ===" && git diff --stat main...HEAD 2>/dev/null || echo "No diff from main"
+echo "=== FILES CHANGED ===" && git diff --name-only main...HEAD 2>/dev/null || echo "No changes from main"
+```
+
+---
+
+**Invoke skill:** `spec-validation`
+
+**Orchestrator:** Arbiter (delegates to Enforcer, Sentinel, Inquisitor, Watcher)
+
+**Process skills used:** `verification-before-completion`, `agent-delegation`, `test-driven-development`

package/.claude/commands/status-spec.md

@@ -8,6 +8,19 @@ Check the current status of a spec and sync progress with reality.
 /status-spec @2025-11-29-stripe-integration
 ```
 
+## Pre-computed Context
+
+```bash
+# Current git state
+echo "=== BRANCH ===" && git branch --show-current
+echo "=== STATUS ===" && git status --short
+echo "=== DIFF STAT ===" && git diff --stat
+echo "=== RECENT COMMITS ===" && git log --oneline -10
+echo "=== SPEC FILES ===" && ls .catalyst/specs/*$ARGUMENTS*/ 2>/dev/null || echo "No spec found for: $ARGUMENTS"
+echo "=== TASKS.MD ===" && cat .catalyst/specs/*$ARGUMENTS*/tasks.md 2>/dev/null | head -80 || echo "No tasks.md"
+echo "=== SPEC STATUS ===" && head -20 .catalyst/specs/*$ARGUMENTS*/spec.md 2>/dev/null || echo "No spec.md"
+```
+
 ---
 
 ## Purpose
@@ -18,13 +31,15 @@ Resume work on a spec after being away. This command:
 3. Syncs tasks.md with reality
 4. Gives you a clear "where we are" summary
 
+Use the pre-computed context above — do NOT re-run these commands. Only run additional commands if specific details are missing.
+
 ---
 
 ## Workflow
 
 ### Phase 1: Read Spec State
 
-Read all spec files:
+Read all spec files (use pre-computed context first, read full files only if needed):
 - `spec.md` → Feature overview, requirements, status
 - `tasks.md` → Task breakdown, marked progress
 - `research.md` → Context and decisions made
@@ -32,18 +47,11 @@ Read all spec files:
 
 ### Phase 2: Check Git Reality
 
-Run git commands to see actual state:
+Use pre-computed git context. Only run additional commands if needed:
 
 ```bash
-# What files are modified but not committed?
-git status --short
-
-# What's the diff for uncommitted work?
-git diff --stat
-
-# Recent commits related to this spec
+# Additional detail if needed
 git log --oneline -10 --grep="{slug}"
-git log --oneline -10 -- "src/" "lib/" "app/"  # Recent code commits
 ```
 
 ### Phase 3: Reconcile Tasks
@@ -234,9 +242,9 @@ VALIDATION STATUS
 
 NEXT STEPS
 ----------
-1. Complete validation: /validate-spec @slug
+1. Complete validation: /review-spec @slug
 2. Review handoff.md when ready
-3. Approve: /approve-spec @slug
+3. Commit: /commit-spec @slug
 ```
 
 ---

package/.claude/hooks/post-edit-format.sh

@@ -0,0 +1,62 @@
+#!/usr/bin/env bash
+# PostToolUse hook: Auto-format files after Edit/Write operations
+# Runs the project's formatter on changed code files.
+# Always exits 0 — formatting is advisory, never blocks.
+
+set -euo pipefail
+
+FILE_PATH="${1:-}"
+
+# Skip if no file path provided or file doesn't exist
+[[ -z "$FILE_PATH" || ! -f "$FILE_PATH" ]] && exit 0
+
+# Get file extension
+EXT="${FILE_PATH##*.}"
+
+# Skip non-code files
+case "$EXT" in
+  md|txt|yaml|yml|json|lock|log|csv|svg|png|jpg|gif|ico|woff|woff2|ttf|eot)
+    exit 0
+    ;;
+esac
+
+# Find project root (where package.json or .git lives)
+PROJECT_ROOT="$(cd "$(dirname "$FILE_PATH")" && git rev-parse --show-toplevel 2>/dev/null || echo "")"
+[[ -z "$PROJECT_ROOT" ]] && exit 0
+
+# --- Formatter detection (first match wins) ---
+
+# Biome
+if [[ -f "$PROJECT_ROOT/biome.json" || -f "$PROJECT_ROOT/biome.jsonc" ]]; then
+  if command -v npx &>/dev/null; then
+    npx --yes @biomejs/biome format --write "$FILE_PATH" 2>/dev/null || true
+    exit 0
+  fi
+fi
+
+# Prettier
+if [[ -f "$PROJECT_ROOT/.prettierrc" || -f "$PROJECT_ROOT/.prettierrc.json" || -f "$PROJECT_ROOT/.prettierrc.js" || -f "$PROJECT_ROOT/.prettierrc.yaml" || -f "$PROJECT_ROOT/.prettierrc.yml" || -f "$PROJECT_ROOT/prettier.config.js" || -f "$PROJECT_ROOT/prettier.config.mjs" ]]; then
+  if command -v npx &>/dev/null; then
+    npx --yes prettier --write "$FILE_PATH" 2>/dev/null || true
+    exit 0
+  fi
+fi
+
+# Check package.json for prettier as dependency (common case: no .prettierrc but prettier installed)
+if [[ -f "$PROJECT_ROOT/package.json" ]] && grep -q '"prettier"' "$PROJECT_ROOT/package.json" 2>/dev/null; then
+  if command -v npx &>/dev/null; then
+    npx --yes prettier --write "$FILE_PATH" 2>/dev/null || true
+    exit 0
+  fi
+fi
+
+# --- TypeScript type-check (non-blocking) ---
+case "$EXT" in
+  ts|tsx)
+    if [[ -f "$PROJECT_ROOT/tsconfig.json" ]] && command -v npx &>/dev/null; then
+      npx --yes tsc --noEmit 2>/dev/null || true
+    fi
+    ;;
+esac
+
+exit 0

package/.claude/hooks/pre-compact-save.sh

@@ -0,0 +1,98 @@
+#!/usr/bin/env bash
+# PreCompact hook: Auto-save current state to tasks.md before context compaction
+# Ensures /primer-spec always has accurate resume info, even if agents forgot to update.
+# Always exits 0 — state saving should never block compaction.
+
+set -euo pipefail
+
+# Find project root
+PROJECT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || echo "")"
+[[ -z "$PROJECT_ROOT" ]] && exit 0
+
+# --- Detect active spec from branch name ---
+BRANCH="$(git branch --show-current 2>/dev/null || echo "")"
+SLUG=""
+
+# Extract slug from branch: feat/YYYY-MM-DD-slug or feat/slug
+if [[ "$BRANCH" =~ ^[^/]+/(.+)$ ]]; then
+  SLUG="${BASH_REMATCH[1]}"
+fi
+
+[[ -z "$SLUG" ]] && exit 0
+
+# --- Find matching tasks.md ---
+TASKS_FILE=""
+
+# Try exact match first
+for dir in "$PROJECT_ROOT"/.catalyst/specs/*-"$SLUG"; do
+  if [[ -f "$dir/tasks.md" ]]; then
+    TASKS_FILE="$dir/tasks.md"
+    break
+  fi
+done
+
+# Try broader match if exact didn't work
+if [[ -z "$TASKS_FILE" ]]; then
+  for dir in "$PROJECT_ROOT"/.catalyst/specs/*"$SLUG"*; do
+    if [[ -f "$dir/tasks.md" ]]; then
+      TASKS_FILE="$dir/tasks.md"
+      break
+    fi
+  done
+fi
+
+[[ -z "$TASKS_FILE" ]] && exit 0
+
+# --- Build state snapshot ---
+TIMESTAMP="$(date -u '+%Y-%m-%dT%H:%M:%SZ')"
+GIT_STATUS="$(git status --short 2>/dev/null | head -20 || echo "unknown")"
+MODIFIED_COUNT="$(git status --short 2>/dev/null | wc -l | tr -d ' ' || echo "0")"
+
+STATE_BLOCK="**Phase:** (check Progress table above)
+**Timestamp:** $TIMESTAMP
+**Branch:** $BRANCH
+**Modified files:** $MODIFIED_COUNT
+**Auto-saved:** Yes (PreCompact hook)
+
+\`\`\`
+$GIT_STATUS
+\`\`\`
+
+> Resume with \`/primer-spec @$SLUG\` in a new conversation."
+
+# --- Update Current Session section ---
+# Replace existing Current Session content, or append if missing
+if grep -q "^## Current Session" "$TASKS_FILE" 2>/dev/null; then
+  # Find the line number of "## Current Session" and the next "##" heading
+  SESSION_LINE="$(grep -n "^## Current Session" "$TASKS_FILE" | head -1 | cut -d: -f1)"
+  NEXT_HEADING="$(tail -n +"$((SESSION_LINE + 1))" "$TASKS_FILE" | grep -n "^## " | head -1 | cut -d: -f1)"
+
+  if [[ -n "$NEXT_HEADING" ]]; then
+    # There's a section after Current Session — replace between them
+    END_LINE="$((SESSION_LINE + NEXT_HEADING - 1))"
+    {
+      head -n "$SESSION_LINE" "$TASKS_FILE"
+      echo ""
+      echo -e "$STATE_BLOCK"
+      echo ""
+      tail -n +"$END_LINE" "$TASKS_FILE"
+    } > "${TASKS_FILE}.tmp" && mv "${TASKS_FILE}.tmp" "$TASKS_FILE"
+  else
+    # Current Session is the last section — replace to end
+    {
+      head -n "$SESSION_LINE" "$TASKS_FILE"
+      echo ""
+      echo -e "$STATE_BLOCK"
+    } > "${TASKS_FILE}.tmp" && mv "${TASKS_FILE}.tmp" "$TASKS_FILE"
+  fi
+else
+  # No Current Session section — append it
+  {
+    echo ""
+    echo "## Current Session"
+    echo ""
+    echo -e "$STATE_BLOCK"
+  } >> "$TASKS_FILE"
+fi
+
+exit 0

package/.claude/rules/coding-standards.md

@@ -0,0 +1,21 @@
+# Coding Standards
+
+These rules apply to ALL code generation, regardless of which skill is active.
+
+## Language
+
+- All generated artifacts MUST be in English (code, comments, docs, commit messages)
+- Communicate with the user in their preferred language
+
+## File Hygiene
+
+- Keep files under 300 lines — split if larger
+- No deep nesting (max 3 levels of indentation for logic)
+- One concept per file — don't mix unrelated concerns
+
+## Quality
+
+- Write minimal code that solves the current requirement
+- Don't add features, abstractions, or config that wasn't requested
+- Prefer clarity over cleverness
+- Delete dead code — don't comment it out

package/.claude/rules/git-workflow.md

@@ -0,0 +1,25 @@
+# Git Workflow Rules
+
+These rules apply to ALL git operations, regardless of which skill is active.
+
+## Branch Naming
+
+- Feature branches: `{branch_prefix}/{spec-slug}` (e.g., `feat/2026-01-11-user-auth`)
+- Read `branch_prefix` from `.catalyst/main/project-config.yaml`
+- Never commit directly to protected branches (`main`, `master`)
+
+## Commit Messages
+
+- Red phase: `test({scope}): write failing tests for {spec}`
+- Green phase: `feat({scope}): implement {spec}`
+- Bug fixes: `fix({scope}): description`
+- Refactors: `refactor({scope}): description`
+- Keep subject line under 72 characters
+- Use imperative mood ("add", not "added")
+
+## Operations
+
+- Always check `git status` before destructive operations
+- Never force-push to shared branches without user confirmation
+- Prefer creating new commits over amending published ones
+- Stage specific files — avoid `git add -A` which may catch secrets

package/.claude/rules/security.md

@@ -0,0 +1,23 @@
+# Security Rules
+
+These rules apply to ALL actions, regardless of which skill is active.
+
+## Secrets
+
+- **NEVER** commit `.env`, `.env.*`, credentials, API keys, or tokens
+- **NEVER** hardcode secrets in source code — use environment variables
+- Verify `.gitignore` includes `.env*` before any git operations
+- If a secret is accidentally staged, **unstage immediately** and rotate the key
+
+## Dependencies
+
+- Do not install packages with known critical CVEs
+- Prefer well-maintained packages with active security practices
+- Pin major versions in production dependencies
+
+## Code
+
+- Sanitize all user input at system boundaries
+- Use parameterized queries — never string-concatenate SQL
+- Escape output to prevent XSS
+- Validate file paths to prevent traversal attacks

package/.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "command": ".claude/hooks/post-edit-format.sh $FILE_PATH"
+      }
+    ],
+    "PreCompact": [
+      {
+        "command": ".claude/hooks/pre-compact-save.sh"
+      }
+    ]
+  }
+}

package/.claude/settings.local.json

@@ -6,8 +6,10 @@
     "deny": [],
     "ask": []
   },
+  "enableAllProjectMcpServers": true,
   "enabledMcpjsonServers": [
-    "shadcn"
-  ],
-  "enableAllProjectMcpServers": true
+    "shadcn",
+    "supabase-local",
+    "exa"
+  ]
 }

package/.claude/skills/build-orchestration/SKILL.md

@@ -1,7 +1,7 @@
 # Build Orchestration
 
 > **When to invoke:** When implementing a specification using strict TDD.
-> **Invoked by:** `/build-spec` command.
+> **Invoked by:** `/build-spec` or `/build-spec-worktree` command.
 > **Orchestrator:** Forge-Master agent.
 
 ## Purpose
@@ -28,7 +28,7 @@ Orchestrate the full build workflow: task breakdown, test writing, foundation, c
 ├── spec.md           # Already exists from /catalyze-spec
 ├── research.md       # Already exists from /catalyze-spec
 ├── tasks.md          # Forger creates (this phase)
-├── validation.md     # Arbiter creates (in /validate-spec)
+├── validation.md     # Arbiter creates (in /review-spec)
 ├── handoff.md        # Updated throughout
 └── assets/
 ```
@@ -38,8 +38,14 @@ Orchestrate the full build workflow: task breakdown, test writing, foundation, c
 ```
 PHASE 0: Setup
 ├── Read .catalyst/main/project-config.yaml
-├── Checkout to development_branch (default: main)
-└── Create branch: {branch_prefix}/{spec-slug}
+├── IF --worktree flag:
+│   ├── mkdir -p {worktree_path}
+│   ├── git worktree add {worktree_path}/{spec-slug} -b {branch_prefix}/{spec-slug} {development_branch}
+│   ├── cd {worktree_path}/{spec-slug}
+│   └── Record worktree path in spec's handoff.md
+├── ELSE (default):
+│   ├── Checkout to development_branch (default: main)
+│   └── Create branch: {branch_prefix}/{spec-slug}
 
 GATE 1: RED FLAG
 └── Commit: "test({scope}): write failing tests for {spec}"
@@ -105,9 +111,15 @@ Phase 6: Integration (Enforcer — cross-boundary tests)
 
 ### Phase 0: Git Setup
 
-1. Read `project-config.yaml` for `development_branch` and `branch_prefix`
-2. Checkout development branch and pull
-3. Create spec feature branch: `{branch_prefix}/{spec-slug}`
+1. Read `project-config.yaml` for `development_branch`, `branch_prefix`, and `worktree_path`
+2. IF `--worktree` flag (from `/build-spec-worktree`):
+   - `mkdir -p {worktree_path}` (default: `.catalyst/worktrees`)
+   - `git worktree add {worktree_path}/{spec-slug} -b {branch_prefix}/{spec-slug} {development_branch}`
+   - `cd {worktree_path}/{spec-slug}` — all subsequent work happens here
+   - Record `worktree: {worktree_path}/{spec-slug}` in the spec's `handoff.md`
+3. ELSE (default — branch checkout):
+   - Checkout development branch and pull
+   - Create spec feature branch: `{branch_prefix}/{spec-slug}`
 
 ### Phase 1: Task Breakdown (Forger)
 
@@ -132,6 +144,9 @@ Only AFTER this commit exists may implementation begin.
 No commit = no implementation. No exceptions.
 ```
 
+> **Context checkpoint:** If context is getting long, compact now. All state is in `tasks.md`.
+> Run `/primer-spec @{slug}` in a new conversation to resume.
+
 - Every task has at least one test
 - All tests executed
 - All tests FAIL (for the right reasons — missing feature, not import errors)
@@ -139,6 +154,9 @@ No commit = no implementation. No exceptions.
 
 ### Phase 3-4: Foundation & Contracts
 
+> **Context checkpoint:** If context is getting long, compact now. All state is in `tasks.md`.
+> Run `/primer-spec @{slug}` in a new conversation to resume.
+
 Spawn Alchemist (foundation) → WAIT → Spawn Smith (contracts) → WAIT
 
 ### Phase 5: Parallel Implementation
@@ -166,8 +184,14 @@ COMMIT: "feat({scope}): implement {spec}"
 Only AFTER this commit exists may integration begin.
 ```
 
+> **Context checkpoint:** If context is getting long, compact now. All state is in `tasks.md`.
+> Run `/primer-spec @{slug}` in a new conversation to resume.
+
 ### Phase 6: Integration
 
+> **Context checkpoint:** If context is getting long, compact now. All state is in `tasks.md`.
+> Run `/primer-spec @{slug}` in a new conversation to resume.
+
 Spawn Enforcer for cross-boundary integration tests.
 
 ## Implementation Rules
@@ -179,13 +203,20 @@ FOR EACH TASK:
 3. Run test → must PASS
 4. Refactor if needed
 5. Run test → must still PASS
-6. Update tasks.md Progress
+6. Update tasks.md Progress — THE AGENT DOING THE WORK MUST DO THIS
 
 NEVER write code without a failing test first
 NEVER write more code than needed to pass the test
 NEVER modify files outside your SCOPE
+NEVER report done without updating tasks.md first
 ```
 
+### tasks.md Update Responsibility
+
+**Every agent (smith, shaper, alchemist, enforcer) MUST update tasks.md before reporting back.**
+The orchestrator (forge-master) verifies and fills gaps, but agents are the primary updaters.
+This ensures `/primer-spec` always reflects actual progress, even if the orchestrator loses context.
+
 ## Failure Modes
 
 | Failure | Action |

package/.claude/skills/spec-approval/SKILL.md

@@ -1,7 +1,7 @@
 # Spec Approval
 
 > **When to invoke:** When accepting an implementation and archiving the spec.
-> **Invoked by:** `/approve-spec` command.
+> **Invoked by:** `/commit-spec` command.
 
 ## Purpose
 
@@ -15,10 +15,10 @@ Final verification, git commit, spec archival, self-documentation (propagate lea
 ## Prerequisites — HARD GATES
 
 > **This skill is the FINAL step in the spec lifecycle.** It runs ONLY after build and validation are complete.
-> **Flow:** `/catalyze-spec` → `/build-spec` → `/validate-spec` → **`/approve-spec`** (you are here)
+> **Flow:** `/catalyze-spec` → `/build-spec` → `/review-spec` → **`/commit-spec`** (you are here)
 >
 > If the spec has not been built yet, STOP and tell the user to run `/build-spec` first.
-> If the spec has not been validated yet, STOP and tell the user to run `/validate-spec` first.
+> If the spec has not been validated yet, STOP and tell the user to run `/review-spec` first.
 
 - `/build-spec` must have been completed (tasks.md exists with completed tasks)
 - Validation must be complete (`validation.md` must show all checks passed)

package/.claude/skills/spec-iteration/SKILL.md

@@ -68,9 +68,11 @@ Phase 5: Implement (Smith/Shaper/Alchemist)
 
 ### Phase 0: Verify State
 
-1. Verify on feature branch: `git branch --show-current`
-2. Read existing spec.md and tasks.md
-3. If NOT on feature branch: ask user to checkout or run `/build-spec`
+1. Check if `.catalyst/worktrees/{spec-slug}` exists
+   - IF exists: `cd` into it (worktree mode)
+2. ELSE: Verify on feature branch: `git branch --show-current`
+3. Read existing spec.md and tasks.md
+4. If neither worktree nor feature branch: ask user to run `/build-spec` or `/build-spec-worktree`
 
 ### Phase 1: Clarify (Oracle — Optional)
 
@@ -116,7 +118,7 @@ Spawn appropriate agents (Smith/Shaper/Alchemist) based on task types. Parallel
 
 | Failure | Action |
 |---------|--------|
-| Not on feature branch | Checkout or run `/build-spec` first |
+| Not on feature branch | Checkout, run `/build-spec`, or `/build-spec-worktree` first |
 | Spec not found | Run `/catalyze-spec` first |
 | tasks.md missing | Run `/build-spec` first |
 | Improvement conflicts with existing | Spawn Oracle to discuss options |

package/.claude/skills/spec-shaping/SKILL.md

@@ -178,4 +178,4 @@ Next steps:
 - Or /iterate-spec if you want changes first
 ```
 
-**IMPORTANT: Do NOT suggest `/approve-spec` after spec shaping.** `/approve-spec` is only for accepting a fully built and validated implementation — it is the FINAL step, not a plan-approval step. The correct flow is: `/catalyze-spec` → `/build-spec` → `/validate-spec` → `/approve-spec`.
+**IMPORTANT: Do NOT suggest `/commit-spec` after spec shaping.** `/commit-spec` is only for committing a fully built and validated implementation — it is the FINAL step, not a plan-approval step. The correct flow is: `/catalyze-spec` → `/build-spec` → `/review-spec` → `/commit-spec`.

package/.claude/skills/spec-validation/SKILL.md

@@ -1,7 +1,7 @@
 # Spec Validation
 
 > **When to invoke:** When running validation checks on a completed implementation.
-> **Invoked by:** `/validate-spec` command.
+> **Invoked by:** `/review-spec` command.
 > **Orchestrator:** Arbiter agent.
 
 ## Purpose
@@ -76,10 +76,13 @@ Spawn all Guardians in parallel:
 - Test user flows
 - Capture screenshots on failure
 
-**Inquisitor** (Code Quality):
+**Inquisitor** (Code Quality + Simplification):
 - Run linters
 - Code review checks
 - Documentation gaps
+- **Code simplification suggestions** (unnecessary abstractions, over-engineering, dead code, verbose patterns)
+- Simplifications must NOT change behavior — only structure
+- Provide before/after snippets for each suggestion
 
 **Watcher** (Security):
 - Dependency audit
@@ -126,8 +129,9 @@ If all validation passes, create handoff.md with:
 - Total: N, Passing: N
 
 ## Quality Checks
-### Lint (Inquisitor)
-- Status: PASS/FAIL, Errors: N, Warnings: N
+### Lint & Simplification (Inquisitor)
+- Lint Status: PASS/FAIL, Errors: N, Warnings: N
+- Simplification Opportunities: N found
 
 ### Security (Watcher)
 - Dependencies: status
@@ -153,7 +157,7 @@ If all validation passes, create handoff.md with:
 ```
 Validation complete!
 Status: READY FOR APPROVAL
-Next: /approve-spec @slug
+Next: /commit-spec @slug
 ```
 
 ### TDD Failure
@@ -167,5 +171,5 @@ Action: Return to /build-spec and follow TDD process
 ```
 Validation failed!
 Failed Checks: [details]
-Action: Fix issues and re-run /validate-spec
+Action: Fix issues and re-run /review-spec
 ```

package/.claude/skills/using-skills/SKILL.md

@@ -44,8 +44,8 @@ Skills tell you HOW. User instructions tell you WHAT.
 | **spec-shaping** | `.claude/skills/spec-shaping/SKILL.md` | `/catalyze-spec` — shaping a new specification |
 | **build-orchestration** | `.claude/skills/build-orchestration/SKILL.md` | `/build-spec` — implementing a specification |
 | **spec-iteration** | `.claude/skills/spec-iteration/SKILL.md` | `/iterate-spec` — updating and continuing a build |
-| **spec-validation** | `.claude/skills/spec-validation/SKILL.md` | `/validate-spec` — quality checks on implementation |
-| **spec-approval** | `.claude/skills/spec-approval/SKILL.md` | `/approve-spec` — final approval and archival |
+| **spec-validation** | `.claude/skills/spec-validation/SKILL.md` | `/review-spec` — quality checks on implementation |
+| **spec-approval** | `.claude/skills/spec-approval/SKILL.md` | `/commit-spec` — final commit and archival |
 | **project-initialization** | `.claude/skills/project-initialization/SKILL.md` | `/catalyze-project` — setting up a new project |
 | **task-building** | `.claude/skills/task-building/SKILL.md` | `/build-task` — building a single task (brownfield) |
 | **spec-update** | `.claude/skills/spec-update/SKILL.md` | `/update-spec` — modifying an existing spec |