@nano-step/skill-manager 5.5.3 → 5.6.1

package/skills/rri-t-testing/assets/rri-t-traceability-matrix.md

@@ -0,0 +1,105 @@
+# RRI-T Traceability Matrix
+
+**Feature:** {feature-name}
+**Date:** {YYYY-MM-DD}
+**Scope:** {scope-description}
+**Phase:** {current-phase}
+
+## Coverage Summary
+
+| Priority | Total Reqs | Covered | Percentage | Status |
+|----------|------------|---------|------------|--------|
+| P0 | {count} | {count} | {pct}% | PASS / CONCERNS / FAIL |
+| P1 | {count} | {count} | {pct}% | PASS / CONCERNS / FAIL |
+| P2 | {count} | {count} | {pct}% | PASS / CONCERNS / FAIL |
+| P3 | {count} | {count} | {pct}% | PASS / CONCERNS / FAIL |
+| **Total** | {count} | {count} | {pct}% | {status} |
+
+### Status Thresholds
+
+| Status | P0 | P1 | Overall |
+|--------|----|----|---------|
+| PASS | 100% | >= 90% | >= 80% |
+| CONCERNS | 100% | 80-89% | 70-79% |
+| FAIL | < 100% | < 80% | < 70% |
+
+---
+
+## Detailed Traceability
+
+### P0 Requirements (Critical)
+
+| Req ID | Requirement | Test Cases | Coverage | Result |
+|--------|-------------|------------|----------|--------|
+| REQ-001 | User can login with valid credentials | TC-001, TC-002 | FULL | PASS |
+| REQ-002 | Data persists after session timeout | TC-003 | FULL | PASS |
+| REQ-003 | Payment transactions are atomic | TC-004, TC-005, TC-006 | FULL | FAIL |
+| REQ-004 | | | | |
+| REQ-005 | | | | |
+
+### P1 Requirements (Major)
+
+| Req ID | Requirement | Test Cases | Coverage | Result |
+|--------|-------------|------------|----------|--------|
+| REQ-101 | Search supports Vietnamese diacritics | TC-101 | FULL | PASS |
+| REQ-102 | Offline changes sync within 60s | TC-102, TC-103 | PARTIAL | CONCERNS |
+| REQ-103 | Role changes take effect immediately | | NONE | MISSING |
+| REQ-104 | | | | |
+| REQ-105 | | | | |
+
+### P2 Requirements (Minor)
+
+| Req ID | Requirement | Test Cases | Coverage | Result |
+|--------|-------------|------------|----------|--------|
+| REQ-201 | | | | |
+| REQ-202 | | | | |
+| REQ-203 | | | | |
+
+### P3 Requirements (Trivial)
+
+| Req ID | Requirement | Test Cases | Coverage | Result |
+|--------|-------------|------------|----------|--------|
+| REQ-301 | | | | |
+| REQ-302 | | | | |
+
+---
+
+## Coverage Legend
+
+| Coverage | Definition |
+|----------|------------|
+| FULL | All acceptance criteria have test cases |
+| PARTIAL | Some acceptance criteria have test cases |
+| NONE | No test cases mapped to requirement |
+
+---
+
+## Gap Prioritization
+
+| Gap # | Requirement | Priority | Risk | Recommendation |
+|-------|-------------|----------|------|----------------|
+| GAP-1 | REQ-103: Role changes take effect immediately | P1 | HIGH | Add TC for role revocation mid-session |
+| GAP-2 | REQ-102: Offline sync (partial coverage) | P1 | MEDIUM | Add TC for 50+ pending changes |
+| GAP-3 | | | | |
+| GAP-4 | | | | |
+| GAP-5 | | | | |
+
+### Gap Severity
+
+| Severity | Definition |
+|----------|------------|
+| CRITICAL | P0 requirement with NONE or PARTIAL coverage |
+| HIGH | P1 requirement with NONE coverage |
+| MEDIUM | P1 requirement with PARTIAL coverage |
+| LOW | P2/P3 requirement with NONE or PARTIAL coverage |
+
+---
+
+## Summary
+
+- **Total Requirements:** {count}
+- **Fully Covered:** {count} ({pct}%)
+- **Partially Covered:** {count} ({pct}%)
+- **Not Covered:** {count} ({pct}%)
+- **Critical Gaps:** {count}
+- **High Gaps:** {count}

package/skills/rri-t-testing/skill.json

@@ -0,0 +1,9 @@
+{
+  "name": "rri-t-testing",
+  "version": "2.0.0",
+  "description": "RRI-T v2: Rapid Risk-Informed Testing with BMAD-enhanced risk scoring, traceability, quality gates, and nano-brain memory persistence",
+  "compatibility": "OpenCode",
+  "agent": null,
+  "commands": [],
+  "tags": ["testing", "qa", "rri-t", "release-gates", "test-cases", "risk-scoring", "traceability", "bmad", "nano-brain"]
+}

package/skills/skill-management/references/tool-categories.md

@@ -145,6 +145,58 @@ Notes:
 - Tools require a page context; select or create a page first.
 - Prefer take_snapshot for element discovery before click/hover/drag.
 
+## Memory & Knowledge Category (Example)
+
+Category name: Memory & Knowledge
+Keywords: memory, search, recall, context, session, codebase, knowledge, symbol, impact, dependency, graph, focus
+Description: Persistent memory, hybrid search, code intelligence, and cross-repo symbol analysis via nano-brain.
+
+Example tools that might appear in this category:
+- memory_search
+  - BM25 full-text keyword search across indexed documents.
+- memory_vsearch
+  - Semantic vector search using embeddings.
+- memory_query
+  - Full hybrid search with query expansion, RRF fusion, and LLM reranking.
+- memory_get
+  - Retrieve a document by path or docid.
+- memory_multi_get
+  - Batch retrieve documents by glob pattern or comma-separated list.
+- memory_write
+  - Write content to daily log with workspace context.
+- memory_set
+  - Set/update a keyed memory (overwrites previous value).
+- memory_delete
+  - Delete a keyed memory.
+- memory_keys
+  - List all keyed memories.
+- memory_status
+  - Show index health, collection info, and model status.
+- memory_index_codebase
+  - Index codebase files in the current workspace.
+- memory_update
+  - Trigger immediate reindex of all collections.
+- memory_focus
+  - Get dependency graph context for a specific file.
+- memory_graph_stats
+  - Get statistics about the file dependency graph.
+- memory_symbols
+  - Query cross-repo symbols (Redis keys, PubSub channels, MySQL tables, API endpoints, HTTP calls, Bull queues).
+- memory_impact
+  - Analyze cross-repo impact of a symbol (writers vs readers, publishers vs subscribers).
+- code_context
+  - 360-degree view of a code symbol — callers, callees, cluster, flows, infrastructure connections.
+- code_impact
+  - Analyze impact of changing a symbol — upstream/downstream dependencies, affected flows, risk level.
+- code_detect_changes
+  - Detect changed symbols and affected flows from git diff.
+
+Notes:
+- Memory tools require nano-brain MCP server to be configured.
+- Code intelligence tools require prior indexing via memory_index_codebase.
+- Use memory_query for best quality results (combines BM25 + vector + reranking).
+- Use memory_search for exact keyword matches, memory_vsearch for conceptual search.
+
 ## GitHub Operations Category (Example)
 
 Category name: GitHub Operations
@@ -220,13 +272,18 @@ Example tools that might appear in this category:
 ## Category Boundary Examples
 Use these to avoid misclassification:
 - "take a screenshot" -> Browser Automation
+- "recall past decisions" -> Memory & Knowledge
 - "list pull requests" -> GitHub Operations
 - "list graphql queries" -> GraphQL Introspection
 - "find docs for lodash" -> Documentation Lookup
+- "what calls this function" -> Memory & Knowledge
+- "search past sessions" -> Memory & Knowledge
 
 ## Common Intent Phrases by Category
 Browser intents:
 - "click", "hover", "fill form", "upload file", "take snapshot"
+Memory intents:
+- "recall", "remember", "past session", "what did we do", "search memory", "save decision", "code context", "impact analysis", "what calls", "dependency graph"
 GitHub intents:
 - "get PR", "list issues", "search repo", "read file"
 GraphQL intents:
@@ -242,6 +299,7 @@ Docs intents:
 
 ## Category Ownership Notes (Semantic Only)
 - Browser Automation: runtime web UI interaction and diagnostics.
+- Memory & Knowledge: persistent cross-session memory, hybrid search, code intelligence, and cross-repo symbol analysis.
 - GitHub Operations: repository metadata and collaboration artifacts.
 - GraphQL Introspection: schema discovery and field metadata only.
 - Documentation Lookup: documentation discovery and lookup.