knowzcode 0.1.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,55 @@
+{
+  "name": "knowzcode-marketplace",
+  "owner": {
+    "name": "Alex Headscarf",
+    "email": "alex@headscarf.com"
+  },
+  "metadata": {
+    "description": "Official KnowzCode plugin marketplace - Platform-agnostic AI development methodology",
+    "version": "0.1.0"
+  },
+  "plugins": [
+    {
+      "name": "kc",
+      "source": "./",
+      "description": "KnowzCode - Platform-agnostic AI development methodology with TDD, quality gates, and structured workflows",
+      "version": "0.1.0",
+      "author": {
+        "name": "Alex Headscarf"
+      },
+      "homepage": "https://github.com/knowz-io/knowzcode",
+      "repository": "https://github.com/knowz-io/knowzcode",
+      "license": "MIT",
+      "keywords": ["tdd", "workflow", "methodology", "quality", "platform-agnostic"],
+      "category": "Development Workflow",
+      "tags": ["tdd", "testing", "quality-assurance", "cross-platform", "methodology"],
+      "commands": [
+        "./commands/work.md",
+        "./commands/init.md",
+        "./commands/fix.md",
+        "./commands/audit.md",
+        "./commands/plan.md",
+        "./commands/connect-mcp.md",
+        "./commands/status.md",
+        "./commands/telemetry.md",
+        "./commands/telemetry-setup.md",
+        "./commands/learn.md",
+        "./commands/register.md"
+      ],
+      "agents": [
+        "./agents/analyst.md",
+        "./agents/architect.md",
+        "./agents/builder.md",
+        "./agents/reviewer.md",
+        "./agents/closer.md",
+        "./agents/microfix-specialist.md",
+        "./agents/knowledge-migrator.md",
+        "./agents/update-coordinator.md"
+      ],
+      "skills": [
+        "./skills/start-work.md",
+        "./skills/continue.md"
+      ]
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "kc",
+  "description": "KnowzCode - Platform-agnostic AI development methodology with TDD, quality gates, and structured workflows",
+  "version": "0.1.0",
+  "author": {
+    "name": "Alex Headscarf"
+  }
+}

package/LICENSE

@@ -0,0 +1,121 @@
+MIT License with Commons Clause
+
+=============================================================================
+ORIGINAL WORK: Noderr
+=============================================================================
+
+Noderr:
+https://noderr.com
+https://github.com/kaithoughtarchitect/noderr
+
+Copyright (c) 2025 Kai ThoughtArchitect
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this framework and associated documentation files (the "Framework"), to deal
+in the Framework without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Framework, and to permit persons to whom the Framework is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Framework.
+
+THE FRAMEWORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE FRAMEWORK OR THE USE OR OTHER DEALINGS IN THE
+FRAMEWORK.
+
+"Commons Clause" License Condition v1.0
+
+The Framework is provided to you by the Licensor under the License, as defined
+below, subject to the following condition:
+
+Without limiting other conditions in the License, the grant of rights under the
+License will not include, and the License does not grant to you, the right to
+Sell the Framework.
+
+For purposes of the foregoing, "Sell" means practicing any or all of the rights
+granted to you under the License to provide to third parties, for a fee or other
+consideration (including without limitation fees for hosting or consulting/support
+services related to the Framework), a product or service whose value derives,
+entirely or substantially, from the functionality of the Framework. Any license
+notice or attribution required by the License must also include this Commons
+Clause License Condition notice.
+
+This restriction does not apply to: using Noderr to develop software for clients,
+teaching Noderr methodology in educational settings, or creating products using
+Noderr as a development tool.
+
+Framework: Noderr - The Node-Based AI Development Methodology (including all
+          documentation, prompts, templates, tracking systems, workflow guides,
+          and associated files in the GitHub repository "noderr" and any
+          distributed packages)
+
+License: MIT
+
+Licensor: Kai ThoughtArchitect
+
+=============================================================================
+DERIVATIVE WORK: KnowzCode
+=============================================================================
+
+KnowzCode:
+https://github.com/AlexHeadscarf/KnowzCode
+
+Copyright (c) 2025 Alex Headscarf
+
+This work is a derivative of Noderr, modified and extended as KnowzCode.
+All modifications and extensions are licensed under the same terms below.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this framework and associated documentation files (the "Framework"), to deal
+in the Framework without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Framework, and to permit persons to whom the Framework is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice (including the Noderr
+attribution above) shall be included in all copies or substantial portions
+of the Framework.
+
+THE FRAMEWORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS (INCLUDING BOTH KAI THOUGHTARCHITECT AND ALEX
+HEADSCARF) BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE FRAMEWORK OR THE USE OR OTHER DEALINGS IN THE FRAMEWORK.
+
+"Commons Clause" License Condition v1.0
+
+The Framework is provided to you by the Licensor under the License, as defined
+below, subject to the following condition:
+
+Without limiting other conditions in the License, the grant of rights under the
+License will not include, and the License does not grant to you, the right to
+Sell the Framework.
+
+For purposes of the foregoing, "Sell" means practicing any or all of the rights
+granted to you under the License to provide to third parties, for a fee or other
+consideration (including without limitation fees for hosting or consulting/support
+services related to the Framework), a product or service whose value derives,
+entirely or substantially, from the functionality of the Framework. Any license
+notice or attribution required by the License must also include this Commons
+Clause License Condition notice.
+
+This restriction does not apply to: using KnowzCode to develop software for
+clients, teaching KnowzCode methodology in educational settings, or creating
+products using KnowzCode as a development tool.
+
+Framework: KnowzCode - Knowledge-Driven Code Development Methodology (including
+          all documentation, prompts, templates, tracking systems, workflow
+          guides, and associated files in the GitHub repository "knowzcode"
+          and any distributed packages, as well as all inherited components
+          from Noderr)
+
+License: MIT
+
+Licensor: Alex Headscarf

package/README.md

@@ -0,0 +1,223 @@
+# KnowzCode
+
+<div align="center">
+
+**Turn any AI coding assistant into a disciplined software engineer.**
+
+[![License: MIT + Commons Clause](https://img.shields.io/badge/License-MIT_+_Commons_Clause-yellow.svg)](LICENSE)
+[![Claude Code Plugin](https://img.shields.io/badge/Claude_Code-Plugin-purple)](https://github.com/knowz-io/knowzcode)
+[![Version](https://img.shields.io/badge/version-1.0.0-blue)](https://github.com/knowz-io/knowzcode/releases)
+
+[Installation](#installation) · [Quick Start](#quick-start) · [How It Works](#how-it-works) · [Commands](#commands) · [Docs](#documentation)
+
+</div>
+
+---
+
+## The Problem
+
+AI coding assistants are powerful — they can read your entire codebase, write complex code, and understand requirements. But without structure, they forget context between sessions, make random changes without considering impact, declare "done" when they've only written code (not verified it), and let documentation drift from reality immediately.
+
+**KnowzCode fixes this.**
+
+## What KnowzCode Does
+
+KnowzCode is a **platform-agnostic development methodology** that lives in a `knowzcode/` directory inside your project. It gives any AI assistant a structured TDD workflow with quality gates, specifications, and session tracking — turning chaotic AI coding into systematic, verifiable software engineering.
+
+- **5-Phase Development Loop** — Impact analysis → specs → TDD implementation → audit → finalization
+- **Quality Gates** — Automated verification at each phase prevents broken code from advancing
+- **Living Documentation** — Architecture diagrams and specs auto-update as code changes
+- **Session Memory** — WorkGroups track complete context so nothing is lost between sessions
+- **Interruption Recovery** — Say "continue" to resume exactly where you left off
+- **Multi-Platform** — Works with Claude Code, Codex, Gemini, Cursor, Copilot, and Windsurf
+
+## How It Works
+
+Every feature follows a structured loop with quality gates between phases:
+
+```
+ ┌─────────────────────────────────────────────────────────┐
+ │                   THE KNOWZCODE LOOP                    │
+ │                                                         │
+ │  You provide a goal (e.g., "Add user authentication")   │
+ │                        ↓                                │
+ │  ┌──────────┐   ┌──────────┐   ┌──────────┐            │
+ │  │ Phase 1A │──→│ Phase 1B │──→│ Phase 2A │            │
+ │  │ Analyze  │   │ Specify  │   │ Build    │            │
+ │  │ Impact   │   │ Design   │   │ with TDD │            │
+ │  └──────────┘   └──────────┘   └──────────┘            │
+ │       ↑              ↑              │                   │
+ │   [approve]      [approve]          ↓                   │
+ │                          ┌──────────┐   ┌──────────┐   │
+ │                          │ Phase 2B │──→│ Phase 3  │   │
+ │                          │ Audit    │   │ Finalize │   │
+ │                          │ Quality  │   │ & Commit │   │
+ │                          └──────────┘   └──────────┘   │
+ │                               ↑                         │
+ │                           [approve]                     │
+ └─────────────────────────────────────────────────────────┘
+```
+
+Each gate requires your approval before proceeding. See the [Workflow Reference](./docs/workflow-reference.md) for details.
+
+## Installation
+
+### Claude Code (Plugin)
+
+```bash
+/plugin marketplace add https://github.com/knowz-io/knowzcode
+/plugin install knowzcode
+cd your-project/
+/kc:init
+```
+
+### npx (Any Platform)
+
+```bash
+npx knowzcode                                    # Interactive setup
+npx knowzcode install --platforms claude,cursor   # Specific platforms
+npx knowzcode install --platforms all             # All 6 platforms
+```
+
+| Platform | Instruction File | Support Level |
+|----------|-----------------|---------------|
+| Claude Code | `CLAUDE.md` | Full (agents + commands) |
+| OpenAI Codex | `AGENTS.md` | Adapter template |
+| Gemini CLI | `GEMINI.md` | Adapter template |
+| Cursor | `.cursor/rules/knowzcode.mdc` | Adapter template |
+| GitHub Copilot | `copilot-instructions.md` | Adapter template |
+| Windsurf | `.windsurf/rules/knowzcode.md` | Adapter template |
+
+### Manual (No Node.js)
+
+```bash
+git clone https://github.com/knowz-io/knowzcode.git
+cd KnowzCode
+./install.sh --target /path/to/your/project       # Linux/macOS
+.\install.ps1 -Target C:\path\to\your\project     # Windows
+```
+
+### Cloud Features (Optional)
+
+Connect to KnowzCode Cloud for vector-powered semantic search, AI Q&A, and learning capture via MCP. See the [Getting Started Guide](./docs/knowzcode_getting_started.md#mcp-integration-cloud-features) for setup.
+
+## Quick Start
+
+### Start a Feature
+
+```bash
+/kc:work "Build user authentication with email and password"
+```
+
+KnowzCode analyzes impact, generates specs, guides TDD implementation, verifies quality, and updates documentation — all with approval gates at each phase.
+
+### Research First
+
+```bash
+/kc:plan "how is authentication implemented?"
+```
+
+Spawns parallel research agents to explore your codebase. After investigation, say "implement" to transition into `/kc:work` with findings pre-loaded.
+
+### Quick Fix
+
+```bash
+/kc:fix "Fix typo in login button text"
+```
+
+Targeted fixes that skip the full loop — for typos, small bugs, and CSS tweaks.
+
+## Commands
+
+| Command | Description | Example |
+|:--------|:------------|:--------|
+| `/kc:init` | Initialize KnowzCode in project | `/kc:init` |
+| `/kc:work <goal>` | Start feature workflow | `/kc:work "Add dark mode"` |
+| `/kc:plan <topic>` | Research before implementing | `/kc:plan "how does auth work?"` |
+| `/kc:audit [type]` | Run quality audits | `/kc:audit security` |
+| `/kc:fix <target>` | Quick targeted fix | `/kc:fix auth.js` |
+| `/kc:connect-mcp` | Configure MCP server | `/kc:connect-mcp <api-key>` |
+| `/kc:register` | Register and configure MCP | `/kc:register` |
+| `/kc:status` | Check MCP connection | `/kc:status` |
+| `/kc:learn` | Capture learnings to vault | `/kc:learn "insight"` |
+| `/kc:telemetry` | Investigate production telemetry | `/kc:telemetry "error 500"` |
+| `/kc:telemetry-setup` | Configure telemetry sources | `/kc:telemetry-setup` |
+
+## Architecture
+
+```
+Layer 4: Platform Enhancements (optional, best experience)
+         Claude Code agents | Codex Agents SDK | Gemini Skills
+         ──────────────────────────────────────────────────────
+Layer 3: Platform Adapters (thin instruction files)
+         CLAUDE.md | AGENTS.md | GEMINI.md | .cursor/rules/*.mdc
+         ──────────────────────────────────────────────────────
+Layer 2: MCP Integration (cross-platform knowledge layer)
+         KnowzCode MCP server → vaults, search, learning capture
+         ──────────────────────────────────────────────────────
+Layer 1: Core Methodology (platform-agnostic, the actual product)
+         knowzcode/ directory → loop, specs, tracker, architecture
+```
+
+The real product is Layer 1 — the `knowzcode/` directory. Everything else enhances it. See [Understanding KnowzCode](./docs/understanding-knowzcode.md) for a deep dive.
+
+## Project Structure
+
+```
+your-project/
+└── knowzcode/
+    ├── knowzcode_loop.md          # The methodology (TDD, quality gates, phases)
+    ├── knowzcode_project.md       # Project goals, tech stack, standards
+    ├── knowzcode_architecture.md  # Auto-maintained architecture docs
+    ├── knowzcode_tracker.md       # WorkGroup status tracking
+    ├── knowzcode_log.md           # Session history
+    ├── specs/                     # Component specifications
+    ├── prompts/                   # Phase prompt templates (works with any AI)
+    ├── workgroups/                # Session data (gitignored)
+    └── enterprise/                # Optional compliance config
+```
+
+**Committed to git:** `knowzcode/*.md`, `knowzcode/specs/`, `knowzcode/prompts/`
+**Gitignored:** `knowzcode/workgroups/`, `knowzcode/environment_context.md`, `knowzcode/*.local.md`
+
+## Documentation
+
+| Guide | Description |
+|:------|:------------|
+| [Getting Started](./docs/knowzcode_getting_started.md) | Complete walkthrough, MCP setup, migration |
+| [Understanding KnowzCode](./docs/understanding-knowzcode.md) | Deep dive into concepts and architecture |
+| [Workflow Reference](./docs/workflow-reference.md) | Phase details, agent delegation, parallel execution |
+| [Prompts Guide](./docs/knowzcode_prompts_guide.md) | All prompts and command reference |
+| [Visual Guide](./docs/knowzcode_guide.md) | File structure roadmap |
+| [Developer Guide](./CLAUDE.md) | Plugin development documentation |
+
+## Contributing
+
+We welcome contributions!
+
+1. Fork the repository
+2. Create a feature branch: `git checkout -b feature/amazing`
+3. Make changes and test thoroughly
+4. Submit a pull request
+
+See **[CLAUDE.md](CLAUDE.md)** for developer documentation.
+
+## Acknowledgments
+
+KnowzCode is built upon the foundation of the [Noderr project](https://github.com/kaithoughtarchitect/noderr) by [@kaithoughtarchitect](https://github.com/kaithoughtarchitect). We're grateful for their pioneering work in systematic AI-driven development.
+
+## License
+
+MIT License with Commons Clause — See [LICENSE](LICENSE) file for details.
+
+---
+
+<div align="center">
+
+**Turn any AI coding assistant into a disciplined software engineer.**
+
+[Get Started](#installation) · [Read the Docs](#documentation) · [Contribute](#contributing)
+
+Built by [Knowz](https://github.com/knowz-io)
+
+</div>

package/agents/analyst.md

@@ -0,0 +1,121 @@
+---
+name: analyst
+description: "KnowzCode: Impact analysis and Change Set proposals"
+tools: Read, Glob, Grep, Bash
+model: opus
+permissionMode: default
+maxTurns: 25
+---
+
+# Analyst
+
+You are the **Analyst** in a KnowzCode development workflow.
+Your expertise: Impact analysis, NodeID classification, Change Set proposals.
+
+## Your Job
+
+Analyze the codebase to understand what needs to change for the given goal, then propose a Change Set with classified NodeIDs.
+
+## NodeID Classification Rules
+
+NodeIDs must be **domain concepts**, not tasks.
+
+### Default: Domain-Area Names (PascalCase)
+
+| Pattern | Examples | Covers |
+|---------|----------|--------|
+| `Authentication` | login form, auth endpoint, token service | All auth components |
+| `FileManagement` | files tab, blob proxy, PDF worker | All file handling |
+| `Checkout` | cart, orders, payment | All purchase flow |
+
+Sub-areas when a domain grows large: `Authentication_OAuth`, `Payments_Stripe`
+
+### Exception: Utility/Config NodeIDs
+
+| Prefix | Examples |
+|--------|----------|
+| `LIB_` | `LIB_DateFormat`, `LIB_Validation` |
+| `CONFIG_` | `CONFIG_FeatureFlags` |
+
+### Invalid NodeIDs (Never Use)
+
+`FIX-001`, `UI-FIX-002`, `TASK-123`, `FEATURE-X` — tasks belong in WorkGroup files, not as NodeIDs.
+
+## Consolidation-First Mindset
+
+Before proposing ANY new NodeID:
+1. `Glob: knowzcode/specs/*.md` to see what exists
+2. If an existing spec covers the same domain, propose updating it
+3. Target: **1 NodeID per WorkGroup** as default
+4. Multi-NodeID only when changes genuinely span unrelated domains
+
+## NodeID Granularity
+
+- One NodeID per new capability, not per file modified
+- Files that use/integrate a capability are "affected files" — no NodeID needed
+- Ask: "Is this creating NEW functionality?" If yes, NodeID. If just integrating, affected file.
+
+## Change Set Format
+
+```markdown
+## Change Set for WorkGroup [ID]
+
+### New Capabilities (NodeIDs)
+| NodeID | Description |
+|--------|-------------|
+| LIB_DateTimeFormat | Timezone formatting utility |
+
+### Affected Files (no NodeIDs needed)
+- JobsPage.tsx - integrate formatDateTime
+- IntakeJobsPage.tsx - integrate formatDateTime
+
+**Specs Required**: 1
+```
+
+## Historical Context
+
+Before analyzing impact:
+1. Scan `knowzcode/workgroups/` for completed WorkGroups touching similar features
+2. Extract implementation patterns, decisions, and lessons learned
+3. Reference relevant context in your Change Set proposal
+
+## Smart Scanning Strategy
+
+- Start with `knowzcode/knowzcode_architecture.md` for component map
+- Targeted grep for goal keywords
+- Read only files directly in the change path
+- Max ~20 tool calls, ~10 deep-read files
+
+## MCP Integration (Optional)
+
+If MCP is configured, enhance your analysis with vault queries:
+
+- `search_knowledge(research_vault, "past decisions about {domain}")` — find relevant architectural decisions
+- `search_knowledge(code_vault, "{affected_component} implementation")` — find related code patterns
+- `ask_question(research_vault, "conventions for {domain}?")` — check team conventions
+
+If MCP is not available, use standard grep/glob — works fine. All analysis works without MCP.
+
+## MCP Learning (Optional)
+
+After Change Set is approved, if MCP is configured:
+- `create_knowledge(research_vault, title="Scope: {goal}", tags=["scope", "change-set"])`
+  with NodeIDs, risk assessment, and user-approved boundaries
+- Skip if MCP unavailable — this is enhancement only
+
+## Exit Expectations
+
+- Produce a complete Change Set with NodeIDs and spec status
+- Flag nodes requiring new specs as `[NEEDS_SPEC]`
+- Include risk assessment and historical context
+- Present to user for approval
+
+## Multi-Agent Coordination
+
+When running in a multi-agent workflow:
+- Your Change Set output feeds into the architect for spec drafting
+- Clarify scope with the architect if NodeIDs overlap with existing specs
+- Answer the builder's questions about affected files and dependencies
+- Answer the reviewer's questions about change scope
+
+For Claude Code Agent Teams behavior, see `knowzcode/claude_code_execution.md`.

package/agents/architect.md

@@ -0,0 +1,121 @@
+---
+name: architect
+description: "KnowzCode: Specification drafting, architecture review, and design decisions"
+tools: Read, Write, Edit, Glob, Grep
+model: opus
+permissionMode: acceptEdits
+maxTurns: 20
+---
+
+# Architect
+
+You are the **Architect** in a KnowzCode development workflow.
+Your expertise: Specification authoring, architecture health review, design pattern assessment.
+
+## Your Job
+
+Draft lean, high-quality specifications for all NodeIDs in the approved Change Set. Also assess architectural alignment of proposed changes.
+
+## Spec Philosophy
+
+Specs are **lean decision records + contracts** — quick reference documents capturing key decisions, interfaces, and verification criteria. Verbose execution logs belong in WorkGroup files, not specs.
+
+### What Goes in a Spec
+
+- **Decisions** future developers need to understand
+- **Interfaces** other code depends on
+- **Verification criteria** that prove correctness (`VERIFY:` statements)
+- **Known gaps** needing future attention
+
+### What Does NOT Go in a Spec
+
+- Step-by-step implementation logic (that's what code is for)
+- Data structure definitions (unless there's a decision to document)
+- Error handling catalogs (capture via `VERIFY:` statements instead)
+
+## The 4-Section Template
+
+```markdown
+# {NodeID}: {Human-Readable Name}
+
+**Updated:** {timestamp}
+**Status:** Draft | Approved | As-Built
+
+## Rules & Decisions
+- Decision: chose X over Y because Z
+- Rule: must always validate before persisting
+
+## Interfaces
+- POST /api/users -> { id, email }
+- Depends on: AuthService for token validation
+
+## Verification Criteria
+- VERIFY: when valid credentials, returns JWT token
+- VERIFY: when email exists, returns 409
+
+## Debt & Gaps
+- TODO: add rate limiting
+```
+
+**Minimum valid spec:** 1+ Rules item, 1+ Interface item, 2+ `VERIFY:` statements.
+
+## Consolidation Mandate
+
+Before creating ANY new spec:
+1. `Glob: knowzcode/specs/*.md` to list all existing specs
+2. Read specs in the same domain area
+3. If >50% domain overlap exists, **UPDATE the existing spec** instead
+4. Target: <20 specs per project
+
+## Architecture Review
+
+When assessing architectural impact:
+- Check layer interactions for affected components
+- Identify drift between documented and implemented architecture
+- Flag pattern violations and consistency concerns
+- Verify flowchart alignment with `knowzcode/knowzcode_architecture.md`
+
+### Architecture Assessment Output
+
+```markdown
+**Architecture Assessment:**
+- Alignment: {HIGH/MEDIUM/LOW}
+- Layer Violations: {list or None}
+- Pattern Concerns: {list or None}
+- Drift Detected: {list or None}
+```
+
+## Enterprise Compliance (Optional)
+
+If `knowzcode/enterprise/compliance_manifest.md` exists and `compliance_enabled: true`:
+- Merge guideline criteria into Verification Criteria as `VERIFY:` statements
+- Address required concerns in Rules & Decisions
+- Flag blocking vs advisory compliance issues
+
+## MCP Integration (Optional)
+
+If MCP is configured, enhance your spec drafting with vault queries:
+
+- `ask_question(research_vault, "conventions for {component_type}?")` — check team conventions before drafting
+- `search_knowledge(research_vault, "{NodeID_domain} patterns")` — find related patterns and prior decisions
+- `search_knowledge(code_vault, "{component_type} implementation")` — find implementation examples to inform interfaces
+
+If MCP is not available, use grep/glob and read existing specs directly. All spec drafting works without MCP.
+
+## Exit Expectations
+
+- All specs use the 4-section format
+- Each spec has 2+ `VERIFY:` statements
+- Tracker statuses updated
+- Present specs to user for approval
+
+## Multi-Agent Coordination
+
+When running in a multi-agent workflow:
+- Receive the approved Change Set from the analyst
+- Clarify scope with the analyst if NodeIDs need adjustment
+- Answer the builder's questions about spec intent and design decisions
+- Answer the reviewer's questions about expected behavior
+- Notify the closer about spec format and any legacy specs needing migration
+
+For Claude Code Agent Teams behavior, see `knowzcode/claude_code_execution.md`.