catalyst-os 1.3.0 → 2.0.0

package/.catalyst/bin/install.js

@@ -162,7 +162,7 @@ function install() {
   ${yellow}Next steps:${reset}
     1. Run ${cyan}/catalyze-project${reset} to initialize your project
     2. Run ${cyan}/catalyze-spec${reset} to create your first specification
-    3. Run ${cyan}/build-spec${reset} to implement it
+    3. Run ${cyan}/forge-spec${reset} to implement it
 
   ${dim}Documentation: https://github.com/Ealikadioglu/catalyst-os${reset}
 `);

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

@@ -25,7 +25,7 @@ git:
     - "main"
     - "master"
 
-  # Path for git worktrees (relative to repo root, used by /build-spec-worktree)
+  # Path for git worktrees (relative to repo root, used by /forge-spec-worktree)
   worktree_path: ".catalyst/worktrees"
 
   # Commit message templates

package/.catalyst/spec-structure.yaml

@@ -25,7 +25,7 @@ files:
   tasks.md:
     owner: forger
     purpose: DAG + progress + decisions + session context (THE living doc)
-    created: build-spec
+    created: forge-spec
     updated_by: [forger, forge-master, builders]
     pattern: living
     note: |
@@ -35,7 +35,7 @@ files:
   handoff.md:
     owner: scribe
     purpose: Human-readable summary (colleague walkthrough)
-    created: build-spec (started), review-spec (finalized)
+    created: forge-spec (started), audit-spec (finalized)
     updated_by: [scribe, arbiter]
     pattern: narrative
     note: |
@@ -45,7 +45,7 @@ files:
   validation.md:
     owner: arbiter
     purpose: Test results, quality checks
-    created: review-spec
+    created: audit-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: "/commit-spec (optional)"
+  created_by: "/seal-spec (optional)"
 
   # Auto-detect patterns by keywords
   pattern_detection:
@@ -316,4 +316,4 @@ library:
 
 completed:
   location: "completed/"
-  description: "Specs moved here after /commit-spec"
+  description: "Specs moved here after /seal-spec"

package/.claude/agents/arbiter.md

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

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

@@ -2,7 +2,7 @@
 name: forge-master
 description: >
   PROACTIVELY DELEGATE build orchestration to this agent. MUST BE USED when:
-  - /build-spec command is invoked
+  - /forge-spec command is invoked
   - A specification needs to be implemented
   - TDD workflow needs to be coordinated
 

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

@@ -0,0 +1,30 @@
+# /archive-spec
+
+Archive a spec without git ceremony. Marks as COMPLETE, moves to completed folder, and checks for library patterns.
+
+> **Use when:** You want to close out a spec without branch management or push suggestions.
+> **For full ceremony:** Use `/seal-spec` instead.
+>
+> **Flow:** `/catalyze-spec` → `/forge-spec` → `/audit-spec` → **`/archive-spec`** (lightweight) or **`/seal-spec`** (full)
+
+## Usage
+
+```
+/archive-spec @2025-11-29-stripe-integration
+/archive-spec @2025-11-29-stripe-integration "closing out"
+```
+
+## Pre-computed Context
+
+```bash
+# Spec state for archival
+echo "=== SPEC FILES ===" && ls .catalyst/specs/*$ARGUMENTS*/ 2>/dev/null || echo "No spec found for: $ARGUMENTS"
+echo "=== SPEC STATUS ===" && head -20 .catalyst/specs/*$ARGUMENTS*/spec.md 2>/dev/null || echo "No spec.md"
+echo "=== TASKS.MD ===" && cat .catalyst/specs/*$ARGUMENTS*/tasks.md 2>/dev/null | head -40 || echo "No tasks.md"
+```
+
+---
+
+**Invoke skill:** `spec-archival`
+
+**Process skills used:** `verification-before-completion`

package/.claude/commands/{review-spec.md → audit-spec.md}

@@ -1,11 +1,15 @@
-# /review-spec
+# /audit-spec
 
 Run validation checks and code simplification on a completed implementation.
 
+> **Lifecycle position:** `/catalyze-spec` → `/forge-spec` → **`/audit-spec`** → `/seal-spec`
+>
+> **Note:** This audits the CODE implementation (quality, security, tests) — not the spec document.
+
 ## Usage
 
 ```
-/review-spec @2025-11-29-stripe-integration
+/audit-spec @2025-11-29-stripe-integration
 ```
 
 ## Pre-computed Context

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

@@ -20,7 +20,7 @@ Request changes to the implementation.
 /discard-spec @spec-name "TDD not followed - tests written after code"
 ```
 
-This routes directly back to `/build-spec` with instructions to follow TDD.
+This routes directly back to `/forge-spec` with instructions to follow TDD.
 
 ---
 
@@ -50,12 +50,12 @@ Based on rejection reason:
 
 | Issue Type | Route To | Command |
 |------------|----------|---------|
-| **TDD not followed** | Enforcer -> Builders | `/build-spec` (restart) |
-| Missing tests | Enforcer | `/build-spec` |
-| Test failures | Enforcer + Builders | `/build-spec` |
-| UI/UX issues | Shaper | `/build-spec` |
-| API issues | Smith | `/build-spec` |
-| Quality issues | Inquisitor | `/review-spec` |
+| **TDD not followed** | Enforcer -> Builders | `/forge-spec` (restart) |
+| Missing tests | Enforcer | `/forge-spec` |
+| Test failures | Enforcer + Builders | `/forge-spec` |
+| UI/UX issues | Shaper | `/forge-spec` |
+| API issues | Smith | `/forge-spec` |
+| Quality issues | Inquisitor | `/audit-spec` |
 | Security issues | Watcher | IMMEDIATE FIX |
 
 ### Phase 3: Update Status
@@ -89,8 +89,8 @@ Changes needed:
 
 Updated: .catalyst/specs/{slug}/validation.md
 
-Next: Fix issues and run /build-spec @2025-11-29-stripe-integration
-      Then /review-spec @2025-11-29-stripe-integration
+Next: Fix issues and run /forge-spec @2025-11-29-stripe-integration
+      Then /audit-spec @2025-11-29-stripe-integration
 ```
 
 ### TDD Violation Rejection
@@ -108,7 +108,7 @@ Required process:
 3. Builders implement features
 4. Verify all tests PASS (green phase)
 
-Next: Run /build-spec @2025-11-29-stripe-integration
+Next: Run /forge-spec @2025-11-29-stripe-integration
       Follow TDD process strictly.
 ```
 

package/.claude/commands/{build-spec-worktree.md → forge-spec-worktree.md}

@@ -1,13 +1,15 @@
-# /build-spec-worktree
+# /forge-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.
+Use this instead of `/forge-spec` when you need worktree isolation — e.g., working on a second spec while another is in progress, or wanting a clean working directory.
+
+> **Lifecycle position:** `/catalyze-spec` → **`/forge-spec-worktree`** → `/audit-spec` → `/seal-spec`
 
 ## Usage
 
 ```
-/build-spec-worktree @2025-11-29-stripe-integration
+/forge-spec-worktree @2025-11-29-stripe-integration
 ```
 
 ---

package/.claude/commands/{build-spec.md → forge-spec.md}

@@ -1,11 +1,13 @@
-# /build-spec
+# /forge-spec
 
 Implement a specification using **strict TDD**.
 
+> **Lifecycle position:** `/catalyze-spec` → **`/forge-spec`** → `/audit-spec` → `/seal-spec`
+
 ## Usage
 
 ```
-/build-spec @2025-11-29-stripe-integration
+/forge-spec @2025-11-29-stripe-integration
 ```
 
 ## Pre-computed Context

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

@@ -155,8 +155,7 @@ Ready to continue. What would you like to work on?
 | Situation | Command |
 |-----------|---------|
 | Context full, need to continue building | `/primer-spec` |
-| Want to add improvement mid-build | `/iterate-spec` |
-| Need full validation | `/review-spec` |
+| Need full validation | `/audit-spec` |
 | Check status without loading context | `/status-spec` |
 
 ---
@@ -164,5 +163,5 @@ Ready to continue. What would you like to work on?
 ## Tips
 
 - Run this FIRST in a new conversation before doing any work
-- After primer, you can run `/iterate-spec` or continue with `/build-spec`
-- If tasks.md doesn't exist, the spec hasn't been built yet - run `/build-spec`
+- After primer, continue with `/forge-spec`
+- If tasks.md doesn't exist, the spec hasn't been built yet - run `/forge-spec`

package/.claude/commands/roadmap.md

@@ -1,6 +1,6 @@
 # /roadmap
 
-Create or update the project roadmap.
+Create or update the project roadmap with spec-grouped entries and actionable next commands.
 
 ## Usage
 
@@ -13,50 +13,57 @@ Create or update the project roadmap.
 
 1. **Read** `.catalyst/main/mission.md` for context
 2. **Read existing** `.catalyst/main/roadmap.md` if present
-3. **Analyze** codebase for current feature state
-4. **Ask** about priorities and timeline:
+3. **Scan specs** in `.catalyst/specs/` to determine current state of each spec
+4. **Analyze** codebase for current feature state
+5. **Ask** about priorities and timeline:
    - What's most important right now?
    - What's blocking progress?
    - What's the target timeline?
-5. **Create/Update** the roadmap
+6. **Resolve commands** for each spec entry (see Command Resolution below)
+7. **Create/Update** the roadmap using the template at `.catalyst/main/temp/temp-roadmap.md`
 
-## Output Format
+## Command Resolution
 
-`.catalyst/main/roadmap.md`:
+The canonical spec workflow is: `/catalyze-spec` → `/forge-spec` → `/audit-spec` → `/seal-spec`
 
-```markdown
-# Project Roadmap
+For each spec entry in the roadmap, determine the next action based on its state:
 
-## Current State
-[Brief assessment of where the project is now]
+| Spec State | How to Detect | Next Command |
+|------------|---------------|--------------|
+| Not yet created | Only exists in roadmap, no spec folder | `!/catalyze-spec "{seed prompt}"` |
+| DRAFT | `spec.md` exists, no `tasks.md` | `!/forge-spec @{slug}` or `!/forge-spec-worktree @{slug}` |
+| IN_PROGRESS | `tasks.md` exists, build ongoing | `!/audit-spec @{slug}` |
+| VALIDATING | `validation.md` exists | `!/seal-spec @{slug}` |
+| COMPLETE | `handoff.md` exists with sealed status | No command (show checkmark) |
 
-## Phase 1: Foundation (Now - 1 month)
-### Goals
-- [Specific, measurable goal]
-- [Another goal]
+> **Worktree tip:** Use `!/forge-spec-worktree` when another spec is already in progress on the current branch, or when file scopes might collide between concurrent specs.
 
-### Key Features
-- [ ] Feature 1 - Description
-- [ ] Feature 2 - Description
+### Detection Logic
 
-## Phase 2: Growth (1-3 months)
-### Goals
-- [Goal]
+For each spec entry, check `.catalyst/specs/{slug}/`:
 
-### Key Features
-- [ ] Feature
+```
+IF no folder exists for this entry:
+  → Status: Planned | Command: !/catalyze-spec "{seed prompt}"
 
-## Phase 3: Scale (3-6 months)
-### Goals
-- [Goal]
+ELSE IF spec.md exists BUT tasks.md does NOT:
+  → Status: DRAFT | Command: !/forge-spec @{slug} (or !/forge-spec-worktree @{slug})
 
-### Key Features
-- [ ] Feature
+ELSE IF tasks.md exists BUT validation.md does NOT:
+  → Status: IN_PROGRESS | Command: !/audit-spec @{slug}
 
-## Long-term Vision
-[Where this is heading in 6-12 months]
+ELSE IF validation.md exists BUT not sealed:
+  → Status: VALIDATING | Command: !/seal-spec @{slug}
 
----
-*Last updated: YYYY-MM-DD*
+ELSE (sealed):
+  → Status: COMPLETE | Command: (none)
 ```
 
+## Output Format
+
+`.catalyst/main/roadmap.md` — uses the structure defined in `.catalyst/main/temp/temp-roadmap.md`
+
+Specs are grouped within time-horizon sections:
+- **Short-Term (1-3 months)** — immediate priorities
+- **Medium-Term (3-6 months)** — next wave of work
+- **Long-Term Vision (6+ months)** — strategic goals, not yet ready for specs

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

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

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

@@ -174,7 +174,7 @@ Tests: N/A
 
 NEXT STEPS
 ----------
-1. Run /build-spec to start implementation
+1. Run /forge-spec to start implementation
 2. Forger will create task breakdown
 3. Enforcer will write tests first (TDD)
 ```
@@ -242,9 +242,9 @@ VALIDATION STATUS
 
 NEXT STEPS
 ----------
-1. Complete validation: /review-spec @slug
+1. Complete validation: /audit-spec @slug
 2. Review handoff.md when ready
-3. Commit: /commit-spec @slug
+3. Commit: /seal-spec @slug
 ```
 
 ---
@@ -262,7 +262,7 @@ tasks.md not found - implementation hasn't started.
 
 NEXT STEPS
 ----------
-Run /build-spec @2025-11-29-stripe-integration to begin.
+Run /forge-spec @2025-11-29-stripe-integration to begin.
 ```
 
 ### Uncommitted Work Not Matching Any Task

package/.claude/commands/sync-project.md

@@ -0,0 +1,28 @@
+# /sync-project
+
+Sync all spec statuses with reality. Scans active specs, detects completed work, updates tasks.md, and archives finished specs.
+
+> **Use when:** You forgot to `/audit-spec` and `/seal-spec` for one or more specs, or want to catch up on housekeeping.
+
+## Usage
+
+```
+/sync-project                    # Sync all active specs
+/sync-project "focus on auth"    # Sync with specific focus
+```
+
+## Pre-computed Context
+
+```bash
+# List all active specs
+echo "=== ACTIVE SPECS ===" && ls -d .catalyst/specs/*/ 2>/dev/null || echo "No active specs"
+echo "=== COMPLETED SPECS ===" && ls -d .catalyst/specs/completed/*/ 2>/dev/null || echo "No completed specs"
+echo "=== GIT STATUS ===" && git status --short
+echo "=== RECENT COMMITS ===" && git log --oneline -15
+```
+
+---
+
+**Invoke skill:** `project-sync`
+
+**Process skills used:** `verification-before-completion`

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` or `/build-spec-worktree` command.
+> **Invoked by:** `/forge-spec` or `/forge-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 /review-spec)
+├── validation.md     # Arbiter creates (in /audit-spec)
 ├── handoff.md        # Updated throughout
 └── assets/
 ```
@@ -112,7 +112,7 @@ Phase 6: Integration (Enforcer — cross-boundary tests)
 ### Phase 0: Git Setup
 
 1. Read `project-config.yaml` for `development_branch`, `branch_prefix`, and `worktree_path`
-2. IF `--worktree` flag (from `/build-spec-worktree`):
+2. IF `--worktree` flag (from `/forge-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

package/.claude/skills/project-sync/SKILL.md

@@ -0,0 +1,114 @@
+# Project Sync
+
+> **When to invoke:** When syncing spec statuses with reality across the project.
+> **Invoked by:** `/sync-project` command.
+
+## Purpose
+
+Scan all active specs, detect which ones are actually complete, update their tasks.md, and move finished specs to the completed folder. This is a housekeeping command for catching up when `/audit-spec` and `/seal-spec` were skipped.
+
+## Skills Referenced
+
+- `verification-before-completion` — Verify actual state before marking complete
+
+## Workflow
+
+### Phase 1: Scan Active Specs
+
+1. List all folders in `.catalyst/specs/` (excluding `completed/`)
+2. For each spec, read:
+   - `spec.md` — status and requirements
+   - `tasks.md` — task progress (if exists)
+   - `validation.md` — validation results (if exists)
+
+### Phase 2: Detect Actual State
+
+For each spec, determine real status by checking:
+
+1. **Git history** — Are there commits referencing this spec?
+2. **Test results** — Do tests pass for this spec's scope?
+3. **File existence** — Are the expected implementation files present?
+4. **tasks.md progress** — Are tasks marked complete?
+
+Classify each spec:
+
+| Detected State | Criteria |
+|---------------|----------|
+| **Stale/Abandoned** | No commits in 30+ days, incomplete tasks |
+| **Complete (unarchived)** | All tasks done, tests pass, but still in active specs |
+| **In Progress** | Some tasks done, recent activity |
+| **Draft** | spec.md exists but no tasks.md or implementation |
+
+### Phase 3: Present Findings
+
+Show the user a summary:
+
+```
+PROJECT SYNC REPORT
+===================
+
+SPECS READY TO ARCHIVE (complete but not moved):
+  ✅ 2026-01-11-user-auth — All 8 tasks done, tests passing
+  ✅ 2026-02-15-stripe-integration — All 6 tasks done, tests passing
+
+SPECS IN PROGRESS:
+  🚧 2026-03-01-notifications — 4/7 tasks done
+  🚧 2026-03-15-search — 2/5 tasks done
+
+STALE SPECS (no activity in 30+ days):
+  ⚠️  2026-01-05-legacy-migration — 0/3 tasks done, last commit 45 days ago
+
+DRAFTS (not yet built):
+  📋 2026-04-01-admin-dashboard — spec.md only, no tasks.md
+```
+
+Ask user: "Which specs should I archive?"
+
+### Phase 4: Archive Confirmed Specs
+
+For each spec the user confirms:
+
+1. Update `tasks.md`:
+   - Mark remaining in-progress tasks as complete (if work is done)
+   - Add sync note:
+     ```markdown
+     ## Synced
+     **Date:** YYYY-MM-DD
+     **Method:** /sync-project (batch archive)
+     ```
+
+2. Update `spec.md` status to `complete`
+
+3. Move to completed:
+   ```
+   .catalyst/specs/{slug}/ → .catalyst/specs/completed/{slug}/
+   ```
+
+4. Check for library extraction (same keyword matching as `/archive-spec`)
+
+### Phase 5: Update Roadmap (Optional)
+
+If `.catalyst/main/roadmap.md` exists:
+1. Update status of archived specs to COMPLETE
+2. Update command sections for completed specs
+
+## Output
+
+```
+Project synced!
+
+Archived: 2 specs
+├── 2026-01-11-user-auth → .catalyst/specs/completed/
+└── 2026-02-15-stripe-integration → .catalyst/specs/completed/
+
+Skipped: 2 specs (still in progress)
+├── 2026-03-01-notifications (4/7 tasks)
+└── 2026-03-15-search (2/5 tasks)
+
+Flagged: 1 stale spec
+└── 2026-01-05-legacy-migration (no activity 45 days)
+
+Library: Added authentication.md, payment-integration.md
+
+Roadmap: Updated .catalyst/main/roadmap.md
+```

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:** `/commit-spec` command.
+> **Invoked by:** `/seal-spec` command.
 
 ## Purpose
 
@@ -15,12 +15,12 @@ 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` → `/review-spec` → **`/commit-spec`** (you are here)
+> **Flow:** `/catalyze-spec` → `/forge-spec` → `/audit-spec` → **`/seal-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 `/review-spec` first.
+> If the spec has not been built yet, STOP and tell the user to run `/forge-spec` first.
+> If the spec has not been validated yet, STOP and tell the user to run `/audit-spec` first.
 
-- `/build-spec` must have been completed (tasks.md exists with completed tasks)
+- `/forge-spec` must have been completed (tasks.md exists with completed tasks)
 - Validation must be complete (`validation.md` must show all checks passed)
 - `handoff.md` must exist
 - TDD compliance verified

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

@@ -0,0 +1,77 @@
+# Spec Archival
+
+> **When to invoke:** When archiving a spec without git ceremony.
+> **Invoked by:** `/archive-spec` command.
+
+## Purpose
+
+Lightweight spec completion: move to completed folder, check for library patterns, update status. No TDD verification, no git branch checks, no commit creation, no push suggestions.
+
+> **For full ceremony with git management:** Use `/seal-spec` instead.
+>
+> **Flow:** `/catalyze-spec` → `/forge-spec` → `/audit-spec` → **`/archive-spec`** (you are here)
+
+## Skills Referenced
+
+- `verification-before-completion` — Verify spec folder exists before archiving
+
+## Workflow
+
+### Phase 1: Read Spec and Verify
+
+1. Read spec.md to understand what's being archived
+2. Read tasks.md to understand current progress (if exists)
+3. Verify spec folder exists in `.catalyst/specs/`
+   - IF NOT FOUND → STOP: "Spec not found: @{slug}"
+
+4. Check spec readiness:
+   - **DRAFT** (no tasks.md): Ask user — "This spec was never built. Archive a draft?"
+   - **IN_PROGRESS** (tasks incomplete): Ask user — "Some tasks are incomplete. Archive anyway?"
+   - **VALIDATING or later**: Proceed without confirmation
+
+### Phase 2: Update tasks.md
+
+1. Mark tasks that are actually done as complete (check git history, file existence, test results)
+2. Leave incomplete tasks as-is — they stay open for visibility
+
+### Phase 3: Library Extraction (Optional)
+
+Auto-detect reusable patterns from spec name/content using keyword matching:
+
+| Pattern Keywords | Suggested Library Item |
+|-----------------|----------------------|
+| stripe, payment | payment-integration.md |
+| auth, oauth, login | authentication.md |
+| upload, s3, storage | file-storage.md |
+| websocket, realtime | real-time-communication.md |
+| email, notification | notifications.md |
+| search, elasticsearch | search-implementation.md |
+| cache, redis | caching-strategy.md |
+| queue, job, worker | background-jobs.md |
+
+Ask user if spec should be added to pattern library. If yes, delegate to Scribe for extraction to `.catalyst/library/`.
+
+### Phase 4: Archive
+
+1. Move spec folder:
+   ```
+   .catalyst/specs/{slug}/ → .catalyst/specs/completed/{slug}/
+   ```
+2. Update spec.md frontmatter status to `complete`
+3. Add completion date to frontmatter
+
+## Output
+
+```
+Spec archived!
+
+Spec: {slug}
+Status: COMPLETE
+
+Archived to: .catalyst/specs/completed/{slug}/
+
+Library: {Added to .catalyst/library/X.md | Skipped}
+
+Note: This was a lightweight archive (no git ceremony).
+For full commit + branch management, use /seal-spec.
+```

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

@@ -167,15 +167,14 @@ Created: .catalyst/specs/YYYY-MM-DD-{slug}/
 ├── handoff.md   <- Living document
 └── assets/      <- UI references (if any)
 
-REMINDER: /build-spec follows strict TDD
+REMINDER: /forge-spec follows strict TDD
   1. Tests written FIRST (Enforcer)
   2. Tests must FAIL (red phase)
   3. Then implement (Builders)
   4. Tests must PASS (green phase)
 
 Next steps:
-- /build-spec @YYYY-MM-DD-{slug} to start TDD build
-- Or /iterate-spec if you want changes first
+- /forge-spec @YYYY-MM-DD-{slug} to start TDD build
 ```
 
-**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`.
+**IMPORTANT: Do NOT suggest `/seal-spec` after spec shaping.** `/seal-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` → `/forge-spec` → `/audit-spec` → `/seal-spec`.

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

@@ -5,7 +5,7 @@
 
 ## Purpose
 
-Update spec documentation (requirements, tasks, research) without continuing to build. Unlike `/iterate-spec`, this STOPS after updating docs.
+Update spec documentation (requirements, tasks, research) without continuing to build.
 
 ## Skills Referenced
 
@@ -79,5 +79,5 @@ Change: {description}
 Updated files: {list}
 Impact: {new/removed requirements and tasks}
 
-Next: Continue with /build-spec or /iterate-spec
+Next: Continue with /forge-spec
 ```

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

@@ -1,8 +1,12 @@
 # Spec Validation
 
 > **When to invoke:** When running validation checks on a completed implementation.
-> **Invoked by:** `/review-spec` command.
+> **Invoked by:** `/audit-spec` command.
 > **Orchestrator:** Arbiter agent.
+>
+> **Lifecycle position:** `/catalyze-spec` → `/forge-spec` → **`/audit-spec`** → `/seal-spec`
+>
+> This skill audits the CODE implementation (quality, security, tests) — not the spec document.
 
 ## Purpose
 
@@ -14,11 +18,16 @@ Orchestrate comprehensive validation: TDD compliance, unit tests, E2E tests, cod
 - `agent-delegation` — Parallel agent spawning rules
 - `test-driven-development` — TDD compliance verification
 
-## Prerequisites
+## Prerequisites — BLOCKING
 
-- Spec must be in "build complete" state
-- All tasks in `tasks.md` marked complete
-- TDD compliance verified (tests pass)
+Before ANY validation begins, verify the spec was actually built:
+
+1. **tasks.md must exist** in the spec folder
+   - IF NOT FOUND → STOP: "No tasks.md found. Run `/forge-spec @{slug}` first."
+2. **Spec status must be IN_PROGRESS or later** (not DRAFT)
+   - IF DRAFT → STOP: "Spec is still in DRAFT. Run `/forge-spec @{slug}` to implement it first."
+3. All tasks in `tasks.md` marked complete
+4. TDD compliance verified (tests pass)
 
 ## Output Location
 
@@ -38,7 +47,7 @@ Before validation begins, verify TDD was followed:
 2. Verify all tests pass
 3. Verify tests were written before implementation
 
-If TDD was skipped → REJECT and return to /build-spec
+If TDD was skipped → REJECT and return to /forge-spec
 ```
 
 ## Parallel Execution
@@ -157,19 +166,19 @@ If all validation passes, create handoff.md with:
 ```
 Validation complete!
 Status: READY FOR APPROVAL
-Next: /commit-spec @slug
+Next: /seal-spec @slug
 ```
 
 ### TDD Failure
 ```
 Validation blocked!
 TDD Compliance: FAILED
-Action: Return to /build-spec and follow TDD process
+Action: Return to /forge-spec and follow TDD process
 ```
 
 ### Validation Failure
 ```
 Validation failed!
 Failed Checks: [details]
-Action: Fix issues and re-run /review-spec
+Action: Fix issues and re-run /audit-spec
 ```

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

@@ -42,13 +42,13 @@ Skills tell you HOW. User instructions tell you WHAT.
 | Skill | Path | Load when... |
 |-------|------|-------------|
 | **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` | `/review-spec` — quality checks on implementation |
-| **spec-approval** | `.claude/skills/spec-approval/SKILL.md` | `/commit-spec` — final commit and archival |
+| **build-orchestration** | `.claude/skills/build-orchestration/SKILL.md` | `/forge-spec` — implementing a specification |
+| **spec-validation** | `.claude/skills/spec-validation/SKILL.md` | `/audit-spec` — quality checks on implementation |
+| **spec-approval** | `.claude/skills/spec-approval/SKILL.md` | `/seal-spec` — final commit and archival |
+| **spec-archival** | `.claude/skills/spec-archival/SKILL.md` | `/archive-spec` — lightweight completion 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 |
+| **project-sync** | `.claude/skills/project-sync/SKILL.md` | `/sync-project` — batch sync and archive specs |
 
 ---
 

package/README.md

@@ -10,10 +10,9 @@
 npx catalyst-os                        # Install to your project
 /catalyze-project                      # Initialize project foundation
 /catalyze-spec "description"           # Shape a feature specification
-/build-spec @spec-name                 # Implement with TDD
-/iterate-spec @spec-name "improvement" # Add improvements mid-build
-/review-spec @spec-name              # Run quality checks
-/commit-spec @spec-name               # Accept and archive
+/forge-spec @spec-name                 # Implement with TDD
+/audit-spec @spec-name                 # Run quality checks
+/seal-spec @spec-name                  # Accept and archive
 ```
 
 ---
@@ -46,11 +45,11 @@ Then run `/catalyze-project` to initialize — this detects your workspace type,
 │   ├── workspace-detection/
 │   ├── spec-shaping/
 │   ├── build-orchestration/
-│   ├── spec-iteration/
 │   ├── spec-validation/
 │   ├── spec-approval/
+│   ├── spec-archival/
 │   ├── project-initialization/
-│   ├── task-building/
+│   ├── project-sync/
 │   └── spec-update/
 └── commands/            # WHEN - Thin triggers (invoke skills)
 
@@ -103,12 +102,12 @@ Without this, skills are optional documentation. With it, they're mandatory proc
 | Skill | Command | Purpose |
 |-------|---------|---------|
 | `spec-shaping` | `/catalyze-spec` | Shape feature requests into specifications |
-| `build-orchestration` | `/build-spec` | DAG-based TDD implementation |
-| `spec-iteration` | `/iterate-spec` | Update and continue mid-build |
-| `spec-validation` | `/review-spec` | Quality checks via Guardian agents |
-| `spec-approval` | `/commit-spec` | Final verification and archival |
+| `build-orchestration` | `/forge-spec` | DAG-based TDD implementation |
+| `spec-validation` | `/audit-spec` | Quality checks via Guardian agents |
+| `spec-approval` | `/seal-spec` | Final verification and archival |
+| `spec-archival` | `/archive-spec` | Lightweight completion and archival |
 | `project-initialization` | `/catalyze-project` | Workspace detection + foundation docs |
-| `task-building` | `/build-task` | Single task (brownfield) |
+| `project-sync` | `/sync-project` | Batch sync and archive specs |
 | `spec-update` | `/update-spec` | Modify spec during planning phase |
 
 ---
@@ -173,10 +172,10 @@ Guardians (Quality)
 ```
   ┌──────────────┐     ┌──────────────┐     ┌──────────────┐     ┌──────────────┐
   │              │     │              │     │              │     │              │
-  │   CATALYZE   │────>│    BUILD     │────>│   VALIDATE   │────>│    COMMIT    │
+  │   CATALYZE   │────>│    FORGE     │────>│    AUDIT     │────>│     SEAL     │
   │              │     │              │     │              │     │              │
-  │ /catalyze-   │     │ /build-spec  │     │ /validate-   │     │ /approve-    │
-  │    spec      │     │              │     │    spec      │     │    spec      │
+  │ /catalyze-   │     │ /forge-spec  │     │ /audit-spec  │     │ /seal-spec   │
+  │    spec      │     │              │     │              │     │              │
   └──────────────┘     └──────────────┘     └──────────────┘     └──────────────┘
          │                    │                    │                    │
          v                    v                    v                    v
@@ -184,15 +183,6 @@ Guardians (Quality)
   │  spec.md     │     │  tasks.md    │     │ validation.md│     │   Commit +   │
   │  research.md │     │  (updated)   │     │  handoff.md  │     │   Archive    │
   └──────────────┘     └──────────────┘     └──────────────┘     └──────────────┘
-                              │
-                              v
-                       ┌──────────────┐
-                       │   ITERATE    │ <--- New idea during build?
-                       │              │
-                       │ /iterate-    │      Updates spec + tasks
-                       │    spec      │      Continues building
-                       └──────────────┘
-
   Context full? New conversation?
   Run /primer-spec @slug to restore awareness before continuing.
 ```
@@ -205,12 +195,12 @@ Guardians (Quality)
 |---------|-------------|--------|
 | `/catalyze-project` | Start new project | mission.md, roadmap.md, tech-stack.md |
 | `/catalyze-spec "feature"` | New feature request | spec.md, research.md |
-| `/build-spec @slug` | Implement feature | tasks.md (updated) |
-| `/iterate-spec @slug "idea"` | Add improvements mid-build | Updated spec + tasks, continues building |
+| `/forge-spec @slug` | Implement feature | tasks.md (updated) |
 | `/primer-spec @slug` | Restore context (new conversation) | Brief status summary |
-| `/build-task "description"` | Modify existing code | task.md in .catalyst/tasks/ |
-| `/review-spec @slug` | Quality checks | validation.md, handoff.md |
-| `/commit-spec @slug` | Finalize | Commit + Archive |
+| `/audit-spec @slug` | Quality checks | validation.md, handoff.md |
+| `/seal-spec @slug` | Finalize | Commit + Archive |
+| `/archive-spec @slug` | Lightweight archive | Archive (no git ceremony) |
+| `/sync-project` | Batch sync spec statuses | Sync report + archives |
 | `/discard-spec @slug "reason"` | Discard implementation | Status: REJECTED |
 | `/status-spec @slug` | Check progress | Current status |
 | `/update-spec @slug "change"` | Modify spec (planning phase) | Updated spec.md |
@@ -296,7 +286,7 @@ Enforcer   -> Builders      │ TDD: tests before code
 
 ## Pattern Library
 
-Reusable implementation patterns extracted from completed specs via `/commit-spec`.
+Reusable implementation patterns extracted from completed specs via `/seal-spec`, `/archive-spec`, or `/sync-project`.
 
 **Location:** `.catalyst/library/`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "catalyst-os",
-  "version": "1.3.0",
+  "version": "2.0.0",
   "scripts": {
     "postinstall": "node .catalyst/bin/install.js",
     "validate": "node .catalyst/bin/validate-artifacts.js"

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

@@ -1,16 +0,0 @@
-# /build-task
-
-Execute a focused task on an existing codebase. Works with or without prior specs.
-
-## Usage
-
-```
-/build-task "change session timeout to 30 days"
-/build-task @2026-01-11-supabase-auth "change session timeout"
-```
-
----
-
-**Invoke skill:** `task-building`
-
-**Process skills used:** `test-driven-development`, `agent-delegation`, `verification-before-completion`, `systematic-debugging`

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

@@ -1,20 +0,0 @@
-# /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/iterate-spec.md

@@ -1,28 +0,0 @@
-# /iterate-spec
-
-Continue building a spec with new improvements discovered during development.
-
-## Usage
-
-```
-/iterate-spec @2025-11-29-stripe-integration "add support for annual billing"
-/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`
-
-**Orchestrator:** Forge-Master (delegates to Oracle, Scribe, Forger, Enforcer, Smith, Shaper, Alchemist)
-
-**Process skills used:** `test-driven-development`, `agent-delegation`, `brainstorming`

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

@@ -1,135 +0,0 @@
-# Spec Iteration
-
-> **When to invoke:** When adding improvements, enhancements, or edge case handling to a spec that's being built.
-> **Invoked by:** `/iterate-spec` command.
-> **Orchestrator:** Forge-Master agent.
-
-## Purpose
-
-Continue building a spec with new improvements discovered during development. Unlike `/update-spec` which stops after updating docs, iteration updates docs AND continues building in one flow.
-
-## Skills Referenced
-
-- `test-driven-development` — New tests must follow TDD
-- `agent-delegation` — Orchestrator rules
-- `verification-before-completion` — Verify before claiming done
-- `brainstorming` — Oracle uses if improvement needs clarification
-
-## Prerequisites
-
-- Spec must exist in `.catalyst/specs/`
-- Build has been started (`tasks.md` exists)
-- On the feature branch from `/build-spec`
-
-## Key Difference
-
-```
-/update-spec  →  Updates docs  →  STOPS  →  Manual /build-spec
-/iterate-spec →  Updates docs  →  CONTINUES BUILDING (single flow)
-```
-
-## Git Workflow
-
-```
-PHASE 0: Verify on feature branch
-GATE 1: RED FLAG → Commit: "test({scope}): add tests for {improvement}"
-GATE 2: GREEN FLAG → Commit: "feat({scope}): {improvement description}"
-```
-
-## TDD IS MANDATORY
-
-```
-1. Task(subagent_type="scribe")    -> Update spec.md
-2. Task(subagent_type="forger")    -> Add new tasks to tasks.md
-3. Task(subagent_type="enforcer")  -> Write tests for NEW tasks (must FAIL)
-4. Verify                          -> Run tests, confirm RED for new tests
-5. Task(subagent_type="smith/shaper/alchemist") -> Implement until GREEN
-```
-
-## Execution Order
-
-```
-Phase 1: Clarify (Oracle — if needed)
-              |
-Phase 2: Update Spec (Scribe)
-              |
-Phase 3: Update Tasks (Forger)
-              |
-Phase 4: Write Tests (Enforcer) — NEW tasks only
-              |
-         GATE 1: RED PHASE — New tests must FAIL, existing PASS
-              |
-Phase 5: Implement (Smith/Shaper/Alchemist)
-              |
-         GATE 2: GREEN PHASE — All tests must PASS
-```
-
-## Workflow Detail
-
-### Phase 0: Verify State
-
-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)
-
-If improvement description is vague, spawn Oracle. Skip if already clear and specific.
-
-### Phase 2: Update Specification (Scribe)
-
-Spawn Scribe to update spec.md:
-- Add new requirements
-- Update Changelog with date and description
-- Keep Status as IN_PROGRESS
-- Do NOT change completed requirements
-
-### Phase 3: Update Tasks (Forger)
-
-Spawn Forger to update tasks.md:
-- Read current tasks, identify completed vs pending
-- Add NEW tasks with `iter-` prefix
-- Update Build DAG with dependencies
-- Do NOT modify completed tasks
-
-### Phase 4: Write Tests (Enforcer) — RED PHASE
-
-Write tests for NEW iteration tasks only. Do NOT modify existing tests.
-
-### GATE 1: Red Phase
-
-- New tests FAIL
-- Existing tests still PASS (no regression)
-- Commit: `test({scope}): add tests for {improvement}`
-
-### Phase 5: Implementation
-
-Spawn appropriate agents (Smith/Shaper/Alchemist) based on task types. Parallel execution allowed if non-overlapping scopes.
-
-### GATE 2: Green Phase
-
-- All new tests PASS
-- All existing tests still PASS
-- Commit: `feat({scope}): {improvement description}`
-
-## Failure Modes
-
-| Failure | Action |
-|---------|--------|
-| 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 |
-| New tests pass immediately | Tests are wrong — rewrite for NEW functionality |
-
-## When to Use
-
-- Discovered better approach during testing
-- Thought of an improvement or enhancement
-- Found an edge case that should be handled
-- Want to add something that makes the feature better
-
-**NOT for bugs** — bugs are implementation issues, not spec changes.
-**NOT for missing requirements** — use `/update-spec` first.

package/.claude/skills/task-building/SKILL.md

@@ -1,96 +0,0 @@
-# Task Building
-
-> **When to invoke:** When executing a focused task on an existing codebase.
-> **Invoked by:** `/build-task` command.
-
-## Purpose
-
-Execute focused, brownfield-compatible tasks. Works with or without prior specs. Simpler flow than full spec build.
-
-## Skills Referenced
-
-- `test-driven-development` — Test assessment and TDD when needed
-- `agent-delegation` — Orchestrator rules
-- `verification-before-completion` — Verify before marking complete
-- `systematic-debugging` — When tests fail during implementation
-
-## When to Use
-
-| Use `/build-task` | Use `/catalyze-spec` |
-|-------------------|----------------------|
-| Modify existing feature | New feature from scratch |
-| Stakeholder change request | Major addition |
-| Mid-level refactoring | Architectural change |
-| Post-completion modifications | Needs research phase |
-| Brownfield projects (no specs) | Greenfield projects |
-
-## Output Location
-
-```
-.catalyst/tasks/YYYY-MM-DD-{slug}.md
-```
-
-Tasks are independent entities. They can optionally reference specs.
-
-## Workflow
-
-### Phase 0: Context Gathering
-
-1. Check for @spec reference → read spec for context
-2. Auto-detect related specs in `.catalyst/specs/`
-3. Create task file
-
-### Phase 1: Test Assessment (Enforcer)
-
-Spawn Enforcer to analyze test coverage:
-
-| Strategy | Condition | Action |
-|----------|-----------|--------|
-| **COVERED** | Existing tests fully cover this change | Skip to Phase 3 |
-| **MODIFY** | Tests exist but assertions need updating | Update tests first |
-| **NEW** | No tests cover this area | Write new tests first |
-
-### Phase 2: Tests (if MODIFY or NEW)
-
-Spawn Enforcer to write/update tests. Tests must FAIL before implementation (TDD).
-
-### Phase 3: Implementation
-
-Spawn appropriate builder based on task scope:
-- Smith for backend
-- Shaper for frontend
-- Alchemist for database
-
-### Phase 4: Verify & Commit
-
-1. Run tests — all must pass
-2. Run lint — no errors
-3. Update task file — mark COMPLETE
-4. Commit with structured message
-
-## Task File Format
-
-```markdown
-# Task: {Title}
-
-> Status: IN_PROGRESS | COMPLETE
-> Created: YYYY-MM-DD
-> Related Spec: @spec-name (optional)
-
-## Description
-{What needs to change and why}
-
-## Test Assessment
-| Strategy | Reason |
-|----------|--------|
-| COVERED / MODIFY / NEW | {Explanation} |
-
-## Changes Required
-- [ ] {Task item}
-
-## Files Modified
-- src/path/to/file.ts
-
-## Commit
-- Hash: {filled on completion}
-```