knowzcode 0.4.0 → 0.5.2

package/commands/init.md

@@ -1,500 +1,616 @@
----
-description: Initialize KnowzCode framework in the current project
----
-
-# KnowzCode Project Initialization
-
-You are the **KnowzCode Initialization Agent**. Set up the KnowzCode framework in the current working directory.
-
-## What KnowzCode Provides
-
-KnowzCode is a structured development methodology that provides:
-- **Structured TDD workflow** with quality gates
-- **Specification-driven development** with living documentation
-- **Comprehensive tracking** of WorkGroups and specifications
-- **Platform-agnostic** — works with Claude Code, Codex, Gemini, Cursor, Copilot, and more
-
-## Steps to Execute
-
-### 1. Check if already initialized
-
-- Look for existing `knowzcode/` directory
-- If exists and has content, ask user:
-  - **Abort** (preserve existing)
-  - **Merge** (add missing files only)
-  - **Overwrite** (reset to templates)
-
-### 2. Create directory structure
-
-```
-knowzcode/
-├── knowzcode_project.md
-├── knowzcode_tracker.md
-├── knowzcode_log.md
-├── knowzcode_architecture.md
-├── knowzcode_loop.md
-├── knowzcode_orchestration.md
-├── platform_adapters.md
-├── environment_context.md
-├── user_preferences.md (if configured)
-├── .gitignore
-├── specs/
-├── workgroups/
-├── prompts/
-└── enterprise/ (optional)
-```
-
-### 3. Copy template files
-
-Use the embedded templates below.
-
-### 4. Generate environment context
-
-- Detect project language, framework, tools
-- Populate `environment_context.md`
-- Include package managers, test runners, build tools
-
-### 5. Capture user preferences (optional)
-
-- Ask: "Would you like to configure development preferences? (optional)"
-- If yes: prompt for testing frameworks, code style, quality priorities
-- Create `knowzcode/user_preferences.md`
-
-### 5.5. Configure orchestration defaults (optional)
-
-Ask: "Would you like to configure agent orchestration defaults? (optional — can be changed later in knowzcode/knowzcode_orchestration.md)"
-
-If yes: prompt for:
-- Max concurrent builders (1-5, default: 5)
-- Scout mode (full/minimal/none, default: full)
-- Default specialists (checkboxes: security-officer, test-advisor, project-advisor)
-- MCP agents enabled (yes/no, default: yes)
-
-If no: generate with all defaults.
-
-Generate `knowzcode/knowzcode_orchestration.md` from the template (always — it's part of the standard file set).
-
-### 6. Create .gitignore
-
-Protect environment-specific files from git:
-```
-environment_context.md
-workgroups/
-*.local.md
-.scratch/
-```
-
-### 7. Detect AI platforms and generate adapters
-
-Check which AI platforms are present and offer to generate adapter files.
-
-**Step 7a: Detect platforms**
-```
-CHECK for existing files:
-  - CLAUDE.md → offer to append KnowzCode section
-  - AGENTS.md or AGENTS.override.md → offer to generate Codex adapter
-  - GEMINI.md or ~/.gemini/GEMINI.md → offer to generate Gemini adapter
-  - .cursor/rules/ or .cursorrules (deprecated) → offer Cursor adapter (.cursor/rules/knowzcode.mdc)
-  - .github/copilot-instructions.md OR .github/ directory → offer Copilot adapter (full prompt files)
-  - .windsurf/rules/ or .windsurfrules (deprecated) → offer Windsurf adapter (.windsurf/rules/knowzcode.md)
-```
-
-**Step 7b: Present options**
-```
-PRESENT to user:
-  "Which AI platform adapters would you like to generate?"
-  Options:
-  - Detected platforms only
-  - All platforms
-  - Skip (just use knowzcode/ directly)
-```
-
-**Step 7c: Generate project-specific adapters**
-
-When generating adapters, inject detected project info to make them project-specific:
-
-1. From `environment_context.md`, extract:
-   - Test runner command (e.g., `npm test`, `pytest`, `dotnet test`)
-   - Build command (e.g., `npm run build`, `go build`)
-   - Language/framework (e.g., TypeScript/React, Python/FastAPI)
-
-2. Inject into adapter templates where applicable:
-   - Replace generic test/build references with detected commands
-   - Add framework-specific notes (e.g., "Use Composer for multi-file React edits" for Cursor)
-
-3. For Codex: note that `AGENTS.override.md` can be used for user-local overrides
-
-**Step 7c-codex: Generate Codex skill files**
-
-When Codex is selected, generate skill files in addition to `AGENTS.md`:
-
-```
-1. Create .codex/skills/kc/ directory
-2. Generate 6 skill files from platform_adapters.md "Codex Skill Files" section:
-   - .codex/skills/kc/work.md
-   - .codex/skills/kc/plan.md
-   - .codex/skills/kc/fix.md
-   - .codex/skills/kc/audit.md
-   - .codex/skills/kc/learn.md
-   - .codex/skills/kc/continue.md
-3. Replace "vX.Y.Z" with current KnowzCode version
-```
-
-**Codex success message:**
-```
-OpenAI Codex adapter generated:
-  AGENTS.md                              (primary instructions)
-  .codex/skills/kc/work.md              (/kc:work — start workflow)
-  .codex/skills/kc/plan.md              (/kc:plan — research)
-  .codex/skills/kc/fix.md               (/kc:fix — quick fix)
-  .codex/skills/kc/audit.md             (/kc:audit — quality audit)
-  .codex/skills/kc/learn.md             (/kc:learn — capture learning)
-  .codex/skills/kc/continue.md          (/kc:continue — resume workflow)
-
-Tip: Run `npx knowzcode install --platforms codex --global` to install
-skills globally to ~/.codex/skills/kc/ (available in all projects).
-```
-
-**Step 7c-gemini: Generate Gemini TOML command files**
-
-When Gemini is selected, generate TOML command files in addition to `GEMINI.md`:
-
-```
-1. Create .gemini/commands/kc/ directory
-2. Generate 7 TOML files from platform_adapters.md "Native Commands" section:
-   - .gemini/commands/kc/work.toml
-   - .gemini/commands/kc/plan.toml
-   - .gemini/commands/kc/fix.toml
-   - .gemini/commands/kc/audit.toml
-   - .gemini/commands/kc/learn.toml
-   - .gemini/commands/kc/status.toml
-   - .gemini/commands/kc/continue.toml
-3. Replace "vX.Y.Z" with current KnowzCode version
-```
-
-**Gemini success message:**
-```
-Gemini CLI adapter generated:
-  GEMINI.md                                  (primary instructions)
-  .gemini/commands/kc/work.toml             (/kc:work — start workflow)
-  .gemini/commands/kc/plan.toml             (/kc:plan — research)
-  .gemini/commands/kc/fix.toml              (/kc:fix — quick fix)
-  .gemini/commands/kc/audit.toml            (/kc:audit — quality audit)
-  .gemini/commands/kc/learn.toml            (/kc:learn — capture learning)
-  .gemini/commands/kc/status.toml           (/kc:status — connection status)
-  .gemini/commands/kc/continue.toml         (/kc:continue — resume workflow)
-```
-
-**Step 7d: Validate generated adapters**
-
-After generation, verify each adapter:
-- References correct `knowzcode/` file paths
-- Contains all 5 phase descriptions
-- Mentions TDD enforcement and quality gates
-- Includes PAUSE/STOP instructions at quality gates
-
-Adapter templates are in `knowzcode/platform_adapters.md`. Copy the relevant sections into the appropriate files.
-
-**Step 7e: Copilot-specific generation**
-
-When Copilot is selected, generate the full prompt file suite in addition to the instructions file:
-
-```
-1. Create .github/ directory if it doesn't exist
-2. Create .github/copilot-instructions.md from platform_adapters.md template Section A
-3. Create .github/prompts/ directory
-4. Generate all 9 prompt files from platform_adapters.md template Section B:
-   - .github/prompts/kc-work.prompt.md
-   - .github/prompts/kc-analyze.prompt.md
-   - .github/prompts/kc-specify.prompt.md
-   - .github/prompts/kc-implement.prompt.md
-   - .github/prompts/kc-audit.prompt.md
-   - .github/prompts/kc-finalize.prompt.md
-   - .github/prompts/kc-fix.prompt.md
-   - .github/prompts/kc-plan.prompt.md
-   - .github/prompts/kc-continue.prompt.md
-5. Replace "vX.Y.Z" in generated files with the current KnowzCode version
-6. Optionally create .vscode/mcp.json skeleton from template Section C
-   (ask user: "Would you like to generate MCP configuration for VS Code?")
-```
-
-**Skip Agent Teams enablement for Copilot** — Copilot uses single-agent sequential execution.
-
-**Copilot success message:**
-```
-GitHub Copilot adapter generated:
-  .github/copilot-instructions.md     (repository-level instructions)
-  .github/prompts/kc-work.prompt.md   (start workflow: #prompt:kc-work)
-  .github/prompts/kc-analyze.prompt.md
-  .github/prompts/kc-specify.prompt.md
-  .github/prompts/kc-implement.prompt.md
-  .github/prompts/kc-audit.prompt.md
-  .github/prompts/kc-finalize.prompt.md
-  .github/prompts/kc-fix.prompt.md    (quick fix: #prompt:kc-fix)
-  .github/prompts/kc-plan.prompt.md   (research: #prompt:kc-plan)
-  .github/prompts/kc-continue.prompt.md (resume: #prompt:kc-continue)
-
-Usage in VS Code:
-  #prompt:kc-work "Build user authentication"  — Start a feature
-  #prompt:kc-fix "Fix login redirect bug"      — Quick fix
-  #prompt:kc-continue                          — Resume where you left off
-
-See knowzcode/copilot_execution.md for the full execution guide.
-```
-
-### 7.5. Enable Agent Teams (Claude Code only)
-
-If the user is on Claude Code, **actively offer** to enable Agent Teams:
-
-**Step 7.5a: Ask the user**
-```
-"Would you like to enable Agent Teams? (recommended for Claude Code)
-
-Agent Teams spawns specialized teammates for each workflow phase,
-giving you richer multi-agent coordination.
-
-Without it, KnowzCode uses subagent delegation (works fine, just less interactive)."
-
-Options:
-  - Yes, for this project only (recommended)
-  - Yes, for all projects (writes to ~/.claude/settings.json)
-  - No (use subagent fallback)
-```
-
-**Step 7.5b: If yes, create/update the appropriate settings file**
-
-- **"This project only"** → write to `.claude/settings.local.json` (project-level, gitignored)
-- **"All projects"** → write to `~/.claude/settings.json` (home-level global config)
-
-Read the target settings file if it exists. Merge the Agent Teams env var into it:
-
-```json
-{
-  "env": {
-    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
-  }
-}
-```
-
-If the file already has other keys, preserve them and merge. If it doesn't exist, create it with the content above.
-
-**Step 7.5c: Windows note**
-
-If the platform is Windows (`process.platform === 'win32'` or detected via environment):
-```
-Note: On Windows, Agent Teams runs in "in-process" mode by default
-(split-pane tmux mode is not supported in Windows Terminal).
-This works correctly — no action needed.
-```
-
-**Step 7.5d: If no, proceed normally** — subagent delegation works without any configuration.
-
-### 8. Optional: Set up enterprise compliance (experimental)
-
-- Ask: "Would you like to set up enterprise compliance features? (optional)"
-- If yes: create `knowzcode/enterprise/` directory with manifest and templates
-- Compliance is disabled by default
-
-### 9. Optional: Configure MCP
-
-Inform user about enhanced features:
-```
-Optional: Connect to KnowzCode Cloud for AI-powered capabilities:
-  New user?     /kc:register
-  Have a key?   /kc:connect-mcp <api-key>
-```
-
-### 10. Report success
-
-```
-KnowzCode initialized successfully!
-
-Created:
-  knowzcode/knowzcode_project.md
-  knowzcode/knowzcode_tracker.md
-  knowzcode/knowzcode_log.md
-  knowzcode/knowzcode_architecture.md
-  knowzcode/knowzcode_loop.md
-  knowzcode/knowzcode_orchestration.md
-  knowzcode/platform_adapters.md
-  knowzcode/.gitignore
-  knowzcode/specs/
-  knowzcode/workgroups/
-  knowzcode/prompts/
-
-Platform adapters: [list generated adapters or "None (skip)"]
-
-Agent Teams: [Enabled (.claude/settings.local.json) | Not enabled (subagent fallback)]
-
-Next steps:
-  1. Review knowzcode/knowzcode_project.md and add project details
-  2. Start your first feature: /kc:work "your feature description"
-  3. Research first: /kc:plan "your question"
-```
-
----
-
-## Template Files
-
-### knowzcode_project.md
-```markdown
-# KnowzCode Project Overview
-
-**Purpose:** Project context for KnowzCode AI agents.
-
-### 1. Project Goal & Core Problem
-*   **Goal:** [To be filled in during first session]
-*   **Core Problem Solved:** [To be filled in during first session]
-
-### 2. Scope & Key Features
-*   **Key Features (In Scope):**
-    *   [Feature 1]: [Description]
-*   **Out of Scope:**
-    *   [Deferred 1]: [Description]
-
-### 3. Technology Stack
-| Category | Technology | Version | Notes |
-|:---------|:-----------|:--------|:------|
-| Language(s) | [Detected] | [Detected] | [Auto-detected] |
-| Testing | [Detected] | [Detected] | [Auto-detected] |
-
-### Links to Other Artifacts
-* **Loop Protocol:** `knowzcode/knowzcode_loop.md`
-* **Session Log:** `knowzcode/knowzcode_log.md`
-* **Architecture:** `knowzcode/knowzcode_architecture.md`
-* **Tracker:** `knowzcode/knowzcode_tracker.md`
-* **Specifications:** `knowzcode/specs/`
-```
-
-### knowzcode_tracker.md
-```markdown
-# KnowzCode Status Map (WorkGroup Tracker)
-
-**Purpose:** Tracks all active and completed WorkGroups.
-
-## Active WorkGroups
-
-*None yet. Run `/kc:work "your feature description"` to create your first WorkGroup.*
-
-## Completed WorkGroups
-
-*None yet.*
-
-**Next WorkGroup ID:** WG-001
-```
-
-### knowzcode_log.md
-```markdown
-# KnowzCode Operational Record
-
-**Purpose:** Session log and quality criteria reference.
-
-## Recent Sessions
-
-*No sessions yet.*
-
-## Reference Quality Criteria
-
-1. **Reliability:** Robust error handling, graceful degradation
-2. **Maintainability:** Clear code structure, good naming, modularity
-3. **Security:** Input validation, secure authentication, data protection
-4. **Performance:** Efficient algorithms, optimized queries
-5. **Testability:** Comprehensive test coverage, clear test cases
-```
-
-### knowzcode_architecture.md
-```markdown
-# KnowzCode Architecture Documentation
-
-**Purpose:** Living architecture documentation for this project.
-
-## System Architecture
-
-*To be populated during first feature development.*
-
-## Key Components
-
-*To be populated during implementation.*
-
-## Data Flow
-
-*To be populated during implementation.*
-```
-
-### environment_context.md
-```markdown
-# KnowzCode Environment Context
-
-**Purpose:** Environment and tooling information.
-
-## Detected Environment
-
-**Platform:** [Auto-detected]
-**Language:** [Auto-detected]
-**Package Manager:** [Auto-detected]
-**Test Runner:** [Auto-detected]
-```
-
-### knowzcode_orchestration.md
-```markdown
-# KnowzCode Orchestration Configuration
-
-**Purpose:** Project-level defaults for team sizing and agent orchestration. Read by `/kc:work` and `/kc:audit` at startup. Per-invocation flags override these settings.
-
----
-
-## Builder Configuration
-
-```yaml
-max_builders: 5
-```
-
----
-
-## Scout Configuration
-
-```yaml
-scout_mode: full
-```
-
----
-
-## Specialist Defaults
-
-```yaml
-default_specialists: []
-```
-
----
-
-## MCP Agent Configuration
-
-```yaml
-mcp_agents_enabled: true
-```
-
----
-
-## Override Precedence
-
-| Setting | Config Default | Flag Override |
-|---------|---------------|--------------|
-| max_builders | `max_builders:` | `--max-builders=N` |
-| scout_mode | `scout_mode:` | `--no-scouts` |
-| default_specialists | `default_specialists:` | `--specialists`, `--no-specialists` |
-| mcp_agents_enabled | `mcp_agents_enabled:` | `--no-mcp` |
-
-Per-invocation flags always win. `--specialists` adds to defaults; `--no-specialists` clears all.
-```
-
----
-
-## Error Handling
-
-If initialization fails:
-1. Report which step failed
-2. Show partial progress
-3. Suggest remediation
-4. Offer to clean up
-
-Execute this initialization now.
+---
+description: Initialize KnowzCode framework in the current project
+---
+
+# KnowzCode Project Initialization
+
+You are the **KnowzCode Initialization Agent**. Set up the KnowzCode framework in the current working directory.
+
+## What KnowzCode Provides
+
+KnowzCode is a structured development methodology that provides:
+- **Structured TDD workflow** with quality gates
+- **Specification-driven development** with living documentation
+- **Comprehensive tracking** of WorkGroups and specifications
+- **Platform-agnostic** — works with Claude Code, Codex, Gemini, Cursor, Copilot, and more
+
+## Steps to Execute
+
+### 1. Check if already initialized
+
+- Look for existing `knowzcode/` directory
+- If exists and has content, ask user:
+  - **Abort** (preserve existing)
+  - **Merge** (add missing files only)
+  - **Overwrite** (reset to templates)
+
+### 2. Create directory structure
+
+```
+knowzcode/
+├── knowzcode_project.md
+├── knowzcode_tracker.md
+├── knowzcode_log.md
+├── knowzcode_architecture.md
+├── knowzcode_loop.md
+├── knowzcode_orchestration.md
+├── platform_adapters.md
+├── environment_context.md
+├── user_preferences.md (if configured)
+├── .gitignore
+├── specs/
+├── workgroups/
+├── prompts/
+└── enterprise/ (optional)
+```
+
+### 3. Copy template files
+
+Use the embedded templates below.
+
+### 4. Generate environment context
+
+- Detect project language, framework, tools
+- Populate `environment_context.md`
+- Include package managers, test runners, build tools
+
+### 5. Capture user preferences (optional)
+
+- Ask: "Would you like to configure development preferences? (optional)"
+- If yes: prompt for testing frameworks, code style, quality priorities
+- Create `knowzcode/user_preferences.md`
+
+### 5.5. Configure orchestration defaults (optional)
+
+Ask: "Would you like to configure agent orchestration defaults? (optional — can be changed later in knowzcode/knowzcode_orchestration.md)"
+
+If yes: prompt for:
+- Max concurrent builders (1-5, default: 5)
+- Scout mode (full/minimal/none, default: full)
+- Default specialists (checkboxes: security-officer, test-advisor, project-advisor)
+- MCP agents enabled (yes/no, default: yes)
+
+If no: generate with all defaults.
+
+Generate `knowzcode/knowzcode_orchestration.md` from the template (always — it's part of the standard file set).
+
+### 6. Create .gitignore
+
+Protect environment-specific files from git:
+```
+environment_context.md
+workgroups/
+*.local.md
+.scratch/
+```
+
+### 7. Detect AI platforms and generate adapters
+
+Check which AI platforms are present and offer to generate adapter files.
+
+**Step 7a: Detect platforms**
+```
+CHECK for existing files:
+  - CLAUDE.md → offer to append KnowzCode section
+  - AGENTS.md or AGENTS.override.md → offer to generate Codex adapter
+  - GEMINI.md or ~/.gemini/GEMINI.md → offer to generate Gemini adapter
+  - .cursor/rules/ or .cursorrules (deprecated) → offer Cursor adapter (.cursor/rules/knowzcode.mdc)
+  - .github/copilot-instructions.md OR .github/ directory → offer Copilot adapter (full prompt files)
+  - .windsurf/rules/ or .windsurfrules (deprecated) → offer Windsurf adapter (.windsurf/rules/knowzcode.md)
+```
+
+**Step 7b: Present options**
+```
+PRESENT to user:
+  "Which AI platform adapters would you like to generate?"
+  Options:
+  - Detected platforms only
+  - All platforms
+  - Skip (just use knowzcode/ directly)
+```
+
+**Step 7c: Generate project-specific adapters**
+
+When generating adapters, inject detected project info to make them project-specific:
+
+1. From `environment_context.md`, extract:
+   - Test runner command (e.g., `npm test`, `pytest`, `dotnet test`)
+   - Build command (e.g., `npm run build`, `go build`)
+   - Language/framework (e.g., TypeScript/React, Python/FastAPI)
+
+2. Inject into adapter templates where applicable:
+   - Replace generic test/build references with detected commands
+   - Add framework-specific notes (e.g., "Use Composer for multi-file React edits" for Cursor)
+
+3. For Codex: note that `AGENTS.override.md` can be used for user-local overrides
+
+**Step 7c-codex: Generate Codex skill files**
+
+When Codex is selected, generate skill files in addition to `AGENTS.md`:
+
+```
+1. Create .agents/skills/ directory
+2. Generate 12 skill files from platform_adapters.md "Codex Skill Files" section:
+   - .agents/skills/kc-work/SKILL.md
+   - .agents/skills/kc-plan/SKILL.md
+   - .agents/skills/kc-fix/SKILL.md
+   - .agents/skills/kc-audit/SKILL.md
+   - .agents/skills/kc-learn/SKILL.md
+   - .agents/skills/kc-continue/SKILL.md
+   - .agents/skills/kc-init/SKILL.md
+   - .agents/skills/kc-status/SKILL.md
+   - .agents/skills/kc-connect-mcp/SKILL.md
+   - .agents/skills/kc-register/SKILL.md
+   - .agents/skills/kc-telemetry/SKILL.md
+   - .agents/skills/kc-telemetry-setup/SKILL.md
+3. Replace "vX.Y.Z" with current KnowzCode version
+```
+
+**Codex success message:**
+```
+OpenAI Codex adapter generated:
+  AGENTS.md                                       (primary instructions)
+  .agents/skills/kc-work/SKILL.md                (/kc:work — start workflow)
+  .agents/skills/kc-plan/SKILL.md                (/kc:plan — research)
+  .agents/skills/kc-fix/SKILL.md                 (/kc:fix — quick fix)
+  .agents/skills/kc-audit/SKILL.md               (/kc:audit — quality audit)
+  .agents/skills/kc-learn/SKILL.md               (/kc:learn — capture learning)
+  .agents/skills/kc-continue/SKILL.md            (/kc:continue — resume workflow)
+  .agents/skills/kc-init/SKILL.md                (/kc:init — initialize project)
+  .agents/skills/kc-status/SKILL.md              (/kc:status — check status)
+  .agents/skills/kc-connect-mcp/SKILL.md         (/kc:connect-mcp — configure MCP)
+  .agents/skills/kc-register/SKILL.md            (/kc:register — register account)
+  .agents/skills/kc-telemetry/SKILL.md           (/kc:telemetry — investigate errors)
+  .agents/skills/kc-telemetry-setup/SKILL.md     (/kc:telemetry-setup — configure sources)
+
+Tip: Run `npx knowzcode install --platforms codex --global` to install
+skills globally to ~/.agents/skills/ (available in all projects).
+```
+
+**Step 7c-gemini-mcp: Offer MCP configuration for Gemini CLI**
+
+After generating GEMINI.md + commands + skills + subagents, run Smart Discovery first:
+1. Check `KNOWZ_API_KEY` environment variable
+2. Check `knowzcode/mcp_config.md` — if `Connected: Yes`, endpoint and key info available
+3. Check `.mcp.json` or `.vscode/mcp.json` for existing API key (extract Bearer token)
+
+If existing config found:
+  "Found existing MCP config (endpoint: {endpoint}, key ending ...{last4}).
+   Configure Gemini using this existing config? [Yes] [No, enter different key] [Skip]"
+  If Yes: write .gemini/settings.json using discovered config (no key prompt needed)
+
+If no existing config found, ask:
+```
+"Would you like to configure MCP for Gemini CLI? (Requires a KnowzCode API key)"
+```
+
+- If **"Yes, I have a key"**: Accept API key →
+  1. Write `.gemini/settings.json` (merge with existing if present):
+     ```json
+     {
+       "mcpServers": {
+         "knowz": {
+           "url": "https://mcp.knowz.io/mcp",
+           "headers": {
+             "Authorization": "Bearer <api-key>",
+             "X-Project-Path": "<project-path>"
+           }
+         }
+       }
+     }
+     ```
+  2. Verify by calling `list_vaults` if possible
+  3. Update `knowzcode/mcp_config.md` with connection status
+- If **"Yes, register first"**: Direct to `/kc:register`
+- If **"No"**: Skip, mention `/kc:connect-mcp` for later setup
+
+**Step 7c-gemini: Generate Gemini TOML commands, skills, and subagents**
+
+When Gemini is selected, generate TOML command files, skill files, and subagent definitions in addition to `GEMINI.md`:
+
+```
+1. Create .gemini/commands/kc/ directory
+2. Generate 12 TOML files from platform_adapters.md "Native Commands" section:
+   - .gemini/commands/kc/work.toml
+   - .gemini/commands/kc/plan.toml
+   - .gemini/commands/kc/fix.toml
+   - .gemini/commands/kc/audit.toml
+   - .gemini/commands/kc/learn.toml
+   - .gemini/commands/kc/status.toml
+   - .gemini/commands/kc/continue.toml
+   - .gemini/commands/kc/init.toml
+   - .gemini/commands/kc/connect-mcp.toml
+   - .gemini/commands/kc/register.toml
+   - .gemini/commands/kc/telemetry.toml
+   - .gemini/commands/kc/telemetry-setup.toml
+3. Create .gemini/skills/ directory
+4. Generate 12 skill files from platform_adapters.md "Gemini Skill Files" section:
+   - .gemini/skills/kc-work/SKILL.md
+   - .gemini/skills/kc-plan/SKILL.md
+   - .gemini/skills/kc-fix/SKILL.md
+   - .gemini/skills/kc-audit/SKILL.md
+   - .gemini/skills/kc-learn/SKILL.md
+   - .gemini/skills/kc-continue/SKILL.md
+   - .gemini/skills/kc-init/SKILL.md
+   - .gemini/skills/kc-status/SKILL.md
+   - .gemini/skills/kc-connect-mcp/SKILL.md
+   - .gemini/skills/kc-register/SKILL.md
+   - .gemini/skills/kc-telemetry/SKILL.md
+   - .gemini/skills/kc-telemetry-setup/SKILL.md
+5. Replace "vX.Y.Z" with current KnowzCode version
+```
+
+**Step 7c-gemini-agents: Generate Gemini subagent files (experimental, opt-in)**
+
+Ask user: "Would you like to generate Gemini subagent definitions? (experimental — requires `experimental.enableAgents: true` in Gemini settings.json)"
+
+If yes:
+```
+1. Create .gemini/agents/ directory
+2. Generate 14 subagent files from platform_adapters.md "Gemini Subagents" section:
+   - .gemini/agents/kc-analyst.md
+   - .gemini/agents/kc-architect.md
+   - .gemini/agents/kc-builder.md
+   - .gemini/agents/kc-reviewer.md
+   - .gemini/agents/kc-closer.md
+   - .gemini/agents/kc-context-scout.md
+   - .gemini/agents/kc-knowz-scout.md
+   - .gemini/agents/kc-knowz-scribe.md
+   - .gemini/agents/kc-microfix.md
+   - .gemini/agents/kc-knowledge-migrator.md
+   - .gemini/agents/kc-update-coordinator.md
+   - .gemini/agents/kc-security-officer.md
+   - .gemini/agents/kc-test-advisor.md
+   - .gemini/agents/kc-project-advisor.md
+3. Replace "vX.Y.Z" with current KnowzCode version
+```
+
+**Gemini success message:**
+```
+Gemini CLI adapter generated:
+  GEMINI.md                                       (primary instructions)
+  .gemini/commands/kc/work.toml                  (/kc:work — start workflow)
+  .gemini/commands/kc/plan.toml                  (/kc:plan — research)
+  .gemini/commands/kc/fix.toml                   (/kc:fix — quick fix)
+  .gemini/commands/kc/audit.toml                 (/kc:audit — quality audit)
+  .gemini/commands/kc/learn.toml                 (/kc:learn — capture learning)
+  .gemini/commands/kc/status.toml                (/kc:status — connection status)
+  .gemini/commands/kc/continue.toml              (/kc:continue — resume workflow)
+  .gemini/commands/kc/init.toml                  (/kc:init — initialize project)
+  .gemini/commands/kc/connect-mcp.toml           (/kc:connect-mcp — configure MCP)
+  .gemini/commands/kc/register.toml              (/kc:register — register account)
+  .gemini/commands/kc/telemetry.toml             (/kc:telemetry — investigate errors)
+  .gemini/commands/kc/telemetry-setup.toml       (/kc:telemetry-setup — configure sources)
+  .gemini/skills/kc-work/SKILL.md                (discoverable skill)
+  .gemini/skills/kc-plan/SKILL.md                (discoverable skill)
+  .gemini/skills/kc-fix/SKILL.md                 (discoverable skill)
+  .gemini/skills/kc-audit/SKILL.md               (discoverable skill)
+  .gemini/skills/kc-learn/SKILL.md               (discoverable skill)
+  .gemini/skills/kc-continue/SKILL.md            (discoverable skill)
+  .gemini/skills/kc-init/SKILL.md                (discoverable skill)
+  .gemini/skills/kc-status/SKILL.md              (discoverable skill)
+  .gemini/skills/kc-connect-mcp/SKILL.md         (discoverable skill)
+  .gemini/skills/kc-register/SKILL.md            (discoverable skill)
+  .gemini/skills/kc-telemetry/SKILL.md           (discoverable skill)
+  .gemini/skills/kc-telemetry-setup/SKILL.md     (discoverable skill)
+  .gemini/agents/kc-*.md (14 subagents)          (experimental — if opted in)
+
+MCP: [Configured (.gemini/settings.json) | Not configured — run /kc:connect-mcp later]
+
+Tip: Run `npx knowzcode install --platforms gemini --global` to install
+skills globally to ~/.gemini/skills/ (available in all projects).
+```
+
+**Step 7d: Validate generated adapters**
+
+After generation, verify each adapter:
+- References correct `knowzcode/` file paths
+- Contains all 5 phase descriptions
+- Mentions TDD enforcement and quality gates
+- Includes PAUSE/STOP instructions at quality gates
+
+Adapter templates are in `knowzcode/platform_adapters.md`. Copy the relevant sections into the appropriate files.
+
+**Step 7e: Copilot-specific generation**
+
+When Copilot is selected, generate the full prompt file suite in addition to the instructions file:
+
+```
+1. Create .github/ directory if it doesn't exist
+2. Create .github/copilot-instructions.md from platform_adapters.md template Section A
+3. Create .github/prompts/ directory
+4. Generate all 9 prompt files from platform_adapters.md template Section B:
+   - .github/prompts/kc-work.prompt.md
+   - .github/prompts/kc-analyze.prompt.md
+   - .github/prompts/kc-specify.prompt.md
+   - .github/prompts/kc-implement.prompt.md
+   - .github/prompts/kc-audit.prompt.md
+   - .github/prompts/kc-finalize.prompt.md
+   - .github/prompts/kc-fix.prompt.md
+   - .github/prompts/kc-plan.prompt.md
+   - .github/prompts/kc-continue.prompt.md
+5. Replace "vX.Y.Z" in generated files with the current KnowzCode version
+6. Optionally create .vscode/mcp.json skeleton from template Section C
+   (ask user: "Would you like to generate MCP configuration for VS Code?")
+```
+
+**Skip Agent Teams enablement for Copilot** — Copilot uses single-agent sequential execution.
+
+**Copilot success message:**
+```
+GitHub Copilot adapter generated:
+  .github/copilot-instructions.md     (repository-level instructions)
+  .github/prompts/kc-work.prompt.md   (start workflow: #prompt:kc-work)
+  .github/prompts/kc-analyze.prompt.md
+  .github/prompts/kc-specify.prompt.md
+  .github/prompts/kc-implement.prompt.md
+  .github/prompts/kc-audit.prompt.md
+  .github/prompts/kc-finalize.prompt.md
+  .github/prompts/kc-fix.prompt.md    (quick fix: #prompt:kc-fix)
+  .github/prompts/kc-plan.prompt.md   (research: #prompt:kc-plan)
+  .github/prompts/kc-continue.prompt.md (resume: #prompt:kc-continue)
+
+Usage in VS Code:
+  #prompt:kc-work "Build user authentication"  — Start a feature
+  #prompt:kc-fix "Fix login redirect bug"      — Quick fix
+  #prompt:kc-continue                          — Resume where you left off
+
+See knowzcode/copilot_execution.md for the full execution guide.
+```
+
+### 7.5. Enable Agent Teams (Claude Code only)
+
+If the user is on Claude Code, **actively offer** to enable Agent Teams:
+
+**Step 7.5a: Ask the user**
+```
+"Would you like to enable Agent Teams? (recommended for Claude Code)
+
+Agent Teams spawns specialized teammates for each workflow phase,
+giving you richer multi-agent coordination.
+
+Without it, KnowzCode uses subagent delegation (works fine, just less interactive)."
+
+Options:
+  - Yes, for this project only (recommended)
+  - Yes, for all projects (writes to ~/.claude/settings.json)
+  - No (use subagent fallback)
+```
+
+**Step 7.5b: If yes, create/update the appropriate settings file**
+
+- **"This project only"** → write to `.claude/settings.local.json` (project-level, gitignored)
+- **"All projects"** → write to `~/.claude/settings.json` (home-level global config)
+
+Read the target settings file if it exists. Merge the Agent Teams env var into it:
+
+```json
+{
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}
+```
+
+If the file already has other keys, preserve them and merge. If it doesn't exist, create it with the content above.
+
+**Step 7.5c: Windows note**
+
+If the platform is Windows (`process.platform === 'win32'` or detected via environment):
+```
+Note: On Windows, Agent Teams runs in "in-process" mode by default
+(split-pane tmux mode is not supported in Windows Terminal).
+This works correctly — no action needed.
+```
+
+**Step 7.5d: If no, proceed normally** — subagent delegation works without any configuration.
+
+### 8. Optional: Set up enterprise compliance (experimental)
+
+- Ask: "Would you like to set up enterprise compliance features? (optional)"
+- If yes: create `knowzcode/enterprise/` directory with manifest and templates
+- Compliance is disabled by default
+
+### 9. Optional: Configure MCP
+
+Inform user about enhanced features:
+```
+Optional: Connect to KnowzCode Cloud for AI-powered capabilities:
+  New user?     /kc:register
+  Have a key?   /kc:connect-mcp <api-key>
+```
+
+### 10. Report success
+
+```
+KnowzCode initialized successfully!
+
+Created:
+  knowzcode/knowzcode_project.md
+  knowzcode/knowzcode_tracker.md
+  knowzcode/knowzcode_log.md
+  knowzcode/knowzcode_architecture.md
+  knowzcode/knowzcode_loop.md
+  knowzcode/knowzcode_orchestration.md
+  knowzcode/platform_adapters.md
+  knowzcode/.gitignore
+  knowzcode/specs/
+  knowzcode/workgroups/
+  knowzcode/prompts/
+
+Platform adapters: [list generated adapters or "None (skip)"]
+
+Agent Teams: [Enabled (.claude/settings.local.json) | Not enabled (subagent fallback)]
+
+Next steps:
+  1. Review knowzcode/knowzcode_project.md and add project details
+  2. Start your first feature: /kc:work "your feature description"
+  3. Research first: /kc:plan "your question"
+```
+
+---
+
+## Template Files
+
+### knowzcode_project.md
+```markdown
+# KnowzCode Project Overview
+
+**Purpose:** Project context for KnowzCode AI agents.
+
+### 1. Project Goal & Core Problem
+*   **Goal:** [To be filled in during first session]
+*   **Core Problem Solved:** [To be filled in during first session]
+
+### 2. Scope & Key Features
+*   **Key Features (In Scope):**
+    *   [Feature 1]: [Description]
+*   **Out of Scope:**
+    *   [Deferred 1]: [Description]
+
+### 3. Technology Stack
+| Category | Technology | Version | Notes |
+|:---------|:-----------|:--------|:------|
+| Language(s) | [Detected] | [Detected] | [Auto-detected] |
+| Testing | [Detected] | [Detected] | [Auto-detected] |
+
+### Links to Other Artifacts
+* **Loop Protocol:** `knowzcode/knowzcode_loop.md`
+* **Session Log:** `knowzcode/knowzcode_log.md`
+* **Architecture:** `knowzcode/knowzcode_architecture.md`
+* **Tracker:** `knowzcode/knowzcode_tracker.md`
+* **Specifications:** `knowzcode/specs/`
+```
+
+### knowzcode_tracker.md
+```markdown
+# KnowzCode Status Map (WorkGroup Tracker)
+
+**Purpose:** Tracks all active and completed WorkGroups.
+
+## Active WorkGroups
+
+*None yet. Run `/kc:work "your feature description"` to create your first WorkGroup.*
+
+## Completed WorkGroups
+
+*None yet.*
+
+**Next WorkGroup ID:** WG-001
+```
+
+### knowzcode_log.md
+```markdown
+# KnowzCode Operational Record
+
+**Purpose:** Session log and quality criteria reference.
+
+## Recent Sessions
+
+*No sessions yet.*
+
+## Reference Quality Criteria
+
+1. **Reliability:** Robust error handling, graceful degradation
+2. **Maintainability:** Clear code structure, good naming, modularity
+3. **Security:** Input validation, secure authentication, data protection
+4. **Performance:** Efficient algorithms, optimized queries
+5. **Testability:** Comprehensive test coverage, clear test cases
+```
+
+### knowzcode_architecture.md
+```markdown
+# KnowzCode Architecture Documentation
+
+**Purpose:** Living architecture documentation for this project.
+
+## System Architecture
+
+*To be populated during first feature development.*
+
+## Key Components
+
+*To be populated during implementation.*
+
+## Data Flow
+
+*To be populated during implementation.*
+```
+
+### environment_context.md
+```markdown
+# KnowzCode Environment Context
+
+**Purpose:** Environment and tooling information.
+
+## Detected Environment
+
+**Platform:** [Auto-detected]
+**Language:** [Auto-detected]
+**Package Manager:** [Auto-detected]
+**Test Runner:** [Auto-detected]
+```
+
+### knowzcode_orchestration.md
+```markdown
+# KnowzCode Orchestration Configuration
+
+**Purpose:** Project-level defaults for team sizing and agent orchestration. Read by `/kc:work` and `/kc:audit` at startup. Per-invocation flags override these settings.
+
+---
+
+## Builder Configuration
+
+```yaml
+max_builders: 5
+```
+
+---
+
+## Scout Configuration
+
+```yaml
+scout_mode: full
+```
+
+---
+
+## Specialist Defaults
+
+```yaml
+default_specialists: []
+```
+
+---
+
+## MCP Agent Configuration
+
+```yaml
+mcp_agents_enabled: true
+```
+
+---
+
+## Override Precedence
+
+| Setting | Config Default | Flag Override |
+|---------|---------------|--------------|
+| max_builders | `max_builders:` | `--max-builders=N` |
+| scout_mode | `scout_mode:` | `--no-scouts` |
+| default_specialists | `default_specialists:` | `--specialists`, `--no-specialists` |
+| mcp_agents_enabled | `mcp_agents_enabled:` | `--no-mcp` |
+
+Per-invocation flags always win. `--specialists` adds to defaults; `--no-specialists` clears all.
+```
+
+---
+
+## Error Handling
+
+If initialization fails:
+1. Report which step failed
+2. Show partial progress
+3. Suggest remediation
+4. Offer to clean up
+
+Execute this initialization now.