catalyst-os 0.2.2 → 0.2.4

package/{bin → .catalyst/bin}/install.js

@@ -131,7 +131,6 @@ function install() {
   // Install config files
   const configs = [
     ['.catalyst/spec-structure.yaml', '.catalyst/spec-structure.yaml'],
-    ['.catalyst/specs/spec-config.yaml', '.catalyst/specs/spec-config.yaml'],
     ['.catalyst/main/project-config.yaml', '.catalyst/main/project-config.yaml']
   ];
 

package/.catalyst/spec-structure.yaml

@@ -239,3 +239,81 @@ context_assembly:
   on_resume:
     - Read tasks.md "## Current Session" section
     - Continue from recorded position
+
+# =============================================================================
+# BUILD DAG STRUCTURE
+# Used by Forger to create task breakdown
+# =============================================================================
+
+build_dag:
+  phases:
+    foundation:
+      agent: alchemist
+      sequential: true
+      description: "Database schema, core setup"
+
+    contracts:
+      agent: smith
+      sequential: true
+      description: "Shared types/interfaces before parallel work"
+
+    parallel:
+      agents: [smith, shaper]
+      multi_instance: true
+      description: "Scope-isolated parallel implementation"
+      rules:
+        - "Each agent has exclusive write scope"
+        - "Agents can read but not modify shared files"
+        - "No overlapping scopes between parallel tasks"
+
+    integration:
+      agent: enforcer
+      sequential: true
+      description: "Cross-boundary testing"
+
+  task_fields:
+    - id          # Unique identifier
+    - agent       # Which agent type (with instance: smith-1, shaper-2)
+    - scope       # Files with exclusive write access
+    - reads       # Files with read-only access
+    - depends_on  # Task IDs that must complete first
+    - blocks      # Task patterns this blocks (e.g., api-*, ui-*)
+    - acceptance  # How to verify completion
+    - estimate    # Time estimate (< 2 hours)
+
+# =============================================================================
+# PATTERN LIBRARY
+# Reusable patterns extracted from completed specs
+# =============================================================================
+
+library:
+  root: "library/"
+  description: "Reusable patterns extracted from completed specs"
+  created_by: "/approve-spec (optional)"
+
+  # Auto-detect patterns by keywords
+  pattern_detection:
+    payment-integration.md:
+      keywords: [stripe, payment, billing, subscription, checkout]
+    authentication.md:
+      keywords: [auth, oauth, login, sso, jwt, session]
+    file-storage.md:
+      keywords: [upload, s3, storage, file, media, image]
+    real-time-communication.md:
+      keywords: [websocket, realtime, socket, live, push]
+    notifications.md:
+      keywords: [email, notification, smtp, push, alert]
+    search-implementation.md:
+      keywords: [search, elasticsearch, algolia, fulltext]
+    caching-strategy.md:
+      keywords: [cache, redis, memcached, performance]
+    background-jobs.md:
+      keywords: [queue, job, worker, bull, async, cron]
+
+# =============================================================================
+# COMPLETED SPECS
+# =============================================================================
+
+completed:
+  location: "completed/"
+  description: "Specs moved here after /approve-spec"

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

@@ -249,9 +249,7 @@ Action: Run /build-spec @2025-11-29-stripe-integration
 
 ### Validation Failure
 ```
-Validation failed!
-
-Spec: 2025-11-29-stripe-integrationFailed Checks:
+Validation failed!Spec: 2025-11-29-stripe-integrationFailed Checks:
 - E2E Tests: 2 failures
 - Security: 1 vulnerability foundCreated: .catalyst/specs/{slug}/validation.md (with details)Action: Fix issues and re-run /validate-spec
 ```

package/.claude/skills/catalysts/spec-orchestration/SKILL.md

@@ -12,7 +12,7 @@ Coordinate the spec shaping workflow from feature request to documented specific
 
 ## Process
 
-1. **Initialize spec folder** (structure defined in `.catalyst/specs/spec-config.yaml`)
+1. **Initialize spec folder** (structure defined in `.catalyst/spec-structure.yaml`)
    ```
    .catalyst/specs/YYYY-MM-DD-{slug}/
    ├── spec.md        # Main specification (Scribe)

package/package.json

@@ -1,18 +1,18 @@
 {
   "name": "catalyst-os",
-  "version": "0.2.2",
+  "version": "0.2.4",
+  "scripts": {
+    "postinstall": "node .catalyst/bin/install.js"
+  },
   "description": "AI-native spec-driven development framework for Claude Code",
   "bin": {
-    "catalyst-os": "bin/install.js"
+    "catalyst-os": ".catalyst/bin/install.js"
   },
   "files": [
-    "bin",
     "AGENTS.md",
     ".claude",
-    ".claude-plugin",
     ".catalyst/standards",
     ".catalyst/spec-structure.yaml",
-    ".catalyst/specs/spec-config.yaml",
     ".catalyst/main/project-config.yaml"
   ],
   "keywords": [

package/.catalyst/specs/spec-config.yaml

@@ -1,114 +0,0 @@
-# Specifications Configuration
-
-# Command to create a new spec
-command: "/catalyze-spec \"description\""
-
-# Spec folder structure
-structure:
-  root: "specs/"
-  pattern: "YYYY-MM-DD-{slug}"
-
-  # Files in each spec folder
-  files:
-    spec.md:
-      owner: scribe
-      description: "Main specification document"
-      created_by: "/catalyze-spec"
-
-    research.md:
-      owner: scribe
-      description: "Compiled research findings"
-      created_by: "/catalyze-spec"
-
-    tasks.md:
-      owner: forger
-      description: "Build DAG with task breakdown"
-      created_by: "/build-spec"
-      structure:
-        - "Build DAG (phases, scope, dependencies)"
-        - "Task details"
-        - "Progress tracking"
-
-    validation.md:
-      owner: arbiter
-      description: "Quality validation results"
-      created_by: "/validate-spec"
-
-    handoff.md:
-      owner: arbiter
-      description: "Living document, completion summary"
-      created_by: "/validate-spec"
-
-    assets/:
-      owner: any
-      description: "Images, diagrams, visual references"
-
-    references/:
-      owner: any
-      optional: true
-      description: "Screenshots, evidence, proof of issues (user-created)"
-
-  # Completed specs location
-  completed: "completed/"
-
-# Pattern library for reusable implementations
-library:
-  root: "library/"
-  description: "Reusable patterns extracted from completed specs"
-  created_by: "/approve-spec (optional)"
-
-  # Auto-detect patterns by keywords
-  pattern_detection:
-    payment-integration.md:
-      keywords: [stripe, payment, billing, subscription, checkout]
-    authentication.md:
-      keywords: [auth, oauth, login, sso, jwt, session]
-    file-storage.md:
-      keywords: [upload, s3, storage, file, media, image]
-    real-time-communication.md:
-      keywords: [websocket, realtime, socket, live, push]
-    notifications.md:
-      keywords: [email, notification, smtp, push, alert]
-    search-implementation.md:
-      keywords: [search, elasticsearch, algolia, fulltext]
-    caching-strategy.md:
-      keywords: [cache, redis, memcached, performance]
-    background-jobs.md:
-      keywords: [queue, job, worker, bull, async, cron]
-
-# Build DAG structure (used by Forger)
-build_dag:
-  phases:
-    foundation:
-      agent: alchemist
-      sequential: true
-      description: "Database schema, core setup"
-
-    contracts:
-      agent: smith
-      sequential: true
-      description: "Shared types/interfaces before parallel work"
-
-    parallel:
-      agents: [smith, shaper]
-      multi_instance: true
-      description: "Scope-isolated parallel implementation"
-      rules:
-        - "Each agent has exclusive write scope"
-        - "Agents can read but not modify shared files"
-        - "No overlapping scopes between parallel tasks"
-
-    integration:
-      agent: enforcer
-      sequential: true
-      description: "Cross-boundary testing"
-
-  task_fields:
-    - id          # Unique identifier
-    - agent       # Which agent type (with instance: smith-1, shaper-2)
-    - scope       # Files with exclusive write access
-    - reads       # Files with read-only access
-    - depends_on  # Task IDs that must complete first
-    - blocks      # Task patterns this blocks (e.g., api-*, ui-*)
-    - acceptance  # How to verify completion
-    - estimate    # Time estimate (< 2 hours)

package/.claude-plugin/plugin.json

@@ -1,43 +0,0 @@
-{
-  "name": "catalyst-os",
-  "version": "0.1.0",
-  "description": "AI-native spec-driven development framework for Claude Code",
-  "author": {
-    "name": "ealikadioglu"
-  },
-  "license": "MIT",
-  "repository": "https://github.com/Ealikadioglu/catalyst-os",
-  "commands": [
-    ".claude/commands/catalyze-project.md",
-    ".claude/commands/catalyze-spec.md",
-    ".claude/commands/build-spec.md",
-    ".claude/commands/build-task.md",
-    ".claude/commands/validate-spec.md",
-    ".claude/commands/approve-spec.md",
-    ".claude/commands/reject-spec.md",
-    ".claude/commands/update-spec.md",
-    ".claude/commands/status-spec.md",
-    ".claude/commands/mission.md",
-    ".claude/commands/roadmap.md",
-    ".claude/commands/tech-stack.md"
-  ],
-  "agents": [
-    ".claude/agents/catalyst.md",
-    ".claude/agents/forge-master.md",
-    ".claude/agents/arbiter.md",
-    ".claude/agents/oracle.md",
-    ".claude/agents/seer.md",
-    ".claude/agents/scout.md",
-    ".claude/agents/surveyor.md",
-    ".claude/agents/scribe.md",
-    ".claude/agents/forger.md",
-    ".claude/agents/enforcer.md",
-    ".claude/agents/smith.md",
-    ".claude/agents/shaper.md",
-    ".claude/agents/alchemist.md",
-    ".claude/agents/necromancer.md",
-    ".claude/agents/inquisitor.md",
-    ".claude/agents/sentinel.md",
-    ".claude/agents/watcher.md"
-  ]
-}