@nano-step/skill-manager 5.0.0 → 5.1.0

package/dist/utils.d.ts

@@ -1,4 +1,4 @@
-export declare const MANAGER_VERSION = "5.0.0";
+export declare const MANAGER_VERSION = "5.1.0";
 export interface SkillManifest {
     name: string;
     version: string;

package/dist/utils.js

@@ -13,7 +13,7 @@ exports.writeText = writeText;
 const path_1 = __importDefault(require("path"));
 const os_1 = __importDefault(require("os"));
 const fs_extra_1 = __importDefault(require("fs-extra"));
-exports.MANAGER_VERSION = "5.0.0";
+exports.MANAGER_VERSION = "5.1.0";
 async function detectOpenCodePaths() {
     const homeConfig = path_1.default.join(os_1.default.homedir(), ".config", "opencode");
     const cwd = process.cwd();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nano-step/skill-manager",
-  "version": "5.0.0",
+  "version": "5.1.0",
   "description": "CLI tool that installs and manages AI agent skills, MCP tool routing, and workflow configurations.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -19,6 +19,8 @@
   "keywords": [
     "nano-step",
     "opencode",
+    "skill",
+    "skill-manager",
     "mcp",
     "model-context-protocol",
     "ai",

package/skills/rri-t-testing/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: rri-t-testing
+description: RRI-T QA methodology skill. Execute 5-phase testing: PREPARE, DISCOVER, STRUCTURE, EXECUTE, ANALYZE. Use before release, creating test cases, or QA review.
+---
+
+# RRI-T Testing Skill
+
+Execute comprehensive QA testing using Reverse Requirements Interview - Testing methodology.
+
+## When to Use
+
+- Testing any feature before release
+- Creating test cases for new features
+- Performing thorough QA review
+- Running stress tests and edge case analysis
+
+## Input
+
+| Param | Req | Description |
+|-------|-----|-------------|
+| feature | Yes | Feature name in kebab-case |
+| phase | No | `prepare`, `discover`, `structure`, `execute`, `analyze` |
+| dimensions | No | `ui-ux,api,performance,security,data,infra,edge-cases` |
+
+## 5 Phases
+
+1. **PREPARE** — Read specs, setup output dir
+2. **DISCOVER** — Interview 5 personas for test scenarios
+3. **STRUCTURE** — Format as Q-A-R-P-T test cases
+4. **EXECUTE** — Run tests, capture screenshots
+5. **ANALYZE** — Calculate coverage, apply release gates
+
+## Output
+
+```
+/ai/test-case/rri-t/{feature-name}/
+├── 01-prepare.md
+├── 02-discover.md
+├── 03-structure.md
+├── 04-execute.md
+├── 05-analyze.md
+└── summary.md
+```
+
+## Templates
+
+Use templates bundled in `assets/` directory of this skill:
+- `rri-t-persona-interview.md` — Persona interviews
+- `rri-t-test-case.md` — Q-A-R-P-T format
+- `rri-t-coverage-dashboard.md` — 7-dimension tracking
+- `rri-t-stress-matrix.md` — 8-axis stress testing
+
+## 7 Dimensions
+
+UI/UX | API | Performance | Security | Data Integrity | Infrastructure | Edge Cases
+
+## 5 Personas
+
+End User | Business Analyst | QA Destroyer | DevOps Tester | Security Auditor
+
+## Release Gates
+
+| GO | NO-GO |
+|----|-------|
+| All 7 dims >= 70% | Any dim < 50% |
+| 5/7 >= 85% | >2 P0 FAILs |
+| Zero P0 FAIL | Critical MISSING |
+
+## Guardrails
+
+1. Test all 7 dimensions
+2. Use all 5 personas
+3. Document everything
+4. PAINFUL is valid (not failure)
+5. Follow release gates
+6. Test Vietnamese locale

package/skills/rri-t-testing/assets/rri-t-coverage-dashboard.md

@@ -0,0 +1,101 @@
+# RRI-T Coverage Dashboard — {feature_name}
+
+Feature: {feature_name}
+Date: {date}
+Release Gate Status: {release_gate_status}
+Release Version: {release_version}
+Owner: {owner}
+Prepared By: {prepared_by}
+
+## Release Gate Criteria
+
+| Rule | Criteria | Status |
+| --- | --- | --- |
+| RG-1 | All 7 dimensions >= 70% coverage | {rg1_status} |
+| RG-2 | At least 5/7 dimensions >= 85% coverage | {rg2_status} |
+| RG-3 | Zero P0 items in FAIL state | {rg3_status} |
+
+## Dimension Coverage
+
+| Dimension | Total | PASS | FAIL | PAINFUL | MISSING | Coverage % | Gate |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| D1: UI/UX | {d1_total} | {d1_pass} | {d1_fail} | {d1_painful} | {d1_missing} | {d1_coverage} | {d1_gate} |
+| D2: API | {d2_total} | {d2_pass} | {d2_fail} | {d2_painful} | {d2_missing} | {d2_coverage} | {d2_gate} |
+| D3: Performance | {d3_total} | {d3_pass} | {d3_fail} | {d3_painful} | {d3_missing} | {d3_coverage} | {d3_gate} |
+| D4: Security | {d4_total} | {d4_pass} | {d4_fail} | {d4_painful} | {d4_missing} | {d4_coverage} | {d4_gate} |
+| D5: Data Integrity | {d5_total} | {d5_pass} | {d5_fail} | {d5_painful} | {d5_missing} | {d5_coverage} | {d5_gate} |
+| D6: Infrastructure | {d6_total} | {d6_pass} | {d6_fail} | {d6_painful} | {d6_missing} | {d6_coverage} | {d6_gate} |
+| D7: Edge Cases | {d7_total} | {d7_pass} | {d7_fail} | {d7_painful} | {d7_missing} | {d7_coverage} | {d7_gate} |
+
+Legend: ✅ PASS | ❌ FAIL | ⚠️ PAINFUL | ☐ MISSING
+
+## Priority Breakdown
+
+| Priority | Total | PASS | FAIL | PAINFUL | MISSING | Coverage % | Gate |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| P0 | {p0_total} | {p0_pass} | {p0_fail} | {p0_painful} | {p0_missing} | {p0_coverage} | {p0_gate} |
+| P1 | {p1_total} | {p1_pass} | {p1_fail} | {p1_painful} | {p1_missing} | {p1_coverage} | {p1_gate} |
+| P2 | {p2_total} | {p2_pass} | {p2_fail} | {p2_painful} | {p2_missing} | {p2_coverage} | {p2_gate} |
+| P3 | {p3_total} | {p3_pass} | {p3_fail} | {p3_painful} | {p3_missing} | {p3_coverage} | {p3_gate} |
+
+## Summary Metrics
+
+- Total Test Cases: {total_tc}
+- Overall Coverage %: {overall_coverage}
+- Dimensions Passing Gate: {dimensions_passing_gate}
+- P0 FAIL Count: {p0_fail_count}
+- P0 PAINFUL Count: {p0_painful_count}
+- MISSING Count: {missing_count}
+- Latest Update: {latest_update}
+- Notes: {summary_notes}
+- Risks: {summary_risks}
+
+## FAIL Items
+
+| TC ID | Priority | Dimension | Description | Assigned To |
+| --- | --- | --- | --- | --- |
+| {fail_tc_id_1} | {fail_priority_1} | {fail_dimension_1} | {fail_description_1} | {fail_assigned_to_1} |
+| {fail_tc_id_2} | {fail_priority_2} | {fail_dimension_2} | {fail_description_2} | {fail_assigned_to_2} |
+| {fail_tc_id_3} | {fail_priority_3} | {fail_dimension_3} | {fail_description_3} | {fail_assigned_to_3} |
+| {fail_tc_id_4} | {fail_priority_4} | {fail_dimension_4} | {fail_description_4} | {fail_assigned_to_4} |
+| {fail_tc_id_5} | {fail_priority_5} | {fail_dimension_5} | {fail_description_5} | {fail_assigned_to_5} |
+
+## PAINFUL Items
+
+| TC ID | Priority | Dimension | Description | UX Impact |
+| --- | --- | --- | --- | --- |
+| {painful_tc_id_1} | {painful_priority_1} | {painful_dimension_1} | {painful_description_1} | {painful_ux_impact_1} |
+| {painful_tc_id_2} | {painful_priority_2} | {painful_dimension_2} | {painful_description_2} | {painful_ux_impact_2} |
+| {painful_tc_id_3} | {painful_priority_3} | {painful_dimension_3} | {painful_description_3} | {painful_ux_impact_3} |
+| {painful_tc_id_4} | {painful_priority_4} | {painful_dimension_4} | {painful_description_4} | {painful_ux_impact_4} |
+| {painful_tc_id_5} | {painful_priority_5} | {painful_dimension_5} | {painful_description_5} | {painful_ux_impact_5} |
+
+## MISSING Items
+
+| TC ID | Priority | Dimension | Description | User Need |
+| --- | --- | --- | --- | --- |
+| {missing_tc_id_1} | {missing_priority_1} | {missing_dimension_1} | {missing_description_1} | {missing_user_need_1} |
+| {missing_tc_id_2} | {missing_priority_2} | {missing_dimension_2} | {missing_description_2} | {missing_user_need_2} |
+| {missing_tc_id_3} | {missing_priority_3} | {missing_dimension_3} | {missing_description_3} | {missing_user_need_3} |
+| {missing_tc_id_4} | {missing_priority_4} | {missing_dimension_4} | {missing_description_4} | {missing_user_need_4} |
+| {missing_tc_id_5} | {missing_priority_5} | {missing_dimension_5} | {missing_description_5} | {missing_user_need_5} |
+
+## Regression Test List
+
+| Test ID | Title | Dimension | Priority | Status |
+| --- | --- | --- | --- | --- |
+| {regression_id_1} | {regression_title_1} | {regression_dimension_1} | {regression_priority_1} | {regression_status_1} |
+| {regression_id_2} | {regression_title_2} | {regression_dimension_2} | {regression_priority_2} | {regression_status_2} |
+| {regression_id_3} | {regression_title_3} | {regression_dimension_3} | {regression_priority_3} | {regression_status_3} |
+| {regression_id_4} | {regression_title_4} | {regression_dimension_4} | {regression_priority_4} | {regression_status_4} |
+| {regression_id_5} | {regression_title_5} | {regression_dimension_5} | {regression_priority_5} | {regression_status_5} |
+
+## Sign-off
+
+| Role | Name | Decision | Notes |
+| --- | --- | --- | --- |
+| QA Lead | {qa_lead_name} | {qa_lead_decision} | {qa_lead_notes} |
+| Dev Lead | {dev_lead_name} | {dev_lead_decision} | {dev_lead_notes} |
+| Product | {product_name} | {product_decision} | {product_notes} |
+
+Decision Legend: {approve_label}/{reject_label}

package/skills/rri-t-testing/assets/rri-t-persona-interview.md

@@ -0,0 +1,226 @@
+# RRI-T Persona Interview — {Feature Name}
+
+**Feature:** {feature-name}
+**Date:** {YYYY-MM-DD}
+**Interviewer:** {agent/person}
+
+## Interview Summary
+| Persona | Questions Generated | Key Concerns |
+|---------|-------------------|--------------|
+| End User | 0/25 | |
+| Business Analyst | 0/25 | |
+| QA Destroyer | 0/25 | |
+| DevOps Tester | 0/25 | |
+| Security Auditor | 0/25 | |
+| **Total** | **0/125** | |
+
+---
+
+## Persona 1: End User (Người dùng cuối)
+
+### Context
+As a household member using {feature-name} daily to manage my family's shared resources, I need the feature to work reliably across different devices, network conditions, and usage patterns. I care about speed, clarity, and not losing my work.
+
+### Questions
+1. What happens when I add an inventory item while my phone has weak 3G signal?
+2. What happens when I start editing a shopping list on mobile, then switch to desktop mid-task?
+3. What happens when I search for "nguyen" but the item name is "Nguyễn Văn A"?
+4. What happens when I accidentally navigate away from a half-filled form?
+5. What happens when I try to delete an item that another household member is currently editing?
+6. What happens when I upload a photo of a receipt and the file is 10MB?
+7. What happens when I filter 500+ inventory items by expiration date on a mid-range phone?
+8. What happens when I receive a phone call while recording a voice note for a meal plan?
+9. What happens when the app shows "1,000,000đ" instead of "1.000.000đ" for Vietnamese currency?
+10. What happens when I'm offline for 2 days and then reconnect with 50 pending changes?
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 2: Business Analyst (Phân tích nghiệp vụ)
+
+### Context
+As someone responsible for ensuring business rules are correctly implemented, I need to verify that household permissions, data ownership, financial calculations, and multi-household scenarios work as specified. I care about data consistency and rule enforcement.
+
+### Questions
+1. What happens when a household member with "viewer" role tries to delete an inventory item?
+2. What happens when a user belongs to 3 households and switches between them rapidly?
+3. What happens when two members simultaneously mark the same shopping list item as "purchased"?
+4. What happens when a household admin removes a member who has pending edits?
+5. What happens when the total expense calculation includes items in different currencies (VND and USD)?
+6. What happens when a recurring meal plan conflicts with a one-time event on the same date?
+7. What happens when a user tries to share an inventory item with a household they don't belong to?
+8. What happens when the system calculates "items expiring in 3 days" across different timezones?
+9. What happens when a household reaches the maximum allowed inventory items (if there's a limit)?
+10. What happens when a deleted household still has active shopping lists in other members' offline caches?
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 3: QA Destroyer (Phá hoại viên QA)
+
+### Context
+As someone whose job is to break things, I need to find every edge case, race condition, and unexpected input that could crash the system or corrupt data. I care about boundary conditions, malformed inputs, and timing attacks.
+
+### Questions
+1. What happens when I paste 50,000 characters into the "item name" field?
+2. What happens when I rapidly click "save" 20 times in 1 second?
+3. What happens when I set my device date to 2099 and create an inventory item?
+4. What happens when I upload a file named `"; DROP TABLE inventory; --"` as an item photo?
+5. What happens when I create an item with expiration date "yesterday" and quantity "-5"?
+6. What happens when I open the app in 10 browser tabs and edit the same item in all of them?
+7. What happens when I force-kill the app during a GraphQL mutation?
+8. What happens when I inject `<script>alert('xss')</script>` into a meal plan description?
+9. What happens when I create a circular dependency (Item A requires Item B, Item B requires Item A)?
+10. What happens when I change my device timezone mid-session and create a timestamped event?
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 4: DevOps Tester (Kiểm thử hạ tầng)
+
+### Context
+As someone responsible for deployment, monitoring, and infrastructure reliability, I need to verify that the feature works under load, handles server restarts gracefully, and doesn't leak resources. I care about scalability, observability, and recovery.
+
+### Questions
+1. What happens when the GraphQL server restarts while a user is mid-sync?
+2. What happens when 100 users simultaneously bulk-import 500 inventory items each?
+3. What happens when the database connection pool is exhausted during peak usage?
+4. What happens when the CDN serving item photos goes down?
+5. What happens when a GraphQL query takes longer than the 30-second timeout?
+6. What happens when the Redis cache is cleared while users have active sessions?
+7. What happens when a deployment rolls out a new schema version while old clients are still connected?
+8. What happens when disk space runs out during a photo upload?
+9. What happens when the monitoring system detects 500 errors but the app still appears functional?
+10. What happens when a user's offline queue grows to 1000+ pending mutations?
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 5: Security Auditor (Kiểm toán bảo mật)
+
+### Context
+As someone responsible for security compliance, I need to verify that authentication, authorization, data exposure, and audit trails are properly implemented. I care about access control, data leakage, and attack surface.
+
+### Questions
+1. What happens when a user's JWT token expires mid-session?
+2. What happens when a user tries to access another household's data by guessing the household ID?
+3. What happens when a removed household member still has cached data on their device?
+4. What happens when someone intercepts the GraphQL request and replays it with modified variables?
+5. What happens when a user tries to upload a malicious file disguised as an image?
+6. What happens when the audit log shows who deleted an item, but the user claims they didn't?
+7. What happens when a user shares their session token with someone outside the household?
+8. What happens when someone uses SQL injection in a search query (even though it's GraphQL)?
+9. What happens when a user's password is compromised and they don't realize it for 3 days?
+10. What happens when the system logs sensitive data (like financial amounts) in plain text?
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Raw Test Ideas (Consolidated)
+| # | Idea | Source Persona | Potential Dimension | Priority Estimate |
+|---|------|---------------|--------------------|--------------------|
+| 1 | | | | |
+| 2 | | | | |
+| 3 | | | | |
+| 4 | | | | |
+| 5 | | | | |
+| 6 | | | | |
+| 7 | | | | |
+| 8 | | | | |
+| 9 | | | | |
+| 10 | | | | |
+| 11 | | | | |
+| 12 | | | | |
+| 13 | | | | |
+| 14 | | | | |
+| 15 | | | | |
+| 16 | | | | |
+| 17 | | | | |
+| 18 | | | | |
+| 19 | | | | |
+| 20 | | | | |

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

@@ -0,0 +1,100 @@
+# RRI-T Stress Matrix Template
+
+## Feature
+- Name: <feature-name>
+- Owner: <owner>
+- Date: <yyyy-mm-dd>
+- Build/Release: <build-id>
+- Environment: <dev/staging/prod>
+
+## Summary
+This template covers RRI-T 8-axis stress testing for a household management app
+(inventory, meal planning, shopping lists, finances).
+
+## Stress Axes Summary
+| Axis | Name | Focus | Notes |
+| --- | --- | --- | --- |
+| 1 | TIME | Deadlines, bulk ops, timeouts | Burst actions, long-running jobs |
+| 2 | DATA | 1000+ rows, search/filter speed | Large inventory, long history |
+| 3 | ERROR | Undo/redo, auto-save recovery, messages | Resilience, recoverability |
+| 4 | COLLAB | Concurrent editing, conflicts, multi-user | Household members overlap |
+| 5 | EMERGENCY | Interruptions, crash recovery | Browser/device failures |
+| 6 | SECURITY | Access revocation, audit logs, session expiry | Role changes, expiring auth |
+| 7 | INFRA | Server crash, RTO<15m, RPO<5m, offline | Service resilience |
+| 8 | LOCALE | Vietnamese diacritics, VND, GMT+7, overflow | Local UX correctness |
+
+## Axis Combination Matrix (Test Where X)
+| Axis | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| 1 TIME | - | X | X | X | X | X | X | X |
+| 2 DATA | X | - | X | X |  | X | X | X |
+| 3 ERROR | X | X | - | X | X |  | X | X |
+| 4 COLLAB | X | X | X | - |  | X |  | X |
+| 5 EMERGENCY | X |  | X |  | - | X | X |  |
+| 6 SECURITY | X | X |  | X | X | - | X | X |
+| 7 INFRA | X | X | X |  | X | X | - | X |
+| 8 LOCALE | X | X | X | X |  | X | X | - |
+
+## Stress Scenarios
+
+### Axis 1: TIME
+| # | Scenario | Steps | Expected | Priority |
+| --- | --- | --- | --- | --- |
+| S-TIME-001 | Bulk add 500 pantry items before dinner | Start timer 2 min, import CSV of pantry items | Import completes, progress visible, no timeout | P1 |
+| S-TIME-002 | Rapid meal plan edits during 10-min window | Update 10 meals in 60s, save each | Saves succeed, no stale data, UI responsive | P1 |
+| S-TIME-003 | Shopping list sync under poor network | Add 30 items quickly, toggle offline/online | Sync resolves within 60s, no duplicates | P2 |
+| S-TIME-004 | Finance entry auto-save timeout | Create expense, wait 45s idle, resume edit | Auto-save persists, no data loss | P2 |
+
+### Axis 2: DATA
+| # | Scenario | Steps | Expected | Priority |
+| S-DATA-001 | Inventory list 1000+ items | Load inventory with 1200 items | Scroll, search, filter remain under 2s | P1 |
+| S-DATA-002 | Shopping history filter speed | Filter 800 past purchases by category | Results appear under 2s, no UI freeze | P2 |
+| S-DATA-003 | Meal plan calendar 6 months | Open 6-month plan view with 180 entries | Render within 3s, no layout shift | P2 |
+| S-DATA-004 | Finance ledger export 2000 rows | Export 2k ledger rows to CSV | Export completes, file accurate | P2 |
+
+### Axis 3: ERROR
+| # | Scenario | Steps | Expected | Priority |
+| S-ERROR-001 | Undo/redo inventory quantity changes | Change item qty 5 times, undo 5, redo 5 | Exact state restored each step | P1 |
+| S-ERROR-002 | Auto-save recovery after crash | Edit meal notes, force close tab, reopen | Draft restored with last autosave | P1 |
+| S-ERROR-003 | Validation error messages | Add expense with negative value | Clear inline error, no save | P2 |
+| S-ERROR-004 | Failed bulk import rollback | Import malformed CSV for pantry | No partial data, error list shown | P1 |
+
+### Axis 4: COLLAB
+| # | Scenario | Steps | Expected | Priority |
+| S-COLLAB-001 | Two users edit shopping list | User A adds 5 items, User B deletes 2 | Conflict warning, final list consistent | P1 |
+| S-COLLAB-002 | Concurrent budget updates | Two users change monthly budget | Latest change prompts merge dialog | P2 |
+| S-COLLAB-003 | Shared meal plan edit | User A updates recipe, User B updates servings | Both changes applied without loss | P2 |
+| S-COLLAB-004 | New member joins household | Invite new user during active edits | New user sees updated list | P3 |
+
+### Axis 5: EMERGENCY
+| # | Scenario | Steps | Expected | Priority |
+| S-EMERGENCY-001 | Browser crash while editing | Edit grocery item notes, kill browser | Reopen, draft restored | P1 |
+| S-EMERGENCY-002 | Power loss during bulk update | Start bulk pantry update, go offline | Partial changes queued or rolled back | P1 |
+| S-EMERGENCY-003 | Device sleep mid-sync | Start sync, close laptop lid | Resume sync without duplication | P2 |
+| S-EMERGENCY-004 | App reload mid-transaction | Save expense, hit refresh instantly | No double charge, one entry saved | P2 |
+
+### Axis 6: SECURITY
+| # | Scenario | Steps | Expected | Priority |
+| S-SECURITY-001 | Access revoked during edit | Admin removes user role mid-edit | User warned, changes blocked, data safe | P1 |
+| S-SECURITY-002 | Session expiry while shopping | Session expires, user adds item | Redirect to login, item queued | P1 |
+| S-SECURITY-003 | Audit log for finance edits | Edit expense amount | Audit entry with user, time, change | P2 |
+| S-SECURITY-004 | Private list access attempt | Non-member tries to open list | Access denied, no data leak | P1 |
+
+### Axis 7: INFRA
+| # | Scenario | Steps | Expected | Priority |
+| S-INFRA-001 | Server crash during sync | Trigger sync, kill server | Retry logic, no data loss | P1 |
+| S-INFRA-002 | RTO < 15m recovery | Simulate outage, restore service | Service back within 15m, status updated | P1 |
+| S-INFRA-003 | RPO < 5m data recovery | Create 3 entries, failover | Max 5m data loss, latest persists | P1 |
+| S-INFRA-004 | Offline mode for shopping list | Go offline, add 10 items | Local cache used, sync on reconnect | P2 |
+
+### Axis 8: LOCALE
+| # | Scenario | Steps | Expected | Priority |
+| S-LOCALE-001 | Diacritic-insensitive search | Search "nguyen" in household members | Finds "Nguyễn" matches | P1 |
+| S-LOCALE-002 | VND currency formatting | View finance summary | Shows "1.000.000đ" not "1,000,000" | P1 |
+| S-LOCALE-003 | Vietnamese text overflow | Open long Vietnamese recipe names | No overflow, wraps cleanly | P2 |
+| S-LOCALE-004 | Date format DD/MM/YYYY | View meal plan date header | Displays DD/MM/YYYY | P1 |
+
+## Notes
+- Attach logs, screenshots, and timings for any P1 or P2 failures.
+- Capture device, OS, browser, and network conditions.
+- Link to any incident or bug IDs created from results.

package/skills/rri-t-testing/assets/rri-t-test-case.md

@@ -0,0 +1,155 @@
+# RRI-T Test Cases — {Feature Name}
+
+**Feature:** {feature-name}
+**Generated from:** Persona Interview ({date})
+**Total Test Cases:** {count}
+
+## Priority Distribution
+| Priority | Count | Description |
+|----------|-------|-------------|
+| P0 | 0 | Critical — blocks release |
+| P1 | 0 | Major — fix before release |
+| P2 | 0 | Minor — next sprint |
+| P3 | 0 | Trivial — backlog |
+
+## Dimension Distribution
+| Dimension | Count | Target Coverage |
+|-----------|-------|----------------|
+| D1: UI/UX | 0 | >= 85% |
+| D2: API | 0 | >= 85% |
+| D3: Performance | 0 | >= 70% |
+| D4: Security | 0 | >= 85% |
+| D5: Data Integrity | 0 | >= 85% |
+| D6: Infrastructure | 0 | >= 70% |
+| D7: Edge Cases | 0 | >= 85% |
+
+---
+
+## Test Cases
+
+### TC-RRI-{FEATURE}-001
+- **Q (Question):** As an end user, what happens when I add an inventory item while on a weak 3G connection?
+- **A (Answer):** The item should be saved locally immediately, show a "syncing" indicator, and sync to the server when connection improves. No data loss should occur.
+- **R (Requirement):** REQ-OFFLINE-001: App must support offline-first operations with automatic sync
+- **P (Priority):** P0
+- **T (Test Case):**
+  - **Preconditions:** 
+    - User logged in to household
+    - Device has weak 3G connection (simulated: 500ms latency, 50% packet loss)
+    - At least 1 existing inventory item for comparison
+  - **Steps:**
+    1. Navigate to Inventory screen
+    2. Tap "Add Item" button
+    3. Fill in: Name "Gạo ST25", Quantity "5", Unit "kg", Expiration "2026-03-15"
+    4. Tap "Save"
+    5. Observe UI feedback
+    6. Wait 30 seconds
+    7. Check item appears in inventory list
+    8. Restore normal network connection
+    9. Wait for sync indicator to complete
+    10. Verify item exists on server (check from another device)
+  - **Expected Result:** 
+    - Item appears in list immediately with "syncing" badge
+    - No error message shown
+    - After network restores, item syncs successfully
+    - Item visible from other devices within 5 seconds of sync
+  - **Dimension:** D3: Performance
+  - **Stress Axis:** TIME, INFRA
+  - **Source Persona:** End User
+- **Result:** ✅ PASS
+- **Notes:** Tested on iPhone 12 with Network Link Conditioner. Sync completed in 3.2s after network restored.
+
+---
+
+### TC-RRI-{FEATURE}-002
+- **Q (Question):** As a business analyst, what happens when a household member with "viewer" role tries to delete an inventory item?
+- **A (Answer):** The delete button should be hidden or disabled for viewers. If they somehow trigger a delete (via API manipulation), the server should reject it with a 403 Forbidden error.
+- **R (Requirement):** REQ-RBAC-003: Viewers can only read data, not modify or delete
+- **P (Priority):** P1
+- **T (Test Case):**
+  - **Preconditions:**
+    - User "viewer@example.com" has "viewer" role in household "Test Family"
+    - Household has inventory item "Sữa tươi" (ID: inv_123)
+    - User logged in on mobile app
+  - **Steps:**
+    1. Login as viewer@example.com
+    2. Navigate to Inventory screen
+    3. Tap on "Sữa tươi" item to view details
+    4. Look for delete button/option
+    5. (If delete button exists) Attempt to tap it
+    6. (Alternative) Use GraphQL client to send deleteInventoryItem mutation directly
+  - **Expected Result:**
+    - Delete button should not be visible in UI
+    - If mutation sent directly, server returns error: `{"errors": [{"message": "Forbidden: insufficient permissions", "extensions": {"code": "FORBIDDEN"}}]}`
+    - Item remains in database unchanged
+  - **Dimension:** D4: Security
+  - **Stress Axis:** SECURITY
+  - **Source Persona:** Business Analyst
+- **Result:** ⚠️ PAINFUL
+- **Notes:** Delete button is correctly hidden, but when mutation sent via GraphQL Playground, error message is generic "Unauthorized" instead of specific "Forbidden: insufficient permissions". UX improvement: add clearer error messages for debugging. Item was NOT deleted (security works), but error clarity needs improvement.
+
+---
+
+### TC-RRI-{FEATURE}-003
+- **Q (Question):** As a QA destroyer, what happens when I paste 50,000 characters into the "item name" field?
+- **A (Answer):** The field should enforce a maximum length (e.g., 200 characters), truncate or reject input gracefully, and show a validation error. The app should not crash or freeze.
+- **R (Requirement):** REQ-VALIDATION-005: All text inputs must have reasonable length limits
+- **P (Priority):** P1
+- **T (Test Case):**
+  - **Preconditions:**
+    - User logged in
+    - On "Add Inventory Item" screen
+    - Clipboard contains 50,000-character string
+  - **Steps:**
+    1. Tap into "Item Name" field
+    2. Paste 50,000-character string
+    3. Observe UI behavior
+    4. Attempt to save the form
+  - **Expected Result:**
+    - Field truncates input to max length (200 chars) OR shows validation error
+    - UI remains responsive (no freeze)
+    - Save button disabled or shows error: "Item name too long (max 200 characters)"
+    - No crash or GraphQL error
+  - **Dimension:** D7: Edge Cases
+  - **Stress Axis:** DATA, ERROR
+  - **Source Persona:** QA Destroyer
+- **Result:** ☐ MISSING
+- **Notes:** Feature not yet implemented. Current behavior: field accepts all 50,000 characters, UI freezes for 2-3 seconds, GraphQL mutation fails with "Payload too large" error. Need to add client-side validation and maxLength attribute.
+
+---
+
+### TC-RRI-{FEATURE}-004
+- **Q (Question):** {From persona's perspective — what are they trying to do/verify?}
+- **A (Answer):** {Expected behavior — what SHOULD happen}
+- **R (Requirement):** {Requirement ID or description}
+- **P (Priority):** P0 | P1 | P2 | P3
+- **T (Test Case):**
+  - **Preconditions:** {required state}
+  - **Steps:**
+    1. {step 1}
+    2. {step 2}
+  - **Expected Result:** {specific, measurable outcome}
+  - **Dimension:** D{n}: {name}
+  - **Stress Axis:** {axis name} (if applicable)
+  - **Source Persona:** {persona name}
+- **Result:** ✅ PASS | ❌ FAIL | ⚠️ PAINFUL | ☐ MISSING
+- **Notes:** {observations, screenshots, bug IDs}
+
+---
+
+### TC-RRI-{FEATURE}-005
+- **Q (Question):** {From persona's perspective — what are they trying to do/verify?}
+- **A (Answer):** {Expected behavior — what SHOULD happen}
+- **R (Requirement):** {Requirement ID or description}
+- **P (Priority):** P0 | P1 | P2 | P3
+- **T (Test Case):**
+  - **Preconditions:** {required state}
+  - **Steps:**
+    1. {step 1}
+    2. {step 2}
+  - **Expected Result:** {specific, measurable outcome}
+  - **Dimension:** D{n}: {name}
+  - **Stress Axis:** {axis name} (if applicable)
+  - **Source Persona:** {persona name}
+- **Result:** ✅ PASS | ❌ FAIL | ⚠️ PAINFUL | ☐ MISSING
+- **Notes:** {observations, screenshots, bug IDs}

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

@@ -0,0 +1,9 @@
+{
+  "name": "rri-t-testing",
+  "version": "1.0.0",
+  "description": "RRI-T QA methodology — 5-phase testing (PREPARE, DISCOVER, STRUCTURE, EXECUTE, ANALYZE) with 7 dimensions, 5 personas, and release gates",
+  "compatibility": "OpenCode",
+  "agent": null,
+  "commands": [],
+  "tags": ["testing", "qa", "rri-t", "release-gates", "test-cases"]
+}

package/skills/skill-management/assets/tools-template.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Agent Skill Tools Cache v2.0.0",
-  "description": "Cache file for MCP tool routing. Generated by /agent-skill-refresh command using semantic AI categorization.",
+  "description": "Cache file for tool routing. Generated by /skill-refresh command using semantic AI categorization.",
   "type": "object",
   "properties": {
     "version": {

package/skills/skill-management/assets/workflow-schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Agent Skill Workflow Definition",
-  "description": "Schema for defining prerequisite workflows in Agent Skill Manager",
+  "description": "Schema for defining prerequisite workflows in Skill Manager",
   "type": "object",
   "properties": {
     "enabled": {

package/skills/skill-management/references/error-handling.md

@@ -12,7 +12,7 @@
 
 ## Automatic Retry Mechanism
 
-The agent-skill-manager automatically retries failed tool executions before returning errors.
+The skill-manager automatically retries failed tool executions before returning errors.
 
 ### Retry Configuration
 - Maximum attempts: 3
@@ -67,7 +67,7 @@ Template:
 ```
 Error: Tool not found: <tool-id>
 Suggestions: <tool-a>, <tool-b>, <tool-c>
-Next: confirm the intended tool or run /agent-skill-refresh.
+Next: confirm the intended tool or run /skill-refresh.
 ```
 
 ## Execution Failure Handling
@@ -113,18 +113,18 @@ Next: confirm retry with new parameters
 
 ## Cache Missing Recovery
 Symptoms:
-- `.opencode/agent-skill-tools.json` missing.
+- `.opencode/skill-tools.json` missing.
 - Cache file invalid or unreadable.
 
 Recovery steps:
 1. Inform that cache is missing or invalid.
-2. Recommend /agent-skill-refresh to regenerate.
+2. Recommend /skill-refresh to regenerate.
 3. Proceed with dynamic tool discovery if possible.
 
 Template:
 ```
-Cache missing or invalid at .opencode/agent-skill-tools.json
-Suggestion: run /agent-skill-refresh
+Cache missing or invalid at .opencode/skill-tools.json
+Suggestion: run /skill-refresh
 Fallback: dynamic discovery enabled
 ```
 
@@ -247,7 +247,7 @@ Decision tree (text form):
    - Yes -> request corrected params.
    - No -> continue.
 5. Is cache missing?
-   - Yes -> recommend /agent-skill-refresh and use dynamic discovery.
+   - Yes -> recommend /skill-refresh and use dynamic discovery.
    - No -> continue.
 6. Unknown failure
    - Provide generic error template and ask for clarification.

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

@@ -6,7 +6,7 @@
 
 This skill uses **semantic categorization**:
 
-1. **Tool discovery** - `/agent-skill-refresh` enumerates all tools available to the agent
+1. **Tool discovery** - `/skill-refresh` enumerates all tools available to the agent
 2. **Semantic analysis** - the AI reads each tool's **name + description**
 3. **Dynamic grouping** - tools are grouped into categories based on what they do
 
@@ -31,12 +31,12 @@ categories are **labels**, not fixed contracts, and can evolve with the tool set
 
 - Categories are **not hard-coded**
 - Category names are **derived from the tools** at refresh time
-- Custom MCP servers are handled automatically
-- The system works with any MCP configuration (MetaMCP, standalone, or custom)
+- Custom tool servers are handled automatically
+- The system works with any tool configuration (MetaMCP, standalone, or custom)
 
 ## Cache File (v2.0.0) - How to Read It
 
-The `/agent-skill-refresh` command writes a cache file using the v2.0.0 schema. This
+The `/skill-refresh` command writes a cache file using the v2.0.0 schema. This
 file is the **source of truth** for the current categorization state.
 
 ### Schema Overview

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

@@ -3,11 +3,11 @@
 # Do not include category catalogs, result summarization, or error templates here.
 
 ## Cache Access and Reading
-Cache location: .opencode/agent-skill-tools.json
-Purpose: fast tool routing without reloading full MCP schemas.
+Cache location: .opencode/skill-tools.json
+Purpose: fast tool routing without reloading full tool schemas.
 
 How to read the cache:
-1. Check if file exists at project root `.opencode/agent-skill-tools.json`.
+1. Check if file exists at project root `.opencode/skill-tools.json`.
 2. Parse JSON into a structured object.
 3. Validate minimal fields: version, refreshed_at, tool_count, categories.
 4. If missing or malformed, fall back to dynamic discovery.
@@ -18,10 +18,10 @@ Cache staleness heuristic:
 
 ## Cache Schema (TypeScript Interface)
 ```ts
-interface AgentSkillToolCache {
+interface SkillToolCache {
   version: string;
   refreshed_at: string; // ISO string
-  mcp_servers: string[];
+  tool_sources: string[];
   tool_count: number;
   categories: {
     [name: string]: {
@@ -156,7 +156,7 @@ params: { fullPage: true }
 ## When to Avoid Cache
 - During tool upgrades or when discrepancies are reported.
 - When a tool id from cache fails execution.
-- When the user references a new MCP server prefix.
+- When the user references a new tool server prefix.
 
 ## Execution Prerequisites
 - Ensure selected tool exists in cache or registry.
@@ -234,7 +234,7 @@ Tool: sequentialthinking { thought: "...", thoughtNumber: 1, totalThoughts: 4, n
 ## Cache Refresh Recommendation Text
 Recommended message:
 ```
-Cache appears stale or missing. Run /agent-skill-refresh to rebuild tool metadata.
+Cache appears stale or missing. Run /skill-refresh to rebuild tool metadata.
 ```
 
 ## Execution Output Metadata (Internal)

package/skills/skill-management/references/workflows.md

@@ -70,7 +70,7 @@ Each prerequisite step has:
 
 ## Session State
 
-Completed prerequisites are tracked in `.opencode/.agent-skill-session.json`:
+Completed prerequisites are tracked in `.opencode/.skill-session.json`:
 
 ```json
 {
@@ -202,26 +202,26 @@ Also matched: 'custom-db-workflow'
 
 ## Managing Workflows
 
-Use `/agent-skill-workflow` command:
+Use `/skill-workflow` command:
 
 ```bash
 # List all workflows
-/agent-skill-workflow list
+/skill-workflow list
 
 # Add from template
-/agent-skill-workflow add --template database
+/skill-workflow add --template database
 
 # Add custom workflow
-/agent-skill-workflow add my-workflow
+/skill-workflow add my-workflow
 
 # Edit existing
-/agent-skill-workflow edit my-workflow
+/skill-workflow edit my-workflow
 
 # Disable temporarily
-/agent-skill-workflow disable my-workflow
+/skill-workflow disable my-workflow
 
 # Remove
-/agent-skill-workflow remove my-workflow
+/skill-workflow remove my-workflow
 ```
 
 ## Best Practices
@@ -230,4 +230,4 @@ Use `/agent-skill-workflow` command:
 2. **Use enforce sparingly** - Only for critical safety workflows
 3. **Keep prerequisites minimal** - Each step adds latency
 4. **Mark optional steps** - Use `required: false` for nice-to-have steps
-5. **Review session state** - Check `.agent-skill-session.json` if prerequisites seem stuck
+5. **Review session state** - Check `.skill-session.json` if prerequisites seem stuck

package/dist/install.d.ts

@@ -1 +0,0 @@
-export declare function install(): Promise<void>;

package/dist/install.js

@@ -1,35 +0,0 @@
-"use strict";
-var __importDefault = (this && this.__importDefault) || function (mod) {
-    return (mod && mod.__esModule) ? mod : { "default": mod };
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.install = install;
-const path_1 = __importDefault(require("path"));
-const chalk_1 = __importDefault(require("chalk"));
-const fs_extra_1 = __importDefault(require("fs-extra"));
-const utils_1 = require("./utils");
-async function install() {
-    const paths = await (0, utils_1.detectOpenCodePaths)();
-    await (0, utils_1.ensureDirExists)(paths.commandDir);
-    await (0, utils_1.ensureDirExists)(paths.skillsDir);
-    const skillTargetDir = path_1.default.join(paths.skillsDir, utils_1.SKILL_DIR_NAME);
-    const commandTargetPath = path_1.default.join(paths.commandDir, "agent-skill-refresh.md");
-    await fs_extra_1.default.copy(paths.templateSkillDir, skillTargetDir, { overwrite: true });
-    const commandTemplate = await (0, utils_1.readText)(paths.templateCommandPath);
-    await (0, utils_1.writeText)(commandTargetPath, commandTemplate);
-    const agentTemplate = await (0, utils_1.readJsonFile)(paths.templateAgentPath, {});
-    const agentConfig = await (0, utils_1.readJsonFile)(paths.agentConfigPath, {});
-    const agents = (agentConfig.agents || {});
-    const templateAgents = (agentTemplate.agents || agentTemplate);
-    agentConfig.agents = { ...agents, ...templateAgents };
-    await (0, utils_1.writeJsonFile)(paths.agentConfigPath, agentConfig);
-    await (0, utils_1.writeJsonFile)(paths.versionFilePath, { version: utils_1.PACKAGE_VERSION, installedAt: new Date().toISOString() });
-    const state = await (0, utils_1.getInstallationState)(paths);
-    if (!state.skillInstalled || !state.commandInstalled || !state.agentInstalled) {
-        throw new Error("Installation verification failed. Some files were not installed.");
-    }
-    if (Object.keys(agentConfig).length > 0 && Object.prototype.hasOwnProperty.call(agentConfig, utils_1.AGENT_ID)) {
-        console.log(chalk_1.default.yellow("agent-skill-manager agent already existed; configuration was updated."));
-    }
-    console.log(chalk_1.default.green("Agent skill manager installed successfully."));
-}

package/dist/remove.d.ts

@@ -1 +0,0 @@
-export declare function remove(): Promise<void>;

package/dist/remove.js

@@ -1,32 +0,0 @@
-"use strict";
-var __importDefault = (this && this.__importDefault) || function (mod) {
-    return (mod && mod.__esModule) ? mod : { "default": mod };
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.remove = remove;
-const path_1 = __importDefault(require("path"));
-const chalk_1 = __importDefault(require("chalk"));
-const fs_extra_1 = __importDefault(require("fs-extra"));
-const utils_1 = require("./utils");
-async function remove() {
-    const paths = await (0, utils_1.detectOpenCodePaths)();
-    const skillTargetDir = path_1.default.join(paths.skillsDir, utils_1.SKILL_DIR_NAME);
-    const commandTargetPath = path_1.default.join(paths.commandDir, "agent-skill-refresh.md");
-    if (await fs_extra_1.default.pathExists(skillTargetDir)) {
-        await fs_extra_1.default.remove(skillTargetDir);
-    }
-    if (await fs_extra_1.default.pathExists(commandTargetPath)) {
-        await fs_extra_1.default.remove(commandTargetPath);
-    }
-    const agentConfig = await (0, utils_1.readJsonFile)(paths.agentConfigPath, {});
-    const agents = (agentConfig.agents || {});
-    if (Object.prototype.hasOwnProperty.call(agents, utils_1.AGENT_ID)) {
-        delete agents[utils_1.AGENT_ID];
-        agentConfig.agents = agents;
-        await (0, utils_1.writeJsonFile)(paths.agentConfigPath, agentConfig);
-    }
-    if (await fs_extra_1.default.pathExists(paths.versionFilePath)) {
-        await fs_extra_1.default.remove(paths.versionFilePath);
-    }
-    console.log(chalk_1.default.green("Agent skill manager removed successfully."));
-}

package/dist/update.d.ts

@@ -1 +0,0 @@
-export declare function update(): Promise<void>;

package/dist/update.js

@@ -1,53 +0,0 @@
-"use strict";
-var __importDefault = (this && this.__importDefault) || function (mod) {
-    return (mod && mod.__esModule) ? mod : { "default": mod };
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.update = update;
-const path_1 = __importDefault(require("path"));
-const chalk_1 = __importDefault(require("chalk"));
-const fs_extra_1 = __importDefault(require("fs-extra"));
-const utils_1 = require("./utils");
-async function update() {
-    const paths = await (0, utils_1.detectOpenCodePaths)();
-    await (0, utils_1.ensureDirExists)(paths.commandDir);
-    await (0, utils_1.ensureDirExists)(paths.skillsDir);
-    const skillTargetDir = path_1.default.join(paths.skillsDir, utils_1.SKILL_DIR_NAME);
-    const commandTargetPath = path_1.default.join(paths.commandDir, "agent-skill-refresh.md");
-    await (0, utils_1.ensureDirExists)(skillTargetDir);
-    const state = await (0, utils_1.getInstallationState)(paths);
-    if (state.installedVersion === utils_1.PACKAGE_VERSION) {
-        console.log(chalk_1.default.green("Agent skill manager is already up to date."));
-        return;
-    }
-    const [skillCustomized, commandCustomized] = await Promise.all([
-        (0, utils_1.directoryDiffersFromTemplate)(skillTargetDir, paths.templateSkillDir),
-        (0, utils_1.fileDiffersFromTemplate)(commandTargetPath, paths.templateCommandPath),
-    ]);
-    if (skillCustomized || commandCustomized) {
-        console.log(chalk_1.default.yellow("Detected customized files. Backups will be created before update."));
-    }
-    if (await fs_extra_1.default.pathExists(skillTargetDir)) {
-        console.log(chalk_1.default.yellow("Backing up existing skill directory before update."));
-        const timestamp = new Date().toISOString().replace(/[:.]/g, "-");
-        const backupDir = `${skillTargetDir}.backup-${timestamp}.bak`;
-        await fs_extra_1.default.copy(skillTargetDir, backupDir, { overwrite: true });
-    }
-    if (await fs_extra_1.default.pathExists(commandTargetPath)) {
-        await (0, utils_1.backupFile)(commandTargetPath, "backup");
-    }
-    if (await fs_extra_1.default.pathExists(paths.agentConfigPath)) {
-        await (0, utils_1.backupFile)(paths.agentConfigPath, "backup");
-    }
-    await fs_extra_1.default.copy(paths.templateSkillDir, skillTargetDir, { overwrite: true });
-    const commandTemplate = await fs_extra_1.default.readFile(paths.templateCommandPath, "utf8");
-    await fs_extra_1.default.writeFile(commandTargetPath, commandTemplate, "utf8");
-    const agentTemplate = await (0, utils_1.readJsonFile)(paths.templateAgentPath, {});
-    const agentConfig = await (0, utils_1.readJsonFile)(paths.agentConfigPath, {});
-    const agents = (agentConfig.agents || {});
-    const templateAgents = (agentTemplate.agents || agentTemplate);
-    agentConfig.agents = { ...agents, ...templateAgents };
-    await (0, utils_1.writeJsonFile)(paths.agentConfigPath, agentConfig);
-    await (0, utils_1.writeJsonFile)(paths.versionFilePath, { version: utils_1.PACKAGE_VERSION, updatedAt: new Date().toISOString() });
-    console.log(chalk_1.default.green("Agent skill manager updated successfully."));
-}