@vheins/local-memory-mcp 0.15.0 → 0.16.0

package/dist/dashboard/server.js

@@ -16,7 +16,7 @@ import {
   handleTaskClaim,
   listResources,
   logger
-} from "../chunk-SWYPZXG3.js";
+} from "../chunk-2EW2PODH.js";
 
 // src/dashboard/server.ts
 import express from "express";

package/dist/mcp/server.js

@@ -60,7 +60,7 @@ import {
   toContextSlug,
   updateSessionFromInitialize,
   updateSessionRoots
-} from "../chunk-SWYPZXG3.js";
+} from "../chunk-2EW2PODH.js";
 
 // src/mcp/server.ts
 import readline from "readline";

package/dist/prompts/architecture-design.md

@@ -14,14 +14,15 @@ category: planning
 tags: [architecture, system-design, components, data-flow, adr]
 ---
 
-## FSM
+## Architecture Design
 
-Entry=S0 → S1 → S2 Exit=done
+Entry=S0 → S1 → S2 → S3 Exit=done
 Guard: S(N) req S(N-1)✅
 
 S0 | review tech_stack & requirements | — | component list, data flow map | —
 S1 | design: component diagram(blocks+responsibilities) + data flow(information movement) + ADRs(rationale) + scalability/reliability(growth+failure) + security(identity,protection,boundaries) | S0✅ | design decisions | —
 S2 | document artifacts | S1✅ | architecture docs | design/architecture/
+S3 | verify: validate component completeness, data flow coherence, ADR traceability, security coverage, scalability assumptions | S2✅ | verified | —
 
 ## Chain
 

package/dist/prompts/business-analyst.md

@@ -0,0 +1,36 @@
+---
+name: business-analyst
+description: Bridge business needs with technical solutions through requirements analysis and documentation.
+arguments:
+  - name: objective
+    description: Analysis goal (requirements-elicitation, user-stories, brd, process-modeling, etc.).
+    required: true
+  - name: domain
+    description: Business domain or project context.
+    required: false
+agent: Business Analyst
+category: workflows
+version: "1.0.0"
+tags: [workflow, analysis, requirements, business, documentation]
+---
+
+## Business Analyst
+
+Entry=S0 → S1 → S2 → S3 → S4  Exit=done
+Guard: S(N) req S(N-1)✅
+
+S0 | elicit: gather stakeholder needs via questions, existing docs, user feedback | objective provided? | raw requirements | —
+S1 | analyze: validate completeness, identify gaps, resolve contradictions, classify by priority (MoSCoW) | S0✅ | validated requirements | —
+S2 | document: write user stories (As a/I want/So that) + acceptance criteria (EARS format) + BRD/PRD sections | S1✅ | requirements artifacts | —
+S3 | validate: review with stakeholders, confirm traceability from need → requirement → acceptance criteria | S2✅ | approved artifacts | —
+S4 | verify: confirm all stakeholder needs addressed, acceptance criteria testable, no ambiguous requirements | S3✅ | verified | —
+
+## Artifact Types
+
+**User Story**: `As a <role>, I want <goal> so that <benefit>.` + Acceptance Criteria (EARS).
+**BRD (Business Requirements Document)**: Executive summary, scope, stakeholder map, functional/non-functional requirements, assumptions, constraints.
+**PRD (Product Requirements Document)**: Problem statement, user personas, feature list, success metrics, release criteria.
+**Process Model**: Current state vs future state workflow diagrams, decision points, handoffs.
+**Stakeholder Map**: Influence/interest matrix, communication plan.
+
+Objective: {{objective}} Domain: {{domain}}

package/dist/prompts/create-task.md

@@ -11,15 +11,16 @@ version: "1.0.0"
 tags: [workflow, task-creation, planning, mcp]
 ---
 
-## FSM
+## Create Task
 
-Entry=S0 → S1 → S2 → S3 Exit=created
+Entry=S0 → S1 → S2 → S3 → S4  Exit=created
 Guard: S(N) req S(N-1)✅; NO code/edit/delete — MCP tools ONLY (allowed: task-create, task-list, task-detail, task-update, memory-store, memory-search, standard-search, standard-store, handoff-list, handoff-update, read)
 
 S0 | pre_analysis: memory-search(architecture/history) + standard-search(if task leads to code/test/refactor/migrate decisions) + handoff-list(pending; close stale that describe completed work) + read code(verify paths+impl) + task-list dedup(DO NOT duplicate; link via parent_id/depends_on) | — | context | —
 S1 | design tasks: atomic(1 logical change), layered(DB/Service/State/UI), context(paths+symbols+APIs), min 1 pos+1 neg test | S0✅ | task specs | —
 S2 | assign attributes: task_code(optional — auto-generated as TASK-xxx if omitted), phase(Discovery|Implementation|Testing), priority(1=Low..5=Critical), strict description format | S1✅ | task attrs | —
 S3 | create via task-create(bulk max 500) + log decisions via memory-store(arch/feature changes; skip simple bugs) | S2✅ | MCP tasks created | —
+S4 | verify: validate task count, description format compliance, parent/depends_on integrity, no duplicates | S3✅ | verified | —
 G1 | blueprint? | src=idea-to-blueprint | → route blueprint flow | —
 G2 | sprint? | src=.agents/documents/tasks/sprints/ | → route sprint flow | —
 

package/dist/prompts/csl-from-docs.md

@@ -11,9 +11,9 @@ version: "1.0.0"
 tags: [workflow, csl, coding-standards, documentation, mcp]
 ---
 
-## FSM
+## CSL from Docs
 
-Entry=G0 → S0 → S1 → S2 → S3  Exit=stored|refused
+Entry=G0 → S0 → S1 → S2 → S3 → S4 Exit=stored|refused
 Guard: S(N) req S(N-1)✅
 
 G0 | path exists + readable + normative? | path provided? | → S0 / refuse | —
@@ -21,5 +21,48 @@ S0 | discover: if dir→list_directory then read_file each; if file→read_file
 S1 | extract atomic rules: 1 entry=1 rule, keep code examples, split bundled, preserve source meaning, ignore boilerplate | S0✅ | atomic entries | —
 S2 | dedup via standard-search (skip if high-confidence match; update if new source more authoritative) | S1✅ | filtered entries | —
 S3 | store via standard-store: parent first→children with parent_id; context=topic area; version=1.0.0(default); is_global=true(unless repo-specific); metadata={original_path, evidence_excerpt} | S2✅ | CSL entries stored | —
+S4 | verify: confirm stored count matches extracted, validate parent/child linkage, check metadata provenance | S3✅ | verified | —
+
+## Atomic Entry Rules
+
+- One entry = one rule. Split bundled guidance into separate entries.
+- DO NOT emit duplicates. If standard-search returns a high-confidence match, skip the entry or update it if the new source is more authoritative.
+- Use parent/child only for genuine hierarchy: parent = umbrella principle, child = narrower enforceable specialization.
+- Keep content concise, imperative, and implementation-relevant.
+- ALWAYS include relevant code examples or snippets from the source that illustrate or enforce the rule.
+- Preserve the source meaning without inventing requirements.
+- Ignore boilerplate, non-normative text, or metadata noise. Do NOT ignore code examples.
+- Do not infer version, language, stack, or scope unless the source makes them explicit.
+- Use metadata to preserve provenance, including the original file path and a short evidence_excerpt for each entry.
+
+## Output Contract
+
+- If tool calls are available:
+  - First, emit standard-search calls to verify existing data.
+  - Then, emit standard-store calls for every unique/new accepted entry.
+  - When parent/child hierarchy exists, emit the parent first, then emit children with parent_id referencing the created parent standard ID.
+- If tool calls are unavailable, return a JSON object with:
+  - standards: Array of standard-store-compatible payloads.
+- Use title-like names for the name field and store the atomic rule text along with its code examples in content.
+- Use context for the topic area (e.g., naming, error-handling, routing, testing, hooks, security).
+- Default version to 1.0.0 only when the source gives no versioning signal.
+- Prefer is_global=true unless the content is clearly repo-specific.
+
+## Refusal Rules
+
+- Refuse when the path does not exist or is not readable.
+- Refuse when the file content is not documentation or not clearly normative reference content.
+- Refuse when the request asks you to guess, invent, or fill missing guidance from prior knowledge.
+- Refuse when no source-backed coding standards can be extracted.
+
+If you refuse, return exactly:
+
+```json
+{
+	"action": "refuse",
+	"reason": "<short explanation>",
+	"missing": ["<missing evidence or source requirement>"]
+}
+```
 
 Path: {{path}} Repo: {{current_repo}}

package/dist/prompts/csl-scrapper.md

@@ -11,9 +11,9 @@ version: "1.0.0"
 tags: [workflow, csl, scraping, coding-standards, mcp]
 ---
 
-## FSM
+## CSL Scrapper
 
-Entry=G0 → S0 → G1 → S1 → S2 → S3 → S4  Exit=stored|refused
+Entry=G0 → S0 → G1 → S1 → S2 → S3 → S4 → S5 Exit=stored|refused
 Guard: S(N) req S(N-1)✅
 
 G0 | source_url provided? | source_url arg exists? | → S0 / refuse | —
@@ -23,5 +23,51 @@ S1 | extract atomic rules: 1 entry=1 rule, keep code examples, detect nav menus
 S2 | dedup via standard-search (skip if high-confidence match; update if new source more authoritative) | S1✅ | filtered entries | —
 S3 | store via standard-store: parent first→children with parent_id; context=topic area; version=1.0.0(default); is_global=true(unless repo-specific); metadata={source_url, evidence_excerpt} | S2✅ | CSL entries stored | —
 S4 | create scrape tasks for each sub-page URL via task-create | sub-page URLs exist? | MCP tasks queued | —
+S5 | verify: confirm stored entries match extracted count, validate parent/child linkage, verify sub-page tasks created | S4✅ | verified | —
+
+## Atomic Entry Rules
+
+- One entry = one rule. Split bundled guidance into separate entries.
+- DO NOT emit duplicates. If standard-search returns a high-confidence match, skip the entry or update it if the new source is more authoritative.
+- Use parent/child only for genuine hierarchy: parent = umbrella principle, child = narrower enforceable specialization.
+- Keep content concise, imperative, and implementation-relevant.
+- ALWAYS include relevant code examples or snippets from the source that illustrate or enforce the rule.
+- Preserve the source meaning without inventing requirements.
+- Ignore marketing copy, release notes, and changelog noise. Do NOT ignore code examples.
+- Do not infer version, language, stack, or scope unless the source makes them explicit.
+- Use metadata to preserve provenance, including the source_url and a short evidence_excerpt for each entry.
+
+## Output Contract
+
+- If tool calls are available:
+  - First, emit standard-search calls to verify existing data.
+  - Emit one standard-store call per unique/new accepted entry.
+  - When parent/child hierarchy exists, emit the parent first, then emit children with parent_id referencing the created parent standard ID.
+  - Emit one task-create call for each discovered documentation sub-page URL. Task title: "Scrape: [URL]".
+- If tool calls are unavailable, return a JSON object with:
+  - standards: Array of standard-store-compatible payloads.
+  - next_urls: Array of sub-page URLs to scrape.
+- Use title-like names for the name field and store the atomic rule text along with its code examples in content.
+- Use context for the topic area (e.g., naming, error-handling, routing, testing, hooks, security).
+- Use parent_id only when the source explicitly shows the rule is nested under a broader parent concept.
+- Default version to 1.0.0 only when the source gives no versioning signal.
+- Prefer is_global=true unless the source is clearly repo-specific.
+
+## Refusal Rules
+
+- Refuse when the URL content is not reachable, not documentation, or not clearly normative reference content.
+- Refuse when the source is too incomplete to verify atomic rules.
+- Refuse when the request asks you to guess, invent, or fill missing guidance from prior knowledge.
+- Refuse when no source-backed coding standards can be extracted.
+
+If you refuse, return exactly:
+
+```json
+{
+	"action": "refuse",
+	"reason": "<short explanation>",
+	"missing": ["<missing evidence or source requirement>"]
+}
+```
 
 Source: {{source_url}} Repo: {{current_repo}}

package/dist/prompts/data-analyst.md

@@ -0,0 +1,36 @@
+---
+name: data-analyst
+description: Analyze data, generate insights, and support data-driven decision making.
+arguments:
+  - name: objective
+    description: Analysis goal (data-analysis, reporting, kpi-tracking, data-quality, etc.).
+    required: true
+  - name: data_source
+    description: Data source, database table, or dataset description.
+    required: false
+agent: Data Analyst
+category: workflows
+version: "1.0.0"
+tags: [workflow, data, analytics, reporting, insights]
+---
+
+## Data Analyst
+
+Entry=S0 → S1 → S2 → S3 → S4  Exit=done
+Guard: S(N) req S(N-1)✅
+
+S0 | understand: clarify objective, identify data sources, define success metrics & KPIs | objective provided? | analysis plan | —
+S1 | collect & prepare: query data, validate data quality, handle missing/inconsistent data, transform as needed | S0✅ | clean dataset | —
+S2 | analyze: perform exploratory data analysis, statistical summaries, trend analysis, correlation detection, segmentation | S1✅ | findings | —
+S3 | report: create report/dashboard spec with visualizations, key insights, recommendations, and supporting evidence | S2✅ | report | —
+S4 | verify: confirm findings are statistically sound, recommendations are actionable, data sources cited, assumptions documented | S3✅ | verified | —
+
+## Analysis Types
+
+**Exploratory Data Analysis (EDA)**: Summary statistics, distributions, outliers, patterns, correlations.
+**Trend Analysis**: Time-series patterns, seasonality, growth rates, anomaly detection.
+**Cohort Analysis**: User grouping, retention analysis, behavioral segmentation.
+**Funnel Analysis**: Conversion rates, drop-off points, optimization opportunities.
+**Root Cause Analysis**: Data-driven investigation, hypothesis testing, causal factors.
+
+Objective: {{objective}} Source: {{data_source}}

package/dist/prompts/documentation-sync.md

@@ -8,12 +8,13 @@ version: "1.0.0"
 tags: [workflow, documentation, memory, sync]
 ---
 
-## FSM
+## Documentation Sync
 
-Entry=S0 → S1 → S2 → S3 Exit=aligned
+Entry=S0 → S1 → S2 → S3 → S4 Exit=aligned
 Guard: S(N) req S(N-1)✅
 
 S0 | search decision memories via memory-search | — | memory entries | —
 S1 | read_file(README.md) + glob & read_file(docs/**/\*.md, .agents/documents/**/_, .kiro/\*\*/_) | S0✅ | doc content | —
 S2 | compare: identify missing/outdated knowledge | S1✅ | gap list | —
 S3 | propose specific changes to align docs | S2✅ | update proposals | —
+S4 | verify: confirm proposal covers all gaps, no contradictory updates | S3✅ | verified | —

package/dist/prompts/export-task-to-github.md

@@ -3,10 +3,10 @@ name: export-task-to-github
 description: Export local tasks to GitHub Issues
 arguments:
   - name: owner
-    description: GitHub repo owner (hint: run `git remote -v` to extract from origin URL)
+    description: "GitHub repo owner (hint: run `git remote -v` to extract from origin URL)"
     required: true
   - name: repo
-    description: GitHub repo name (hint: run `git remote -v` to extract from origin URL)
+    description: "GitHub repo name (hint: run `git remote -v` to extract from origin URL)"
     required: true
   - name: task_id
     description: Local task ID
@@ -17,9 +17,9 @@ version: "1.0.0"
 tags: [workflow, github, task-sync, mcp]
 ---
 
-## FSM
+## Export Task to GitHub
 
-Entry=S0 → S1 → G1 → S2 → S3 → S4 Exit=exported|skipped
+Entry=S0 → S1 → G1 → S2 → S3 → S4 → S5 Exit=exported|skipped
 Guard: S(N) req S(N-1)✅; MCP + GitHub tools ONLY
 
 S0 | fetch task via task-detail | task_id exists? | task data | —
@@ -28,3 +28,4 @@ G1 | dedup gate — if exists→update local task metadata with URL, DO NOT re-c
 S2 | create issue via issue_write (match title/body, append task_code+id) | G1→new | GitHub issue created | —
 S3 | post comments via add_issue_comment | S2✅ | comments transferred | —
 S4 | link: task-update with GitHub URL + comment | S3✅ | task updated | —
+S5 | verify: confirm issue exists on GitHub, check URL in task metadata | S4✅ | verified | —

package/dist/prompts/fix-suggestion.md

@@ -17,13 +17,14 @@ category: debugging
 tags: [fix, patch, bug-fix, code-change, test-case, debugging]
 ---
 
-## FSM
+## Fix Suggestion
 
-Entry=S0 → S1 Exit=suggestion
+Entry=S0 → S1 → S2 Exit=suggestion
 Guard: S(N) req S(N-1)✅
 
 S0 | analyze inputs (tech_stack, bug_description, root_cause) | all req provided? | diagnosis | —
 S1 | produce: explanation + before/after diff(`diff ... `) + meta checklist + regression test | S0✅ | fix suggestion | —
+S2 | verify: confirm fix addresses root cause, test covers regression | S1✅ | verified | —
 
 ## Output Format (S1)
 

package/dist/prompts/import-github-issues.md

@@ -8,9 +8,9 @@ version: "1.0.0"
 tags: [workflow, github, issue-import, mcp]
 ---
 
-## FSM
+## Import GitHub Issues
 
-Entry=S0 → S1 → S2 → S3 → S4 Exit=imported
+Entry=S0 → S1 → S2 → S3 → S4 → S5 Exit=imported
 Guard: S(N) req S(N-1)✅
 Hint: If repo not auto-detected, run `git remote -v` to get owner/repo from origin URL.
 
@@ -19,3 +19,4 @@ S1 | dedup via task-list (skip if GH-{number} exists) | S0✅ | filtered issues
 S2 | create MCP tasks: task_code=GH-{number} (auto-generated as TASK-xxx if omitted), EXACT title/body (DO NOT summarize), tags=labels, phase=backlog|triage, metadata=URL | S1✅ | tasks created | —
 S3 | import comments via issue_read → task-update | S2✅ | comments linked | —
 S4 | report created count | S3✅ | summary | —
+S5 | verify: confirm created task count matches new issues, no duplicates | S4✅ | verified | —

package/dist/prompts/learning-retrospective.md

@@ -11,12 +11,19 @@ version: "1.0.0"
 tags: [workflow, retrospective, memory, knowledge-management]
 ---
 
-## FSM
+## Learning Retrospective
 
-Entry=S0 → S1  Exit=stored
+Entry=S0 → S1 → S2 Exit=stored
 Guard: S(N) req S(N-1)✅
 
 S0 | identify: mistakes (bugs/quirks), decisions (trade-offs/pivots), patterns (conventions) | task_id? | knowledge items | —
 S1 | store via memory-store (type=mistake|decision|pattern, include tech tags, concise) | S0✅ | durable memories | —
+S2 | verify: confirm stored count matches identified items, check type correctness | S1✅ | verified | —
+
+## Directives
+
+- Use type: mistake | decision | pattern.
+- Include technology tags.
+- Keep content concise.
 
 Task: {{task_id}}

package/dist/prompts/memory-agent-core.md

@@ -8,9 +8,22 @@ version: "1.0.0"
 tags: [memory, workflow, guardrails, mcp]
 ---
 
-## FSM — Execution Policy
+## Memory Guardian Protocol
 
-Entry=S0 → S1 → S2 → S3 → S4 → S5  Exit=act
+You are a memory-aware agent. Memory is project truth, not a suggestion.
+
+## Core Rules
+
+- Use hybrid search (70% Cosine + 30% BM25) with 0.55 threshold.
+- NEVER contradict stored decisions without memory-update or supersedes.
+- Use ONLY highly relevant memories + standards.
+- Acknowledge after code gen using memory: memory-acknowledge(used|irrelevant|contradictory).
+- Store ONLY if durable + affects future behavior.
+- NEVER store coordination state (claims, file ownership) as memory.
+
+## Execution Policy
+
+Entry=S0 → S1 → S2 → S3 → S4 → S5 → S6 Exit=act
 Guard: S(N) req S(N-1)✅; NEVER contradict stored decisions without memory-update or supersedes
 
 S0 | orient: task-list + handoff-list (close stale pending) | session start? | active context | —
@@ -19,11 +32,13 @@ S2 | search: memory-search(Hybrid: 70% Cosine+30% BM25, 0.55 threshold) + standa
 S3 | retrieve: memory-detail for full content if pointer rows insufficient | S2✅ | hydrated entries | —
 S4 | select: use ONLY highly relevant memories + standards | S3✅ | filtered knowledge | —
 S5 | acknowledge: after code gen using memory → memory-acknowledge(used|irrelevant|contradictory) | code generated? | feedback | —
+S6 | verify: confirm no stored decisions contradicted, acknowledge called after code gen | S5✅ | verified | —
 
-## FSM — Creation Policy
+## Creation Policy
 
-Entry=S0 → S1  Exit=stored
+Entry=S0 → S1 → S2 Exit=stored
 Guard: store ONLY if durable + affects future behavior; use supersedes for overrides
 
 S0 | categorize: type + tech tags; NEVER store coordination state (claims, file ownership) as memory | is durable? | classified | —
 S1 | store: memory-store(decisions/patterns) or standard-store(normative rules) or handoff-create(transfer ctx) | S0✅ | stored | —
+S2 | verify: confirm stored entity matches category, no forbidden types mixed in | S1✅ | verified | —

package/dist/prompts/memory-guided-review.md

@@ -11,14 +11,15 @@ version: "1.0.0"
 tags: [code-review, memory, compliance, mcp]
 ---
 
-## FSM
+## Memory Guided Review
 
-Entry=S0 → S1 → S2 → S3  Exit=reviewed
+Entry=S0 → S1 → S2 → S3 → S4  Exit=reviewed
 Guard: S(N) req S(N-1)✅
 
 S0 | search: memory-search (file_path) + standard-search (lang, stack, repo) | file_path provided? | relevant rules | —
 S1 | hydrate: memory-detail for relevant pointers | S0✅ | full rules | —
 S2 | evaluate compliance vs patterns, documented mistakes, standards | S1✅ | violation list | —
 S3 | feedback: suggest fixes citing source (memory|standard) | S2✅ | review report | —
+S4 | verify: confirm all relevant rules evaluated, no missed violations | S3✅ | verified | —
 
 File: {{file_path}}

package/dist/prompts/memory-index-policy.md

@@ -8,15 +8,16 @@ version: "1.0.0"
 tags: [memory, indexing, policy, mcp]
 ---
 
-## FSM
+## Memory Index Policy
 
-Entry=G0 → S0 → S1 → S2  Exit=stored|rejected
+Entry=G0 → S0 → S1 → S2 → S3  Exit=stored|rejected
 Guard: S(N) req S(N-1)✅
 
 G0 | is durable + project-specific? NOT forbidden types? | content provided? | → S0 / reject | —
 S0 | classify type (code_fact|decision|mistake|pattern|task_archive) + tech tags | G0✅ | classified | —
 S1 | scope: is_global ONLY if cross-repo applicable | S0✅ | scoped | —
 S2 | store via memory-store | S1✅ | memory created | —
+S3 | verify: confirm type matches content, scope is correct, tags are accurate | S2✅ | verified | —
 
 ## Forbidden (G0→reject)
 

package/dist/prompts/project-briefing.md

@@ -8,9 +8,9 @@ version: "1.0.0"
 tags: [workflow, briefing, onboarding, memory, backlog]
 ---
 
-## FSM
+## Project Briefing
 
-Entry=S0 → S1-4(parallel) → S5 → S6  Exit=briefed
+Entry=S0 → S1-4(parallel) → S5 → S6 → S7  Exit=briefed
 Guard: S(N) req S(N-1)✅
 
 S0 | identify current repo | — | repo context | —
@@ -20,3 +20,4 @@ S3 | load memory: memory-search or memory-recap; hydrate via memory-detail | S0
 S4 | load standards: standard-search (repo, stack) | S0✅ | applicable standards | —
 S5 | summarize core: active task + pending handoffs + standards + top decisions | S1-4✅ | briefing | —
 S6 | propose next steps based on active queue; priority: 1=Low 2=Normal 3=Medium 4=High 5=Critical | S5✅ | action plan | —
+S7 | verify: confirm all sources loaded (tasks, handoffs, memory, standards), briefing complete | S6✅ | verified | —

package/dist/prompts/qa-analyst.md

@@ -0,0 +1,36 @@
+---
+name: qa-analyst
+description: Design test strategies, create test plans, and ensure software quality.
+arguments:
+  - name: objective
+    description: QA goal (test-plan, test-cases, test-strategy, regression-suite, etc.).
+    required: true
+  - name: tech_stack
+    description: Technology stack and testing frameworks in use.
+    required: false
+agent: QA Analyst
+category: workflows
+version: "1.0.0"
+tags: [workflow, testing, quality-assurance, test-planning]
+---
+
+## QA Analyst
+
+Entry=S0 → S1 → S2 → S3 → S4  Exit=done
+Guard: S(N) req S(N-1)✅
+
+S0 | analyze: review requirements, user stories, and acceptance criteria; identify test scope & risk areas | objective provided? | scope & risks | —
+S1 | design test strategy: define test levels (unit/integration/e2e), test types (functional/regression/performance/security), environment needs, entry/exit criteria | S0✅ | test strategy | —
+S2 | create test artifacts: write test cases (positive + negative + edge cases), test data requirements, trace to requirements | S1✅ | test artifacts | —
+S3 | review: peer-review test cases for coverage, clarity, and correctness; update based on feedback | S2✅ | reviewed artifacts | —
+S4 | verify: confirm all acceptance criteria covered, risk areas addressed, test cases are deterministic and traceable | S3✅ | verified | —
+
+## Test Design Techniques
+
+**Equivalence Partitioning**: Divide input into valid/invalid partitions, test one from each.
+**Boundary Value Analysis**: Test boundaries of equivalence partitions (min, max, just inside, just outside).
+**Decision Table**: Map combinations of conditions to expected outcomes.
+**State Transition**: Test state changes and valid/invalid transitions.
+**Exploratory Testing**: Simultaneously learn, design, and execute tests without predefined scripts.
+
+Objective: {{objective}} Stack: {{tech_stack}}

package/dist/prompts/review-and-audit.md

@@ -11,15 +11,26 @@ version: "1.0.0"
 tags: [workflow, audit, ux, gap-analysis, mcp]
 ---
 
-## FSM
+## Review and Audit
 
-Entry=S0 → S1 → S2 → S3 Exit=done
+Entry=S0 → S1 → S2 → S3 → S4 Exit=done
 Guard: S(N) req S(N-1)✅; NO code/edit/delete — read+MCP tools ONLY
 
 S0 | sequential discovery: docs → code → UI (chrome-dev-tools) | — | findings | —
 S1 | pre-task analysis: memory-search (0.55 threshold) + standard-search + handoff-list + task-list dedup | S0✅ | context | —
 S2 | design tasks: atomic, attributes (task_code optional — auto-generated as TASK-xxx, phase, priority, agent, model), strict description format | S1✅ | task specs | —
 S3 | create via task-create + log decisions via memory-store + standard-store for coding rules | S2✅ | MCP tasks | —
+S4 | verify: confirm task count matches gap count, description format compliance, parent/child linkage | S3✅ | verified | —
+
+## FORBIDDEN: NON-EXECUTION
+
+DO NOT edit/create/delete files, run commands, or implement code.
+Allowed: Read code, chrome-dev-tools, task-create, memory-store, task-list, memory-search, standard-search, handoff-list, handoff-update.
+
+## SELF-CHECK
+
+- No implementation.
+- ONLY MCP tool calls.
 
 ## Description Format (STRICT — used in S2)
 

package/dist/prompts/review-and-post-issue.md

@@ -3,10 +3,10 @@ name: review-and-post-issue
 description: Audit documentation against implementation; generate GitHub issues for gaps.
 arguments:
   - name: owner
-    description: GitHub repo owner. (hint: run `git remote -v` to extract from origin URL)
+    description: "GitHub repo owner. (hint: run `git remote -v` to extract from origin URL)"
     required: true
   - name: repo
-    description: GitHub repo name. (hint: run `git remote -v` to extract from origin URL)
+    description: "GitHub repo name. (hint: run `git remote -v` to extract from origin URL)"
     required: true
   - name: target
     description: Module, feature, or component to audit.
@@ -17,15 +17,31 @@ version: "1.0.0"
 tags: [workflow, audit, github, issue-triage]
 ---
 
-## FSM
+## Review and Post Issue
 
-Entry=S0 → S1 → S2 → S3 Exit=done
+Entry=S0 → S1 → S2 → S3 → S4 Exit=done
 Guard: S(N) req S(N-1)✅; NO code/edit/delete — GitHub+MCP tools ONLY
 
 S0 | sequential discovery: docs → code → UI (chrome-dev-tools if applicable) | — | findings | —
 S1 | pre-issue analysis: memory-search (0.55 threshold) + search_issues dedup (comment on related if distinct) | S0✅ | context | —
 S2 | design issues: atomic, strict body format, labels | S1✅ | issue specs | —
 S3 | create via issue_write(method=create) | S2✅ | GitHub issues | —
+S4 | verify: confirm issue count matches gap count, all issues created on GitHub | S3✅ | verified | —
+
+## FORBIDDEN: NON-EXECUTION
+
+DO NOT edit/create/delete files, run commands, or implement code.
+Allowed: Read code, chrome-dev-tools, memory-search, GitHub search_issues, issue_write.
+
+## OUTPUT: GITHUB ONLY
+
+ONLY call: search_issues, issue_write (method: create), memory-search.
+No prose. No external plans.
+
+## SELF-CHECK
+
+- No implementation.
+- ONLY GitHub/Memory tool calls.
 
 ## Issue Body Format (STRICT — used in S2)
 

package/dist/prompts/root-cause-analysis.md

@@ -17,14 +17,15 @@ version: "1.0.0"
 tags: [root-cause, 5-why, debugging, diagnosis]
 ---
 
-## FSM
+## Root Cause Analysis
 
-Entry=S0 → S1 → S2 → S3  Exit=diagnosis
+Entry=S0 → S1 → S2 → S3 → S4  Exit=diagnosis
 Guard: S(N) req S(N-1)✅
 
 S0 | restate symptom: technical problem statement | tech_stack + bug_description provided? | symptom statement | —
 S1 | 5-why analysis: causal chain from symptom to core failure | S0✅ | causal chain | —
 S2 | identify root cause: "root cause is [X] because [Y], allowing [Z]" | S1✅ | root cause | —
 S3 | recommend fix addressing root cause + prevention (monitoring/test) | S2✅ | recommendation | —
+S4 | verify: confirm causal chain is logically sound, root cause is minimal sufficient explanation | S3✅ | verified | —
 
 Stack: {{tech_stack}} Bug: {{bug_description}} Symptoms: {{symptoms}}

package/dist/prompts/scrum-master.md

@@ -0,0 +1,35 @@
+---
+name: scrum-master
+description: Facilitate Scrum ceremonies, remove blockers, and optimize team delivery.
+arguments:
+  - name: objective
+    description: Session goal (sprint-planning, daily-standup, retrospective, blocker-resolution, etc.).
+    required: true
+  - name: sprint_context
+    description: Current sprint number, backlog items, velocity data.
+    required: false
+agent: Scrum Master
+category: workflows
+version: "1.0.0"
+tags: [workflow, agile, scrum, ceremonies, facilitation]
+---
+
+## Scrum Master
+
+Entry=S0 → S1 → S2 → S3  Exit=done
+Guard: S(N) req S(N-1)✅
+
+S0 | orient: identify ceremony type + load sprint context (task-list, backlog items, blockers) | objective provided? | context | —
+S1 | facilitate: run ceremony (sprint planning → decompose + estimate; daily standup → sync + unblock; retrospective → reflect + action items; backlog grooming → refine + re-prioritize; blocker resolution → diagnose + escalate) | S0✅ | ceremony output | —
+S2 | document: record action items, decisions, impediments via task-create + memory-store | S1✅ | artifacts | —
+S3 | verify: confirm all action items captured, blockers documented with owners, ceremony objectives met | S2✅ | verified | —
+
+## Ceremony Guides
+
+**Sprint Planning**: Decompose product backlog into tasks, estimate effort, define sprint goal, confirm capacity.
+**Daily Standup**: Each member: what I did yesterday, what I'll do today, blockers.
+**Sprint Retrospective**: What went well, what to improve, action items for next sprint.
+**Backlog Grooming**: Refine user stories, split large items, re-prioritize based on value/effort.
+**Blocker Resolution**: Identify root cause, determine escalation path, assign resolution owner.
+
+Objective: {{objective}} Sprint: {{sprint_context}}