specweave 1.0.255 → 1.0.256

package/CLAUDE.md

@@ -1,4 +1,4 @@
-<!-- SW:META template="claude" version="1.0.254" sections="header,start,autodetect,metarule,rules,workflow,reflect,context,structure,taskformat,secrets,syncing,testing,tdd,api,limits,troubleshooting,lazyloading,principles,linking,mcp,auto,docs" -->
+<!-- SW:META template="claude" version="1.0.255" sections="header,start,autodetect,metarule,rules,workflow,reflect,context,structure,taskformat,secrets,syncing,testing,tdd,api,limits,troubleshooting,lazyloading,principles,linking,mcp,auto,docs" -->
 
 <!-- SW:SECTION:hook-priority version="1.0.171" -->
 ## ⛔ Hook Instructions Override Everything
@@ -11,7 +11,7 @@
 | **"SKILL FIRST"** | Call shown skill FIRST → chain domain skills → implement |
 <!-- SW:END:hook-priority -->
 
-<!-- SW:SECTION:header version="1.0.254" -->
+<!-- SW:SECTION:header version="1.0.255" -->
 **Framework**: SpecWeave | **Truth**: `spec.md` + `tasks.md`
 <!-- SW:END:header -->
 
@@ -48,7 +48,7 @@ If auto-activation fails, invoke explicitly: `Skill({ skill: "name" })`
 
 **Native LSP broken in v2.1.0+.** Use: `specweave lsp refs|def|hover src/file.ts SymbolName`
 
-<!-- SW:SECTION:start version="1.0.254" -->
+<!-- SW:SECTION:start version="1.0.255" -->
 ## Getting Started
 
 **Initial increment**: `0001-project-setup` (auto-created by `specweave init`)
@@ -58,7 +58,7 @@ If auto-activation fails, invoke explicitly: `Skill({ skill: "name" })`
 2. **Customize**: Edit spec.md and use for setup tasks
 <!-- SW:END:start -->
 
-<!-- SW:SECTION:autodetect version="1.0.254" -->
+<!-- SW:SECTION:autodetect version="1.0.255" -->
 ## Auto-Detection
 
 SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
@@ -68,7 +68,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 **Opt-out phrases**: "Just brainstorm first" | "Don't plan yet" | "Quick discussion" | "Let's explore ideas"
 <!-- SW:END:autodetect -->
 
-<!-- SW:SECTION:metarule version="1.0.254" -->
+<!-- SW:SECTION:metarule version="1.0.255" -->
 ## Workflow Orchestration
 
 ### 1. Plan Mode Default
@@ -95,7 +95,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 ```
 <!-- SW:END:metarule -->
 
-<!-- SW:SECTION:rules version="1.0.254" -->
+<!-- SW:SECTION:rules version="1.0.255" -->
 ## Rules
 
 1. **Files** → `.specweave/increments/####-name/` (see Structure section for details)
@@ -116,7 +116,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
    Discover org from config: `repository.organization` → `sync.profiles` → `umbrella.childRepos` → filesystem
 <!-- SW:END:rules -->
 
-<!-- SW:SECTION:workflow version="1.0.254" -->
+<!-- SW:SECTION:workflow version="1.0.255" -->
 ## Workflow
 
 `/sw:increment "X"` → `/sw:do` → `/sw:progress` → `/sw:done 0001`
@@ -142,7 +142,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 Before git operations, scan: `for d in repositories packages services apps libs workspace; do [ -d "$d" ] && find "$d" -maxdepth 2 -name ".git" -type d; done`
 <!-- SW:END:save-nested-repos -->
 
-<!-- SW:SECTION:reflect version="1.0.254" -->
+<!-- SW:SECTION:reflect version="1.0.255" -->
 ## Skill Memories
 
 SpecWeave learns from corrections. Learnings saved here automatically. Edit or delete as needed.
@@ -163,7 +163,7 @@ SpecWeave learns from corrections. Learnings saved here automatically. Edit or d
 - Prefer leaderboard-style reporting for analysis
 - Auto mode: Stop hook creates implicit loops via block/approve pattern
 
-<!-- SW:SECTION:context version="1.0.254" -->
+<!-- SW:SECTION:context version="1.0.255" -->
 ## Context
 
 **Before implementing**: Check ADRs at `.specweave/docs/internal/architecture/adr/`
@@ -171,7 +171,7 @@ SpecWeave learns from corrections. Learnings saved here automatically. Edit or d
 **Load context**: `/sw:docs <topic>` loads relevant living docs into conversation
 <!-- SW:END:context -->
 
-<!-- SW:SECTION:structure version="1.0.254" -->
+<!-- SW:SECTION:structure version="1.0.255" -->
 ## Structure
 
 ```
@@ -186,7 +186,7 @@ SpecWeave learns from corrections. Learnings saved here automatically. Edit or d
 **Everything else → subfolders**: `reports/` | `logs/` | `scripts/` | `backups/`
 <!-- SW:END:structure -->
 
-<!-- SW:SECTION:taskformat version="1.0.254" -->
+<!-- SW:SECTION:taskformat version="1.0.255" -->
 ## Task Format
 
 ```markdown
@@ -196,7 +196,7 @@ SpecWeave learns from corrections. Learnings saved here automatically. Edit or d
 ```
 <!-- SW:END:taskformat -->
 
-<!-- SW:SECTION:secrets version="1.0.254" -->
+<!-- SW:SECTION:secrets version="1.0.255" -->
 ## Secrets Check
 
 **BEFORE CLI tools**: Check existing config first!
@@ -210,7 +210,7 @@ gh auth status
 **SECURITY**: NEVER use `grep TOKEN .env` without `-q` flag - it exposes credentials in terminal!
 <!-- SW:END:secrets -->
 
-<!-- SW:SECTION:syncing version="1.0.254" -->
+<!-- SW:SECTION:syncing version="1.0.255" -->
 ## External Sync (GitHub/JIRA/ADO)
 
 **Primary command**: `/sw:progress-sync` — syncs tasks.md → spec.md → living docs → external tools (auto-creates missing issues)
@@ -231,7 +231,7 @@ gh auth status
 **After task completion**: Run `/sw:progress-sync` or `/sw-github:push` to sync changes to external tools.
 <!-- SW:END:syncing -->
 
-<!-- SW:SECTION:testing version="1.0.254" -->
+<!-- SW:SECTION:testing version="1.0.255" -->
 ## Testing
 
 BDD in tasks.md | Unit >80% | `.test.ts` (Vitest)
@@ -250,7 +250,7 @@ vi.mock('./module', () => ({ func: mockFn }));
 **Install CLI**: `npm install -g @playwright/cli@latest`
 <!-- SW:END:testing -->
 
-<!-- SW:SECTION:tdd version="1.0.254" -->
+<!-- SW:SECTION:tdd version="1.0.255" -->
 ## TDD Mode (Test-Driven Development)
 
 **When `testing.defaultTestMode: "TDD"` is configured**, follow RED-GREEN-REFACTOR discipline:
@@ -311,7 +311,7 @@ When TDD is enabled, tasks include phase markers:
 **Rule**: Complete dependencies BEFORE dependent tasks (RED before GREEN).
 <!-- SW:END:tdd -->
 
-<!-- SW:SECTION:api version="1.0.254" -->
+<!-- SW:SECTION:api version="1.0.255" -->
 ## API Development (OpenAPI-First)
 
 **For API projects only.** Commands: `/sw:api-docs --all` | `--openapi` | `--postman` | `--validate`
@@ -319,13 +319,13 @@ When TDD is enabled, tasks include phase markers:
 Enable in config: `{"apiDocs":{"enabled":true,"openApiPath":"openapi.yaml"}}`
 <!-- SW:END:api -->
 
-<!-- SW:SECTION:limits version="1.0.254" -->
+<!-- SW:SECTION:limits version="1.0.255" -->
 ## Limits
 
 **Max 1500 lines/file** — extract before adding
 <!-- SW:END:limits -->
 
-<!-- SW:SECTION:troubleshooting version="1.0.254" -->
+<!-- SW:SECTION:troubleshooting version="1.0.255" -->
 ## Troubleshooting
 
 | Issue | Fix |
@@ -338,7 +338,7 @@ Enable in config: `{"apiDocs":{"enabled":true,"openApiPath":"openapi.yaml"}}`
 | Session stuck | Kill + `rm -f .specweave/state/*.lock` + restart |
 <!-- SW:END:troubleshooting -->
 
-<!-- SW:SECTION:lazyloading version="1.0.254" -->
+<!-- SW:SECTION:lazyloading version="1.0.255" -->
 ## Plugin Auto-Loading
 
 Plugins load automatically based on project type and keywords. Manual install if needed:
@@ -352,7 +352,7 @@ export SPECWEAVE_DISABLE_AUTO_LOAD=1         # Disable auto-load
 **Token savings**: Core ~3-5K tokens vs all plugins ~60K+
 <!-- SW:END:lazyloading -->
 
-<!-- SW:SECTION:principles version="1.0.254" -->
+<!-- SW:SECTION:principles version="1.0.255" -->
 ## Principles
 
 ### SpecWeave Principles
@@ -368,7 +368,7 @@ export SPECWEAVE_DISABLE_AUTO_LOAD=1         # Disable auto-load
 - **Demand Elegance**: For non-trivial changes, pause and ask "is there a more elegant way?" - but skip this for simple, obvious fixes (don't over-engineer).
 <!-- SW:END:principles -->
 
-<!-- SW:SECTION:linking version="1.0.254" -->
+<!-- SW:SECTION:linking version="1.0.255" -->
 ## Bidirectional Linking
 
 Tasks ↔ User Stories auto-linked via AC-IDs: `AC-US1-01` → `US-001`
@@ -376,7 +376,7 @@ Tasks ↔ User Stories auto-linked via AC-IDs: `AC-US1-01` → `US-001`
 Task format: `**AC**: AC-US1-01, AC-US1-02` (CRITICAL for linking)
 <!-- SW:END:linking -->
 
-<!-- SW:SECTION:mcp version="1.0.254" -->
+<!-- SW:SECTION:mcp version="1.0.255" -->
 ## External Services
 
 **Priority**: CLI tools first (simpler) → MCP for complex integrations
@@ -398,7 +398,7 @@ claude mcp add --transport stdio postgres -- npx -y @modelcontextprotocol/server
 MCP supports lazy-loading (auto mode) - tools load on-demand when >10% context.
 <!-- SW:END:mcp -->
 
-<!-- SW:SECTION:auto version="1.0.254" -->
+<!-- SW:SECTION:auto version="1.0.255" -->
 ## Auto Mode
 
 **Commands**: `/sw:auto` (start) | `/sw:auto-status` (check) | `/sw:cancel-auto` (emergency only)
@@ -415,7 +415,7 @@ MCP supports lazy-loading (auto mode) - tools load on-demand when >10% context.
 **STOP & ASK** if: Spec conflicts | Task unnecessary | Requirement ambiguous
 <!-- SW:END:auto -->
 
-<!-- SW:SECTION:docs version="1.0.254" -->
+<!-- SW:SECTION:docs version="1.0.255" -->
 ## Docs
 
 [spec-weave.com](https://spec-weave.com)

package/README.md

@@ -1,8 +1,8 @@
 # SpecWeave
 
-**The spec-driven skill layer for AI coding agents.** First-class support for Claude Code — compatible with any LLM-powered coding tool.
+**The spec-driven Skill Fabric for AI coding agents.** Program your AI in English. Ship features while you sleep.
 
-*Coordinate parallel AI agents. Prevent task overlap. Quality gates. Ship features while you sleep.*
+*First-class support for Claude Code — compatible with any LLM-powered coding tool.*
 
 [![NPM Version](https://img.shields.io/npm/v/specweave?color=brightgreen)](https://www.npmjs.com/package/specweave)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
@@ -15,16 +15,85 @@ npm install -g specweave   # Requires Node.js 20.12.0+
 
 ---
 
-## Quick Demo
+## What Are Skills?
 
-```bash
-/sw:increment "User authentication"   # AI creates spec + plan + tasks
-/sw:auto                               # Autonomous execution for hours
-/sw:grill 0001                         # Senior-level code review
-/sw:done 0001                          # Validate and complete
+**Skills are programs written in English** — not prompts, not templates, but reusable logic that controls how AI thinks, decides, and acts.
+
+```
+Without SpecWeave:                          With SpecWeave:
+─────────────────                           ───────────────
+"Use React Hook Form with Zod..."           "Add a login form"
+"Remember, we use Tailwind..."              → AI already knows your patterns.
+"Don't forget the test pattern..."          → It remembered from last time.
+"Wait, I told you this yesterday..."        → Fix once, learned permanently.
+```
+
+Each skill is a **programmable AI behavior** you can customize without forking. Fix once, remembered permanently. 100+ skills ship out of the box — PM, Architect, QA, Security, DevOps, Frontend, Backend, Mobile, ML.
+
+**You don't need to learn Claude Code docs.** SpecWeave handles hooks, plugins, CLAUDE.md, and context management for you. Install, describe your feature, skills do the rest.
+
+---
+
+## The Workflow
+
+Just describe what you want. SpecWeave handles the rest.
+
+```
+You: "Build me a checkout flow with Stripe"
+  ↓
+SpecWeave asks 5-10 clarifying questions
+  (What payment methods? Guest checkout? Subscriptions? Which UI library?)
+  ↓
+Creates: spec.md → plan.md → tasks.md
+  ↓
+You: "Go ahead and build it"
+  → autonomous execution for hours
+  (writes code, runs tests, fixes failures, syncs to GitHub/JIRA)
+  ↓
+You wake up. Review finished work.
+  Tests cover technical correctness. You check the UI and UX.
+  ↓
+You: "Looks good, ship it"
+  → validated, documented, shipped.
+```
+
+**Solo developer:**
+```
+You: "I need user authentication with OAuth and magic links"
+  → SpecWeave interviews you, creates spec + plan + tasks
+You: "Build it"
+  → AI works autonomously for hours
+You: "Ship it"
+  → reviewed, validated, done.
+```
+
+**Agent team (parallel):**
+```
+You: "Build an e-commerce MVP"
+  → SpecWeave splits into auth, payments, catalog
+  → 3 agents work in parallel across iTerm/tmux panes
+```
+
+**Brownfield project:**
 ```
+You: "Migrate the checkout page to React"
+  → SpecWeave analyzes existing code, plans strangler fig migration
+  → TDD-first autonomous execution
+```
+
+<details>
+<summary><strong>Under the hood</strong> — SpecWeave auto-activates these skills from natural language:</summary>
+
+| You say | SpecWeave runs |
+|---------|---------------|
+| "Build me X" | `/sw:increment` → spec + plan + tasks |
+| "Go ahead" / "Build it" | `/sw:auto` → autonomous execution |
+| "Ship it" / "We're done" | `/sw:done` → quality gates + close |
+| "Split this into teams" | `/sw:team-lead` → parallel agents |
+| "Review the code" | `/sw:grill` → critical code review |
 
-**What happens:** Claude creates a full specification, executes tasks autonomously, runs tests, fixes failures, and syncs progress to GitHub/JIRA. You review finished work.
+You can also invoke commands directly for fine-grained control.
+</details>
 
 ---
 
@@ -41,63 +110,66 @@ SpecWeave solves this with **file-based coordination**:
 └── tasks.md   ← DO: Implementation tasks with tests
 ```
 
-Each increment is a self-contained scope. Each agent knows exactly what's taken and what's available. No overlap. No conflicts. Six months later, search "OAuth" and find exactly what was decided, who approved it, and why.
+### Three Pillars
 
-### What Makes It Different
+**Programmable AI** — Skills are programs in English. Customize any skill's behavior via `skill-memories/*.md` without forking. Your rules override defaults. Original skills keep getting updates.
 
-- **Extensible skills (SOLID Open/Closed)** — skills are programs written in human language. Customize any skill's behavior via `skill-memories/*.md` without forking. Your rules override defaults. Original skills keep getting updates. No other AI tool lets you do this.
-- **Plan as source of truth** — spec.md + plan.md + tasks.md drive all implementation. Code is a derivative of the plan, never the other way around. Change your mind mid-build? Update the plan first, then regenerate code.
-- **Parallel agent coordination** — multiple Claude Code sessions, OpenClaw instances, or remote agents work on different increments without stepping on each other.
-- **Autonomous execution** — runs for hours, not minutes. Write, test, fix, repeat.
-- **Persistent memory** — AI learns from corrections. Fix once, remembered permanently.
-- **Quality gates** — Code Grill reviews code like a demanding senior engineer before every release.
-- **Living documentation** — specs, ADRs, and runbooks sync automatically after every task.
-- **100+ specialized skills** — PM, Architect, QA, Security, DevOps, Frontend, Mobile, ML, and more collaborate on deliverables.
-- **External sync** — GitHub Issues, JIRA, Azure DevOps — bidirectional, real-time.
-- **Self-improving** — captures what works and what doesn't. Gets smarter over time.
-- **LSP integration** — semantic code intelligence for TypeScript, Python, Go, Rust, Java, C#.
+**Autonomous Teams** — Run agent swarms across iTerm/tmux panes. Each agent owns an increment. File-based coordination prevents conflicts. Work on auth, payments, and notifications simultaneously.
+
+**Enterprise Ready** — Compliance audit trails in git. Brownfield analysis for legacy code. Bidirectional sync with GitHub, JIRA, Azure DevOps. Multi-repo coordination. Production-grade from day one.
 
 ---
 
-## Extensible Skills (Open/Closed Principle)
+## Agent Swarms
+
+Run multiple AI agents on the same repository — locally, in the cloud, or with [OpenClaw](https://openclaw.ai). Each agent owns an isolated increment. No conflicts.
+
+```
+iTerm2 / tmux split panes:
+┌──────────────────┬──────────────────┬──────────────────┐
+│  Agent 1 (auth)  │ Agent 2 (payments)│ Agent 3 (catalog)│
+│  /sw:auto        │  /sw:auto         │  /sw:auto        │
+│  ████████░░ 80%  │  ██████░░░░ 60%   │  ████░░░░░░ 40%  │
+└──────────────────┴──────────────────┴──────────────────┘
+```
+
+`/sw:team-lead "feature"` splits work → each agent runs `/sw:auto` → quality gates ensure consistency → progress syncs to GitHub/JIRA.
 
-**Skills are programs you can customize without forking.**
+**[Full agent teams guide](https://spec-weave.com/docs/guides/agent-teams-and-swarms)**
+
+---
+
+## Enterprise Ready
+
+SpecWeave is built for the reality of enterprise development.
 
-Unlike traditional tools where behavior is locked, SpecWeave skills follow the **Open/Closed Principle** from SOLID:
-- **Closed for modification** — don't edit SKILL.md
-- **Open for extension** — customize via `.specweave/skill-memories/*.md`
+- **Compliance audit trails** — every decision tracked in version-controlled spec files. SOC 2, HIPAA, FDA ready.
+- **Brownfield excellence** — automated codebase analysis, strangler fig migrations, knowledge preservation. 90%+ of enterprise work is brownfield.
+- **Multi-repo coordination** — specs reference cross-repo dependencies. Agent teams work across repositories.
+- **External sync** — GitHub Issues, JIRA, Azure DevOps — bidirectional, real-time. Local-first, works offline.
+- **Multi-environment** — dev, QA, staging, UAT, production deployment pipelines.
+
+**[Enterprise documentation](https://spec-weave.com/docs/enterprise)**
+
+---
+
+## Extensible Skills (Open/Closed Principle)
 
-**Example: Teaching the Frontend Skill**
+**Customize any skill without forking.**
 
 ```bash
 # First time
 You: "Generate a login form"
 Claude: *creates form with useState*
-You: "No, we always use React Hook Form + Zod validation"
+You: "No, we always use React Hook Form + Zod"
 
 # SpecWeave learns this → .specweave/skill-memories/frontend.md
 
-# Next session
+# Next session — any agent, any skill
 You: "Generate a signup form"
-Claude: *automatically uses React Hook Form + Zod* ✓
+Claude: *automatically uses React Hook Form + Zod*
 ```
 
-**Your customizations:**
-```markdown
-# .specweave/skill-memories/frontend.md
-
-### Form Handling
-- Use React Hook Form for all forms
-- Combine with Zod for validation schemas
-- Never use plain useState for form state
-
-### Component Preferences
-- Import from @/components/ui design system
-- Tailwind utilities only, no inline styles
-```
-
-**Why this matters:**
-
 | Traditional Tools | SpecWeave Skills |
 |------------------|------------------|
 | Obfuscated behavior | Transparent SKILL.md |
@@ -111,9 +183,7 @@ Claude: *automatically uses React Hook Form + Zod* ✓
 /sw:reflect-status   # See what Claude has learned
 ```
 
-Every skill (PM, Architect, QA, Security, DevOps, Frontend, Backend) can be customized. You're not using tools — you're **programming them** to match your exact patterns.
-
-**For skill developers:** Design skills with extension points. See [Skill Development Guidelines](#skill-development-guidelines) for SOLID patterns.
+**[Skills deep dive](https://spec-weave.com/docs/overview/skills-as-programs)** | **[Skill development guidelines](https://spec-weave.com/docs/guides/skill-development-guidelines)**
 
 ---
 
@@ -126,63 +196,28 @@ specweave init .
 ```
 
 Then in Claude Code:
-```bash
-/sw:increment "Add dark mode"   # Describe your feature
-/sw:auto                        # Ship while you sleep
-```
-
-> **Node.js 20.12.0+** required (22 LTS recommended). Getting `SyntaxError`? [Upgrade instructions](https://spec-weave.com/docs/guides/troubleshooting/common-errors#node-version-error).
-
----
-
-## Parallel Development
-
-Run multiple AI agents on the same repository — locally, in the cloud, or with [OpenClaw](https://openclaw.ai). SpecWeave's increment files are the coordination layer:
-
 ```
-Agent 1 (local Claude Code)    Agent 2 (cloud)           Agent 3 (OpenClaw)
-working on: 0001-auth          working on: 0002-payments  working on: 0003-notifications
-         │                              │                           │
-         └──────────────────────────────┼───────────────────────────┘
-                                        │
-                           .specweave/increments/
-                           ├── 0001-auth/tasks.md           ← Agent 1's scope
-                           ├── 0002-payments/tasks.md       ← Agent 2's scope
-                           └── 0003-notifications/tasks.md  ← Agent 3's scope
+You: "Add dark mode to the app"
+→ SpecWeave creates spec, plans architecture, builds it autonomously.
 ```
 
-**How it works:**
-1. Create increments for each feature: `/sw:increment "auth"`, `/sw:increment "payments"`
-2. Each agent picks an increment and runs `/sw:auto` — tasks.md tracks exactly what's done
-3. Agents work in isolated scopes — different files, different specs, different tests
-4. Quality gates (`/sw:grill`) ensure consistent standards regardless of which agent built it
-5. Progress syncs to GitHub/JIRA so you see everything in one place
-
-**Why this matters:** OpenClaw and Claude Code sessions are stateless by default. SpecWeave's spec/plan/tasks files persist across sessions and agents — your coordination layer survives restarts, crashes, and context window limits.
-
-**Agent team commands:**
-
-| Command | Purpose |
-|---------|---------|
-| `/sw:team-lead "feature"` | Split feature across parallel agents |
-| `/sw:team-status` | Monitor all agent progress |
-| `/sw:team-merge` | Merge completed work in dependency order |
-
-**[Full agent teams guide](https://spec-weave.com/docs/guides/agent-teams-and-swarms)**
+> **Node.js 20.12.0+** required (22 LTS recommended). Getting `SyntaxError`? [Upgrade instructions](https://spec-weave.com/docs/guides/troubleshooting/common-errors#node-version-error).
 
 ---
 
 ## Core Commands
 
-| Command | Purpose |
-|---------|---------|
-| `/sw:increment "feature"` | Create spec + plan + tasks |
-| `/sw:auto` | Autonomous execution |
-| `/sw:do` | Execute one task at a time |
-| `/sw:grill` | Code review before close |
-| `/sw:done` | Close with quality validation |
-| `/sw:sync-progress` | Push to GitHub / JIRA / ADO |
-| `/sw:next` | Auto-close + suggest next |
+All commands activate automatically from natural language. Use directly for fine-grained control.
+
+| Command | Purpose | Natural trigger |
+|---------|---------|----------------|
+| `/sw:increment "feature"` | Create spec + plan + tasks | "Build me X" |
+| `/sw:auto` | Autonomous execution | "Go ahead and build it" |
+| `/sw:do` | Execute one task at a time | "Do the next task" |
+| `/sw:grill` | Code review before close | "Review the code" |
+| `/sw:done` | Close with quality validation | "Ship it" |
+| `/sw:progress-sync` | Push to GitHub / JIRA / ADO | "Sync progress" |
+| `/sw:next` | Auto-close + suggest next | "What's next?" |
 
 **[Full command reference](https://spec-weave.com/docs/commands/overview)**
 
@@ -206,12 +241,14 @@ When you close an increment, external tools update automatically.
 |------------|-----------|-------------|----------------|
 | **Parallel agent coordination** | Increment-scoped isolation | No | No |
 | **Autonomous execution** | Hours of unattended `/sw:auto` | No | No |
+| **Agent swarms (iTerm/tmux)** | Visual parallel monitoring | No | No |
 | **Quality gates** | Code Grill before every release | No | No |
 | **Living documentation** | Auto-updated after every task | Manual | Manual |
 | **Self-improving AI** | Learns from corrections | No | No |
+| **Enterprise compliance** | SOC 2, HIPAA, FDA audit trails | No | No |
 | **External sync** | GitHub / JIRA / ADO bidirectional | No | No |
+| **Brownfield support** | Analyzer + migration patterns | No | No |
 | **Specialized skills** | 100+ (PM, QA, DevOps, ML...) | 21 agents | None |
-| **Works with OpenClaw** | Yes | Partial | Partial |
 | **Spec/plan/tasks workflow** | Yes | Yes | Yes |
 | **Agent-agnostic** | Claude Code + OpenClaw + Copilot + Codex | Multi-IDE | Multi-IDE |
 
@@ -219,7 +256,7 @@ When you close an increment, external tools update automatically.
 
 ## Built With SpecWeave
 
-> This framework builds itself. Every feature, bug fix, and release is spec-driven.
+> SpecWeave builds itself. Every feature, bug fix, and release is spec-driven.
 
 **[Browse increments](https://github.com/anton-abyzov/specweave/tree/develop/.specweave/increments)** — see how SpecWeave develops SpecWeave.
 
@@ -233,108 +270,6 @@ When you close an increment, external tools update automatically.
 
 [Discord](https://discord.gg/UYg4BGJ65V) · [YouTube](https://www.youtube.com/@antonabyzov) · [GitHub Issues](https://github.com/anton-abyzov/specweave/issues)
 
-## Skill Development Guidelines
-
-**Design skills that users can extend without modification.**
-
-When creating SpecWeave skills, follow the **Open/Closed Principle** (SOLID):
-
-### Structure for Extension
-
-**SKILL.md** (closed for modification)
-```markdown
-# Your Skill
-
-## Core Behavior
-1. Always do X
-2. Check for Y
-3. Output Z format
-
-## Extension Points
-Users can customize:
-- Component preferences
-- Validation rules
-- Output formatting
-- Error handling
-
-See `.specweave/skill-memories/{skill-name}.md` for customizations.
-```
-
-`skill-memories/{skill-name}.md` (open for extension)
-```markdown
-### Component Preferences
-- Use Material UI instead of Chakra
-- Dark mode by default
-
-### Custom Validation
-When validating forms:
-1. Check email domain against allowlist
-2. Require 2FA for admin roles
-```
-
-### SOLID Principles for Skills
-
-| Principle | Application |
-|-----------|-------------|
-| **Single Responsibility** | One skill = one domain (Frontend, Backend, Testing, etc.) |
-| **Open/Closed** | Core logic in SKILL.md (closed), customizations in skill-memories (open) |
-| **Liskov Substitution** | Customizations shouldn't break skill contracts (output format, interface) |
-| **Interface Segregation** | Expose clear extension points, don't force users to override large blocks |
-| **Dependency Inversion** | Depend on patterns/abstractions, let skill-memories provide concrete implementations |
-
-### Design Patterns
-
-**✓ DO:**
-- Expose clear extension points in SKILL.md
-- Document what users can customize
-- Provide examples in skill-memories templates
-- Read skill-memories at runtime before executing logic
-- Use conditional logic: "If skill-memories defines X, use X; else default behavior"
-
-**✗ DON'T:**
-- Hard-code preferences that vary by project
-- Make users fork SKILL.md to customize behavior
-- Ignore skill-memories content
-- Create monolithic skills that do everything
-
-### Example: Extensible Frontend Skill
-
-```markdown
-# SKILL.md (core logic)
-
-## Component Generation
-
-**Default behavior:**
-1. Use React functional components
-2. TypeScript with Props interface
-3. Export as default
-
-**Extension points (check skill-memories/frontend.md):**
-- component.framework (React | Vue | Angular)
-- component.exportStyle (default | named)
-- component.testFramework (Vitest | Jest | Testing Library)
-- styling.approach (Tailwind | CSS Modules | Styled Components)
-
-**Logic:**
-```typescript
-// Read skill-memories first
-const userPrefs = readSkillMemories('frontend');
-
-// Apply customizations or use defaults
-const framework = userPrefs?.component?.framework || 'React';
-const styling = userPrefs?.styling?.approach || 'CSS Modules';
-```
-```
-
-### Testing Your Skill's Extensibility
-
-1. **Write SKILL.md** with default behavior
-2. **Create skill-memories template** showing extension points
-3. **Test with customizations** - does the skill respect user preferences?
-4. **Document limitations** - what CAN'T be customized?
-
-**Good skill design = Users extend your logic without ever touching your source.**
-
 ## License
 
 MIT — [github.com/anton-abyzov/specweave](https://github.com/anton-abyzov/specweave)

package/dist/src/core/ac-checkbox-formatter.d.ts

@@ -0,0 +1,24 @@
+/**
+ * AC Checkbox Formatter — Provider-specific AC state formatting
+ *
+ * Formats acceptance criteria states into checkbox markup for:
+ * - GitHub: `- [x] **AC-ID**: description`
+ * - JIRA:   `(/) AC-ID: description`
+ * - ADO:    `<li>☑ AC-ID: description</li>`
+ *
+ * @module ac-checkbox-formatter
+ */
+export interface ACState {
+    id: string;
+    description: string;
+    completed: boolean;
+}
+export type ACCheckboxFormat = 'github' | 'jira' | 'ado';
+/**
+ * Format AC states into provider-specific checkbox markup.
+ *
+ * Returns empty string for empty acStates array.
+ * Includes a progress header with completed/total count and percentage.
+ */
+export declare function formatACCheckboxes(acStates: ACState[], format: ACCheckboxFormat): string;
+//# sourceMappingURL=ac-checkbox-formatter.d.ts.map

package/dist/src/core/ac-checkbox-formatter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ac-checkbox-formatter.d.ts","sourceRoot":"","sources":["../../../src/core/ac-checkbox-formatter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,MAAM,WAAW,OAAO;IACtB,EAAE,EAAE,MAAM,CAAC;IACX,WAAW,EAAE,MAAM,CAAC;IACpB,SAAS,EAAE,OAAO,CAAC;CACpB;AAED,MAAM,MAAM,gBAAgB,GAAG,QAAQ,GAAG,MAAM,GAAG,KAAK,CAAC;AAEzD;;;;;GAKG;AACH,wBAAgB,kBAAkB,CAChC,QAAQ,EAAE,OAAO,EAAE,EACnB,MAAM,EAAE,gBAAgB,GACvB,MAAM,CAyBR"}