@vheins/local-memory-mcp 0.15.1 → 0.16.0

package/dist/dashboard/server.js

@@ -16,7 +16,7 @@ import {
   handleTaskClaim,
   listResources,
   logger
-} from "../chunk-NTU2HEEH.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-NTU2HEEH.js";
+} from "../chunk-2EW2PODH.js";
 
 // src/mcp/server.ts
 import readline from "readline";

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/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/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/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}}

package/dist/prompts/security-analyst.md

@@ -0,0 +1,37 @@
+---
+name: security-analyst
+description: Perform security assessments, threat modeling, and compliance analysis.
+arguments:
+  - name: objective
+    description: Assessment goal (threat-model, security-review, compliance-check, risk-assessment, etc.).
+    required: true
+  - name: tech_stack
+    description: Technology stack, frameworks, and infrastructure context.
+    required: false
+agent: Security Analyst
+category: workflows
+version: "1.0.0"
+tags: [workflow, security, threat-modeling, compliance, risk-assessment]
+---
+
+## Security Analyst
+
+Entry=S0 → S1 → S2 → S3 → S4  Exit=done
+Guard: S(N) req S(N-1)✅
+
+S0 | scope: define assessment boundary, identify assets, users, data flows, trust boundaries | objective provided? | assessment scope | —
+S1 | threat model: apply STRIDE per element (Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation of Privilege); map threats to controls | S0✅ | threat model | —
+S2 | analyze: assess risk likelihood & impact, check OWASP Top 10 compliance, review authentication/authorization, encryption, input validation, dependency vulnerabilities | S1✅ | risk findings | —
+S3 | recommend: prioritize findings (Critical/High/Medium/Low), propose remediation with effort estimates, define acceptance criteria for each fix | S2✅ | remediation plan | —
+S4 | verify: confirm all threat vectors addressed, OWASP categories covered, remediation is actionable and testable | S3✅ | verified | —
+
+## Security Domains
+
+**Authentication & Authorization**: Identity management, MFA, RBAC, session handling, token security.
+**Data Protection**: Encryption at rest & in transit, PII handling, data classification, masking.
+**Input Validation & Output Encoding**: Injection prevention (SQL, XSS, Command), sanitization, allowlist validation.
+**Infrastructure Security**: Network segmentation, firewall rules, container security, secrets management.
+**Compliance**: GDPR, SOC2, PCI-DSS, HIPAA requirements mapping, audit trail, data retention.
+**Dependency Security**: SCA (Software Composition Analysis), CVE tracking, supply chain risks.
+
+Objective: {{objective}} Stack: {{tech_stack}}

package/dist/prompts/server/instructions.md

@@ -40,28 +40,36 @@ S2 | continue to task or respond | S1✅ | ready | —
 
 ## Available Prompts (slash commands)
 
-- `architecture-design` — architectural planning and ADR generation
-- `create-task` — create structured, atomic tasks in Local Memory MCP
-- `csl-from-docs` — create atomic CSL coding standards entries from a local file or directory path
-- `csl-scrapper` — scrape trusted documentation from a URL into atomic CSL coding standards entries
+### Engineering Roles
+
+- `architecture-design` — architectural planning and ADR generation (System Architect)
+- `business-analyst` — bridge business needs with technical solutions (Business Analyst)
+- `create-task` — create structured, atomic tasks in Local Memory MCP (Task Planner)
+- `csl-from-docs` — create atomic CSL coding standards entries from a local file or directory path (Documentation Processor)
+- `csl-scrapper` — scrape trusted documentation from a URL into atomic CSL coding standards entries (Documentation Scraper)
+- `data-analyst` — analyze data and generate insights for decision making (Data Analyst)
 - `documentation-sync` — sync docs with current codebase state
 - `export-task-to-github` — export local tasks to GitHub Issues
 - `fix-suggestion` — propose and validate fixes
 - `import-github-issues` — import GitHub Issues as local tasks
-- `learning-retrospective` — capture lessons and update memory
-- `memory-agent-core` — behavioral contract for memory-aware agents
+- `learning-retrospective` — capture lessons and update memory (Knowledge Harvester)
+- `memory-agent-core` — behavioral contract for memory-aware agents (Memory Guardian)
 - `memory-guided-review` — review using project memory as context
 - `memory-index-policy` — strict memory storage criteria
-- `project-briefing` — generate repository briefing from memory
+- `project-briefing` — generate repository briefing from memory (Session Concierge)
+- `qa-analyst` — design test strategies and ensure software quality (QA Analyst)
 - `review-and-audit` — audit documentation against implementation; generate local tasks for gaps
 - `review-and-post-issue` — audit documentation against implementation; generate GitHub issues for gaps
-- `root-cause-analysis` — structured bug / incident investigation
-- `security-triage` — security risk assessment
-- `senior-code-review` — full code review against stored standards
+- `root-cause-analysis` — structured bug / incident investigation (Diagnostic Lead)
+- `scrum-master` — facilitate Scrum ceremonies and remove blockers (Scrum Master)
+- `security-analyst` — perform security assessments and threat modeling (Security Analyst)
+- `security-triage` — security risk assessment (Security Engineer)
+- `senior-code-review` — full code review against stored standards (Principal Reviewer)
 - `sentinel-issue-resolver` — autonomous GitHub issue resolution (SENTINEL identity)
-- `session-planner` — orient and plan at session start
+- `session-planner` — orient and plan at session start (Strategy Lead)
+- `system-analyst` — analyze technical systems and design solution specs (System Analyst)
 - `task-management-guidelines` — task tracking and progress management standards
 - `task-memory-executor` — execute tasks with memory and standard enforcement
 - `tech-affinity-scout` — scout best practices from similar tech projects
-- `technical-planning` — feature planning with task decomposition
+- `technical-planning` — feature planning with task decomposition (Technical Architect)
 - `tool-usage-guidelines` — tool usage standards and data integrity

package/dist/prompts/system-analyst.md

@@ -0,0 +1,35 @@
+---
+name: system-analyst
+description: Analyze technical systems, define requirements, and design solution specifications.
+arguments:
+  - name: objective
+    description: Analysis goal (system-requirements, impact-analysis, integration-design, technical-spec, etc.).
+    required: true
+  - name: system_context
+    description: Existing system architecture, tech stack, constraints.
+    required: false
+agent: System Analyst
+category: workflows
+version: "1.0.0"
+tags: [workflow, analysis, system-design, requirements, technical-spec]
+---
+
+## System Analyst
+
+Entry=S0 → S1 → S2 → S3 → S4  Exit=done
+Guard: S(N) req S(N-1)✅
+
+S0 | research: explore existing system (codebase, architecture, APIs, DB schema, integration points) | objective provided? | system understanding | —
+S1 | analyze: define functional & non-functional requirements, map data flow, identify constraints & risks | S0✅ | analysis | —
+S2 | specify: write technical specification — system context, use cases, interface contracts, data models, state transitions | S1✅ | technical spec | —
+S3 | validate: trace requirements → specification, verify consistency with existing architecture, check feasibility | S2✅ | validated spec | —
+S4 | verify: confirm all requirements addressed, spec is self-contained, implementation-ready, testable | S3✅ | verified | —
+
+## Artifact Types
+
+**Technical Specification**: System context, use case model, interface contracts, data dictionaries, state machines, sequence flows.
+**Impact Analysis**: Affected components, breaking changes, migration paths, rollback strategy.
+**Integration Design**: API contracts, event schemas, data mapping, error handling, SLA commitments.
+**Requirements Traceability Matrix**: Business req → Functional req → Technical spec → Test case.
+
+Objective: {{objective}} Context: {{system_context}}

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vheins/local-memory-mcp",
-	"version": "0.15.1",
+	"version": "0.16.0",
 	"description": "MCP Local Memory Service for coding copilot agents",
 	"mcpName": "io.github.vheins/local-memory-mcp",
 	"type": "module",