@nolrm/contextkit 1.0.3 → 1.1.0

package/README.md

@@ -162,7 +162,7 @@ ContextKit installs reusable slash commands for supported platforms:
 | `/doc-arch`            | Generate architecture docs — stack-aware (Level 1). Output: `docs/<topic>.md`, or `docs/architecture.md` if no topic given. Pass a topic name, PR number, or leave blank to infer from branch. |
 | `/doc-feature`         | Generate feature-level docs (`docs/features/<name>.md`) — stack-aware (Level 2)                                                 |
 | `/doc-component`       | Generate component-level docs colocated with the target file — stack-aware (Level 3)                                            |
-| `/spec`                | Turn a product overview into an implementation-ready spec — UX flows, DB schema, API contracts, and phased build plan           |
+| `/spec`                | Turn a product overview into a reference spec — data model, API contracts, UX flows, and squad-ready stories. Single CTO pass per scope. |
 | `/spec-component`      | Write a component spec (MD-first) before any code is created                                                                    |
 | `/squad`               | Kick off a squad task — one task or many (auto-detects batch mode). Pushes back with clarifying questions if the task is vague. |
 | `/squad-architect`     | Design the technical plan from the PO spec                                                                                      |
@@ -170,6 +170,7 @@ ContextKit installs reusable slash commands for supported platforms:
 | `/squad-test`          | Classify test levels, write and run tests against acceptance criteria                                                           |
 | `/squad-review`        | Review the full pipeline and give a verdict                                                                                     |
 | `/squad-doc`           | Create companion `.md` files for new/modified code after review passes                                                          |
+| `/squad-spec [scope]`  | Load a spec scope and run the full pipeline for every story. Use with `/loop /clear /squad-spec [scope]` for context-safe continuous execution. |
 | `/squad-go`            | Extract tasks from the current conversation and run the full pipeline immediately — no second command needed                     |
 | `/squad-auto`          | Auto-run the full pipeline after `/squad` kickoff (sequential)                                                                  |
 | `/squad-auto-parallel`    | Auto-run the pipeline in parallel using Claude Code agents (Claude Code only)                                                   |
@@ -277,46 +278,36 @@ If you have a screenshot, mockup, or design image relevant to the task, paste or
 
 ## Spec Pipeline
 
-The spec pipeline turns a high-level product overview into an implementation-ready spec. It runs before the squad — producing the UX flows, DB schema, API contracts, and phased build plan that make stories possible.
+The spec pipeline turns a high-level product overview into a full reference spec — data model, API contracts, UX flows, and squad-ready stories. It runs before the squad, one scope at a time.
 
 ```bash
 /spec          # Start or continue — picks up the next unchecked scope automatically
 /spec 02-jobs  # Run a specific scope by name
 /spec --redo 01-identity-auth  # Re-run a completed scope from scratch
+/spec --reset  # Delete the entire spec/ folder and start over
 ```
 
 ### How It Works
 
-`/spec` reads a product overview file (`PROJECT_OVERVIEW.md`, `OVERVIEW.md`, `BRIEF.md`, or any `.md` file you point it to) and runs a multi-round pipeline for each scope:
+Each `/spec` run is a single inline CTO pass — no sub-agents, no revision rounds. The CTO reads the overview and any prior scope specs (for consistency), then writes the full `SPEC.md` for that scope.
 
-| Round | Who runs | What happens |
-|-------|----------|-------------|
-| 0 — Brief | CTO | Reads the overview, defines scope boundaries, writes a brief all agents share |
-| 1 — Domain experts | UX, Data, Systems, Planner (parallel) | Each produces their section independently from the brief |
-| 2 — Challenges | CTO | Reads all four sections, writes challenges — gaps, contradictions, missing decisions |
-| 3 — Revisions | UX, Data, Systems, Planner (parallel) | Each addresses the CTO's challenges, flags unresolvable items as OPEN DECISIONs |
-| Final — Author | CTO | Resolves open decisions, writes the unified `SPEC.md` |
+Each `SPEC.md` contains: data model (full schema + ERD), API contracts (all endpoints with request/response), UX flows (key journeys and edge cases), a story table with sizes and dependencies, and copy-paste `/squad` commands for every story.
 
 ### Output Structure
 
-Each scope produces a folder with all working artifacts and a final `SPEC.md`:
+Each scope produces one `SPEC.md`. Progress and index files track the full project:
 
 ```
 spec/
   PROGRESS.md              ← scope checklist, updated after each run
-  INDEX.md                 ← master TOC linking all SPEC.md files
+  INDEX.md                 ← links to every completed SPEC.md
 
   01-identity-auth/
-    00-brief.md            ← CTO's scoping brief
-    01-ux.md               ← UX flows and screens
-    02-data.md             ← DB schema and relationships
-    03-systems.md          ← API contracts and services
-    04-plan.md             ← build phases and stories
-    05-challenges.md       ← CTO's Round 2 challenges
-    SPEC.md                ← final unified spec for this scope
-```
+    SPEC.md                ← full spec for this scope
 
-Run `/spec` once per scope. Each run appends to `spec/INDEX.md`. When all scopes are done, feed individual `SPEC.md` files into `/squad` as implementation tasks.
+  02-jobs-scheduling/
+    SPEC.md
+```
 
 ### First Run
 
@@ -324,6 +315,19 @@ On the first run, the CTO reads the entire overview and identifies all logical s
 
 If no standard overview file is found, `/spec` lists all `.md` files in the directory and asks you to pick.
 
+### From Spec to Squad
+
+Each `SPEC.md` ends with a `### Squad Commands` section — copy-paste `/squad` commands for every story. Run them one at a time, or use `/squad-spec` to implement an entire scope automatically:
+
+```bash
+# Option 1 — one story at a time
+/squad "S1 — Workspace schema: create workspaces table with RLS policies"
+/squad-auto
+
+# Option 2 — entire scope, context-safe
+/loop /clear /squad-spec 01-identity-auth
+```
+
 ---
 
 ## Hooks & Quality Gates

package/lib/commands/install.js

@@ -985,6 +985,10 @@ Any design decisions, trade-offs, or open questions to resolve before coding.
         `${this.repoUrl}/commands/squad/squad-go.md`,
         '.contextkit/commands/squad/squad-go.md'
       );
+      await this.downloadManager.downloadFile(
+        `${this.repoUrl}/commands/squad/squad-spec.md`,
+        '.contextkit/commands/squad/squad-spec.md'
+      );
       await this.downloadManager.downloadFile(
         `${this.repoUrl}/commands/dev/health-check.md`,
         '.contextkit/commands/dev/health-check.md'
@@ -995,22 +999,6 @@ Any design decisions, trade-offs, or open questions to resolve before coding.
         `${this.repoUrl}/commands/spec/spec.md`,
         '.contextkit/commands/spec/spec.md'
       );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-ux.md`,
-        '.contextkit/commands/spec/spec-ux.md'
-      );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-data.md`,
-        '.contextkit/commands/spec/spec-data.md'
-      );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-systems.md`,
-        '.contextkit/commands/spec/spec-systems.md'
-      );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-planner.md`,
-        '.contextkit/commands/spec/spec-planner.md'
-      );
 
       // Download doc family commands
       await this.downloadManager.downloadFile(

package/lib/commands/update.js

@@ -348,20 +348,8 @@ class UpdateCommand {
         '.contextkit/commands/spec/spec.md'
       );
       await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-ux.md`,
-        '.contextkit/commands/spec/spec-ux.md'
-      );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-data.md`,
-        '.contextkit/commands/spec/spec-data.md'
-      );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-systems.md`,
-        '.contextkit/commands/spec/spec-systems.md'
-      );
-      await this.downloadManager.downloadFile(
-        `${this.repoUrl}/commands/spec/spec-planner.md`,
-        '.contextkit/commands/spec/spec-planner.md'
+        `${this.repoUrl}/commands/squad/squad-spec.md`,
+        '.contextkit/commands/squad/squad-spec.md'
       );
 
       // Download doc family commands

package/lib/integrations/claude-integration.js

@@ -26,6 +26,7 @@ class ClaudeIntegration extends BaseIntegration {
       '.claude/skills/squad-reset/SKILL.md',
       '.claude/skills/squad-doc/SKILL.md',
       '.claude/skills/squad-go/SKILL.md',
+      '.claude/skills/squad-spec/SKILL.md',
       '.claude/skills/spec/SKILL.md',
       '.claude/skills/spec-component/SKILL.md',
       '.claude/skills/ck/SKILL.md',
@@ -490,6 +491,24 @@ Use \`/squad\` instead when you want to review specs before execution starts.
 `
     );
 
+    await this.writeGeneratedFile(
+      '.claude/skills/squad-spec/SKILL.md',
+      `---
+description: Implement every story in a spec scope — loops continuously with context cleared between stories. Run /spec first to generate the scope.
+argument-hint: '[scope-slug]'
+allowed-tools: Read, Edit, Write, Glob, Grep, Bash
+effort: high
+context: fork
+---
+
+Read \`.contextkit/commands/squad/squad-spec.md\` and execute it.
+
+Processes one story per invocation. Run with \`/loop /clear /squad-spec [scope]\` to implement all stories continuously with a clean context between each one.
+
+Run \`/spec\` first to generate the scope, then \`/squad-spec [scope-slug]\` to implement it.
+`
+    );
+
     // Doc family skills
     await this.writeGeneratedFile(
       '.claude/skills/doc-arch/SKILL.md',
@@ -610,7 +629,8 @@ Load and apply the project's ContextKit standards before taking action in an age
     console.log(chalk.dim('    /squad-review      — Review and write verdict'));
     console.log(
       chalk.dim(
-        '    /squad-go               — Extract tasks from conversation and run full pipeline'
+        '    /squad-go               — Extract tasks from conversation and run full pipeline',
+        '    /squad-spec [scope]     — Load a spec scope and run the full pipeline for every story'
       )
     );
     console.log(chalk.dim('    /squad-auto             — Auto-run full pipeline (recommended)'));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nolrm/contextkit",
-  "version": "1.0.3",
+  "version": "1.1.0",
   "description": "ContextKit - Context Engineering + Agentic AI Pipelines. Scaffold structured standards for AI assistants and run autonomous multi-role pipelines (PO → Architect → Dev → Test → Review → Doc) grounded by that same context layer. Works with Cursor, Claude Code, Copilot, Codex, Gemini, Aider, and more.",
   "main": "lib/index.js",
   "bin": {