knowzcode - npm Package Compare versions
| { | ||
| "name": "knowzcode", | ||
| "description": "KnowzCode - Platform-agnostic AI development methodology with TDD, quality gates, and structured workflows", | ||
| "version": "0.9.0", | ||
| "version": "0.10.0", | ||
| "keywords": ["tdd", "development-methodology", "quality-gates", "agents", "code-review"], | ||
@@ -6,0 +6,0 @@ "author": { |
@@ -40,2 +40,4 @@ --- | ||
| When creating new specs, include `**KnowledgeId:**` (empty) after `**Status:**`. When updating existing specs, preserve the existing `**KnowledgeId:**` value unchanged — it is managed by vault sync agents. | ||
| ## Consolidation Mandate | ||
@@ -42,0 +44,0 @@ |
+1
-0
@@ -56,2 +56,3 @@ --- | ||
| - If migrating from legacy format, rewrite completely | ||
| - **Preserve the `**KnowledgeId:**` field if present** — do not remove or modify it | ||
@@ -58,0 +59,0 @@ ### Step 2: Architecture Check |
@@ -102,5 +102,16 @@ --- | ||
| - Content format templates (from vault config) | ||
| - Source file path (WorkGroup file) | ||
| - Source file path (WorkGroup or spec file) | ||
| - **KnowledgeId** — if the source file has a `**KnowledgeId:**` value (non-empty), include it in the prompt as `knowledgeId: {value}`. If absent or empty, omit it. | ||
| 5. **Create task and dispatch**: `TaskCreate("Writer: Capture Phase {N}: {wgid}")` → dispatch `knowz:writer` with the prompt | ||
| ### KnowledgeId Writeback | ||
| When a `knowz:writer` task completes, parse its output for structured ID lines: | ||
| - `CREATED_KNOWLEDGE_ID: {id} (source: {path})` — A new cloud item was created. Use `Edit` to add or update `**KnowledgeId:** {id}` in the source file at `{path}`. Place it after `**Status:**` for specs, after `**Autonomous Mode:**` for workgroups. | ||
| - `UPDATED_KNOWLEDGE_ID: {id} (source: {path})` — Existing cloud item was updated. No file edit needed (ID already present). | ||
| - `REMOVED_KNOWLEDGE_ID: {id} (source: {path})` — Cloud item no longer exists (user deleted it). Use `Edit` to remove the `**KnowledgeId:** {id}` line from the source file at `{path}`. | ||
| **Failure handling:** If the Edit fails, log a warning and continue — the next sync will create a new cloud item. | ||
| ### Reader Dispatch | ||
@@ -107,0 +118,0 @@ |
@@ -193,2 +193,3 @@ --- | ||
| **Status:** Migrated | ||
| **KnowledgeId:** | ||
@@ -195,0 +196,0 @@ ## Rules & Decisions |
@@ -92,2 +92,3 @@ # KnowzCode - Development Methodology & Operational Protocol | ||
| **Status:** Draft | Approved | As-Built | ||
| **KnowledgeId:** [optional — set automatically when synced to vault] | ||
@@ -116,2 +117,4 @@ ## Rules & Decisions | ||
| > **KnowledgeId** is optional and managed automatically by vault sync. Do not set manually. When present, vault captures update the existing cloud item instead of creating duplicates. If the cloud item is deleted, the field is automatically removed. | ||
| **Backward compatibility:** Old numbered-section specs remain valid until naturally touched. When finalizing, rewrite in the new format. | ||
@@ -118,0 +121,0 @@ |
@@ -203,2 +203,3 @@ # KnowzCode: Migrate Knowledge | ||
| **Status:** Migrated | ||
| **KnowledgeId:** | ||
| **Migrated From:** {source_path} ({source_format} format) | ||
@@ -205,0 +206,0 @@ |
+1
-1
| { | ||
| "name": "knowzcode", | ||
| "version": "0.9.0", | ||
| "version": "0.10.0", | ||
| "description": "Platform-agnostic AI development methodology with TDD, quality gates, and structured workflows", | ||
@@ -5,0 +5,0 @@ "type": "module", |
+1
-1
@@ -9,3 +9,3 @@ # KnowzCode | ||
| [](https://github.com/knowz-io/knowz-skills) | ||
| [](https://github.com/knowz-io/knowz-skills/releases) | ||
| [](https://github.com/knowz-io/knowz-skills/releases) | ||
@@ -12,0 +12,0 @@ [Installation](#installation) · [Quick Start](#quick-start) · [When to Use It](#when-to-use-knowzcode) · [How It Works](#how-it-works) · [Commands](#commands) · [Docs](#documentation) |
@@ -441,2 +441,23 @@ --- | ||
| ### Vault Write Continuation | ||
| After Step 5.5 resolves (including if the user chose C/Skip), remain responsive to vault-write intent in follow-up messages. Watch for: | ||
| - "save this to vault", "capture this", "document this in the vault" | ||
| - "save as {type}" (e.g., "save as Guidelines", "save as a Decision") | ||
| - "put this in knowz", "add this to the vault" | ||
| - Any follow-up referencing vault/knowz + save/capture/document intent | ||
| When detected: | ||
| 1. Ask the user what content to save (or confirm if they specified) | ||
| 2. Resolve target vault from `knowzcode/knowzcode_vaults.md` | ||
| 3. Dispatch `knowz:writer` via Task() with a self-contained prompt: | ||
| - Content to save (from exploration findings or user-specified content) | ||
| - Target vault ID | ||
| - Title and tags derived from the content | ||
| - Category hint if the user specified one (e.g., "Guidelines") | ||
| 4. Report success/failure to the user | ||
| This ensures vault writes work even after the structured A/B/C window closes. | ||
| ## Step 6: Listen for Implementation Intent | ||
@@ -443,0 +464,0 @@ |
@@ -38,2 +38,3 @@ # Quality Gates — Work Skill | ||
| - DM knowledge-liaison: `"Capture Phase 1A: {wgid}. Your task: #{task-id}"` | ||
| - Include the WorkGroup file's `**KnowledgeId:**` value (if present) so knowledge-liaison can pass it to knowz:writer for update mode | ||
| - The knowledge-liaison owns extraction, vault routing, and writer dispatch (see `agents/knowledge-liaison.md` — Phase Extraction Guide) | ||
@@ -81,2 +82,3 @@ | ||
| - DM knowledge-liaison: `"Capture Phase 2A: {wgid}. Your task: #{task-id}"` | ||
| - Include the WorkGroup file's `**KnowledgeId:**` value (if present) so knowledge-liaison can pass it to knowz:writer for update mode | ||
| - The knowledge-liaison owns extraction, vault routing, and writer dispatch (see `agents/knowledge-liaison.md` — Phase Extraction Guide) | ||
@@ -147,2 +149,3 @@ | ||
| - DM knowledge-liaison: `"Capture Phase 2B: {wgid}. Your task: #{task-id}"` | ||
| - Include the WorkGroup file's `**KnowledgeId:**` value (if present) so knowledge-liaison can pass it to knowz:writer for update mode | ||
| - The knowledge-liaison owns extraction, vault routing, and writer dispatch (see `agents/knowledge-liaison.md` — Phase Extraction Guide) | ||
@@ -155,3 +158,3 @@ | ||
| When complete, if MCP is configured, vaults are available, and knowledge-liaison is active: | ||
| - The closer DMs knowledge-liaison: `"Capture Phase 3: {wgid}. Your task: #{task-id}"`. The knowledge-liaison dispatches `knowz:writer` for Phase 3 capture. The lead waits for the writer task to complete before shutdown. | ||
| - The closer DMs knowledge-liaison: `"Capture Phase 3: {wgid}. Your task: #{task-id}"`. Include the WorkGroup and spec files' `**KnowledgeId:**` values if present. The knowledge-liaison dispatches `knowz:writer` for Phase 3 capture. The lead waits for the writer task to complete before shutdown. | ||
@@ -158,0 +161,0 @@ Update workgroup to "Closed" and report: |
@@ -66,2 +66,3 @@ # Agent Spawn Prompts — Work Skill | ||
| > **Ongoing**: Accept capture DMs from the lead (at quality gates) and closer (Phase 3). Accept `"Log: ..."` and `"Consider: ..."` from any agent. Accept `"VaultQuery: ..."` from any agent. Dispatch `knowz:writer` and `knowz:reader` as needed. | ||
| > **KnowledgeId sync**: When dispatching `knowz:writer`, check source files (specs, workgroups) for `**KnowledgeId:**` values and include them in dispatch prompts. After writer completes, parse output for `CREATED_KNOWLEDGE_ID`/`REMOVED_KNOWLEDGE_ID` signals and edit source files accordingly. | ||
@@ -68,0 +69,0 @@ **Dispatch**: |
@@ -242,2 +242,3 @@ --- | ||
| **Autonomous Mode**: Active/Inactive | ||
| **KnowledgeId:** | ||
@@ -357,3 +358,7 @@ ## Change Set | ||
| 5. Report completion. | ||
| 6. **Progress capture** (if MCP is configured): Read `knowzcode/knowzcode_vaults.md`, resolve vault IDs. Check for existing entry via `search_by_title_pattern("WorkGroup: {wgid}*")` — update if found, create if not. Then write a WorkGroup completion record to the vault via `create_knowledge` (or `update_knowledge` if entry exists). Also check for duplicates via `search_knowledge` before creating. | ||
| 6. **Progress capture** (if MCP is configured): Read `knowzcode/knowzcode_vaults.md`, resolve vault IDs. Read the WorkGroup file for the `**KnowledgeId:**` value. | ||
| - **If KnowledgeId exists**: call `get_knowledge_item(id)`. If found → `update_knowledge` with the completion record. If not found → remove `**KnowledgeId:**` from the WorkGroup file, fall through to create. | ||
| - **If no KnowledgeId**: check for existing entry via `search_by_title_pattern("WorkGroup: {wgid}*")` — update if found, create if not. | ||
| - **After create**: write the returned ID back as `**KnowledgeId:**` in the WorkGroup file. | ||
| - **If MCP unavailable**: skip capture gracefully, preserve existing KnowledgeId. | ||
@@ -360,0 +365,0 @@ **DONE** — 3 agents skipped (analyst, architect, reviewer, closer). |
Sorry, the diff of this file is too big to display
New alerts
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 3 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Fixed alerts
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 3 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
661141
0.42%- Number of low supply chain risk alerts
27
-6.9%Worsened metrics
- Lines of code
1903
-1.35%