knowzcode 0.3.7 → 0.4.0

package/knowzcode/user_preferences.md

@@ -1,120 +1,120 @@
-# User Development Preferences
-
----
-
-**Purpose:** This document captures your personal development preferences and coding standards. These preferences integrate with KnowzCode's workflow while respecting your style and approach.
-
-**Last Updated:** [ISO timestamp - to be filled during init]
-**Source:** User-provided during initialization
-
----
-
-## Core Principles
-
-[User-provided principles, or "Not configured"]
-
-*Examples:*
-- Test-Driven Development (TDD mandatory)
-- Immutable data structures preferred
-- Functional programming patterns
-- Domain-Driven Design (DDD)
-- SOLID principles
-
----
-
-## Testing Approach
-
-[User-provided testing preferences, or "Follows KnowzCode TDD requirements"]
-
-*Examples:*
-- **Framework:** XUnit / Jest / PyTest / Playwright
-- **Style:** Behavior-driven / Unit-first / Integration-focused
-- **Coverage:** Minimum 80% / All public APIs / Critical paths only
-- **Patterns:** AAA (Arrange-Act-Assert) / Given-When-Then
-- **Mocking:** Moq / Jest mocks / unittest.mock
-
----
-
-## Code Style
-
-[User-provided style preferences, or "Standard for language/framework"]
-
-*Examples:*
-- **Naming:** PascalCase for methods, camelCase for variables
-- **Structure:** Small functions (max 20 lines), single responsibility
-- **Comments:** Self-documenting code, minimal comments
-- **Formatting:** Prettier / Black / Standard formatter
-- **Linting:** ESLint / Flake8 / Custom rules
-
----
-
-## Language-Specific Patterns
-
-[User-provided language-specific preferences, or "N/A"]
-
-*Examples (C#):*
-- Nullable reference types always enabled
-- Records for immutable DTOs
-- No null-suppression operators
-- FluentValidation for schema validation
-
-*Examples (JavaScript/TypeScript):*
-- Strict TypeScript mode
-- Functional components with hooks (React)
-- Async/await over promises
-- ESM imports
-
-*Examples (Python):*
-- Type hints for all public functions
-- Dataclasses for structured data
-- f-strings for formatting
-- PEP 8 compliance
-
----
-
-## Quality Priorities
-
-[User-provided quality focus areas, or "Standard KnowzCode priorities"]
-
-*Rank your top priorities (1-5):*
-1. [e.g., Reliability / Security / Performance / Maintainability / Testability]
-2. [...]
-3. [...]
-4. [...]
-5. [...]
-
----
-
-## Project-Specific Conventions
-
-[Any project-specific rules or patterns, or "See project CLAUDE.md"]
-
-*Examples:*
-- Database migrations must be reviewed before merge
-- All API endpoints require OpenAPI documentation
-- Error handling uses Result types (no exceptions)
-- Logging format: structured JSON with correlation IDs
-
----
-
-## Integration with KnowzCode
-
-**Non-Negotiable (KnowzCode Framework):**
-- Test-Driven Development (TDD) is mandatory
-- Quality gates must pass at each phase
-- Living documentation must be maintained
-- Incremental verified progress required
-
-**Flexible (Your Preferences):**
-- Testing framework choice (as long as TDD followed)
-- Code style and naming conventions
-- Language-specific patterns
-- Quality priority ranking
-- Project-specific conventions
-
-**Conflict Resolution:**
-When your preferences conflict with KnowzCode requirements, the framework takes precedence for workflow aspects (TDD, quality gates), but your preferences apply for implementation style (naming, patterns, tools).
-
----
-
-*This document should be reviewed and updated as project conventions evolve.*
+# User Development Preferences
+
+---
+
+**Purpose:** This document captures your personal development preferences and coding standards. These preferences integrate with KnowzCode's workflow while respecting your style and approach.
+
+**Last Updated:** [ISO timestamp - to be filled during init]
+**Source:** User-provided during initialization
+
+---
+
+## Core Principles
+
+[User-provided principles, or "Not configured"]
+
+*Examples:*
+- Test-Driven Development (TDD mandatory)
+- Immutable data structures preferred
+- Functional programming patterns
+- Domain-Driven Design (DDD)
+- SOLID principles
+
+---
+
+## Testing Approach
+
+[User-provided testing preferences, or "Follows KnowzCode TDD requirements"]
+
+*Examples:*
+- **Framework:** XUnit / Jest / PyTest / Playwright
+- **Style:** Behavior-driven / Unit-first / Integration-focused
+- **Coverage:** Minimum 80% / All public APIs / Critical paths only
+- **Patterns:** AAA (Arrange-Act-Assert) / Given-When-Then
+- **Mocking:** Moq / Jest mocks / unittest.mock
+
+---
+
+## Code Style
+
+[User-provided style preferences, or "Standard for language/framework"]
+
+*Examples:*
+- **Naming:** PascalCase for methods, camelCase for variables
+- **Structure:** Small functions (max 20 lines), single responsibility
+- **Comments:** Self-documenting code, minimal comments
+- **Formatting:** Prettier / Black / Standard formatter
+- **Linting:** ESLint / Flake8 / Custom rules
+
+---
+
+## Language-Specific Patterns
+
+[User-provided language-specific preferences, or "N/A"]
+
+*Examples (C#):*
+- Nullable reference types always enabled
+- Records for immutable DTOs
+- No null-suppression operators
+- FluentValidation for schema validation
+
+*Examples (JavaScript/TypeScript):*
+- Strict TypeScript mode
+- Functional components with hooks (React)
+- Async/await over promises
+- ESM imports
+
+*Examples (Python):*
+- Type hints for all public functions
+- Dataclasses for structured data
+- f-strings for formatting
+- PEP 8 compliance
+
+---
+
+## Quality Priorities
+
+[User-provided quality focus areas, or "Standard KnowzCode priorities"]
+
+*Rank your top priorities (1-5):*
+1. [e.g., Reliability / Security / Performance / Maintainability / Testability]
+2. [...]
+3. [...]
+4. [...]
+5. [...]
+
+---
+
+## Project-Specific Conventions
+
+[Any project-specific rules or patterns, or "See project CLAUDE.md"]
+
+*Examples:*
+- Database migrations must be reviewed before merge
+- All API endpoints require OpenAPI documentation
+- Error handling uses Result types (no exceptions)
+- Logging format: structured JSON with correlation IDs
+
+---
+
+## Integration with KnowzCode
+
+**Non-Negotiable (KnowzCode Framework):**
+- Test-Driven Development (TDD) is mandatory
+- Quality gates must pass at each phase
+- Living documentation must be maintained
+- Incremental verified progress required
+
+**Flexible (Your Preferences):**
+- Testing framework choice (as long as TDD followed)
+- Code style and naming conventions
+- Language-specific patterns
+- Quality priority ranking
+- Project-specific conventions
+
+**Conflict Resolution:**
+When your preferences conflict with KnowzCode requirements, the framework takes precedence for workflow aspects (TDD, quality gates), but your preferences apply for implementation style (naming, patterns, tools).
+
+---
+
+*This document should be reviewed and updated as project conventions evolve.*

package/package.json

@@ -1,53 +1,53 @@
-{
-  "name": "knowzcode",
-  "version": "0.3.7",
-  "description": "Platform-agnostic AI development methodology with TDD, quality gates, and structured workflows",
-  "type": "module",
-  "bin": {
-    "knowzcode": "./bin/knowzcode.mjs"
-  },
-  "files": [
-    "bin/",
-    "knowzcode/",
-    "agents/",
-    "commands/",
-    "skills/",
-    ".claude-plugin/"
-  ],
-  "scripts": {
-    "prepublishOnly": "node bin/knowzcode.mjs --version"
-  },
-  "keywords": [
-    "ai",
-    "tdd",
-    "workflow",
-    "methodology",
-    "quality-gates",
-    "platform-agnostic",
-    "claude",
-    "codex",
-    "gemini",
-    "cursor",
-    "copilot",
-    "windsurf",
-    "development"
-  ],
-  "author": {
-    "name": "Alex Headscarf"
-  },
-  "homepage": "https://github.com/knowz-io/knowzcode",
-  "bugs": {
-    "url": "https://github.com/knowz-io/knowzcode/issues"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/knowz-io/knowzcode.git"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "license": "MIT",
-  "engines": {
-    "node": ">=18"
-  }
-}
+{
+  "name": "knowzcode",
+  "version": "0.4.0",
+  "description": "Platform-agnostic AI development methodology with TDD, quality gates, and structured workflows",
+  "type": "module",
+  "bin": {
+    "knowzcode": "./bin/knowzcode.mjs"
+  },
+  "files": [
+    "bin/",
+    "knowzcode/",
+    "agents/",
+    "commands/",
+    "skills/",
+    ".claude-plugin/"
+  ],
+  "scripts": {
+    "prepublishOnly": "node bin/knowzcode.mjs --version"
+  },
+  "keywords": [
+    "ai",
+    "tdd",
+    "workflow",
+    "methodology",
+    "quality-gates",
+    "platform-agnostic",
+    "claude",
+    "codex",
+    "gemini",
+    "cursor",
+    "copilot",
+    "windsurf",
+    "development"
+  ],
+  "author": {
+    "name": "Alex Headscarf"
+  },
+  "homepage": "https://github.com/knowz-io/knowzcode",
+  "bugs": {
+    "url": "https://github.com/knowz-io/knowzcode/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/knowz-io/knowzcode.git"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "license": "MIT",
+  "engines": {
+    "node": ">=18"
+  }
+}

package/skills/alias-resolver.json

@@ -1,6 +1,6 @@
 {
   "name": "alias-resolver",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Resolves friendly natural-language aliases to KnowzCode canonical values (phase, audit, plan, workgroup_type).",
   "parameters": [
     {"name": "domain", "type": "string", "required": true},

package/skills/architecture-diff.json

@@ -1,6 +1,6 @@
 {
   "name": "architecture-diff",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Highlights differences between specs and the Mermaid flowchart in knowzcode_architecture.md.",
   "parameters": [],
   "actions": [

package/skills/check-installation-status.json

@@ -1,6 +1,6 @@
 {
   "name": "check-installation-status",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Checks if KnowzCode is initialized in the current project and reports current status",
 
   "parameters": [],

package/skills/continue.md

@@ -1,126 +1,126 @@
----
-name: continue
-description: Detect continuation intent and resume active WorkGroup workflow
-trigger: User says "continue", "keep going", "resume", or similar continuation intent
----
-
-# Continue Skill
-
-**Purpose**: Detect when user wants to continue work and resume the active WorkGroup with proper context restoration.
-
-## Trigger Patterns
-
-Activate when user message matches ANY of these patterns:
-- "continue"
-- "keep going"
-- "resume"
-- "carry on"
-- "next"
-- "continue with this"
-- "let's continue"
-- "keep working"
-
-**Context Requirements**:
-- Must be in a KnowzCode-initialized project (knowzcode/ directory exists)
-- Should NOT trigger if user is clearly giving new instructions
-- Should NOT trigger during explicit command execution
-
-## When NOT to Trigger
-
-- User is giving specific new instructions
-- User is asking a question
-- Already executing a /kc:* command
-- knowzcode/ directory doesn't exist
-
-## Skill Behavior
-
-When triggered:
-
-### Step 1: Find Active WorkGroup
-
-Search `knowzcode/knowzcode_tracker.md` for `[WIP]` entries.
-
-- **One active WorkGroup**: Use it automatically
-- **Multiple active**: Present options to user
-- **None active**: Inform user and suggest `/kc:work`
-
-### Step 2: Load WorkGroup Context
-
-Read `knowzcode/workgroups/{WorkGroupID}.md` to determine:
-- Current phase
-- Primary goal
-- Change Set
-- Outstanding todos
-- **Autonomous Mode**: If the WorkGroup file contains `**Autonomous Mode**: Active`, restore `AUTONOMOUS_MODE = true` and announce: `> **Autonomous Mode: RESTORED** — continuing with auto-approved gates.`
-- **Orchestration Config**: If `knowzcode/knowzcode_orchestration.md` exists, parse and restore `MAX_BUILDERS`, `SCOUT_MODE`, `MCP_AGENTS_ENABLED`, `DEFAULT_SPECIALISTS` (same logic as work.md Step 2.4). Defaults apply if file is absent.
-
-### Step 3: Resume at Current Phase
-
-Read `knowzcode/knowzcode_loop.md` and resume the workflow at the detected phase.
-
-#### Parallel Mode Detection
-
-If the WorkGroup file contains a `## Current Stage` section (instead of `Current Phase`):
-- This is a **parallel-mode WorkGroup**
-- Read the per-NodeID phase table to determine what's in progress
-- Resume by recreating the team and spawning agents appropriate for the current stage:
-  - **Stage 0/1**: Spawn analyst + architect. If `SCOUT_MODE != "none"` and context is stale, re-spawn scout(s) per SCOUT_MODE.
-  - **Stage 2**: Spawn builder(s) per the dependency map + reviewer if any NodeIDs are past implementation
-  - **Stage 3**: Spawn closer
-- Builders and reviewer persist through gap loops (don't respawn per iteration)
-- Announce: `**Resuming Parallel Teams** — Stage {N}: {description}`
-
-If resuming mid-Stage-2 (e.g., builder was implementing, reviewer had started auditing):
-- Read the per-NodeID status table to determine which NodeIDs need builders and which need reviewer
-- Carry forward existing context by reading the WorkGroup file
-
-#### Sequential Mode Detection
-
-If the WorkGroup file contains `Current Phase:` (standard format):
-- This is a **sequential-mode WorkGroup**
-- Create tasks only for the **remaining** phases (not completed ones):
-
-| Detected Phase | Remaining Work |
-|----------------|----------------|
-| 1A | All phases (1A → 1B → 2A → 2B → 3) |
-| 1B | Specs + implementation + audit + finalization |
-| 2A | Implementation + audit + finalization |
-| 2B | Audit + finalization |
-| 3 | Finalization only |
-
-**Set up execution mode** — check `~/.claude/settings.json` and `.claude/settings.json` for `"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"` in the `env` block. If found, Agent Teams is available — create a team named `kc-{wgid}` and activate delegate mode (you coordinate only, never write code directly). Read `knowzcode/claude_code_execution.md` for team conventions. For each remaining phase, spawn one teammate with the spawn prompt from the corresponding phase section of `/kc:work`, create a task, wait for completion, present quality gate, shut down teammate. Shut down all teammates when done or on cancel.
-
-If Agent Teams is not available, announce `**Execution Mode: Subagent Delegation** — Agent Teams not available (add "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" to the env block in settings.json, then restart Claude Code)` and use `Task()` calls to delegate each remaining phase to the named agent.
-
-Follow the same phase delegation patterns (spawn prompts, quality gates, gap loop) as `/kc:work`.
-
-### Step 4: Present Status
-
-```markdown
-## Resuming WorkGroup: {wgid}
-
-**Goal**: {primary goal}
-**Phase**: {current phase}
-**NodeIDs**: {list}
-
-**Outstanding Todos**:
-{list from WorkGroup file}
-
-Continuing from where we left off...
-```
-
-Then proceed with the appropriate phase using the same agents as `/kc:work`.
-
-## Logging
-
-```markdown
----
-**Type:** SkillActivation
-**Timestamp:** [timestamp]
-**Skill:** continue
-**Trigger:** User said "{user_message}"
-**WorkGroup:** {wgid}
-**Phase:** {current phase}
-**Logged By:** AI-Agent
----
-```
+---
+name: continue
+description: Detect continuation intent and resume active WorkGroup workflow
+trigger: User says "continue", "keep going", "resume", or similar continuation intent
+---
+
+# Continue Skill
+
+**Purpose**: Detect when user wants to continue work and resume the active WorkGroup with proper context restoration.
+
+## Trigger Patterns
+
+Activate when user message matches ANY of these patterns:
+- "continue"
+- "keep going"
+- "resume"
+- "carry on"
+- "next"
+- "continue with this"
+- "let's continue"
+- "keep working"
+
+**Context Requirements**:
+- Must be in a KnowzCode-initialized project (knowzcode/ directory exists)
+- Should NOT trigger if user is clearly giving new instructions
+- Should NOT trigger during explicit command execution
+
+## When NOT to Trigger
+
+- User is giving specific new instructions
+- User is asking a question
+- Already executing a /kc:* command
+- knowzcode/ directory doesn't exist
+
+## Skill Behavior
+
+When triggered:
+
+### Step 1: Find Active WorkGroup
+
+Search `knowzcode/knowzcode_tracker.md` for `[WIP]` entries.
+
+- **One active WorkGroup**: Use it automatically
+- **Multiple active**: Present options to user
+- **None active**: Inform user and suggest `/kc:work`
+
+### Step 2: Load WorkGroup Context
+
+Read `knowzcode/workgroups/{WorkGroupID}.md` to determine:
+- Current phase
+- Primary goal
+- Change Set
+- Outstanding todos
+- **Autonomous Mode**: If the WorkGroup file contains `**Autonomous Mode**: Active`, restore `AUTONOMOUS_MODE = true` and announce: `> **Autonomous Mode: RESTORED** — continuing with auto-approved gates.`
+- **Orchestration Config**: If `knowzcode/knowzcode_orchestration.md` exists, parse and restore `MAX_BUILDERS`, `SCOUT_MODE`, `MCP_AGENTS_ENABLED`, `DEFAULT_SPECIALISTS` (same logic as work.md Step 2.4). Defaults apply if file is absent.
+
+### Step 3: Resume at Current Phase
+
+Read `knowzcode/knowzcode_loop.md` and resume the workflow at the detected phase.
+
+#### Parallel Mode Detection
+
+If the WorkGroup file contains a `## Current Stage` section (instead of `Current Phase`):
+- This is a **parallel-mode WorkGroup**
+- Read the per-NodeID phase table to determine what's in progress
+- Resume by recreating the team and spawning agents appropriate for the current stage:
+  - **Stage 0/1**: Spawn analyst + architect. If `SCOUT_MODE != "none"` and context is stale, re-spawn scout(s) per SCOUT_MODE.
+  - **Stage 2**: Spawn builder(s) per the dependency map + reviewer if any NodeIDs are past implementation
+  - **Stage 3**: Spawn closer
+- Builders and reviewer persist through gap loops (don't respawn per iteration)
+- Announce: `**Resuming Parallel Teams** — Stage {N}: {description}`
+
+If resuming mid-Stage-2 (e.g., builder was implementing, reviewer had started auditing):
+- Read the per-NodeID status table to determine which NodeIDs need builders and which need reviewer
+- Carry forward existing context by reading the WorkGroup file
+
+#### Sequential Mode Detection
+
+If the WorkGroup file contains `Current Phase:` (standard format):
+- This is a **sequential-mode WorkGroup**
+- Create tasks only for the **remaining** phases (not completed ones):
+
+| Detected Phase | Remaining Work |
+|----------------|----------------|
+| 1A | All phases (1A → 1B → 2A → 2B → 3) |
+| 1B | Specs + implementation + audit + finalization |
+| 2A | Implementation + audit + finalization |
+| 2B | Audit + finalization |
+| 3 | Finalization only |
+
+**Set up execution mode** — check `~/.claude/settings.json` and `.claude/settings.json` for `"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"` in the `env` block. If found, Agent Teams is available — create a team named `kc-{wgid}` and activate delegate mode (you coordinate only, never write code directly). Read `knowzcode/claude_code_execution.md` for team conventions. For each remaining phase, spawn one teammate with the spawn prompt from the corresponding phase section of `/kc:work`, create a task, wait for completion, present quality gate, shut down teammate. Shut down all teammates when done or on cancel.
+
+If Agent Teams is not available, announce `**Execution Mode: Subagent Delegation** — Agent Teams not available (add "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" to the env block in settings.json, then restart Claude Code)` and use `Task()` calls to delegate each remaining phase to the named agent.
+
+Follow the same phase delegation patterns (spawn prompts, quality gates, gap loop) as `/kc:work`.
+
+### Step 4: Present Status
+
+```markdown
+## Resuming WorkGroup: {wgid}
+
+**Goal**: {primary goal}
+**Phase**: {current phase}
+**NodeIDs**: {list}
+
+**Outstanding Todos**:
+{list from WorkGroup file}
+
+Continuing from where we left off...
+```
+
+Then proceed with the appropriate phase using the same agents as `/kc:work`.
+
+## Logging
+
+```markdown
+---
+**Type:** SkillActivation
+**Timestamp:** [timestamp]
+**Skill:** continue
+**Trigger:** User said "{user_message}"
+**WorkGroup:** {wgid}
+**Phase:** {current phase}
+**Logged By:** AI-Agent
+---
+```

package/skills/environment-guard.json

@@ -1,6 +1,6 @@
 {
   "name": "environment-guard",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Verifies that knowzcode/environment_context.md no longer contains placeholder brackets.",
   "parameters": [],
   "actions": [

package/skills/generate-workgroup-id.json

@@ -1,6 +1,6 @@
 {
   "name": "generate-workgroup-id",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Generates a WorkGroupID following the KnowzCode convention [type]-[slug]-YYYYMMDD-HHMMSS. The slug is a 2-4 word descriptor extracted from the goal.",
   "parameters": [
     {

package/skills/install-knowzcode.json

@@ -1,6 +1,6 @@
 {
   "name": "install-knowzcode",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Initializes KnowzCode directory structure and required files in the current project",
 
   "parameters": [

package/skills/load-core-context.json

@@ -1,6 +1,6 @@
 {
   "name": "load-core-context",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "description": "Loads the KnowzCode project overview, architecture, tracker, log header, and automation manifest for downstream steps.",
   "parameters": [],
   "actions": [