catalyst-os 1.1.1 → 1.3.0

package/.catalyst/bin/validate-artifacts.js

@@ -0,0 +1,213 @@
+#!/usr/bin/env node
+/**
+ * Validate structural integrity of all catalyst-os artifacts.
+ * Run: node .catalyst/bin/validate-artifacts.js
+ * Exit code: 0 = all valid, 1 = errors found
+ */
+
+const fs = require('fs');
+const path = require('path');
+
+const ROOT = path.resolve(__dirname, '..', '..');
+let errors = 0;
+let warnings = 0;
+
+function error(msg) {
+  console.error(`  ✗ ${msg}`);
+  errors++;
+}
+
+function warn(msg) {
+  console.warn(`  ⚠ ${msg}`);
+  warnings++;
+}
+
+function ok(msg) {
+  console.log(`  ✓ ${msg}`);
+}
+
+// --- Helpers ---
+
+function fileExists(relPath) {
+  return fs.existsSync(path.join(ROOT, relPath));
+}
+
+function readFile(relPath) {
+  const full = path.join(ROOT, relPath);
+  if (!fs.existsSync(full)) return null;
+  return fs.readFileSync(full, 'utf8');
+}
+
+function listDir(relPath) {
+  const full = path.join(ROOT, relPath);
+  if (!fs.existsSync(full)) return [];
+  return fs.readdirSync(full);
+}
+
+function extractFrontmatter(content) {
+  const match = content.match(/^---\n([\s\S]*?)\n---/);
+  if (!match) return null;
+  // Simple YAML key extraction (no full parser needed)
+  const fm = {};
+  for (const line of match[1].split('\n')) {
+    const kv = line.match(/^(\w+):\s*(.+)/);
+    if (kv) fm[kv[1]] = kv[2].trim();
+  }
+  return fm;
+}
+
+// --- Validators ---
+
+console.log('\n📦 Catalyst OS Artifact Validation\n');
+
+// 1. Skills
+console.log('Skills:');
+const skillDirs = listDir('.claude/skills').filter(d => !d.startsWith('.'));
+if (skillDirs.length === 0) {
+  error('No skills found in .claude/skills/');
+} else {
+  for (const dir of skillDirs) {
+    const skillPath = `.claude/skills/${dir}/SKILL.md`;
+    const content = readFile(skillPath);
+    if (!content) {
+      error(`${skillPath} — missing`);
+    } else if (content.trim().length < 10) {
+      error(`${skillPath} — empty or too short`);
+    } else {
+      ok(dir);
+    }
+  }
+}
+
+// 2. Agents
+console.log('\nAgents:');
+const agentFiles = listDir('.claude/agents').filter(f => f.endsWith('.md'));
+if (agentFiles.length === 0) {
+  error('No agents found in .claude/agents/');
+} else {
+  const requiredFields = ['name', 'description', 'model'];
+  for (const file of agentFiles) {
+    const content = readFile(`.claude/agents/${file}`);
+    if (!content) {
+      error(`${file} — cannot read`);
+      continue;
+    }
+    const fm = extractFrontmatter(content);
+    if (!fm) {
+      error(`${file} — missing YAML frontmatter`);
+      continue;
+    }
+    const missing = requiredFields.filter(f => !fm[f]);
+    if (missing.length > 0) {
+      error(`${file} — missing frontmatter fields: ${missing.join(', ')}`);
+    } else {
+      ok(file.replace('.md', ''));
+    }
+  }
+}
+
+// 3. Commands
+console.log('\nCommands:');
+const cmdFiles = listDir('.claude/commands').filter(f => f.endsWith('.md'));
+if (cmdFiles.length === 0) {
+  error('No commands found in .claude/commands/');
+} else {
+  for (const file of cmdFiles) {
+    const content = readFile(`.claude/commands/${file}`);
+    if (!content || content.trim().length < 10) {
+      error(`${file} — empty or too short`);
+    } else {
+      ok(file.replace('.md', ''));
+    }
+  }
+}
+
+// 4. Skill Index consistency (using-skills references vs actual skills)
+console.log('\nSkill Index:');
+const usingSkills = readFile('.claude/skills/using-skills/SKILL.md');
+if (usingSkills) {
+  // Extract skill paths from the index tables
+  const pathMatches = usingSkills.matchAll(/`\.claude\/skills\/([^/]+)\/SKILL\.md`/g);
+  const referenced = new Set();
+  for (const m of pathMatches) {
+    referenced.add(m[1]);
+  }
+
+  // Check referenced skills exist
+  for (const skill of referenced) {
+    if (!fileExists(`.claude/skills/${skill}/SKILL.md`)) {
+      error(`using-skills references "${skill}" but .claude/skills/${skill}/SKILL.md doesn't exist`);
+    }
+  }
+
+  // Check actual skills are referenced
+  for (const dir of skillDirs) {
+    if (!referenced.has(dir)) {
+      warn(`Skill "${dir}" exists but is not listed in using-skills/SKILL.md`);
+    }
+  }
+
+  if (errors === 0) ok('All skill references valid');
+} else {
+  error('using-skills/SKILL.md not found');
+}
+
+// 5. spec-structure.yaml file references
+console.log('\nSpec Structure:');
+if (fileExists('.catalyst/spec-structure.yaml')) {
+  ok('spec-structure.yaml exists');
+} else {
+  error('.catalyst/spec-structure.yaml missing');
+}
+
+// 6. Core files
+console.log('\nCore Files:');
+const coreFiles = ['CLAUDE.md', 'AGENTS.md', 'package.json', '.catalyst/main/project-config.yaml'];
+for (const f of coreFiles) {
+  if (fileExists(f)) {
+    ok(f);
+  } else {
+    error(`${f} — missing`);
+  }
+}
+
+// 7. Hooks (if settings.json references them)
+console.log('\nHooks:');
+const settings = readFile('.claude/settings.json');
+if (settings) {
+  try {
+    const parsed = JSON.parse(settings);
+    const hooks = parsed.hooks || {};
+    for (const [event, hookList] of Object.entries(hooks)) {
+      for (const hook of hookList) {
+        const cmd = hook.command || '';
+        // Extract script path from command (first token before any args)
+        const scriptPath = cmd.split(/\s/)[0];
+        if (scriptPath && scriptPath.startsWith('.')) {
+          if (fileExists(scriptPath)) {
+            ok(`${event}: ${scriptPath}`);
+          } else {
+            error(`${event}: ${scriptPath} — referenced in settings.json but missing`);
+          }
+        }
+      }
+    }
+  } catch (e) {
+    error(`settings.json — invalid JSON: ${e.message}`);
+  }
+} else {
+  warn('No .claude/settings.json found');
+}
+
+// --- Summary ---
+console.log('\n' + '─'.repeat(40));
+if (errors > 0) {
+  console.error(`\n❌ ${errors} error(s), ${warnings} warning(s)\n`);
+  process.exit(1);
+} else if (warnings > 0) {
+  console.log(`\n⚠️  ${warnings} warning(s), 0 errors\n`);
+  process.exit(0);
+} else {
+  console.log('\n✅ All artifacts valid\n');
+  process.exit(0);
+}

package/.catalyst/main/project-config.yaml

@@ -25,6 +25,9 @@ git:
     - "main"
     - "master"
 
+  # Path for git worktrees (relative to repo root, used by /build-spec-worktree)
+  worktree_path: ".catalyst/worktrees"
+
   # Commit message templates
   commit_templates:
     red_phase: "test({scope}): write failing tests for {spec}"

package/.catalyst/spec-structure.yaml

@@ -35,7 +35,7 @@ files:
   handoff.md:
     owner: scribe
     purpose: Human-readable summary (colleague walkthrough)
-    created: build-spec (started), validate-spec (finalized)
+    created: build-spec (started), review-spec (finalized)
     updated_by: [scribe, arbiter]
     pattern: narrative
     note: |
@@ -45,7 +45,7 @@ files:
   validation.md:
     owner: arbiter
     purpose: Test results, quality checks
-    created: validate-spec
+    created: review-spec
     updated_by: [arbiter, enforcer, sentinel, inquisitor, watcher]
 
   assets/:
@@ -289,7 +289,7 @@ build_dag:
 library:
   root: "library/"
   description: "Reusable patterns extracted from completed specs"
-  created_by: "/approve-spec (optional)"
+  created_by: "/commit-spec (optional)"
 
   # Auto-detect patterns by keywords
   pattern_detection:
@@ -316,4 +316,4 @@ library:
 
 completed:
   location: "completed/"
-  description: "Specs moved here after /approve-spec"
+  description: "Specs moved here after /commit-spec"

package/.claude/agents/alchemist.md

@@ -41,7 +41,8 @@ You handle all database concerns including schema design, migrations, and data t
 5. **Indexes**: Plan for query performance
 6. **Migration**: Write safe, reversible migrations
 7. **Self-Review**: Before reporting done (see below)
-8. **Report**: Actual test/migration output, files changed, any concerns
+8. **Update tasks.md**: Mark your task as done (see below) — MANDATORY
+9. **Report**: Actual test/migration output, files changed, any concerns
 
 ## Self-Review Before Reporting
 
@@ -72,6 +73,33 @@ Before reporting task completion to the orchestrator, review your own work:
 
 If you find issues during self-review, fix them before reporting.
 
+## MANDATORY: Update tasks.md on Completion
+
+**After your task passes self-review, you MUST update tasks.md BEFORE reporting back.**
+
+The orchestrator may lose context or the conversation may end before it updates. If you don't do this, your work looks like it never happened.
+
+### How to Update
+
+1. **Find tasks.md**: Read `.catalyst/specs/*/tasks.md` (the spec you're working on)
+2. **Update the Progress table**: Change your task's status from `⚡ Active` to `✓ Done`
+3. **Add commit hash** if you committed
+4. **Update Current Session**: Note what's next based on the DAG
+
+### Example
+
+Before:
+```
+| db-schema | ⚡ Active | alchemist | Pending | Working... |
+```
+
+After:
+```
+| db-schema | ✓ Done | alchemist | ✓ Pass | Schema migrated, types generated |
+```
+
+**If you skip this step, `/primer-spec` will show the spec as not started and all your progress is invisible.**
+
 ## When Receiving Review Feedback
 
 Follow `.claude/skills/receiving-code-review/SKILL.md`:

package/.claude/agents/arbiter.md

@@ -2,7 +2,7 @@
 name: arbiter
 description: >
   PROACTIVELY DELEGATE validation orchestration to this agent. MUST BE USED when:
-  - /validate-spec command is invoked
+  - /review-spec command is invoked
   - Implementation is complete and needs quality checks
   - Production readiness needs to be verified
 

package/.claude/agents/enforcer.md

@@ -85,6 +85,32 @@ Write test → Run (PASS) → Revert the fix → Run (MUST FAIL) → Restore fix
 If it doesn't fail when reverted, the test is worthless.
 ```
 
+## MANDATORY: Update tasks.md on Completion
+
+**After completing your test-writing or integration task, you MUST update tasks.md BEFORE reporting back.**
+
+The orchestrator may lose context or the conversation may end before it updates. If you don't do this, your work looks like it never happened.
+
+### How to Update
+
+1. **Find tasks.md**: Read `.catalyst/specs/*/tasks.md` (the spec you're working on)
+2. **Update the Progress table**: Change your task's status from `⚡ Active` to `✓ Done`
+3. **Update Current Session**: Note what's next based on the DAG
+
+### Example
+
+Before:
+```
+| integration | ⚡ Active | enforcer | Pending | Running E2E tests |
+```
+
+After:
+```
+| integration | ✓ Done | enforcer | ✓ Pass | All integration tests passing |
+```
+
+**If you skip this step, `/primer-spec` will show the spec as not started and all your progress is invisible.**
+
 ## Principles
 
 - **Red First**: Tests must fail before implementation — and you must WATCH them fail

package/.claude/agents/forge-master.md

@@ -52,6 +52,14 @@ Before any action, load `.claude/skills/using-skills/SKILL.md` and check which s
 - Flag blockers immediately
 - Never skip failing tests
 
+## Context Awareness
+
+Long builds consume enormous context. At each phase gate:
+- Check if context is getting long
+- Remind the user: *"Context checkpoint — good time to compact if needed. `/primer-spec @{slug}` to resume."*
+- Always update `tasks.md ## Current Session` before suggesting compaction
+- The PreCompact hook will auto-save state, but proactive updates are better
+
 ## DAG Execution Model
 
 ### Reading the DAG
@@ -133,6 +141,8 @@ This commit is PROOF that red phase happened.
 No commit = no implementation. No exceptions.
 ```
 
+> **Context checkpoint:** Update `tasks.md ## Current Session`, then tell the user: *"Good point to compact if context is long. `/primer-spec @{slug}` to resume."*
+
 ### 3. Foundation Phase (Sequential)
 ```
 Spawn: Alchemist
@@ -177,6 +187,8 @@ This commit is PROOF that green phase happened.
 No commit = no integration. No exceptions.
 ```
 
+> **Context checkpoint:** Update `tasks.md ## Current Session`, then tell the user: *"Good point to compact if context is long. `/primer-spec @{slug}` to resume."*
+
 ### 6. Integration Phase (Sequential)
 ```
 Spawn: Enforcer
@@ -214,9 +226,18 @@ Agent reports "task complete, tests pass":
 1. Check: Did the agent include actual test output in its report?
 2. Check: Does VCS diff show the expected file changes?
 3. Run: Execute the test command for that scope yourself
-4. ONLY THEN: Mark the task as Done in tasks.md
+4. Verify: Did the agent update tasks.md Progress table? (agents are instructed to)
+5. If NOT updated: Update tasks.md yourself IMMEDIATELY
+6. ONLY THEN: Consider the task Done
 ```
 
+### CRITICAL: tasks.md Must Stay Current
+
+Agents are instructed to update tasks.md themselves. But if an agent fails to do so:
+- **You MUST update tasks.md immediately** after verifying completion
+- Do NOT defer this — if the conversation ends, stale tasks.md means `/primer-spec` shows no progress
+- Update BOTH the Progress table AND the Current Session section
+
 ## Escalation Protocol
 
 See: `.claude/skills/agent-delegation/SKILL.md`

package/.claude/agents/inquisitor.md

@@ -13,7 +13,7 @@ color: red
 skills: lint-checking, code-review
 ---
 
-You are the Inquisitor, a code quality specialist who reviews code for issues.
+You are the Inquisitor, a code quality specialist who reviews code for issues and proposes simplifications.
 
 ## Opening
 
@@ -21,7 +21,7 @@ You are the Inquisitor, a code quality specialist who reviews code for issues.
 
 ## Role
 
-You enforce code quality standards through linting, pattern review, and code review.
+You enforce code quality standards through linting, pattern review, code review, and **code simplification**.
 
 ## Behavior
 
@@ -31,6 +31,7 @@ You enforce code quality standards through linting, pattern review, and code rev
 - Provide actionable fix suggestions
 - Avoid nitpicking
 - Ensure test coverage
+- **Identify code that can be simplified without changing behavior**
 
 ## Review Checklist
 
@@ -59,6 +60,22 @@ You enforce code quality standards through linting, pattern review, and code rev
 - Testable structure
 - Reasonable complexity
 
+### Code Simplification
+
+Look for and suggest fixes for:
+- **Unnecessary abstractions** — helpers/utilities created for one-time use; inline them
+- **Over-engineered patterns** — factory patterns, strategy patterns, builders where a simple function suffices
+- **Overly defensive code** — error handling for impossible scenarios, redundant null checks on non-nullable types
+- **Dead code** — unused imports, unreachable branches, commented-out code
+- **Premature generalization** — config objects, feature flags, or extensibility hooks for things that have only one use
+- **Verbose patterns** — 10 lines that could be 3 without losing clarity
+
+**Rules for simplification:**
+- NEVER change behavior — only structure
+- NEVER remove error handling at system boundaries (user input, external APIs)
+- Verify tests still pass after each simplification
+- If unsure whether something is dead code, leave it and flag it as "candidate for removal"
+
 ## Output
 
 Provide review with:
@@ -66,5 +83,5 @@ Provide review with:
 - Critical issues (must fix)
 - Major issues (should fix)
 - Minor issues (nice to fix)
-- Suggestions for improvement
+- **Simplification opportunities** (with before/after snippets)
 - What's done well

package/.claude/agents/shaper.md

@@ -41,7 +41,8 @@ You implement frontend functionality including React components, pages, and UI f
 5. **Style**: Apply styling to match design
 6. **Polish**: Add interactions, transitions, states
 7. **Self-Review**: Before reporting done (see below)
-8. **Report**: Actual test output, files changed, any concerns
+8. **Update tasks.md**: Mark your task as done (see below) — MANDATORY
+9. **Report**: Actual test output, files changed, any concerns
 
 ## Self-Review Before Reporting
 
@@ -68,6 +69,33 @@ Before reporting task completion to the orchestrator, review your own work:
 
 If you find issues during self-review, fix them before reporting.
 
+## MANDATORY: Update tasks.md on Completion
+
+**After your task passes self-review, you MUST update tasks.md BEFORE reporting back.**
+
+The orchestrator may lose context or the conversation may end before it updates. If you don't do this, your work looks like it never happened.
+
+### How to Update
+
+1. **Find tasks.md**: Read `.catalyst/specs/*/tasks.md` (the spec you're working on)
+2. **Update the Progress table**: Change your task's status from `⚡ Active` to `✓ Done`
+3. **Add commit hash** if you committed
+4. **Update Current Session**: Note what's next based on the DAG
+
+### Example
+
+Before:
+```
+| ui-profile | ⚡ Active | shaper-1 | Pending | Working... |
+```
+
+After:
+```
+| ui-profile | ✓ Done | shaper-1 | ✓ Pass | Profile page complete |
+```
+
+**If you skip this step, `/primer-spec` will show the spec as not started and all your progress is invisible.**
+
 ## When Receiving Review Feedback
 
 Follow `.claude/skills/receiving-code-review/SKILL.md`:

package/.claude/agents/smith.md

@@ -40,7 +40,8 @@ You implement backend functionality including APIs, services, business logic, an
 4. **Implement**: Write code to pass tests (green phase)
 5. **Refactor**: Clean up while keeping tests green
 6. **Self-Review**: Before reporting done (see below)
-7. **Report**: Actual test output, files changed, any concerns
+7. **Update tasks.md**: Mark your task as done (see below) — MANDATORY
+8. **Report**: Actual test output, files changed, any concerns
 
 ## Self-Review Before Reporting
 
@@ -67,6 +68,33 @@ Before reporting task completion to the orchestrator, review your own work:
 
 If you find issues during self-review, fix them before reporting.
 
+## MANDATORY: Update tasks.md on Completion
+
+**After your task passes self-review, you MUST update tasks.md BEFORE reporting back.**
+
+The orchestrator may lose context or the conversation may end before it updates. If you don't do this, your work looks like it never happened.
+
+### How to Update
+
+1. **Find tasks.md**: Read `.catalyst/specs/*/tasks.md` (the spec you're working on)
+2. **Update the Progress table**: Change your task's status from `⚡ Active` to `✓ Done`
+3. **Add commit hash** if you committed
+4. **Update Current Session**: Note what's next based on the DAG
+
+### Example
+
+Before:
+```
+| api-auth | ⚡ Active | smith-1 | Pending | Working... |
+```
+
+After:
+```
+| api-auth | ✓ Done | smith-1 | ✓ Pass | Implemented auth endpoints |
+```
+
+**If you skip this step, `/primer-spec` will show the spec as not started and all your progress is invisible.**
+
 ## When Receiving Review Feedback
 
 Follow `.claude/skills/receiving-code-review/SKILL.md`:

package/.claude/commands/build-spec-worktree.md

@@ -0,0 +1,19 @@
+# /build-spec-worktree
+
+Implement a specification using **strict TDD** in an isolated git worktree.
+
+Use this instead of `/build-spec` when you need worktree isolation — e.g., working on a second spec while another is in progress, or wanting a clean working directory.
+
+## Usage
+
+```
+/build-spec-worktree @2025-11-29-stripe-integration
+```
+
+---
+
+**Invoke skill:** `build-orchestration` with `--worktree`
+
+**Orchestrator:** Forge-Master (delegates to Forger, Enforcer, Smith, Shaper, Alchemist)
+
+**Process skills used:** `test-driven-development`, `agent-delegation`, `verification-before-completion`, `systematic-debugging`

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

@@ -8,6 +8,18 @@ Implement a specification using **strict TDD**.
 /build-spec @2025-11-29-stripe-integration
 ```
 
+## Pre-computed Context
+
+```bash
+# Detect spec and branch state
+echo "=== BRANCH ===" && git branch --show-current
+echo "=== STATUS ===" && git status --short
+echo "=== SPEC FILES ===" && ls .catalyst/specs/*$ARGUMENTS*/ 2>/dev/null || echo "No spec found for: $ARGUMENTS"
+echo "=== SPEC FRONTMATTER ===" && head -30 .catalyst/specs/*$ARGUMENTS*/spec.md 2>/dev/null || echo "No spec.md"
+echo "=== TASKS EXIST? ===" && head -5 .catalyst/specs/*$ARGUMENTS*/tasks.md 2>/dev/null || echo "No tasks.md yet (fresh build)"
+echo "=== PROJECT CONFIG ===" && cat .catalyst/main/project-config.yaml 2>/dev/null || echo "No project config"
+```
+
 ---
 
 **Invoke skill:** `build-orchestration`

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

@@ -0,0 +1,20 @@
+# /commit-spec
+
+Commit, archive, and propagate learnings from a **fully built and validated** implementation.
+
+> **Lifecycle position:** This is the FINAL step. Only use after `/build-spec` and `/review-spec` have completed successfully.
+>
+> **Flow:** `/catalyze-spec` → `/build-spec` → `/review-spec` → **`/commit-spec`**
+
+## Usage
+
+```
+/commit-spec @2025-11-29-stripe-integration
+/commit-spec @2025-11-29-stripe-integration "Great work!"
+```
+
+---
+
+**Invoke skill:** `spec-approval`
+
+**Process skills used:** `verification-before-completion`, `agent-delegation`

package/.claude/commands/{reject-spec.md → discard-spec.md}

@@ -1,13 +1,13 @@
-# /reject-spec
+# /discard-spec
 
 Request changes to the implementation.
 
 ## Usage
 
 ```
-/reject-spec @2025-11-29-stripe-integration "reason"
-/reject-spec @2025-11-29-stripe-integration "UI doesn't match mockup"
-/reject-spec @2025-11-29-stripe-integration "TDD not followed"
+/discard-spec @2025-11-29-stripe-integration "reason"
+/discard-spec @2025-11-29-stripe-integration "UI doesn't match mockup"
+/discard-spec @2025-11-29-stripe-integration "TDD not followed"
 ```
 
 ---
@@ -17,7 +17,7 @@ Request changes to the implementation.
 **If TDD was not followed, this is an automatic rejection reason:**
 
 ```
-/reject-spec @spec-name "TDD not followed - tests written after code"
+/discard-spec @spec-name "TDD not followed - tests written after code"
 ```
 
 This routes directly back to `/build-spec` with instructions to follow TDD.
@@ -55,7 +55,7 @@ Based on rejection reason:
 | Test failures | Enforcer + Builders | `/build-spec` |
 | UI/UX issues | Shaper | `/build-spec` |
 | API issues | Smith | `/build-spec` |
-| Quality issues | Inquisitor | `/validate-spec` |
+| Quality issues | Inquisitor | `/review-spec` |
 | Security issues | Watcher | IMMEDIATE FIX |
 
 ### Phase 3: Update Status
@@ -77,7 +77,7 @@ Update `tasks.md` with action items:
 
 ### Standard Rejection
 ```
-Spec rejected - changes requested
+Spec discarded - changes requested
 
 Spec: 2025-11-29-stripe-integration
 Reason: UI doesn't match mockup
@@ -90,12 +90,12 @@ Changes needed:
 Updated: .catalyst/specs/{slug}/validation.md
 
 Next: Fix issues and run /build-spec @2025-11-29-stripe-integration
-      Then /validate-spec @2025-11-29-stripe-integration
+      Then /review-spec @2025-11-29-stripe-integration
 ```
 
 ### TDD Violation Rejection
 ```
-Spec rejected - TDD VIOLATION
+Spec discarded - TDD VIOLATION
 
 Spec: 2025-11-29-stripe-integration
 Reason: TDD not followed - tests written after code

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

@@ -9,6 +9,16 @@ Continue building a spec with new improvements discovered during development.
 /iterate-spec @2025-11-29-stripe-integration "handle edge case where user cancels mid-checkout"
 ```
 
+## Pre-computed Context
+
+```bash
+# Current state for iteration
+echo "=== BRANCH ===" && git branch --show-current
+echo "=== STATUS ===" && git status --short
+echo "=== TASKS.MD ===" && cat .catalyst/specs/*$ARGUMENTS*/tasks.md 2>/dev/null | head -80 || echo "No tasks.md for: $ARGUMENTS"
+echo "=== SPEC FRONTMATTER ===" && head -30 .catalyst/specs/*$ARGUMENTS*/spec.md 2>/dev/null || echo "No spec.md"
+```
+
 ---
 
 **Invoke skill:** `spec-iteration`