@ngocsangairvds/vsaf 3.1.14 → 3.1.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ngocsangairvds/vsaf",
-  "version": "3.1.14",
+  "version": "3.1.15",
   "description": "VSAF — Agentic AI SDLC Framework. 3 integrated tools: BMAD, GitNexus, Superpowers. 2-layer review.",
   "keywords": ["claude", "claude-code", "ai", "sdlc", "framework", "bmad", "gitnexus", "superpowers"],
   "bin": {

package/src/global.js

@@ -32,22 +32,16 @@ function installSkills() {
   fs.mkdirSync(SKILLS_DST, { recursive: true });
 
   let installed = 0;
-  let skipped   = 0;
 
   for (const entry of fs.readdirSync(SKILLS_SRC, { withFileTypes: true })) {
     const src = path.join(SKILLS_SRC, entry.name);
     const dst = path.join(SKILLS_DST, entry.name);
 
-    if (fs.existsSync(dst)) {
-      skipped++;
-      continue;
-    }
-
     entry.isDirectory() ? copyDir(src, dst) : copyFile(src, dst);
     installed++;
   }
 
-  ok(`${installed} skill(s) installed, ${skipped} already present`);
+  ok(`${installed} skill(s) installed/updated`);
 }
 
 // ── Binary helpers ───────────────────────────────────────────────────────────

package/src/project.js

@@ -116,7 +116,6 @@ function syncLocalBmadSkills() {
   ];
 
   let installed = 0;
-  let skipped = 0;
 
   for (const targetRoot of targets) {
     fs.mkdirSync(targetRoot, { recursive: true });
@@ -125,17 +124,12 @@ function syncLocalBmadSkills() {
       const src = path.join(SKILLS_SRC, entry.name);
       const dst = path.join(targetRoot, entry.name);
 
-      if (fs.existsSync(dst)) {
-        skipped++;
-        continue;
-      }
-
       entry.isDirectory() ? copyDir(src, dst) : copyFile(src, dst);
       installed++;
     }
   }
 
-  ok(`${installed} BMAD skill copy(ies), ${skipped} already present`);
+  ok(`${installed} BMAD skill(s) installed/updated`);
 }
 
 function initGitNexus() {

package/tools/skills/vsaf-build/SKILL.md

@@ -34,9 +34,9 @@ Implement code strictly following PRD, SRS, and testcases, one task at a time, w
   ```
 
 ### Step 1 — Read PRD + SRS + testcase (mandatory — must read all 3 fully)
-- Read the PRD file in `docs/project/planning-artifacts/` — understand WHY and WHAT
-- Read the SRS file in `docs/project/srs/` — understand HOW, FRs/NFRs
-- Read the testcase file in `docs/project/testcases/` — understand acceptance criteria
+- Read the PRD file in `.vsaf/docs/planning-artifacts/` — understand WHY and WHAT
+- Read the SRS file in `.vsaf/docs/srs/` — understand HOW, FRs/NFRs
+- Read the testcase file in `.vsaf/docs/testcases/` — understand acceptance criteria
 - Confirm FR/NFR → testcase mapping before starting
 - If a gap is found (FR/NFR without testcase, or testcase contradicts SRS): NOTIFY USER before continuing
 - **Do NOT start coding without having read all 3 documents**

package/tools/skills/vsaf-discover/SKILL.md

@@ -21,14 +21,14 @@ Thoroughly understand the domain, market, user needs, and technical feasibility
 ### Step 1 — Domain Research
 - Use skill `bmad-domain-research` to deep dive into the domain/industry
 - Output: terminology, business rules, regulatory constraints, domain patterns
-- Save to `docs/project/planning-artifacts/domain-research-[topic].md`
+- Save to `.vsaf/docs/planning-artifacts/domain-research-[topic].md`
 
 ### Step 2 — Market Research
 - Use skill `bmad-market-research` to analyze:
   - Competition landscape: who is doing what, strengths/weaknesses
   - Customer needs: pain points, underserved segments
   - Market trends: which directions are growing
-- Save to `docs/project/planning-artifacts/market-research-[topic].md`
+- Save to `.vsaf/docs/planning-artifacts/market-research-[topic].md`
 
 ### Step 3 — Technical Feasibility
 - Use skill `bmad-technical-research` to assess:
@@ -36,12 +36,12 @@ Thoroughly understand the domain, market, user needs, and technical feasibility
   - Integration constraints
   - Performance/scale requirements
   - Build vs buy decisions
-- Save to `docs/project/planning-artifacts/tech-research-[topic].md`
+- Save to `.vsaf/docs/planning-artifacts/tech-research-[topic].md`
 
 ### Step 4 — Product Brief
 - Use skill `bmad-product-brief` to synthesize findings into a product brief
 - Product brief = summary of: what problem, for whom, what solution, why now
-- Save to `docs/project/planning-artifacts/product-brief-[name].md`
+- Save to `.vsaf/docs/planning-artifacts/product-brief-[name].md`
 
 ### Step 5 — PRFAQ Challenge (Working Backwards)
 - Use skill `bmad-prfaq` to stress-test the product concept
@@ -55,7 +55,7 @@ Thoroughly understand the domain, market, user needs, and technical feasibility
 - PRD includes: vision, goals, FRs, NFRs, epics, user stories, success metrics
 - After creation: use skill `bmad-validate-prd` to validate the PRD meets standards
 - If validation FAILs: John will use `bmad-edit-prd` to fix issues immediately
-- Save to `docs/project/planning-artifacts/prd-[name].md`
+- Save to `.vsaf/docs/planning-artifacts/prd-[name].md`
 
 ### Step 7 — Multi-agent Review (Party Mode)
 - Use skill `bmad-party-mode` to organize a roundtable:
@@ -69,11 +69,11 @@ Thoroughly understand the domain, market, user needs, and technical feasibility
 ## Discovery Complete: [product/domain]
 
 ### Research artifacts
-- Domain research:  docs/project/planning-artifacts/domain-research-[topic].md
-- Market research:  docs/project/planning-artifacts/market-research-[topic].md
-- Tech research:    docs/project/planning-artifacts/tech-research-[topic].md
-- Product brief:    docs/project/planning-artifacts/product-brief-[name].md
-- PRD:              docs/project/planning-artifacts/prd-[name].md
+- Domain research:  .vsaf/docs/planning-artifacts/domain-research-[topic].md
+- Market research:  .vsaf/docs/planning-artifacts/market-research-[topic].md
+- Tech research:    .vsaf/docs/planning-artifacts/tech-research-[topic].md
+- Product brief:    .vsaf/docs/planning-artifacts/product-brief-[name].md
+- PRD:              .vsaf/docs/planning-artifacts/prd-[name].md
 
 ### Key findings
 - [3-5 bullet point summary]

package/tools/skills/vsaf-doc-prd/SKILL.md

@@ -14,7 +14,7 @@ Must have run `/vsaf-plan` and have its output before running this skill.
 ## Steps
 
 ### Step 0 — Determine mode: Create or Edit
-- Check if a PRD already exists in `docs/project/planning-artifacts/` for this feature
+- Check if a PRD already exists in `.vsaf/docs/planning-artifacts/` for this feature
 - **If none exists** → Mode: CREATE (create from scratch)
 - **If one exists** → Mode: EDIT (edit based on feedback/changes)
   - Ask user: "A PRD already exists. Do you want to create a new one from scratch or edit the existing one?"
@@ -25,7 +25,7 @@ Must have run `/vsaf-plan` and have its output before running this skill.
 - Use skill `bmad-agent-pm` (John) to guide the PRD creation process from `/vsaf-plan` output
 - John will call skill `bmad-create-prd` to generate a standard PRD
 - PRD must include: vision, goals, FRs, NFRs, epics, user stories, success metrics, scope, out-of-scope, assumptions
-- Save to `docs/project/planning-artifacts/prd-[feature].md`
+- Save to `.vsaf/docs/planning-artifacts/prd-[feature].md`
 
 #### Mode EDIT:
 - Use skill `bmad-edit-prd` to edit the existing PRD
@@ -43,7 +43,7 @@ Must have run `/vsaf-plan` and have its output before running this skill.
 ## PRD Created/Updated
 
 ### File
-- docs/project/planning-artifacts/prd-[feature].md
+- .vsaf/docs/planning-artifacts/prd-[feature].md
 - Mode: [CREATE / EDIT]
 - Validation: [PASS / FAIL — details if fail]
 

package/tools/skills/vsaf-doc-srs/SKILL.md

@@ -15,9 +15,9 @@ Analyze the PRD and write a feature-level SRS following a standard template —
 
 ## Configuration
 ```yaml
-outputDir: docs/project/srs
-featureTemplate: _bmad/bmm/1-analysis/bmad-document-project/templates/srs-feature-template.md
-systemTemplate: _bmad/bmm/1-analysis/bmad-document-project/templates/srs-system-template.md
+outputDir: .vsaf/docs/srs
+featureTemplate: .vsaf/_bmad/bmm/1-analysis/bmad-document-project/templates/srs-feature-template.md
+systemTemplate: .vsaf/_bmad/bmm/1-analysis/bmad-document-project/templates/srs-system-template.md
 ```
 
 ## Steps
@@ -27,7 +27,7 @@ systemTemplate: _bmad/bmm/1-analysis/bmad-document-project/templates/srs-system-
 Before starting, check if the user has provided sufficient information:
 
 **Required:**
-- [ ] PRD document (file path or content) — typically at `docs/project/planning-artifacts/prd-[feature].md`
+- [ ] PRD document (file path or content) — typically at `.vsaf/docs/planning-artifacts/prd-[feature].md`
 - [ ] Figma link (URL figma.com/design/...) — if available
 
 If PRD is missing, **stop immediately** and request from the user:
@@ -48,7 +48,7 @@ Only continue when the PRD is available.
 ---
 
 ### Step 1 — Determine mode: Create or Edit
-- Check if an SRS already exists in `docs/project/srs/` for this feature
+- Check if an SRS already exists in `.vsaf/docs/srs/` for this feature
 - **If none exists** → Mode: CREATE
 - **If one exists** → Mode: EDIT
   - Ask user: "An SRS already exists. Do you want to create a new one from scratch or edit the existing one?"
@@ -104,7 +104,7 @@ After this step, output a **"Gap Analysis Report"** and ask the user if they wan
 
 ### Step 4 — Write SRS following the Feature Template
 
-Read the template at `_bmad/bmm/1-analysis/bmad-document-project/templates/srs-feature-template.md` and write the SRS **strictly following the template structure**, including all 12 sections (0-11):
+Read the template at `.vsaf/_bmad/bmm/1-analysis/bmad-document-project/templates/srs-feature-template.md` and write the SRS **strictly following the template structure**, including all 12 sections (0-11):
 
 0. **Preamble** — Document information, change log table, approval table
 1. **Introduction** — Objectives, scope, reference documents
@@ -140,14 +140,14 @@ Read the template at `_bmad/bmm/1-analysis/bmad-document-project/templates/srs-f
 ---
 
 ### Step 6 — Save SRS file
-Save the SRS document to: `docs/project/srs/SRS-[project-name]-[FR-ID]-[feature-name]-v1.0.md`
+Save the SRS document to: `.vsaf/docs/srs/SRS-[project-name]-[FR-ID]-[feature-name]-v1.0.md`
 
 ### Step 7 — Output to user
 ```
 ## SRS Created/Updated
 
 ### File
-- docs/project/srs/SRS-[project-name]-[FR-ID]-[feature-name]-v1.0.md
+- .vsaf/docs/srs/SRS-[project-name]-[FR-ID]-[feature-name]-v1.0.md
 - Mode: [CREATE / EDIT]
 - Use Cases written: [N]
 - Validation: [PASS / FAIL — details if fail]
@@ -159,7 +159,7 @@ Save the SRS document to: `docs/project/srs/SRS-[project-name]-[FR-ID]-[feature-
 - [SRS sections still containing {{...}} that need additional input]
 
 ## Next step
-Run /vsaf-test docs/project/srs/SRS-[...].md to generate testcases
+Run /vsaf-test .vsaf/docs/srs/SRS-[...].md to generate testcases
 ```
 
 ## Notes

package/tools/skills/vsaf-docs/SKILL.md

@@ -29,7 +29,7 @@ Ensure documentation is always up to date and AI agents have sufficient context.
 ### Step 2 — Generate project documentation
 - Use skill `bmad-document-project` to generate/update project docs
 - Output: architecture description, module breakdown, API endpoints, data flows
-- Save to `docs/project/`
+- Save to `.vsaf/docs/`
 
 ### Step 3 — Generate project context for AI
 - Use skill `bmad-generate-project-context` to create `project-context.md`

package/tools/skills/vsaf-onboard/SKILL.md

@@ -38,8 +38,8 @@ Build a full mental model of the project before touching any code.
 - Identify: hot symbols (many callers), risk areas (high fan-out)
 
 ### Step 7 — Read project documentation + synthesize
-- Read `docs/project/planning-artifacts/` to find PRDs, ADRs, architecture docs
-- Read `docs/project/srs/` to find existing SRS documents
+- Read `.vsaf/docs/planning-artifacts/` to find PRDs, ADRs, architecture docs
+- Read `.vsaf/docs/srs/` to find existing SRS documents
 - Synthesize all findings into a project overview
 
 ### Step 8 — Output to user

package/tools/skills/vsaf-plan/SKILL.md

@@ -33,7 +33,7 @@ Fully understand the requirement, analyze impact, and determine the implementati
 - Use skill `bmad-agent-architect` to propose an architecture approach
 - Compare alternatives, choose the most suitable approach
 - **If risk is HIGH or > 3 modules**: use skill `bmad-create-architecture` to create a formal ADR (Architecture Decision Record)
-  - Save to `docs/project/planning-artifacts/adr-[feature].md`
+  - Save to `.vsaf/docs/planning-artifacts/adr-[feature].md`
 
 ### Step 4 — Dual Brainstorm
 

package/tools/skills/vsaf-retro/SKILL.md

@@ -91,4 +91,4 @@ Date: [YYYY-MM-DD]
 - Retro must be data-backed — do not accept "I feel like..." without evidence
 - If GitNexus index is stale: run `vsaf index` before the retro
 - Action items must be actionable and have an owner — do not write vague "improve testing"
-- Save retro output to `docs/project/implementation-artifacts/retro-[sprint].md` to track historical data
+- Save retro output to `.vsaf/docs/implementation-artifacts/retro-[sprint].md` to track historical data

package/tools/skills/vsaf-ship/SKILL.md

@@ -10,7 +10,7 @@ Multi-layer review, verify scope, validate architecture, push PR. Ensure code ha
 
 ## Prerequisites
 - Have run `/vsaf-build` with PRD + SRS + testcase
-- Have run `/vsaf-test run` — results file exists at `docs/project/testcases/[feature]-results.md`
+- Have run `/vsaf-test run` — results file exists at `.vsaf/docs/testcases/[feature]-results.md`
 - Ship gate from `/vsaf-test run` = PASS
 - No failing tests
 
@@ -78,7 +78,7 @@ git push origin feature/<name>
 ```
 PR description must include:
 - Impact summary (from GitNexus detect_changes)
-- Test results file path: `docs/project/testcases/[feature]-results.md`
+- Test results file path: `.vsaf/docs/testcases/[feature]-results.md`
 - Adversarial triage: MUST FIX: 0, SHOULD FIX: N, NOTED: N
 - Shape check result
 
@@ -98,7 +98,7 @@ PR description must include:
 ### PR
 - Branch: feature/[name]
 - PR: [link]
-- Test results: docs/project/testcases/[feature]-results.md
+- Test results: .vsaf/docs/testcases/[feature]-results.md
 
 ## Next step
 - Run /vsaf-retro if this is the end of a sprint/epic

package/tools/skills/vsaf-sprint/SKILL.md

@@ -33,7 +33,7 @@ Manage backlog and sprints for the project — break PRD/SRS into stories, creat
   - Prioritize stories (MoSCoW or WSJF)
   - Assign stories to sprint based on capacity
   - Identify dependencies between stories
-- Save sprint plan to `docs/project/planning-artifacts/sprint-plan.md`
+- Save sprint plan to `.vsaf/docs/planning-artifacts/sprint-plan.md`
 
 #### Step 3 — Output
 ```
@@ -94,12 +94,12 @@ Or: /vsaf-plan <story description> to start the first feature
 #### Step 1 — Create story file
 - Use skill `bmad-create-story` with story ID from the sprint plan
 - Story file includes: full context, acceptance criteria, technical notes, dependencies
-- Save to `docs/project/planning-artifacts/stories/story-[id].md`
+- Save to `.vsaf/docs/planning-artifacts/stories/story-[id].md`
 
 #### Step 2 — Output
 ```
 ## Story Created: [story title]
-- File: docs/project/planning-artifacts/stories/story-[id].md
+- File: .vsaf/docs/planning-artifacts/stories/story-[id].md
 
 ### Next step
 Run /vsaf-plan <story description> to plan implementation

package/tools/skills/vsaf-test/SKILL.md

@@ -21,7 +21,7 @@ Create comprehensive testcase coverage documentation from SRS to serve as a cont
 
 ## Prerequisites
 - Already ran `/vsaf-doc-prd` and `/vsaf-doc-srs`
-- SRS file exists in `docs/project/srs/`
+- SRS file exists in `.vsaf/docs/srs/`
 
 ## Steps
 
@@ -30,7 +30,7 @@ Create comprehensive testcase coverage documentation from SRS to serve as a cont
 - Reference existing patterns to generate testcases consistent with the codebase
 
 ### Step 1 — Generate test cases from SRS (BMAD qa)
-- Use skill `bmad-qa-generate-e2e-tests` with the SRS file in `docs/project/srs/` as input
+- Use skill `bmad-qa-generate-e2e-tests` with the SRS file in `.vsaf/docs/srs/` as input
 - Test cases must cover: happy path, edge cases, error cases, NFRs
 - Source: from FRs/NFRs in SRS — NOT based on implementation
 
@@ -50,7 +50,7 @@ Create comprehensive testcase coverage documentation from SRS to serve as a cont
 - Each testcase has: input, expected output, pass/fail criteria
 
 ### Step 5 — Save testcase document
-- Save testcases to `docs/project/testcases/[feature].md`
+- Save testcases to `.vsaf/docs/testcases/[feature].md`
 - Format:
 
 ```markdown
@@ -89,7 +89,7 @@ Create comprehensive testcase coverage documentation from SRS to serve as a cont
 - Implementation readiness: [PASS / FAIL]
 
 Files:
-- docs/project/testcases/[feature].md
+- .vsaf/docs/testcases/[feature].md
 
 ## Next step
 [If PASS]: Run /vsaf-build <path/to/prd> <path/to/srs> <path/to/testcases>
@@ -105,7 +105,7 @@ Execute the full test suite, verify coverage matches changed code, write a struc
 
 ## Prerequisites
 - Already ran `/vsaf-build` — code implementation is complete
-- Testcase file exists at `docs/project/testcases/[feature].md`
+- Testcase file exists at `.vsaf/docs/testcases/[feature].md`
 
 ## Steps
 
@@ -132,7 +132,7 @@ Execute the full test suite, verify coverage matches changed code, write a struc
 - Record constraint compliance results in the results file
 
 ### Step 6 — Write results file
-- Save results to `docs/project/testcases/[feature]-results.md`
+- Save results to `.vsaf/docs/testcases/[feature]-results.md`
 - Format:
 
 ```markdown
@@ -188,7 +188,7 @@ Date: [YYYY-MM-DD]
 - Shape check: [PASS / SKIP / FAIL]
 - Ship gate: [PASS ✓ / FAIL ✗]
 
-Results file: docs/project/testcases/[feature]-results.md
+Results file: .vsaf/docs/testcases/[feature]-results.md
 
 ## Next step
 [If PASS]: Run /vsaf-ship