knowzcode 0.4.0 → 0.6.0

package/knowzcode/prompts/[LOOP_2A]__Implement_Change_Set.md

@@ -1,55 +1,55 @@
-# KnowzCode: [LOOP 2A] Authorize Implementation
-
-**WorkGroupID for Implementation:**
-[Orchestrator: Re-state the `WorkGroupID` that you have reviewed and are now approving for implementation. This confirms all associated specs are approved.]
-
-> **Automation Path:** Use `/kc-step phase=2A workgroup_id=<ID>` to activate the `builder` subagent. The command enforces the `environment-guard` skill and writes back tracker updates once the loop instructions are complete.
-
-**Remember:**
-- Cross-check code updates against the latest specs and refresh them if implementation diverges.
-- Record in-progress work and emerging tasks in `knowzcode/workgroups/<WorkGroupID>.md`, keeping every todo prefixed with `KnowzCode:`.
-
-**WorkGroupID:** `[wip-timestamp-to-implement]`
-
----
-
-## Your Mission
-You are authorized to begin the core development phase for the specified `WorkGroupID`. All associated specifications are approved.
-
-Your task is to autonomously execute the planning, committing, implementation, and initial verification cycle. Your work on this prompt begins at **Step 4** of the `knowzcode_loop.md` and is considered complete only after **Step 6A** has passed successfully.
-
-**NOTE:** Your implementation will be independently audited for completeness in Loop 2B after you report success here.
-
-**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the sequence from **Step 4 (ARC-Principle-Based Planning)** through to the completion of **Step 6A (Implementation & Initial Verification)**.
-
----
-
-### Execution Protocol
-
-1.  **Plan & Commit (Step 4):**
-    *   Develop your internal implementation plan for the entire Change Set.
-    *   **CRITICAL CHECKPOINT:** After developing your plan, evaluate its complexity. If the plan is exceptionally complex or high-risk, you **MUST PAUSE** now and present the plan for Orchestrator review as per Step 4.2 of the loop. If the plan is straightforward, proceed.
-    *   Perform the **Pre-Implementation Commit** as per Step 4.3.
-
-2.  **Implement (Step 5):**
-    *   Execute your plan, creating and modifying all necessary code to fulfill the specs for the *entire* Change Set.
-
-3.  **Verify (Step 6A):**
-    *   Conduct a full initial verification of the *entire* Change Set, following the iterative "fix and re-verify" cycle as detailed in `knowzcode_loop.md`.
-
-### Reporting
-
-*   **On Success:** Once the entire Change Set has passed all verification steps defined in Step 6A, report your success and readiness for the audit.
-    *   **Success Report:**
-    > "Implementation and Initial Verification for `WorkGroupID: [ID]` (Steps 4-6A) is complete. All code has been written, and all self-conducted tests and ARC criteria have passed. The Change Set is now ready for the Loop 2B Implementation Completeness Audit. Awaiting the `[LOOP_2B]__Verify_Implementation.md` command."
-
-*   **On Blocker:** If you pause at the planning checkpoint, or encounter an unresolvable issue, report the specific blocker.
-    *   **Blocker Report:**
-    > "Execution paused for `WorkGroupID: [ID]`. [Clearly describe the blocker...]"
-
-### Final State & Next Prompt
-
-*   Upon successful completion, you will **PAUSE**.
-*   The next command from the Orchestrator for this `WorkGroupID` will be **`[LOOP_2B]__Verify_Implementation.md`**.
-
----
+# KnowzCode: [LOOP 2A] Authorize Implementation
+
+**WorkGroupID for Implementation:**
+[Orchestrator: Re-state the `WorkGroupID` that you have reviewed and are now approving for implementation. This confirms all associated specs are approved.]
+
+> **Automation Path:** Use `/kc-step phase=2A workgroup_id=<ID>` to activate the `builder` subagent. The command enforces the `environment-guard` skill and writes back tracker updates once the loop instructions are complete.
+
+**Remember:**
+- Cross-check code updates against the latest specs and refresh them if implementation diverges.
+- Record in-progress work and emerging tasks in `knowzcode/workgroups/<WorkGroupID>.md`, keeping every todo prefixed with `KnowzCode:`.
+
+**WorkGroupID:** `[wip-timestamp-to-implement]`
+
+---
+
+## Your Mission
+You are authorized to begin the core development phase for the specified `WorkGroupID`. All associated specifications are approved.
+
+Your task is to autonomously execute the planning, committing, implementation, and initial verification cycle. Your work on this prompt begins at **Step 4** of the `knowzcode_loop.md` and is considered complete only after **Step 6A** has passed successfully.
+
+**NOTE:** Your implementation will be independently audited for completeness in Loop 2B after you report success here.
+
+**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the sequence from **Step 4 (ARC-Principle-Based Planning)** through to the completion of **Step 6A (Implementation & Initial Verification)**.
+
+---
+
+### Execution Protocol
+
+1.  **Plan & Commit (Step 4):**
+    *   Develop your internal implementation plan for the entire Change Set.
+    *   **CRITICAL CHECKPOINT:** After developing your plan, evaluate its complexity. If the plan is exceptionally complex or high-risk, you **MUST PAUSE** now and present the plan for Orchestrator review as per Step 4.2 of the loop. If the plan is straightforward, proceed.
+    *   Perform the **Pre-Implementation Commit** as per Step 4.3.
+
+2.  **Implement (Step 5):**
+    *   Execute your plan, creating and modifying all necessary code to fulfill the specs for the *entire* Change Set.
+
+3.  **Verify (Step 6A):**
+    *   Conduct a full initial verification of the *entire* Change Set, following the iterative "fix and re-verify" cycle as detailed in `knowzcode_loop.md`.
+
+### Reporting
+
+*   **On Success:** Once the entire Change Set has passed all verification steps defined in Step 6A, report your success and readiness for the audit.
+    *   **Success Report:**
+    > "Implementation and Initial Verification for `WorkGroupID: [ID]` (Steps 4-6A) is complete. All code has been written, and all self-conducted tests and ARC criteria have passed. The Change Set is now ready for the Loop 2B Implementation Completeness Audit. Awaiting the `[LOOP_2B]__Verify_Implementation.md` command."
+
+*   **On Blocker:** If you pause at the planning checkpoint, or encounter an unresolvable issue, report the specific blocker.
+    *   **Blocker Report:**
+    > "Execution paused for `WorkGroupID: [ID]`. [Clearly describe the blocker...]"
+
+### Final State & Next Prompt
+
+*   Upon successful completion, you will **PAUSE**.
+*   The next command from the Orchestrator for this `WorkGroupID` will be **`[LOOP_2B]__Verify_Implementation.md`**.
+
+---

package/knowzcode/prompts/[LOOP_2B]__Verify_Implementation.md

@@ -1,72 +1,72 @@
-# KnowzCode: [LOOP 2B] Verify Implementation Completeness
-
-**WorkGroupID for Audit:**
-[Orchestrator: Re-state the `WorkGroupID` that has completed Loop 2A and requires an implementation audit.]
-
-> **Automation Path:** Trigger `/kc-step phase=2B workgroup_id=<ID>` or `/kc-audit audit=implementation workgroup_id=<ID>` to run the `reviewer` subagent in read-only mode. It utilizes `spec-quality-check`, `tracker-scan`, and `log-entry-builder` skills to compute the completion percentage.
-
-**Remember:**
-- Flag any spec discrepancies you uncover and update the relevant files in `knowzcode/specs/`.
-- Add follow-up todos to `knowzcode/workgroups/<WorkGroupID>.md` (each entry prefixed `KnowzCode:`) so unresolved work is obvious.
-
-**WorkGroupID:** `[wip-timestamp-to-audit]`
-
----
-
-## Your Mission
-This is a **READ-ONLY** quality gate to audit the completeness of the implementation for the given `WorkGroupID`. You will compare the work done against the approved specifications and report an objective completion percentage.
-
-**CRITICAL RULE: You MUST NOT modify any files. This is a verification step, not a correction step.**
-
-**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the audit defined in **Step 6B**.
-
----
-
-### Execution Protocol
-
-#### Phase 0: Reconnaissance (READ-ONLY)
-1.  **Identify Audit Scope:** Get all `NodeID`s associated with the `WorkGroupID` from `knowzcode_tracker.md`.
-2.  **List Artifacts:** List all source code files that were created or modified for this `WorkGroupID`.
-3.  **Map Built Features:** Briefly map what was built (e.g., components, functions, features, tests).
-
-#### Phase 1: Specification-to-Code Audit
-1.  **Load Specs:** For each `NodeID` in your scope, load its approved specification from `specs/`.
-2.  **Verify Spec-to-Code:** For each spec, systematically verify that every requirement, function, and error handling case listed in the spec has been implemented in the code.
-3.  **Verify Code-to-Spec:** Check for any "orphan" code—features or functions that were implemented but are not described in any specification.
-4.  **Calculate Completion:** Based on your findings, calculate an objective, quantitative **completion percentage**. (e.g., "8 of 10 requirements implemented = 80% complete").
-
-#### Phase 2: Synthesize Findings & Report
-*   Compile a single, comprehensive audit report.
-
-### Audit Report Structure
-
-Your report **must** include the following sections:
-> **WorkGroupID:** `[ID]`
-> **Overall Implementation Completion:** [Calculated Percentage]%
->
-> **1. Fully Implemented Requirements:**
-> *   [List of spec requirements that are 100% complete]
->
-> **2. Partially Implemented Requirements:**
-> *   [Requirement X]: Implemented basic case, but missing error handling for [condition].
-> *   [Requirement Y]: Feature exists, but is missing [specific part].
->
-> **3. Not Implemented Requirements:**
-> *   [List of spec requirements that were not implemented at all]
->
-> **4. Orphan Code (Not in Specs):**
-> *   [Function `calculate_extra_value()` in `file.py` has no corresponding spec requirement.]
->
-> **5. Risk Assessment:**
-> *   [Brief assessment of the risk of proceeding with the current implementation state. e.g., "Low risk, missing features are non-critical." or "High risk, core security function is incomplete."]
->
-> **Awaiting Orchestrator decision.**
-
-### Orchestrator Decision Points
-Based on your report, the Orchestrator will choose one of the following paths:
-*   **(A) Complete Gaps:** Return to implementation (Step 5) to address the identified gaps.
-*   **(B) Accept & Proceed:** Accept the current implementation as-is and proceed to Loop 3 for finalization.
-*   **(C) Modify Specs:** Update the specifications to match the "as-built" code, formally accepting the deviations.
-*   **(D) Cancel:** Cancel the WorkGroupID and potentially revert the changes.
-
----
+# KnowzCode: [LOOP 2B] Verify Implementation Completeness
+
+**WorkGroupID for Audit:**
+[Orchestrator: Re-state the `WorkGroupID` that has completed Loop 2A and requires an implementation audit.]
+
+> **Automation Path:** Trigger `/kc-step phase=2B workgroup_id=<ID>` or `/kc-audit audit=implementation workgroup_id=<ID>` to run the `reviewer` subagent in read-only mode. It utilizes `spec-quality-check`, `tracker-scan`, and `log-entry-builder` skills to compute the completion percentage.
+
+**Remember:**
+- Flag any spec discrepancies you uncover and update the relevant files in `knowzcode/specs/`.
+- Add follow-up todos to `knowzcode/workgroups/<WorkGroupID>.md` (each entry prefixed `KnowzCode:`) so unresolved work is obvious.
+
+**WorkGroupID:** `[wip-timestamp-to-audit]`
+
+---
+
+## Your Mission
+This is a **READ-ONLY** quality gate to audit the completeness of the implementation for the given `WorkGroupID`. You will compare the work done against the approved specifications and report an objective completion percentage.
+
+**CRITICAL RULE: You MUST NOT modify any files. This is a verification step, not a correction step.**
+
+**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the audit defined in **Step 6B**.
+
+---
+
+### Execution Protocol
+
+#### Phase 0: Reconnaissance (READ-ONLY)
+1.  **Identify Audit Scope:** Get all `NodeID`s associated with the `WorkGroupID` from `knowzcode_tracker.md`.
+2.  **List Artifacts:** List all source code files that were created or modified for this `WorkGroupID`.
+3.  **Map Built Features:** Briefly map what was built (e.g., components, functions, features, tests).
+
+#### Phase 1: Specification-to-Code Audit
+1.  **Load Specs:** For each `NodeID` in your scope, load its approved specification from `specs/`.
+2.  **Verify Spec-to-Code:** For each spec, systematically verify that every requirement, function, and error handling case listed in the spec has been implemented in the code.
+3.  **Verify Code-to-Spec:** Check for any "orphan" code—features or functions that were implemented but are not described in any specification.
+4.  **Calculate Completion:** Based on your findings, calculate an objective, quantitative **completion percentage**. (e.g., "8 of 10 requirements implemented = 80% complete").
+
+#### Phase 2: Synthesize Findings & Report
+*   Compile a single, comprehensive audit report.
+
+### Audit Report Structure
+
+Your report **must** include the following sections:
+> **WorkGroupID:** `[ID]`
+> **Overall Implementation Completion:** [Calculated Percentage]%
+>
+> **1. Fully Implemented Requirements:**
+> *   [List of spec requirements that are 100% complete]
+>
+> **2. Partially Implemented Requirements:**
+> *   [Requirement X]: Implemented basic case, but missing error handling for [condition].
+> *   [Requirement Y]: Feature exists, but is missing [specific part].
+>
+> **3. Not Implemented Requirements:**
+> *   [List of spec requirements that were not implemented at all]
+>
+> **4. Orphan Code (Not in Specs):**
+> *   [Function `calculate_extra_value()` in `file.py` has no corresponding spec requirement.]
+>
+> **5. Risk Assessment:**
+> *   [Brief assessment of the risk of proceeding with the current implementation state. e.g., "Low risk, missing features are non-critical." or "High risk, core security function is incomplete."]
+>
+> **Awaiting Orchestrator decision.**
+
+### Orchestrator Decision Points
+Based on your report, the Orchestrator will choose one of the following paths:
+*   **(A) Complete Gaps:** Return to implementation (Step 5) to address the identified gaps.
+*   **(B) Accept & Proceed:** Accept the current implementation as-is and proceed to Loop 3 for finalization.
+*   **(C) Modify Specs:** Update the specifications to match the "as-built" code, formally accepting the deviations.
+*   **(D) Cancel:** Cancel the WorkGroupID and potentially revert the changes.
+
+---

package/knowzcode/prompts/[LOOP_3]__Finalize_And_Commit.md

@@ -1,67 +1,67 @@
-# KnowzCode: [LOOP 3] Finalize & Commit Change Set
-
-**WorkGroupID for Finalization:**
-[Orchestrator: Re-state the `WorkGroupID` that has passed implementation and verification, authorizing its finalization and commit.]
-
-> **Automation Path:** Execute `/kc-step phase=3 workgroup_id=<ID>` to hand off to the `closer` subagent. It chains `tracker-update`, `log-entry-builder`, and `architecture-diff` skills to wrap up the loop.
-
-**Remember:**
-- Finalize every spec in `knowzcode/specs/` to reflect the as-built system.
-- Close or add remaining todos in `knowzcode/workgroups/<WorkGroupID>.md`, ensuring all entries keep the `KnowzCode:` prefix.
-
-**WorkGroupID:** `[wip-timestamp-to-finalize]`
-
----
-
-## Your Mission
-The implementation and verification for the specified `WorkGroupID` is complete. You are now authorized to execute the final phase of the KnowzCode loop: documentation, logging, and committing.
-
-**CRITICAL RULE: The implementation phase is complete. Your work in this phase is strictly limited to updating KnowzCode's own project and specification files (`.md` files) to reflect the finished work. You MUST NOT write or modify any more application source code (e.g., `.js`, `.py`, `.html` files).**
-
-**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the sequence from **Step 7 through Step 10**.
-
----
-
-### Execution Protocol
-
-1.  **Finalize Specifications (Step 7):**
-    *   For **each** `NodeID` in the `WorkGroupID`, update its spec file in `specs/` to the "as-built" state, ensuring it perfectly reflects the verified code.
-
-2.  **Check Architecture (Step 8):**
-    *   Conduct the Flowchart Consistency Check. If you find a simple discrepancy, fix `knowzcode_architecture.md` directly. If it's complex, document it in the log.
-
-3.  **Log Operation (Step 9):**
-    *   Create the single, comprehensive `ARC-Completion` log entry in `knowzcode_log.md`. Ensure it includes the flowchart check outcome, any unforeseen ripple effects, and project overview updates. Use an environment-sourced timestamp.
-
-4.  **Update Tracker, Schedule Debt, & Check Project Overview (Step 10):**
-    *   **Update Tracker:** In `knowzcode_tracker.md`, mark all nodes in the `WorkGroupID` as `[VERIFIED]` and clear their `WorkGroupID`.
-    *   **Schedule Debt:** Perform the "Technical Debt Scheduling" step. For any nodes with documented debt, create new `REFACTOR_` tasks in the tracker.
-    *   **Update Project Overview:** Check if this Change Set impacts `knowzcode_project.md`:
-        - New major features → Update "Key Features" section
-        - New libraries/tools → Update "Technology Stack" table
-        - Architecture changes → Update "Architecture Decisions"
-        - Scope expansion → Update "Scope & Key Features"
-    *   **Final Commit:** Stage ALL changes using `git add -A` (this includes source code from implementation AND knowzcode/ files), then commit with a descriptive `feat:` message.
-
-### Final Report
-
-*   Once all steps above are complete, provide a final confirmation report.
-
-**Example Response Format:**
-> "Finalization for `WorkGroupID: [ID]` is complete.
->
-> *   All specifications have been updated to the 'as-built' state.
-> *   The architecture flowchart has been checked and updated.
-> *   A complete `ARC-Completion` entry has been logged.
-> *   The tracker is updated, and all nodes are now `[VERIFIED]`.
-> *   **Project Overview Updates:** [None | Updated sections: Technology Stack, Key Features]
-> *   The final `feat:` commit has been made to version control.
-> *   **New Refactor Tasks Created:** [List any REFACTOR_ nodes created, or 'None'].
->
-> This Change Set is now fully complete and documented. Awaiting next `PrimaryGoal` via a new Work Session."
-
-### Final State
-
-*   Upon successful completion, the KnowzCode loop for this `WorkGroupID` is **finished**. You will return to an idle state.
-
----
+# KnowzCode: [LOOP 3] Finalize & Commit Change Set
+
+**WorkGroupID for Finalization:**
+[Orchestrator: Re-state the `WorkGroupID` that has passed implementation and verification, authorizing its finalization and commit.]
+
+> **Automation Path:** Execute `/kc-step phase=3 workgroup_id=<ID>` to hand off to the `closer` subagent. It chains `tracker-update`, `log-entry-builder`, and `architecture-diff` skills to wrap up the loop.
+
+**Remember:**
+- Finalize every spec in `knowzcode/specs/` to reflect the as-built system.
+- Close or add remaining todos in `knowzcode/workgroups/<WorkGroupID>.md`, ensuring all entries keep the `KnowzCode:` prefix.
+
+**WorkGroupID:** `[wip-timestamp-to-finalize]`
+
+---
+
+## Your Mission
+The implementation and verification for the specified `WorkGroupID` is complete. You are now authorized to execute the final phase of the KnowzCode loop: documentation, logging, and committing.
+
+**CRITICAL RULE: The implementation phase is complete. Your work in this phase is strictly limited to updating KnowzCode's own project and specification files (`.md` files) to reflect the finished work. You MUST NOT write or modify any more application source code (e.g., `.js`, `.py`, `.html` files).**
+
+**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the sequence from **Step 7 through Step 10**.
+
+---
+
+### Execution Protocol
+
+1.  **Finalize Specifications (Step 7):**
+    *   For **each** `NodeID` in the `WorkGroupID`, update its spec file in `specs/` to the "as-built" state, ensuring it perfectly reflects the verified code.
+
+2.  **Check Architecture (Step 8):**
+    *   Conduct the Flowchart Consistency Check. If you find a simple discrepancy, fix `knowzcode_architecture.md` directly. If it's complex, document it in the log.
+
+3.  **Log Operation (Step 9):**
+    *   Create the single, comprehensive `ARC-Completion` log entry in `knowzcode_log.md`. Ensure it includes the flowchart check outcome, any unforeseen ripple effects, and project overview updates. Use an environment-sourced timestamp.
+
+4.  **Update Tracker, Schedule Debt, & Check Project Overview (Step 10):**
+    *   **Update Tracker:** In `knowzcode_tracker.md`, mark all nodes in the `WorkGroupID` as `[VERIFIED]` and clear their `WorkGroupID`.
+    *   **Schedule Debt:** Perform the "Technical Debt Scheduling" step. For any nodes with documented debt, create new `REFACTOR_` tasks in the tracker.
+    *   **Update Project Overview:** Check if this Change Set impacts `knowzcode_project.md`:
+        - New major features → Update "Key Features" section
+        - New libraries/tools → Update "Technology Stack" table
+        - Architecture changes → Update "Architecture Decisions"
+        - Scope expansion → Update "Scope & Key Features"
+    *   **Final Commit:** Stage ALL changes using `git add -A` (this includes source code from implementation AND knowzcode/ files), then commit with a descriptive `feat:` message.
+
+### Final Report
+
+*   Once all steps above are complete, provide a final confirmation report.
+
+**Example Response Format:**
+> "Finalization for `WorkGroupID: [ID]` is complete.
+>
+> *   All specifications have been updated to the 'as-built' state.
+> *   The architecture flowchart has been checked and updated.
+> *   A complete `ARC-Completion` entry has been logged.
+> *   The tracker is updated, and all nodes are now `[VERIFIED]`.
+> *   **Project Overview Updates:** [None | Updated sections: Technology Stack, Key Features]
+> *   The final `feat:` commit has been made to version control.
+> *   **New Refactor Tasks Created:** [List any REFACTOR_ nodes created, or 'None'].
+>
+> This Change Set is now fully complete and documented. Awaiting next `PrimaryGoal` via a new Work Session."
+
+### Final State
+
+*   Upon successful completion, the KnowzCode loop for this `WorkGroupID` is **finished**. You will return to an idle state.
+
+---

package/knowzcode/specs/Readme.md

@@ -1,10 +1,10 @@
-\# Component Specifications
-
-
-
-This directory will contain specification files for each component (NodeID) in your project.
-
-
-
-Files will be named like: `API\_UserAuth.md`, `UI\_Dashboard.md`, etc.
-
+\# Component Specifications
+
+
+
+This directory will contain specification files for each component (NodeID) in your project.
+
+
+
+Files will be named like: `API\_UserAuth.md`, `UI\_Dashboard.md`, etc.
+

package/knowzcode/telemetry_config.md

@@ -1,89 +1,89 @@
-# Telemetry Configuration
-
-> **This file configures telemetry sources for `/kc:telemetry` investigations.**
->
-> Run `/kc:telemetry-setup` to auto-discover and configure sources.
-
----
-
-## Sentry
-
-| Field | Value |
-|-------|-------|
-| Enabled | false |
-| Method | |
-| Organization | |
-
-### Environment Mapping
-
-| Environment | Project |
-|-------------|---------|
-| production | |
-| staging | |
-| dev | |
-
----
-
-## Azure Application Insights
-
-| Field | Value |
-|-------|-------|
-| Enabled | false |
-| Subscription | |
-| Resource Group | |
-
-### Environment Mapping
-
-| Environment | App Name | App ID |
-|-------------|----------|--------|
-| production | | |
-| staging | | |
-| dev | | |
-
----
-
-## Configuration Notes
-
-- **Sentry Method**: How to connect to Sentry (`cli` for Sentry CLI, `mcp` for MCP tools)
-- **Sentry Organization**: Your Sentry organization slug (e.g., `my-company`)
-- **Sentry Project**: Format is `org-slug/project-slug` (e.g., `my-company/backend-api`)
-- **App Insights App ID**: The Application ID from Azure portal (GUID format)
-- **Subscription**: Your Azure subscription ID (optional, uses default if not set)
-
-### Auto-Discovery
-
-Run `/kc:telemetry-setup` to:
-1. Detect installed telemetry tools (sentry-cli, az CLI)
-2. Verify authentication status
-3. Auto-discover available resources
-4. Interactively configure environment mappings
-5. Update this file with discovered values
-
-### Manual Configuration
-
-Edit the tables above directly to configure telemetry sources:
-
-```markdown
-## Sentry
-
-| Field | Value |
-|-------|-------|
-| Enabled | true |
-| Method | cli |
-| Organization | my-company |
-
-### Environment Mapping
-
-| Environment | Project |
-|-------------|---------|
-| production | my-company/backend-prod |
-| staging | my-company/backend-staging |
-| dev | my-company/backend-dev |
-```
-
----
-
-## Last Updated
-
-- **Date**: (not configured)
-- **By**: (not configured)
+# Telemetry Configuration
+
+> **This file configures telemetry sources for `/kc:telemetry` investigations.**
+>
+> Run `/kc:telemetry-setup` to auto-discover and configure sources.
+
+---
+
+## Sentry
+
+| Field | Value |
+|-------|-------|
+| Enabled | false |
+| Method | |
+| Organization | |
+
+### Environment Mapping
+
+| Environment | Project |
+|-------------|---------|
+| production | |
+| staging | |
+| dev | |
+
+---
+
+## Azure Application Insights
+
+| Field | Value |
+|-------|-------|
+| Enabled | false |
+| Subscription | |
+| Resource Group | |
+
+### Environment Mapping
+
+| Environment | App Name | App ID |
+|-------------|----------|--------|
+| production | | |
+| staging | | |
+| dev | | |
+
+---
+
+## Configuration Notes
+
+- **Sentry Method**: How to connect to Sentry (`cli` for Sentry CLI, `mcp` for MCP tools)
+- **Sentry Organization**: Your Sentry organization slug (e.g., `my-company`)
+- **Sentry Project**: Format is `org-slug/project-slug` (e.g., `my-company/backend-api`)
+- **App Insights App ID**: The Application ID from Azure portal (GUID format)
+- **Subscription**: Your Azure subscription ID (optional, uses default if not set)
+
+### Auto-Discovery
+
+Run `/kc:telemetry-setup` to:
+1. Detect installed telemetry tools (sentry-cli, az CLI)
+2. Verify authentication status
+3. Auto-discover available resources
+4. Interactively configure environment mappings
+5. Update this file with discovered values
+
+### Manual Configuration
+
+Edit the tables above directly to configure telemetry sources:
+
+```markdown
+## Sentry
+
+| Field | Value |
+|-------|-------|
+| Enabled | true |
+| Method | cli |
+| Organization | my-company |
+
+### Environment Mapping
+
+| Environment | Project |
+|-------------|---------|
+| production | my-company/backend-prod |
+| staging | my-company/backend-staging |
+| dev | my-company/backend-dev |
+```
+
+---
+
+## Last Updated
+
+- **Date**: (not configured)
+- **By**: (not configured)