specweave 1.0.593 → 2.0.0

package/plugins/SKILLS-VS-AGENTS.md

@@ -1,267 +0,0 @@
-# Skills and Subagents: SpecWeave's Architecture
-
-> Based on official Claude Code documentation: https://code.claude.com/docs/en/skills and https://code.claude.com/docs/en/sub-agents
-
-## Claude Code Extensibility Overview
-
-Before diving into SpecWeave-specific architecture, here's the full landscape of Claude Code's extension mechanisms — AI and non-AI alike.
-
-### All Extension Points
-
-| Mechanism | What It Is | AI-Powered? | Docs |
-|-----------|-----------|-------------|------|
-| **Skills** | Markdown instructions Claude follows (reference, tasks, `/commands`) | Yes (LLM reads them) | [skills](https://code.claude.com/docs/en/skills) |
-| **Custom Subagents** | Isolated AI workers with own context, memory, model | Yes (separate LLM context) | [sub-agents](https://code.claude.com/docs/en/sub-agents) |
-| **Agent Teams** | Multiple agents working in parallel, communicating via messages | Yes (multiple LLM sessions) | [agent-teams](https://code.claude.com/docs/en/agent-teams) |
-| **Hooks** | Shell scripts triggered by tool events (PreToolUse, PostToolUse, etc.) | No (pure shell) | [hooks](https://code.claude.com/docs/en/hooks) |
-| **MCP Servers** | External tool servers (databases, APIs, Slack, Figma, etc.) | No (tool providers) | [mcp](https://code.claude.com/docs/en/mcp) |
-| **Plugins** | Packages that bundle skills + agents + hooks + commands | Mixed | [plugins](https://code.claude.com/docs/en/plugins) |
-| **CLAUDE.md** | Persistent project/user instructions loaded every session | No (static text) | [memory](https://code.claude.com/docs/en/memory) |
-| **Permissions** | Allow/deny rules for tools, skills, agents | No (configuration) | [permissions](https://code.claude.com/docs/en/permissions) |
-| **Settings** | JSON config for models, tools, environment | No (configuration) | [settings](https://code.claude.com/docs/en/settings) |
-
-### How They Compose
-
-```
-User Request
-    ↓
-Claude Code (main conversation)
-    ├── Reads: CLAUDE.md, settings, permissions
-    ├── Has: Skills (loaded by keyword or /command)
-    ├── Uses: MCP Servers (external tools)
-    ├── Spawns: Custom Subagents (isolated workers)
-    │   └── Subagent preloads: Skills (injected at startup)
-    │   └── Subagent uses: MCP Servers, Hooks
-    ├── Spawns: Built-in Subagents (Explore, Plan, general-purpose)
-    ├── Orchestrates: Agent Teams (parallel multi-agent work)
-    └── Triggers: Hooks (shell scripts on tool events)
-```
-
-### Non-AI Tools in SpecWeave
-
-SpecWeave uses several non-AI extension points:
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| **Guard hooks** (skill-chain, interview, spec-template) | Hooks (shell) | Enforce delegation rules — block writes unless correct agent registered |
-| **`specweave` CLI** | External tool (Node.js) | Create increments, validate specs, manage lifecycle |
-| **`!`command`` injection** | Shell preprocessing | Inject dynamic context (config, project info) into skills before Claude sees them |
-| **State files** (`.specweave/state/`) | File system | Coordination between agents via marker files |
-| **MCP servers** (Figma, Gmail, etc.) | MCP | External integrations Claude can use during any phase |
-
----
-
-## TL;DR
-
-**SpecWeave uses both Skills AND Custom Subagents — each for what it's best at.**
-
-- **Skills** = reusable instructions (reference knowledge, standalone tasks, user-invocable `/commands`)
-- **Custom Subagents** = persistent, isolated workers that preload skills (memory, resumability, background execution)
-- **The pattern**: Subagents preload skills via the `skills:` field — subagent owns isolation + memory, skill owns domain logic
-
-## When to Use What
-
-| Use Case | Mechanism | Why |
-|----------|-----------|-----|
-| **Orchestrated agent** (PM, Architect, Planner) | Custom subagent + preloaded skill | Memory, resumability, auto-compaction, guaranteed skill injection |
-| **Standalone heavy task** (grill, brainstorm) | Skill with `context: fork` | Self-contained, user-invocable, no memory needed |
-| **Reference knowledge** (api-conventions, style guide) | Skill, NO `context: fork` | Must run inline to enrich main conversation |
-| **Quick research** | Built-in subagent (Explore, Plan, general-purpose) | Read-only, disposable, no custom setup |
-
-### Decision Flowchart
-
-```
-Does the agent need persistent memory or resumability?
-  YES → Custom subagent (with skills: preloading)
-  NO  →
-    Is it a standalone task producing output?
-      YES → Skill with context: fork
-      NO  →
-        Is it reference/knowledge for the main conversation?
-          YES → Skill, NO context: fork (runs inline)
-          NO  → Built-in subagent (Explore/Plan/general-purpose)
-```
-
-## The Core Pattern: Subagents Preloading Skills
-
-This is the recommended architecture for SpecWeave's orchestrated agents:
-
-```
-plugins/specweave/
-├── agents/
-│   ├── sw-pm.md            # Subagent definition (model, memory, skills)
-│   ├── sw-architect.md     # Each preloads its corresponding skill
-│   └── sw-planner.md
-├── skills/
-│   ├── pm/
-│   │   ├── SKILL.md        # Domain logic, phases, templates
-│   │   ├── phases/         # Supporting files loaded on demand
-│   │   └── templates/
-│   ├── architect/
-│   │   └── SKILL.md
-```
-
-### How It Works
-
-**Subagent file** (`agentssw-pm.md`):
-```yaml
----
-name: sw-pm
-description: Product Manager for writing spec.md...
-model: opus
-memory: project
-skills:
-  - sw:pm              # Preloads the PM skill content at startup
----
-
-You are a Product Manager specializing in spec-driven development.
-```
-
-**Skill file** (`skills/pm/SKILL.md`):
-```yaml
----
-description: Product Manager for spec-driven development...
-context: fork
-model: opus
----
-
-# Product Manager Skill
-...full domain logic, phases, templates...
-```
-
-> **Note**: Skills have `context: fork` and `model` for standalone invocation (e.g., `sw:pm`). When preloaded by a subagent, the subagent's isolation takes precedence — `context: fork` doesn't cause "double-forking".
-
-**Why this works**:
-- The **subagent** owns: isolation, memory, model, resumability, background execution
-- The **skill** owns: domain logic, supporting files (phases, templates), user-invocable `sw:pm`
-- The `skills:` field **guarantees** skill content is injected at startup (no discovery step needed)
-- Users can still run `sw:pm` directly for ad-hoc spec work outside increment flow
-
-### Invocation from the Increment Orchestrator
-
-```typescript
-// The increment skill spawns subagents (NOT skills):
-Agent({ subagent_type: "sw:sw-pm", prompt: "Write spec for increment XXXX-name: ..." })
-Agent({ subagent_type: "sw:sw-architect", prompt: "Design architecture for increment XXXX-name..." })
-Agent({ subagent_type: "sw:sw-planner", prompt: "Generate tasks for increment XXXX-name..." })
-```
-
-## Feature Comparison
-
-| Feature | Skill (`context: fork`) | Custom Subagent |
-|---------|------------------------|-----------------|
-| **Isolated context** | Yes | Yes |
-| **Auto-activation by keywords** | Yes | No (must be explicitly spawned) |
-| **User-invocable** (`/name`) | Yes | No (only via Agent tool) |
-| **Persistent memory** | No | Yes (`memory: project/user/local`) |
-| **Resumable** (by agent ID) | No | Yes |
-| **Background execution** | No (blocks caller) | Yes (`run_in_background: true` or Ctrl+B) |
-| **Auto-compaction** | No | Yes (at ~95% capacity) |
-| **Permission mode override** | No | Yes (`permissionMode:`) |
-| **Skills preloading** | No | Yes (`skills:` field) |
-| **Hooks** | Yes | Yes |
-| **Custom model** | Yes (`model:`) | Yes (`model:`) |
-| **Distributed via plugins** | `plugins/X/skills/` | `plugins/X/agents/` |
-| **Supporting files** | Yes (phases/, templates/) | No (but preloaded skills can have them) |
-
-## When NOT to Use `context: fork`
-
-A skill should **not** have `context: fork` when:
-
-1. **A subagent preloads it** — the subagent already provides isolation. Adding `context: fork` would double-fork (skill forks inside already-forked subagent = wasted tokens)
-2. **It provides reference knowledge** — conventions, patterns, style guides that Claude needs in the main conversation context
-3. **It needs conversation history** — `context: fork` creates a fresh context; the skill won't see prior messages
-
-**DO use `context: fork`** when:
-- The skill is a **standalone task** producing output (grill, brainstorm, code-simplifier)
-- No custom subagent wraps it
-- You want isolation without creating a full subagent definition
-
-**SpecWeave validator note**: The SpecWeave skill validator does NOT recognize `context`, `model`, `agent`, or `allowed-tools` in frontmatter — these are Claude Code attributes. SpecWeave only supports: `argument-hint`, `compatibility`, `description`, `disable-model-invocation`, `license`, `metadata`, `name`, `user-invokable`. For skills preloaded by subagents, put `model` and `context` on the **subagent**, not the skill.
-
-## Built-in Subagents for Research
-
-For explicit research/exploration, use Claude Code's built-in subagents:
-
-| Subagent | Model | Tools | Use Case |
-|----------|-------|-------|----------|
-| **Explore** | Haiku | Read-only | Fast codebase search, file discovery |
-| **Plan** | Inherited | Read-only | Architecture planning, design research |
-| **general-purpose** | Inherited | All | Complex multi-step research + modification |
-
-```typescript
-Agent({ subagent_type: "Explore", prompt: "Find all API endpoints", description: "API exploration" })
-Agent({ subagent_type: "general-purpose", prompt: "Research Stripe integration patterns", description: "Stripe research" })
-```
-
-## SpecWeave Agent Catalog
-
-### Core Orchestration Agents (Subagent + Skill)
-
-| Agent | Subagent | Preloads Skill | Writes | Model |
-|-------|----------|---------------|--------|-------|
-| **PM** | `sw-pm` | `sw:pm` | spec.md | Opus |
-| **Architect** | `sw-architect` | `sw:architect` | plan.md | Opus |
-| **Planner** | `sw-planner` | (inline BDD logic) | tasks.md | Sonnet |
-
-### Standalone Skills (context: fork)
-
-| Skill | Purpose | Why not a subagent? |
-|-------|---------|-------------------|
-| `sw:grill` | Code review before ship | No memory needed, one-shot |
-| `sw:brainstorm` | Multi-perspective ideation | Spawns parallel lenses, disposable |
-| `sw:judge-llm` | Deep validation | One-shot evaluation |
-
-### Reference Skills (inline, no fork)
-
-| Skill | Purpose |
-|-------|---------|
-| `api-conventions` | API design patterns |
-| `error-handling-patterns` | Error handling standards |
-
-## FAQ
-
-### Q: When should I create a custom subagent vs a skill with `context: fork`?
-**A:** If the agent needs **persistent memory**, **resumability**, or **background execution** — make it a custom subagent. If it's a **one-shot task** or **user-invocable command** — make it a skill with `context: fork`. If it's **reference knowledge** — skill without fork.
-
-### Q: Can a skill work both standalone AND preloaded by a subagent?
-**A:** Yes. Remove `context: fork` from the skill. Users invoke it directly via `sw:pm` (runs inline). The subagent preloads it via `skills: [sw:pm]` (runs in subagent's isolated context). Same logic, two execution modes.
-
-### Q: What happens if the skills: preloading fails?
-**A:** The subagent still runs — it just won't have the skill content injected. The subagent's own markdown body (system prompt) is always available. To guard against this, keep critical instructions in the subagent body and use skills for detailed/phase logic.
-
-### Q: Can subagents spawn other subagents?
-**A:** No. Subagents cannot nest. If you need chained delegation, the **main conversation** (or orchestrator skill) spawns each subagent sequentially.
-
-### Q: Why did custom agents fail before?
-**A:** SpecWeave originally used subfolder structure (`agents/<name>/AGENT.md`). Claude Code expected flat files (`agents/<name>.md`). This was fixed — flat `.md` files in `agents/` now work correctly.
-
-## Official Documentation
-
-### AI Extension Points
-- **Skills**: https://code.claude.com/docs/en/skills
-- **Subagents**: https://code.claude.com/docs/en/sub-agents
-- **Agent Teams**: https://code.claude.com/docs/en/agent-teams
-
-### Non-AI Extension Points
-- **Hooks**: https://code.claude.com/docs/en/hooks
-- **MCP Servers**: https://code.claude.com/docs/en/mcp
-- **Permissions**: https://code.claude.com/docs/en/permissions
-- **Settings**: https://code.claude.com/docs/en/settings
-- **Memory (CLAUDE.md)**: https://code.claude.com/docs/en/memory
-
-### Distribution
-- **Plugins**: https://code.claude.com/docs/en/plugins
-- **Plugin Components Reference**: https://code.claude.com/docs/en/plugins-reference
-
-### Full Index
-- **All docs**: https://code.claude.com/docs/llms.txt
-
-## Summary
-
-1. **Subagents + Skills together** — subagent owns isolation/memory, skill owns domain logic
-2. **`context: fork`** for standalone tasks only (grill, brainstorm, judge)
-3. **No `context: fork`** on skills preloaded by subagents (avoids double-fork)
-4. **No `context: fork`** on reference/knowledge skills (need inline context)
-5. **Built-in subagents** (Explore, Plan, general-purpose) for ad-hoc research
-6. **Agent()** to invoke custom subagents, **Skill()** for standalone skills

package/plugins/VALIDATION-REPORT.md

@@ -1,134 +0,0 @@
-# LLM-as-Judge Validation Report
-
-> Validation date: 2026-01-24
-> Validated against: Official Claude Code documentation (https://code.claude.com/docs/en/skills)
-
-## Executive Summary
-
-| Category | Count | Status |
-|----------|-------|--------|
-| Total Skills | 100+ | Audited |
-| `allowed-tools:` (correct) | 51 | ✅ PASS |
-| `tools:` (incorrect) | 6 | ❌ FAIL - needs fix |
-| `context: fork` (for isolation) | 44 | ✅ PASS |
-| No agents folders remaining | 0 | ✅ PASS |
-
-## Critical Issues Found
-
-### Issue 1: Incorrect `tools:` Frontmatter (6 files)
-
-Per official Claude Code documentation, the correct field is `allowed-tools:`, NOT `tools:`.
-
-**Affected files:**
-1. `plugins/specweave-diagrams/skills/diagrams/SKILL.md`
-2. `plugins/specweave-backend/skills/python-backend/SKILL.md`
-3. `plugins/specweave-backend/skills/nodejs-backend/SKILL.md`
-4. `plugins/specweave-backend/skills/dotnet-backend/SKILL.md`
-5. `plugins/specweave-ado/skills/ado-mapper/SKILL.md`
-6. `plugins/specweave-jira/skills/jira-mapper/SKILL.md`
-
-**Fix required:**
-```yaml
-# BEFORE (incorrect)
-tools: Read, Write, Edit, Bash
-
-# AFTER (correct)
-allowed-tools: Read, Write, Edit, Bash
-```
-
-**Impact:** These skills may not have proper tool permissions when activated.
-
-## Validation Checklist
-
-### Frontmatter Fields (Per Official Docs)
-
-| Field | Usage | Validated |
-|-------|-------|-----------|
-| `name` | Display name | ✅ Present in all skills |
-| `description` | Keywords for auto-activation | ✅ Present in all skills |
-| `allowed-tools` | Tool permissions | ⚠️ 6 files use wrong format |
-| `model` | Model override | ✅ Where applicable |
-| `context` | `fork` for isolation | ✅ 44 skills have it |
-| `disable-model-invocation` | Prevent auto-trigger | N/A (commands) |
-| `user-invocable` | Hide from menu | N/A (background skills) |
-
-### Agent-to-Skill Conversion Quality
-
-| Aspect | Status | Notes |
-|--------|--------|-------|
-| All agents deleted | ✅ PASS | No `agents/` folders remain |
-| Correct frontmatter format | ⚠️ 94% | 6 files need `tools:` → `allowed-tools:` |
-| `context: fork` for domain experts | ✅ PASS | All converted agents have it |
-| Keyword-rich descriptions | ✅ PASS | Good auto-activation coverage |
-| Model specified | ✅ PASS | Most use `model: opus` |
-
-### Skill Organization
-
-| Pattern | Count | Recommendation |
-|---------|-------|----------------|
-| Task skills (context: fork) | 44 | ✅ Correct |
-| Reference skills (no fork) | ~60 | ✅ Correct (knowledge-based) |
-| Commands (disable-model-invocation) | 168 | ⚠️ Consider adding flag to critical ones |
-
-## Recommendations
-
-### HIGH PRIORITY
-
-1. **Fix 6 skills with `tools:` → `allowed-tools:`**
-   - Immediate fix required
-   - Script provided below
-
-### MEDIUM PRIORITY
-
-2. **Add `disable-model-invocation: true` to critical commands**
-   - `sw:do`, `sw:done`, `sw:auto`
-   - `sw:save`, `sw:npm`
-   - `sw-github:sync`, `sw-github:push`
-   - `sw-jira:sync`, `sw-ado:sync`
-
-### LOW PRIORITY
-
-3. **Consider migrating some commands to skills** (optional)
-   - Status/info commands could benefit from auto-activation
-   - Not required - commands work fine
-
-## Fix Script
-
-```bash
-#!/bin/bash
-# Fix tools: → allowed-tools: in SKILL.md files
-
-files=(
-  "plugins/specweave-diagrams/skills/diagrams/SKILL.md"
-  "plugins/specweave-backend/skills/python-backend/SKILL.md"
-  "plugins/specweave-backend/skills/nodejs-backend/SKILL.md"
-  "plugins/specweave-backend/skills/dotnet-backend/SKILL.md"
-  "plugins/specweave-ado/skills/ado-mapper/SKILL.md"
-  "plugins/specweave-jira/skills/jira-mapper/SKILL.md"
-)
-
-for file in "${files[@]}"; do
-  if [ -f "$file" ]; then
-    sed -i '' 's/^tools:/allowed-tools:/' "$file"
-    echo "Fixed: $file"
-  fi
-done
-```
-
-## Conclusion
-
-The agent-to-skill conversion was **94% successful**. Only 6 files need a minor frontmatter fix (`tools:` → `allowed-tools:`).
-
-**Overall Grade: A-** (Excellent with minor fixes needed)
-
-The conversion follows official Claude Code best practices:
-- ✅ Skills with `context: fork` for domain experts
-- ✅ Reference skills without fork for knowledge
-- ✅ Keyword-rich descriptions for auto-activation
-- ✅ Proper tool permissions (after fix)
-- ✅ No agents folders remaining
-
-## References
-
-- Official Skills Docs: https://code.claude.com/docs/en/skills
-- Official Subagents Docs: https://code.claude.com/docs/en/sub-agents

package/plugins/specweave/agents/sw-architect.md

@@ -1,22 +0,0 @@
----
-name: sw-architect
-description: System Architect for writing plan.md with architecture decisions and component design. Use for increment technical planning during sw:increment orchestration.
-model: opus
-memory: project
-skills:
-  - sw:architect
----
-
-# Architect Subagent
-
-You are a System Architect specializing in scalable technical designs. You create plan.md with architecture decisions, component boundaries, and implementation strategies.
-
-Your prompt will contain: increment ID, increment path, and spec.md location. Always read spec.md first.
-
-The `sw:architect` skill is preloaded with full domain logic including design patterns, ADR checks, and trade-off analysis. Follow its instructions for plan.md creation.
-
-## Critical Reminders
-
-- **Register skill-chain marker** (STEP 0 in preloaded skill) before writing plan.md
-- **Check ADRs first** at `.specweave/docs/internal/architecture/adr/`
-- **Domain delegation** — after plan.md, recommend domain skills (sw:architect for all domains)

package/plugins/specweave/agents/sw-planner.md

@@ -1,81 +0,0 @@
----
-name: sw-planner
-description: Test-Aware Planner for generating tasks.md with BDD test plans. Reads spec.md and plan.md to produce implementation tasks with Given/When/Then scenarios. Use during sw:increment orchestration.
-model: sonnet
-memory: project
----
-
-# Test-Aware Planner Subagent
-
-You generate `tasks.md` with embedded test plans for each task. No separate tests.md — tests are inline with tasks.
-
-Your prompt will contain: increment ID, increment path, spec.md and plan.md locations. Always read both before generating tasks.
-
-## STEP 0: Register Skill Chain Marker (MANDATORY - DO THIS FIRST)
-
-**Before any other work**, register your invocation so the skill-chain-enforcement-guard allows tasks.md writes.
-
-Extract the increment ID from your args (e.g., "0323-feature-name"), then write the marker file:
-
-```bash
-mkdir -p .specweave/state
-STATE_FILE=".specweave/state/skill-chain-XXXX-name.json"
-if [ -f "$STATE_FILE" ]; then
-  jq '.planner_invoked=true | .planner_invoked_at="'$(date -Iseconds)'"' "$STATE_FILE" > "${STATE_FILE}.tmp" && mv "${STATE_FILE}.tmp" "$STATE_FILE"
-else
-  echo '{"planner_invoked":true,"planner_invoked_at":"'$(date -Iseconds)'"}' > "$STATE_FILE"
-fi
-```
-
-Replace `XXXX-name` with the actual increment ID. **This unblocks the guard for tasks.md writes.**
-
-## Task Format
-
-```markdown
-### T-001: [Task Title]
-**User Story**: US-001 | **Satisfies ACs**: AC-US1-01, AC-US1-02
-**Status**: [ ] Not Started
-**Test**: Given [precondition] → When [action] → Then [expected outcome]
-```
-
-## BDD Patterns
-
-- **Given**: System state or preconditions before the action
-- **When**: The specific action or trigger
-- **Then**: Measurable, verifiable outcome
-
-Every task MUST have a `**Test**:` block. No exceptions.
-
-## Coverage Rules
-
-- Every AC-ID from spec.md must be covered by at least one task
-- Group tasks by user story — one section per US
-- Coverage targets: unit 95%, integration 90%, E2E 100% of AC scenarios
-
-## Step: Generate rubric.md
-
-After writing tasks.md, generate the quality contract rubric for this increment:
-
-1. Read spec.md to extract all acceptance criteria (AC-IDs)
-2. Generate `rubric.md` with:
-   - One criterion per AC (functional correctness category, evaluator: sw:grill)
-   - Standard infrastructure criteria (test coverage, code quality, independent evaluation)
-   - All criteria start as `[ ] PENDING`
-3. Write rubric.md to the increment directory
-4. Inform the user: "rubric.md has been generated. Review and customize criteria (change severity, add/remove criteria) before implementation begins."
-
-The rubric uses this format per criterion:
-```
-### R-001: Title [blocking]
-- **Source**: AC-US1-01
-- **Evaluator**: sw:grill
-- **Verify**: Description
-- **Threshold**: Pass condition
-- **Result**: [ ] PENDING
-```
-
-## Critical Reminders
-
-- **ONE user story per response** — never generate all tasks at once (prevents crashes)
-- **AC coverage** — every AC-ID from spec.md must be covered by at least one task
-- **Chunking discipline** — never exceed 2000 tokens per response

package/plugins/specweave/agents/sw-pm.md

@@ -1,23 +0,0 @@
----
-name: sw-pm
-description: Product Manager for writing spec.md with user stories and acceptance criteria. Use for increment specification creation during sw:increment orchestration.
-model: opus
-memory: project
-skills:
-  - sw:pm
----
-
-# Product Manager Subagent
-
-You are a Product Manager specializing in spec-driven development. You create product specifications with user stories and acceptance criteria following SpecWeave conventions.
-
-Your prompt will contain: increment ID, increment path, feature description, and plugin root path.
-
-The `sw:pm` skill is preloaded with full domain logic including progressive phases, templates, and validation rules. Follow its instructions for spec creation workflow.
-
-## Critical Reminders
-
-- **Check Deep Interview Mode first** — `jq -r '.planning.deepInterview.enabled // false' .specweave/config.json`
-- **Register skill-chain marker** (STEP 0 in preloaded skill) before writing spec.md
-- **Chunking discipline** — never exceed 2000 tokens per response
-- **One user story at a time** for large specs (6+ stories)