knowzcode 0.3.7 → 0.4.0

package/knowzcode/prompts/Refactor_Node.md

@@ -1,72 +1,72 @@
-# KnowzCode: Refactor Node
-
-**Target NodeID:** [The NodeID to be refactored, e.g., `API_UserSearch`]
-**Refactoring Goal:** [The specific goal, e.g., "Improve performance by optimizing database queries"]
-
-> **Automation Path:** Begin with `/kc-step phase=1A` targeting the `REFACTOR_<NodeID>` tracker entry to scope the Change Set before executing this prompt.
-
----
-
-## Your Mission
-You have been assigned a technical debt task to refactor the specified `TargetNodeID`. Your goal is to improve the internal quality of the code (e.g., performance, readability, simplicity) **without changing its external behavior or interfaces.**
-
-**CRITICAL RULE: The functional contract of the node, as defined by its existing Verification Criteria, MUST NOT change. All existing tests and verification criteria must still pass after the refactoring is complete.**
-
----
-
-### Pre-Flight Check
-Before proceeding, confirm the following:
-*   The `TargetNodeID` is in a stable, `[VERIFIED]` state in `knowzcode/knowzcode_tracker.md`.
-*   The goal is purely internal improvement, not adding features or fixing functional bugs. If this is not the case, **STOP** and inform the Orchestrator that a different protocol is required.
-
----
-
-### Refactoring Protocol
-
-#### Phase 1: Planning & Setup
-1.  **Initiate Work:**
-    *   In `knowzcode/knowzcode_tracker.md`, find the row for the `TargetNodeID`. Change its `Status` from `[VERIFIED]` to `[WIP]` and assign a new, unique `WorkGroupID` (e.g., `refactor-<timestamp>`).
-2.  **Review & Plan:**
-    *   Thoroughly review the existing code for the `TargetNodeID`.
-    *   Review its spec at `knowzcode/specs/[TargetNodeID].md`, paying close attention to the `VERIFY:` statements in the Verification Criteria section. These are your success metrics.
-    *   Develop a clear internal plan for the refactoring.
-
-#### Phase 2: Implementation & Verification
-1.  **Execute Refactoring:**
-    *   Incrementally apply your planned improvements to the code.
-    *   Ensure all existing functionality is preserved.
-2.  **Full Verification:**
-    *   After refactoring, conduct a **full verification** against the *existing* `knowzcode/specs/[TargetNodeID].md`.
-    *   All original `VERIFY:` statements from the Verification Criteria section **must** pass. This proves there have been no functional regressions.
-    *   Run all associated unit and integration tests.
-    *   Iterate on your refactoring until the code is improved AND all verification checks pass.
-
-#### Phase 3: Documentation & Final Commit
-1.  **Update Specification (If Necessary):**
-    *   If the internal "Core Logic" was significantly changed (e.g., a different algorithm is now used), update that section of the spec to reflect the new, cleaner approach.
-    *   **Do not change the Interfaces or Verification Criteria sections.**
-2.  **Log Operation:**
-    *   Prepend a `RefactorCompletion` entry to `knowzcode/knowzcode_log.md`. The entry **MUST** use the following format and an environment-sourced timestamp:
-        ```markdown
-        ---
-        **Type:** RefactorCompletion
-        **Timestamp:** [Generated Timestamp]
-        **WorkGroupID:** [The WorkGroupID for this refactor]
-        **NodeID(s):** [TargetNodeID]
-        **Logged By:** AI-Agent
-        **Details:**
-        - **Goal:** [Original refactoring goal].
-        - **Summary of Improvements:** [List of specific improvements made, e.g., "Replaced N+1 query with a single JOIN", "Extracted duplicated logic into a helper function"].
-        - **Verification:** Confirmed that all original Verification Criteria for the node still pass, ensuring no functional regressions.
-        ---
-        ```
-3.  **Update Tracker & Finalize:**
-    *   In `knowzcode/knowzcode_tracker.md`:
-        *   Find the row for `TargetNodeID`, change its `Status` back to `[VERIFIED]`, and clear its `WorkGroupID`.
-        *   If a `REFACTOR_[TargetNodeID]` task exists, **delete that entire row** from the tracker.
-4.  **Final Commit:**
-    *   Commit all changes (code, spec updates, log, tracker) with a descriptive `refactor:` message (e.g., `refactor(API_UserSearch): Optimize query performance`).
-
-### Final Report
-*   Once all steps are complete, provide a concise confirmation report.
-> "✓ Refactoring of `[TargetNodeID]` is complete. The technical debt task has been resolved, logged, and committed. The tracker has been updated."
+# KnowzCode: Refactor Node
+
+**Target NodeID:** [The NodeID to be refactored, e.g., `API_UserSearch`]
+**Refactoring Goal:** [The specific goal, e.g., "Improve performance by optimizing database queries"]
+
+> **Automation Path:** Begin with `/kc-step phase=1A` targeting the `REFACTOR_<NodeID>` tracker entry to scope the Change Set before executing this prompt.
+
+---
+
+## Your Mission
+You have been assigned a technical debt task to refactor the specified `TargetNodeID`. Your goal is to improve the internal quality of the code (e.g., performance, readability, simplicity) **without changing its external behavior or interfaces.**
+
+**CRITICAL RULE: The functional contract of the node, as defined by its existing Verification Criteria, MUST NOT change. All existing tests and verification criteria must still pass after the refactoring is complete.**
+
+---
+
+### Pre-Flight Check
+Before proceeding, confirm the following:
+*   The `TargetNodeID` is in a stable, `[VERIFIED]` state in `knowzcode/knowzcode_tracker.md`.
+*   The goal is purely internal improvement, not adding features or fixing functional bugs. If this is not the case, **STOP** and inform the Orchestrator that a different protocol is required.
+
+---
+
+### Refactoring Protocol
+
+#### Phase 1: Planning & Setup
+1.  **Initiate Work:**
+    *   In `knowzcode/knowzcode_tracker.md`, find the row for the `TargetNodeID`. Change its `Status` from `[VERIFIED]` to `[WIP]` and assign a new, unique `WorkGroupID` (e.g., `refactor-<timestamp>`).
+2.  **Review & Plan:**
+    *   Thoroughly review the existing code for the `TargetNodeID`.
+    *   Review its spec at `knowzcode/specs/[TargetNodeID].md`, paying close attention to the `VERIFY:` statements in the Verification Criteria section. These are your success metrics.
+    *   Develop a clear internal plan for the refactoring.
+
+#### Phase 2: Implementation & Verification
+1.  **Execute Refactoring:**
+    *   Incrementally apply your planned improvements to the code.
+    *   Ensure all existing functionality is preserved.
+2.  **Full Verification:**
+    *   After refactoring, conduct a **full verification** against the *existing* `knowzcode/specs/[TargetNodeID].md`.
+    *   All original `VERIFY:` statements from the Verification Criteria section **must** pass. This proves there have been no functional regressions.
+    *   Run all associated unit and integration tests.
+    *   Iterate on your refactoring until the code is improved AND all verification checks pass.
+
+#### Phase 3: Documentation & Final Commit
+1.  **Update Specification (If Necessary):**
+    *   If the internal "Core Logic" was significantly changed (e.g., a different algorithm is now used), update that section of the spec to reflect the new, cleaner approach.
+    *   **Do not change the Interfaces or Verification Criteria sections.**
+2.  **Log Operation:**
+    *   Prepend a `RefactorCompletion` entry to `knowzcode/knowzcode_log.md`. The entry **MUST** use the following format and an environment-sourced timestamp:
+        ```markdown
+        ---
+        **Type:** RefactorCompletion
+        **Timestamp:** [Generated Timestamp]
+        **WorkGroupID:** [The WorkGroupID for this refactor]
+        **NodeID(s):** [TargetNodeID]
+        **Logged By:** AI-Agent
+        **Details:**
+        - **Goal:** [Original refactoring goal].
+        - **Summary of Improvements:** [List of specific improvements made, e.g., "Replaced N+1 query with a single JOIN", "Extracted duplicated logic into a helper function"].
+        - **Verification:** Confirmed that all original Verification Criteria for the node still pass, ensuring no functional regressions.
+        ---
+        ```
+3.  **Update Tracker & Finalize:**
+    *   In `knowzcode/knowzcode_tracker.md`:
+        *   Find the row for `TargetNodeID`, change its `Status` back to `[VERIFIED]`, and clear its `WorkGroupID`.
+        *   If a `REFACTOR_[TargetNodeID]` task exists, **delete that entire row** from the tracker.
+4.  **Final Commit:**
+    *   Commit all changes (code, spec updates, log, tracker) with a descriptive `refactor:` message (e.g., `refactor(API_UserSearch): Optimize query performance`).
+
+### Final Report
+*   Once all steps are complete, provide a concise confirmation report.
+> "✓ Refactoring of `[TargetNodeID]` is complete. The technical debt task has been resolved, logged, and committed. The tracker has been updated."

package/knowzcode/prompts/Spec_Verification_Checkpoint.md

@@ -1,59 +1,59 @@
-# KnowzCode: Spec Verification Checkpoint
-
-**WorkGroupID for Verification:**
-[Orchestrator: Re-state the `WorkGroupID` that requires specification verification.]
-
-> **Automation Path:** Use `/kc-audit audit=spec workgroup_id=<ID>` to run the `reviewer` subagent against the draft specs before implementation.
-
-**WorkGroupID:** `[wip-timestamp-to-verify]`
-
----
-
-## Your Mission
-This is a **READ-ONLY** quality gate to ensure all specifications for the given `WorkGroupID` are complete and ready for implementation. You must systematically check every spec file associated with the WorkGroupID against the quality criteria.
-
-**CRITICAL RULE: You MUST NOT modify any files during this check. This is a verification step, not a correction step.**
-
-**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the quality check defined in **Step 3.5**.
-
----
-
-### Execution Protocol
-
-1.  **Identify Scope:**
-    *   Using the `WorkGroupID`, identify all `NodeID`s from `knowzcode_tracker.md` that are part of this verification task.
-
-2.  **Systematic Spec Review:**
-    *   For **each** `NodeID` in the scope, read its corresponding `specs/[NodeID].md` file.
-    *   Verify the following for each file:
-        *   **Existence:** Does the spec file actually exist?
-        *   **Completeness:** Are all 4 sections filled out? (Rules & Decisions, Interfaces, Verification Criteria, Debt & Gaps). Legacy 7-section format also accepted.
-        *   **Clarity:** Are the `VERIFY:` statements (or legacy `ARC_XXX_01:` criteria) specific, testable, and unambiguous? Minimum 2 VERIFY: statements per spec.
-        *   **Consistency:** Do the dependencies listed in Interfaces align with the Change Set?
-
-3.  **Synthesize Findings & Report:**
-    *   After reviewing all specs, compile a single report summarizing the overall quality.
-
-### Reporting
-
-*   **On Success:** If all specs are present, complete, and meet quality standards.
-    *   **Success Report:**
-    > "Specification Verification Checkpoint for `WorkGroupID: [ID]` is complete. All specs are present, complete, and meet quality standards. Ready to proceed to implementation. Awaiting the `[LOOP_2A]__Implement_Change_Set.md` command."
-
-*   **On Issues Found:** If any specs are missing, incomplete, or have quality issues.
-    *   **Issues Report:**
-    > "Specification Verification Checkpoint for `WorkGroupID: [ID]` is complete. The following issues were found:
-    >
-    > *   **Missing Specs:**
-    >     *   `[NodeID_X]`
-    > *   **Incomplete Specs:**
-    >     *   `[NodeID_Y]`: 'Verification Criteria' section is empty or has <2 VERIFY: statements.
-    >     *   `[NodeID_Z]`: 'Rules & Decisions' section contains only placeholder text.
-    >
-    > Recommendation: Return to `LOOP 1B` to address these specification issues before proceeding with implementation."
-
-### Final State
-
-*   Upon completion of your report, you will **PAUSE**.
-*   The Orchestrator will decide whether to proceed to Loop 2A or return to Loop 1B to fix the specs.
----
+# KnowzCode: Spec Verification Checkpoint
+
+**WorkGroupID for Verification:**
+[Orchestrator: Re-state the `WorkGroupID` that requires specification verification.]
+
+> **Automation Path:** Use `/kc-audit audit=spec workgroup_id=<ID>` to run the `reviewer` subagent against the draft specs before implementation.
+
+**WorkGroupID:** `[wip-timestamp-to-verify]`
+
+---
+
+## Your Mission
+This is a **READ-ONLY** quality gate to ensure all specifications for the given `WorkGroupID` are complete and ready for implementation. You must systematically check every spec file associated with the WorkGroupID against the quality criteria.
+
+**CRITICAL RULE: You MUST NOT modify any files during this check. This is a verification step, not a correction step.**
+
+**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the quality check defined in **Step 3.5**.
+
+---
+
+### Execution Protocol
+
+1.  **Identify Scope:**
+    *   Using the `WorkGroupID`, identify all `NodeID`s from `knowzcode_tracker.md` that are part of this verification task.
+
+2.  **Systematic Spec Review:**
+    *   For **each** `NodeID` in the scope, read its corresponding `specs/[NodeID].md` file.
+    *   Verify the following for each file:
+        *   **Existence:** Does the spec file actually exist?
+        *   **Completeness:** Are all 4 sections filled out? (Rules & Decisions, Interfaces, Verification Criteria, Debt & Gaps). Legacy 7-section format also accepted.
+        *   **Clarity:** Are the `VERIFY:` statements (or legacy `ARC_XXX_01:` criteria) specific, testable, and unambiguous? Minimum 2 VERIFY: statements per spec.
+        *   **Consistency:** Do the dependencies listed in Interfaces align with the Change Set?
+
+3.  **Synthesize Findings & Report:**
+    *   After reviewing all specs, compile a single report summarizing the overall quality.
+
+### Reporting
+
+*   **On Success:** If all specs are present, complete, and meet quality standards.
+    *   **Success Report:**
+    > "Specification Verification Checkpoint for `WorkGroupID: [ID]` is complete. All specs are present, complete, and meet quality standards. Ready to proceed to implementation. Awaiting the `[LOOP_2A]__Implement_Change_Set.md` command."
+
+*   **On Issues Found:** If any specs are missing, incomplete, or have quality issues.
+    *   **Issues Report:**
+    > "Specification Verification Checkpoint for `WorkGroupID: [ID]` is complete. The following issues were found:
+    >
+    > *   **Missing Specs:**
+    >     *   `[NodeID_X]`
+    > *   **Incomplete Specs:**
+    >     *   `[NodeID_Y]`: 'Verification Criteria' section is empty or has <2 VERIFY: statements.
+    >     *   `[NodeID_Z]`: 'Rules & Decisions' section contains only placeholder text.
+    >
+    > Recommendation: Return to `LOOP 1B` to address these specification issues before proceeding with implementation."
+
+### Final State
+
+*   Upon completion of your report, you will **PAUSE**.
+*   The Orchestrator will decide whether to proceed to Loop 2A or return to Loop 1B to fix the specs.
+---

package/knowzcode/prompts/[LOOP_1A]__Propose_Change_Set.md

@@ -1,52 +1,52 @@
-# KnowzCode: [LOOP 1A] Propose Change Set
-
-**Primary Goal:** [Orchestrator: Re-state the confirmed feature or task, e.g., "Implement a user logout button and its backend logic."]
-
-> **Automation Path:** Run `/kc-step phase=1A` to engage the `analyst` subagent with the `load-core-context`, `tracker-scan`, and `generate-workgroup-id` skills preloaded. Review the summary in `knowzcode/automation_manifest.md` if you need a refresher on available helpers.
-
-**Remember:**
-- Inspect existing specs in `knowzcode/specs/` for every impacted NodeID and note gaps.
-- Log discovery tasks in `knowzcode/workgroups/<WorkGroupID>.md` — each line must start with `KnowzCode:` so todos stay visible on-screen.
-
----
-
-## Your Mission
-You have been given a `PrimaryGoal`. Your sole objective for this step is to perform a system-wide impact analysis and propose a complete "Change Set" required to achieve this goal. This is the first critical step of the KnowzCode development loop.
-
-**CRITICAL RULE: Your work in this phase is strictly limited to updating KnowzCode's own project and specification files (`.md` files). You MUST NOT write or modify any application source code (e.g., `.js`, `.py`, `.html` files).**
-
-**Reference:** Your actions are governed by `knowzcode_loop.md`, specifically **Steps 1.2 and 1.3**.
-
----
-
-### Step 1: Analyze System-Wide Impact (Ref: `knowzcode_loop.md` - Step 1.2)
-
-*   Thoroughly analyze the `PrimaryGoal` in the context of the entire project, including `knowzcode_architecture.md`, `knowzcode_tracker.md`, and all files in the `specs/` directory.
-*   Your analysis **MUST** identify the complete Change Set, which includes:
-    1.  All **new `NodeID`s** that must be created.
-    2.  All **existing `NodeID`s** that will be impacted or require modification. This includes nodes that are currently `[TESTED]` or `[TODO]` but whose specifications or code will need to be updated to support the new feature.
-
-### Step 2: Propose the Change Set for Orchestrator Review (Ref: `knowzcode_loop.md` - Step 1.3)
-
-*   Synthesize your analysis into a clear, itemized list for the Orchestrator.
-*   For each existing node, you **must** briefly state its current status and the reason for its inclusion (e.g., "modify to add new endpoint," "update spec to handle new state").
-*   Present this list as the final proposed Change Set.
-
-**Example Response Format:**
-> "Analysis complete. To achieve the goal of '[PrimaryGoal]', I propose the following Change Set for your approval:
-> 
-> *   **New Nodes to Create:**
->     *   `UI_LogoutButton`: The user-facing button component.
->     *   `API_LogoutEndpoint`: The backend endpoint to handle the logout request.
-> *   **Existing Nodes to be Modified (will become part of the Work Group):**
->     *   `SVC_AuthSession` (Status: `[VERIFIED]`): Will be modified to add a method for invalidating a user's session.
->     *   `UI_Navbar` (Status: `[VERIFIED]`): The spec and code will be updated to include the new `UI_LogoutButton`.
-> 
-> Please review and confirm this complete Change Set. Your confirmation via the `[LOOP 1B]` prompt will authorize me to mark all these nodes as `[WIP]` and proceed."
-
-### Step 3: Pause for Confirmation
-
-*   **Your work for this prompt is now complete.**
-*   You will now **PAUSE** and await the Orchestrator's next command, which will be **`[LOOP_1B]__Draft_Specs.md`**. Do not take any further action.
-
----
+# KnowzCode: [LOOP 1A] Propose Change Set
+
+**Primary Goal:** [Orchestrator: Re-state the confirmed feature or task, e.g., "Implement a user logout button and its backend logic."]
+
+> **Automation Path:** Run `/kc-step phase=1A` to engage the `analyst` subagent with the `load-core-context`, `tracker-scan`, and `generate-workgroup-id` skills preloaded. Review the summary in `knowzcode/automation_manifest.md` if you need a refresher on available helpers.
+
+**Remember:**
+- Inspect existing specs in `knowzcode/specs/` for every impacted NodeID and note gaps.
+- Log discovery tasks in `knowzcode/workgroups/<WorkGroupID>.md` — each line must start with `KnowzCode:` so todos stay visible on-screen.
+
+---
+
+## Your Mission
+You have been given a `PrimaryGoal`. Your sole objective for this step is to perform a system-wide impact analysis and propose a complete "Change Set" required to achieve this goal. This is the first critical step of the KnowzCode development loop.
+
+**CRITICAL RULE: Your work in this phase is strictly limited to updating KnowzCode's own project and specification files (`.md` files). You MUST NOT write or modify any application source code (e.g., `.js`, `.py`, `.html` files).**
+
+**Reference:** Your actions are governed by `knowzcode_loop.md`, specifically **Steps 1.2 and 1.3**.
+
+---
+
+### Step 1: Analyze System-Wide Impact (Ref: `knowzcode_loop.md` - Step 1.2)
+
+*   Thoroughly analyze the `PrimaryGoal` in the context of the entire project, including `knowzcode_architecture.md`, `knowzcode_tracker.md`, and all files in the `specs/` directory.
+*   Your analysis **MUST** identify the complete Change Set, which includes:
+    1.  All **new `NodeID`s** that must be created.
+    2.  All **existing `NodeID`s** that will be impacted or require modification. This includes nodes that are currently `[TESTED]` or `[TODO]` but whose specifications or code will need to be updated to support the new feature.
+
+### Step 2: Propose the Change Set for Orchestrator Review (Ref: `knowzcode_loop.md` - Step 1.3)
+
+*   Synthesize your analysis into a clear, itemized list for the Orchestrator.
+*   For each existing node, you **must** briefly state its current status and the reason for its inclusion (e.g., "modify to add new endpoint," "update spec to handle new state").
+*   Present this list as the final proposed Change Set.
+
+**Example Response Format:**
+> "Analysis complete. To achieve the goal of '[PrimaryGoal]', I propose the following Change Set for your approval:
+> 
+> *   **New Nodes to Create:**
+>     *   `UI_LogoutButton`: The user-facing button component.
+>     *   `API_LogoutEndpoint`: The backend endpoint to handle the logout request.
+> *   **Existing Nodes to be Modified (will become part of the Work Group):**
+>     *   `SVC_AuthSession` (Status: `[VERIFIED]`): Will be modified to add a method for invalidating a user's session.
+>     *   `UI_Navbar` (Status: `[VERIFIED]`): The spec and code will be updated to include the new `UI_LogoutButton`.
+> 
+> Please review and confirm this complete Change Set. Your confirmation via the `[LOOP 1B]` prompt will authorize me to mark all these nodes as `[WIP]` and proceed."
+
+### Step 3: Pause for Confirmation
+
+*   **Your work for this prompt is now complete.**
+*   You will now **PAUSE** and await the Orchestrator's next command, which will be **`[LOOP_1B]__Draft_Specs.md`**. Do not take any further action.
+
+---

package/knowzcode/prompts/[LOOP_1B]__Draft_Specs.md

@@ -1,75 +1,75 @@
-# KnowzCode: [LOOP 1B] Authorize Change Set & Draft Specs
-
-**Confirmed Change Set:**
-[Orchestrator: Copy and paste the *exact* Change Set that the agent proposed and you are approving. This serves as the official, unambiguous authorization.]
-
-> **Automation Path:** Invoke `/kc-step phase=1B workgroup_id=<ID>` to delegate to the `architect` subagent. This automatically applies the `spec-template`, `spec-quality-check`, and `tracker-update` skills before presenting draft specs.
-
-**Remember:**
-- Update each affected spec in `knowzcode/specs/` using the lean 4-section template (Rules & Decisions, Interfaces, Verification Criteria, Debt & Gaps).
-- Capture spec todo items in `knowzcode/workgroups/<WorkGroupID>.md` (prefix every bullet with `KnowzCode:`).
-
-*   **New Nodes to Create:**
-    *   `[NodeID_A]`
-    *   `[NodeID_B]`
-*   **Existing Nodes to be Modified:**
-    *   `[NodeID_C]` (Status: `[VERIFIED]`)
-    *   `[NodeID_D]` (Status: `[TODO]`)
-
----
-
-## Your Mission
-The Change Set has been confirmed. Your first action is to **update the `knowzcode_tracker.md`** to reflect the start of this work. Then, proceed to draft or refine all required specifications directly in their respective files.
-
-**CRITICAL RULE: Your work in this phase is strictly limited to updating KnowzCode's own project and specification files (`.md` files). You MUST NOT write or modify any application source code (e.g., `.js`, `.py`, `.html` files).**
-
-**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the sequence from **Step 1.4 to Step 3**.
-
----
-
-### Step 1: Establish Work Group & Update Tracker (Ref: `knowzcode_loop.md` - Step 1.4)
-
-*   Generate a single, unique `WorkGroupID` for this session (e.g., `wip-<timestamp>`).
-*   In `knowzcode_tracker.md`, immediately update every node listed in the confirmed Change Set above:
-    1.  Set its `Status` to `[WIP]`.
-    2.  Assign the new `WorkGroupID` to it.
-*   This action formally begins the work session and reserves the nodes for this task.
-
-### Step 2: Draft and Refine Specifications (Ref: `knowzcode_loop.md` - Steps 2 & 3)
-
-*   Now that the tracker is updated, execute a **full Context Assembly (Step 2)** from the loop to gather all necessary information for the entire Change Set.
-*   Proceed to **Specification Management (Step 3)**:
-    *   For each **new** node in the Change Set, **create and write** its complete specification to a new file at `specs/[NodeID].md`.
-    *   For each **existing** node in the Change Set, **read, modify, and save** its specification file at `specs/[NodeID].md`.
-
-### Step 3: Report Readiness for Review (Ref: `knowzcode_loop.md` - Step 3.3)
-
-*   Once all spec files for the *entire* Change Set have been created or updated, **do not output their contents.**
-*   Instead, report that the administrative and drafting phases are complete, providing a clear list of the files that are now ready for the Orchestrator's review.
-
-**Example Response Format:**
-> "Authorization received. The `knowzcode_tracker.md` has been updated and all nodes in `WorkGroupID: [ID]` are now marked as `[WIP]`.
->
-> The specification drafting and refinement phase is also complete. The following files are now ready for your review in the `specs/` directory:
->
-> *   **New Specs Created:**
->     *   `specs/[NodeID_A].md`
->     *   `specs/[NodeID_B].md`
-> *   **Existing Specs Modified:**
->     *   `specs/[NodeID_C].md`
->     *   `specs/[NodeID_D].md`
->
-> Please review these files at your convenience. Based on a Change Set size of [Number] nodes, I recommend we proceed to [Spec Verification Checkpoint | LOOP 2A]. Your approval via the next prompt will authorize the next step."
-
-### Step 4: Verification Recommendation
-*   **Assess the Change Set size.**
-    *   If the Change Set involves **10 or more NodeIDs**, recommend that the Orchestrator runs the **`Spec_Verification_Checkpoint.md`** prompt next.
-    *   If the Change Set is **5-9 NodeIDs**, note that the checkpoint is optional but suggested.
-    *   For **<5 NodeIDs**, proceed directly to Loop 2.
-
-### Step 5: Pause for Approval
-
-*   **Your work for this prompt is now complete.**
-*   You will now **PAUSE** and await the Orchestrator's next command. This will either be the **Spec Verification Checkpoint** for large change sets, or **`[LOOP_2A]__Implement_Change_Set.md`** to begin implementation. Do not take any further action.
-
----
+# KnowzCode: [LOOP 1B] Authorize Change Set & Draft Specs
+
+**Confirmed Change Set:**
+[Orchestrator: Copy and paste the *exact* Change Set that the agent proposed and you are approving. This serves as the official, unambiguous authorization.]
+
+> **Automation Path:** Invoke `/kc-step phase=1B workgroup_id=<ID>` to delegate to the `architect` subagent. This automatically applies the `spec-template`, `spec-quality-check`, and `tracker-update` skills before presenting draft specs.
+
+**Remember:**
+- Update each affected spec in `knowzcode/specs/` using the lean 4-section template (Rules & Decisions, Interfaces, Verification Criteria, Debt & Gaps).
+- Capture spec todo items in `knowzcode/workgroups/<WorkGroupID>.md` (prefix every bullet with `KnowzCode:`).
+
+*   **New Nodes to Create:**
+    *   `[NodeID_A]`
+    *   `[NodeID_B]`
+*   **Existing Nodes to be Modified:**
+    *   `[NodeID_C]` (Status: `[VERIFIED]`)
+    *   `[NodeID_D]` (Status: `[TODO]`)
+
+---
+
+## Your Mission
+The Change Set has been confirmed. Your first action is to **update the `knowzcode_tracker.md`** to reflect the start of this work. Then, proceed to draft or refine all required specifications directly in their respective files.
+
+**CRITICAL RULE: Your work in this phase is strictly limited to updating KnowzCode's own project and specification files (`.md` files). You MUST NOT write or modify any application source code (e.g., `.js`, `.py`, `.html` files).**
+
+**Reference:** Your actions are governed by `knowzcode_loop.md`, executing the sequence from **Step 1.4 to Step 3**.
+
+---
+
+### Step 1: Establish Work Group & Update Tracker (Ref: `knowzcode_loop.md` - Step 1.4)
+
+*   Generate a single, unique `WorkGroupID` for this session (e.g., `wip-<timestamp>`).
+*   In `knowzcode_tracker.md`, immediately update every node listed in the confirmed Change Set above:
+    1.  Set its `Status` to `[WIP]`.
+    2.  Assign the new `WorkGroupID` to it.
+*   This action formally begins the work session and reserves the nodes for this task.
+
+### Step 2: Draft and Refine Specifications (Ref: `knowzcode_loop.md` - Steps 2 & 3)
+
+*   Now that the tracker is updated, execute a **full Context Assembly (Step 2)** from the loop to gather all necessary information for the entire Change Set.
+*   Proceed to **Specification Management (Step 3)**:
+    *   For each **new** node in the Change Set, **create and write** its complete specification to a new file at `specs/[NodeID].md`.
+    *   For each **existing** node in the Change Set, **read, modify, and save** its specification file at `specs/[NodeID].md`.
+
+### Step 3: Report Readiness for Review (Ref: `knowzcode_loop.md` - Step 3.3)
+
+*   Once all spec files for the *entire* Change Set have been created or updated, **do not output their contents.**
+*   Instead, report that the administrative and drafting phases are complete, providing a clear list of the files that are now ready for the Orchestrator's review.
+
+**Example Response Format:**
+> "Authorization received. The `knowzcode_tracker.md` has been updated and all nodes in `WorkGroupID: [ID]` are now marked as `[WIP]`.
+>
+> The specification drafting and refinement phase is also complete. The following files are now ready for your review in the `specs/` directory:
+>
+> *   **New Specs Created:**
+>     *   `specs/[NodeID_A].md`
+>     *   `specs/[NodeID_B].md`
+> *   **Existing Specs Modified:**
+>     *   `specs/[NodeID_C].md`
+>     *   `specs/[NodeID_D].md`
+>
+> Please review these files at your convenience. Based on a Change Set size of [Number] nodes, I recommend we proceed to [Spec Verification Checkpoint | LOOP 2A]. Your approval via the next prompt will authorize the next step."
+
+### Step 4: Verification Recommendation
+*   **Assess the Change Set size.**
+    *   If the Change Set involves **10 or more NodeIDs**, recommend that the Orchestrator runs the **`Spec_Verification_Checkpoint.md`** prompt next.
+    *   If the Change Set is **5-9 NodeIDs**, note that the checkpoint is optional but suggested.
+    *   For **<5 NodeIDs**, proceed directly to Loop 2.
+
+### Step 5: Pause for Approval
+
+*   **Your work for this prompt is now complete.**
+*   You will now **PAUSE** and await the Orchestrator's next command. This will either be the **Spec Verification Checkpoint** for large change sets, or **`[LOOP_2A]__Implement_Change_Set.md`** to begin implementation. Do not take any further action.
+
+---