@ngocsangairvds/vsaf 4.0.7 → 4.0.8

package/skills/sdlc/bmad-correct-course/workflow.md

@@ -0,0 +1,267 @@
+# Correct Course - Sprint Change Management Workflow
+
+**Goal:** Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.
+
+**Your Role:** You are a Developer navigating change management. Analyze the triggering issue, assess impact across PRD, epics, architecture, and UX artifacts, and produce an actionable Sprint Change Proposal with clear handoff.
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `user_name`
+- `communication_language`, `document_output_language`
+- `user_skill_level`
+- `implementation_artifacts`
+- `planning_artifacts`
+- `project_knowledge`
+- `date` as system-generated current datetime
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+- Language MUST be tailored to `{user_skill_level}`
+- Generate all documents in `{document_output_language}`
+- DOCUMENT OUTPUT: Updated epics, stories, or PRD sections. Clear, actionable changes. User skill level (`{user_skill_level}`) affects conversation style ONLY, not document updates.
+
+### Paths
+
+- `default_output_file` = `{planning_artifacts}/sprint-change-proposal-{date}.md`
+
+### Input Files
+
+| Input | Path | Load Strategy |
+|-------|------|---------------|
+| PRD | `{planning_artifacts}/*prd*.md` (whole) or `{planning_artifacts}/*prd*/*.md` (sharded) | FULL_LOAD |
+| Epics | `{planning_artifacts}/*epic*.md` (whole) or `{planning_artifacts}/*epic*/*.md` (sharded) | FULL_LOAD |
+| Architecture | `{planning_artifacts}/*architecture*.md` (whole) or `{planning_artifacts}/*architecture*/*.md` (sharded) | FULL_LOAD |
+| UX Design | `{planning_artifacts}/*ux*.md` (whole) or `{planning_artifacts}/*ux*/*.md` (sharded) | FULL_LOAD |
+| Spec | `{planning_artifacts}/*spec-*.md` (whole) | FULL_LOAD |
+| Document Project | `{project_knowledge}/index.md` (sharded) | INDEX_GUIDED |
+
+### Context
+
+- Load `**/project-context.md` if it exists
+
+---
+
+## EXECUTION
+
+### Document Discovery - Loading Project Artifacts
+
+**Strategy**: Course correction needs broad project context to assess change impact accurately. Load all available planning artifacts.
+
+**Discovery Process for FULL_LOAD documents (PRD, Epics, Architecture, UX Design, Spec):**
+
+1. **Search for whole document first** - Look for files matching the whole-document pattern (e.g., `*prd*.md`, `*epic*.md`, `*architecture*.md`, `*ux*.md`, `*spec-*.md`)
+2. **Check for sharded version** - If whole document not found, look for a directory with `index.md` (e.g., `prd/index.md`, `epics/index.md`)
+3. **If sharded version found**:
+   - Read `index.md` to understand the document structure
+   - Read ALL section files listed in the index
+   - Process the combined content as a single document
+4. **Priority**: If both whole and sharded versions exist, use the whole document
+
+**Discovery Process for INDEX_GUIDED documents (Document Project):**
+
+1. **Search for index file** - Look for `{project_knowledge}/index.md`
+2. **If found**: Read the index to understand available documentation sections
+3. **Selectively load sections** based on relevance to the change being analyzed — do NOT load everything, only sections that relate to the impacted areas
+4. **This document is optional** — skip if `{project_knowledge}` does not exist (greenfield projects)
+
+**Fuzzy matching**: Be flexible with document names — users may use variations like `prd.md`, `bmm-prd.md`, `product-requirements.md`, etc.
+
+**Missing documents**: Not all documents may exist. PRD and Epics are essential; Architecture, UX Design, Spec, and Document Project are loaded if available. HALT if PRD or Epics cannot be found.
+
+<workflow>
+
+<step n="1" goal="Initialize Change Navigation">
+  <action>Load **/project-context.md for coding standards and project-wide patterns (if exists)</action>
+  <action>Confirm change trigger and gather user description of the issue</action>
+  <action>Ask: "What specific issue or change has been identified that requires navigation?"</action>
+  <action>Verify access to required project documents:</action>
+    - PRD (Product Requirements Document)
+    - Current Epics and Stories
+    - Architecture documentation
+    - UI/UX specifications
+  <action>Ask user for mode preference:</action>
+    - **Incremental** (recommended): Refine each edit collaboratively
+    - **Batch**: Present all changes at once for review
+  <action>Store mode selection for use throughout workflow</action>
+
+<action if="change trigger is unclear">HALT: "Cannot navigate change without clear understanding of the triggering issue. Please provide specific details about what needs to change and why."</action>
+
+<action if="core documents are unavailable">HALT: "Need access to project documents (PRD, Epics, Architecture, UI/UX) to assess change impact. Please ensure these documents are accessible."</action>
+</step>
+
+<step n="2" goal="Execute Change Analysis Checklist">
+  <action>Read fully and follow the systematic analysis from: checklist.md</action>
+  <action>Work through each checklist section interactively with the user</action>
+  <action>Record status for each checklist item:</action>
+    - [x] Done - Item completed successfully
+    - [N/A] Skip - Item not applicable to this change
+    - [!] Action-needed - Item requires attention or follow-up
+  <action>Maintain running notes of findings and impacts discovered</action>
+  <action>Present checklist progress after each major section</action>
+
+<action if="checklist cannot be completed">Identify blocking issues and work with user to resolve before continuing</action>
+</step>
+
+<step n="3" goal="Draft Specific Change Proposals">
+<action>Based on checklist findings, create explicit edit proposals for each identified artifact</action>
+
+<action>For Story changes:</action>
+
+- Show old → new text format
+- Include story ID and section being modified
+- Provide rationale for each change
+- Example format:
+
+  ```
+  Story: [STORY-123] User Authentication
+  Section: Acceptance Criteria
+
+  OLD:
+  - User can log in with email/password
+
+  NEW:
+  - User can log in with email/password
+  - User can enable 2FA via authenticator app
+
+  Rationale: Security requirement identified during implementation
+  ```
+
+<action>For PRD modifications:</action>
+
+- Specify exact sections to update
+- Show current content and proposed changes
+- Explain impact on MVP scope and requirements
+
+<action>For Architecture changes:</action>
+
+- Identify affected components, patterns, or technology choices
+- Describe diagram updates needed
+- Note any ripple effects on other components
+
+<action>For UI/UX specification updates:</action>
+
+- Reference specific screens or components
+- Show wireframe or flow changes needed
+- Connect changes to user experience impact
+
+<check if="mode is Incremental">
+  <action>Present each edit proposal individually</action>
+  <ask>Review and refine this change? Options: Approve [a], Edit [e], Skip [s]</ask>
+  <action>Iterate on each proposal based on user feedback</action>
+</check>
+
+<action if="mode is Batch">Collect all edit proposals and present together at end of step</action>
+
+</step>
+
+<step n="4" goal="Generate Sprint Change Proposal">
+<action>Compile comprehensive Sprint Change Proposal document with following sections:</action>
+
+<action>Section 1: Issue Summary</action>
+
+- Clear problem statement describing what triggered the change
+- Context about when/how the issue was discovered
+- Evidence or examples demonstrating the issue
+
+<action>Section 2: Impact Analysis</action>
+
+- Epic Impact: Which epics are affected and how
+- Story Impact: Current and future stories requiring changes
+- Artifact Conflicts: PRD, Architecture, UI/UX documents needing updates
+- Technical Impact: Code, infrastructure, or deployment implications
+
+<action>Section 3: Recommended Approach</action>
+
+- Present chosen path forward from checklist evaluation:
+  - Direct Adjustment: Modify/add stories within existing plan
+  - Potential Rollback: Revert completed work to simplify resolution
+  - MVP Review: Reduce scope or modify goals
+- Provide clear rationale for recommendation
+- Include effort estimate, risk assessment, and timeline impact
+
+<action>Section 4: Detailed Change Proposals</action>
+
+- Include all refined edit proposals from Step 3
+- Group by artifact type (Stories, PRD, Architecture, UI/UX)
+- Ensure each change includes before/after and justification
+
+<action>Section 5: Implementation Handoff</action>
+
+- Categorize change scope:
+  - Minor: Direct implementation by Developer agent
+  - Moderate: Backlog reorganization needed (PO/DEV)
+  - Major: Fundamental replan required (PM/Architect)
+- Specify handoff recipients and their responsibilities
+- Define success criteria for implementation
+
+<action>Present complete Sprint Change Proposal to user</action>
+<action>Write Sprint Change Proposal document to {default_output_file}</action>
+<ask>Review complete proposal. Continue [c] or Edit [e]?</ask>
+</step>
+
+<step n="5" goal="Finalize and Route for Implementation">
+<action>Get explicit user approval for complete proposal</action>
+<ask>Do you approve this Sprint Change Proposal for implementation? (yes/no/revise)</ask>
+
+<check if="no or revise">
+  <action>Gather specific feedback on what needs adjustment</action>
+  <action>Return to appropriate step to address concerns</action>
+  <goto step="3">If changes needed to edit proposals</goto>
+  <goto step="4">If changes needed to overall proposal structure</goto>
+
+</check>
+
+<check if="yes the proposal is approved by the user">
+  <action>Finalize Sprint Change Proposal document</action>
+  <action>Determine change scope classification:</action>
+
+- **Minor**: Can be implemented directly by Developer agent
+- **Moderate**: Requires backlog reorganization and PO/DEV coordination
+- **Major**: Needs fundamental replan with PM/Architect involvement
+
+<action>Provide appropriate handoff based on scope:</action>
+
+</check>
+
+<check if="Minor scope">
+  <action>Route to: Developer agent for direct implementation</action>
+  <action>Deliverables: Finalized edit proposals and implementation tasks</action>
+</check>
+
+<check if="Moderate scope">
+  <action>Route to: Product Owner / Developer agents</action>
+  <action>Deliverables: Sprint Change Proposal + backlog reorganization plan</action>
+</check>
+
+<check if="Major scope">
+  <action>Route to: Product Manager / Solution Architect</action>
+  <action>Deliverables: Complete Sprint Change Proposal + escalation notice</action>
+
+<action>Confirm handoff completion and next steps with user</action>
+<action>Document handoff in workflow execution log</action>
+</check>
+
+</step>
+
+<step n="6" goal="Workflow Completion">
+<action>Summarize workflow execution:</action>
+  - Issue addressed: {{change_trigger}}
+  - Change scope: {{scope_classification}}
+  - Artifacts modified: {{list_of_artifacts}}
+  - Routed to: {{handoff_recipients}}
+
+<action>Confirm all deliverables produced:</action>
+
+- Sprint Change Proposal document
+- Specific edit proposals with before/after
+- Implementation handoff plan
+
+<action>Report workflow completion to user with personalized message: "Correct Course workflow complete, {user_name}!"</action>
+<action>Remind user of success criteria and next steps for Developer agent</action>
+</step>
+
+</workflow>

package/skills/sdlc/discovery/SKILL.md

@@ -93,9 +93,9 @@ Use `/bmad-advanced-elicitation` — grill questions BASED ON system understandi
 
 Two complementary brainstorming approaches:
 
-**4a — Structured brainstorm (Superpowers)**
+**4a — Structured brainstorm**
 
-Use `/superpowers:brainstorming` for structured exploration:
+Based on grill answers + system analysis, propose:
 - 2-3 viable approaches with trade-offs
 - Risk/constraint evaluation per approach
 - Recommended option with reasoning

package/skills/sdlc/pack.yaml

@@ -34,7 +34,7 @@ skills:
 
 # Bundled external skills — deployed WITHOUT pack prefix (as-is)
 bundled:
-  # BMAD skills (15) — used by discovery, prd, architecture, srs, test-design, review
+  # BMAD skills (17) — used by discovery, prd, architecture, srs, test-design, implement, review
   - bmad-advanced-elicitation
   - bmad-brainstorming
   - bmad-domain-research
@@ -50,6 +50,8 @@ bundled:
   - bmad-code-review
   - bmad-party-mode
   - bmad-qa-generate-e2e-tests
+  - bmad-checkpoint-preview
+  - bmad-correct-course
 
   # mattpocock skills (5) — lean alternative for bugfix/known-domain flows
   - grill-me

package/skills/sdlc/prd/SKILL.md

@@ -63,8 +63,15 @@ Record results in `02-prd.md` §Grill Log.
 [PRD] [3/5] Creating PRD from grill results... ⏳
 ```
 
-Use `/bmad-create-prd` — generate PRD from grill results.
-Write to `02-prd.md` §Requirements: goals, user stories, FRs, NFRs, success metrics.
+Based on grill results from Step 2, create structured PRD:
+
+1. **Goals** — business goals + success metrics
+2. **User Stories** — each MUST have acceptance criteria (Given/When/Then)
+3. **Functional Requirements** — unique ID per requirement (FR-001, FR-002...)
+4. **Non-Functional Requirements** — unique ID (NFR-001, NFR-002...) — performance, security, scalability
+5. **Success Metrics** — measurable KPIs tied to goals
+
+Write to `02-prd.md` §Requirements.
 
 ```
 [PRD] [3/5] Creating PRD from grill results... ✅
@@ -76,9 +83,17 @@ Write to `02-prd.md` §Requirements: goals, user stories, FRs, NFRs, success met
 [PRD] [4/5] Validate + adversarial review... ⏳
 ```
 
-Use `/bmad-validate-prd` — validate completeness, clarity, testability.
-Write to `02-prd.md` §Validation.
-If FAIL → fix inline, re-validate.
+**4a — Validate PRD:**
+
+Check the PRD for:
+- Completeness — all user stories covered by FRs? All FRs traceable to a user story?
+- Clarity — any ambiguous requirements? Can each FR be implemented without guessing?
+- Testability — can each FR be verified with a test case?
+- Consistency — any FRs that contradict each other?
+
+Write to `02-prd.md` §Validation. If FAIL → fix inline, re-validate.
+
+**4b — Adversarial review:**
 
 Use `/bmad-review-adversarial-general` — cynical review to find gaps.
 Write to `02-prd.md` §Adversarial.

package/skills/sdlc/review/SKILL.md

@@ -69,11 +69,15 @@ Write to `08-review.md` §Verification.
 [REVIEW] [3/5] Adversarial code review... ⏳
 ```
 
-Use `/bmad-code-review` — adversarial code review:
-- Security vulnerabilities
-- Data integrity risks
-- SOLID violations
-- Naming consistency with CONTEXT.md
+Perform adversarial code review on the feature branch diff:
+
+1. **Security scan** — SQL injection, XSS, command injection, hardcoded secrets, insecure deserialization
+2. **Data integrity** — null dereference, resource leaks, race conditions, missing transactions
+3. **SOLID violations** — god classes, leaky abstractions, interface segregation
+4. **Naming consistency** — verify against CONTEXT.md terminology
+5. **SRS compliance** — every FR/NFR implemented? Any extra scope not in SRS?
+
+Classify each finding: MUST FIX / SHOULD FIX / NOTED.
 Write to `08-review.md` §Code Review.
 
 #### Quality Gate Re-check (SonarQube)

package/skills/sdlc/sdlc-health/SKILL.md

@@ -38,7 +38,7 @@ Use the Read tool to check each of these 16 skill files (sdlc-health is excluded
 
 ### Check 2: BMAD Skills (filesystem)
 
-Check these 15 BMAD skills — required by discovery, prd, architecture, srs, test-design, review:
+Check these 17 BMAD skills — required by discovery, prd, architecture, srs, test-design, review:
 
 ```
 .claude/skills/bmad-advanced-elicitation/SKILL.md
@@ -56,6 +56,8 @@ Check these 15 BMAD skills — required by discovery, prd, architecture, srs, te
 .claude/skills/bmad-code-review/SKILL.md
 .claude/skills/bmad-party-mode/SKILL.md
 .claude/skills/bmad-qa-generate-e2e-tests/SKILL.md
+.claude/skills/bmad-checkpoint-preview/SKILL.md
+.claude/skills/bmad-correct-course/SKILL.md
 ```
 
 ### Check 3: mattpocock Skills (filesystem)
@@ -136,7 +138,7 @@ After completing all checks, print this summary:
 | Category             | Status | Details                                 |
 |----------------------|--------|-----------------------------------------|
 | SDLC Skills (16)     |   {s}  | {deployed}/{16} deployed                |
-| BMAD Skills (15)     |   {s}  | {deployed}/{15} deployed                |
+| BMAD Skills (17)     |   {s}  | {deployed}/{17} deployed                |
 | mattpocock Skills (5)|   {s}  | {deployed}/{5} deployed                 |
 | Plugins              |   {s}  | superpowers {s}                         |
 | MCP tools            |   {s}  | vsaf {s}, gitnexus {s}               |
@@ -161,5 +163,5 @@ Replace `{s}` with: ✓ (pass), ✗ (required missing), ⚠ (optional missing).
 - ✗ = required missing → must fix before using SDLC
 - ⚠ = optional missing → SDLC works but some features unavailable
 
-**Required:** all 16 SDLC skills, all 15 BMAD skills, all 5 mattpocock skills, superpowers plugin, gh binary, graphify binary + skill, gitnexus MCP, .mcp.json entries
+**Required:** all 16 SDLC skills, all 17 BMAD skills, all 5 mattpocock skills, superpowers plugin, gh binary, graphify binary + skill, gitnexus MCP, .mcp.json entries
 **Optional:** docker, sonar-scanner, vsaf MCP (only for coroutine engine)

package/skills/sdlc/setup/SKILL.md

@@ -28,7 +28,7 @@ Run the install script:
 node "$(vsaf skill path sdlc)/install-deps.mjs"
 ```
 
-If `vsaf skill path` is not available, find `install-deps.mjs` in the SDLC skill pack directory (`.vsaf/skills/` or the installed pack location) and run it with `node`.
+If `vsaf skill path` is not available, find `install-deps.mjs` in the SDLC skill pack directory (`.claude/skills/` or the installed pack location) and run it with `node`.
 
 This script will:
 - Ensure `package.json` exists

package/skills/sdlc/srs/SKILL.md

@@ -45,12 +45,13 @@ All output documents (05-srs.md) MUST be written in Vietnamese. Section headers,
 [SRS] [2/3] Writing SRS from PRD + ADR... ⏳
 ```
 
-Use `/bmad-agent-analyst` — derive SRS from PRD + ADR.
-Each FR/NFR must have:
-- Unique ID (FR-001, NFR-001)
-- Trace to PRD user story (US-xxx)
-- Input/Output spec
-- Constraints
+Derive SRS from PRD + ADR. For each FR/NFR:
+
+1. **Unique ID** — FR-001, NFR-001 (sequential, no gaps)
+2. **Traceability** — trace to PRD user story (US-xxx)
+3. **Input/Output spec** — `{class}.{method}({params}): {return}` or API contract
+4. **Constraints** — performance, security, data validation rules
+5. **Pre/Post conditions** — system state before and after execution
 
 Write to `05-srs.md`.
 

package/skills/sdlc/test-design/SKILL.md

@@ -37,12 +37,16 @@ You are a QA Lead. Your mission: design test cases FROM the SRS (spec), NOT from
 [TEST-DESIGN] [2/4] Generating test cases from SRS... ⏳
 ```
 
-Use `/bmad-qa-generate-e2e-tests` — derive tests from SRS FRs/NFRs.
-Each test case must have:
-- Unique ID (TC-001)
-- Trace to FR/NFR → PRD user story
-- Type: unit / integration / e2e
-- Precondition, Steps, Expected result
+Derive test cases from SRS FRs/NFRs. For each requirement, design ≥1 test case:
+
+1. **Unique ID** — TC-001 (sequential)
+2. **Traceability** — TC → FR/NFR → PRD user story (US-xxx)
+3. **Type** — unit / integration / e2e (based on requirement scope)
+4. **Precondition** — system state before test
+5. **Steps** — exact actions to execute
+6. **Expected result** — concrete, verifiable outcome (not "should work")
+
+Prioritize: happy path first, then error paths, then edge cases.
 
 ```
 [TEST-DESIGN] [2/4] Generating test cases from SRS... ✅

package/skills/sdlc/workflows/hotfix-tdd.yaml

@@ -3,11 +3,11 @@ description: "Sub-flow: TDD RED → GREEN → Test Gate — write failing test,
 
 nodes:
   - id: red
-    command: hotfix-red
+    command: sdlc-hotfix-red
     depends_on: []
 
   - id: green
-    command: hotfix-green
+    command: sdlc-hotfix-green
     depends_on: [red]
 
   - id: test-gate

package/skills/sdlc/workflows/hotfix.yaml

@@ -3,15 +3,15 @@ description: "Hotfix — Bug report → Analyze → TDD (RED → GREEN) → Test
 
 nodes:
   - id: analyze
-    command: hotfix-analyze
+    command: sdlc-hotfix-analyze
     workspace: false
 
   - id: red
-    command: hotfix-red
+    command: sdlc-hotfix-red
     depends_on: [analyze]
 
   - id: green
-    command: hotfix-green
+    command: sdlc-hotfix-green
     depends_on: [red]
 
   - id: test-gate
@@ -24,11 +24,11 @@ nodes:
       inject_error: true
 
   - id: review
-    command: hotfix-review
+    command: sdlc-hotfix-review
     depends_on: [test-gate]
     workspace: false
 
   - id: ship
-    command: ship
+    command: sdlc-ship
     depends_on: [review]
     workspace: false

package/skills/sdlc/workflows/master-sdlc.yaml

@@ -2,26 +2,26 @@ name: master-sdlc
 description: "Full SDLC pipeline — Discovery → PRD → Architecture → SRS → Test Design → Implement → Review → Feature Complete → Ship"
 nodes:
   - id: discovery
-    command: discovery
+    command: sdlc-discovery
     workspace: false
   - id: prd
-    command: prd
+    command: sdlc-prd
     depends_on: [discovery]
     workspace: false
   - id: architecture
-    command: architecture
+    command: sdlc-architecture
     depends_on: [prd]
     workspace: false
   - id: srs
-    command: srs
+    command: sdlc-srs
     depends_on: [architecture]
     workspace: false
   - id: test-design
-    command: test-design
+    command: sdlc-test-design
     depends_on: [srs]
     workspace: false
   - id: implement
-    command: implement
+    command: sdlc-implement
     depends_on: [test-design]
   - id: test-gate
     bash: |
@@ -32,14 +32,14 @@ nodes:
       max_retries: 3
       inject_error: true
   - id: review
-    command: review
+    command: sdlc-review
     depends_on: [test-gate]
     workspace: false
   - id: complete
-    command: feature-complete
+    command: sdlc-feature-complete
     depends_on: [review]
     workspace: false
   - id: ship
-    command: ship
+    command: sdlc-ship
     depends_on: [complete]
     workspace: false

package/skills/sdlc/workflows/onboarding.yaml

@@ -2,8 +2,8 @@ name: onboarding
 description: "Utility — Onboarding: docs graph + code graph + env setup (not part of main flow)"
 nodes:
   - id: docs
-    command: onboard-docs
+    command: sdlc-onboard-docs
     workspace: false
   - id: code
-    command: onboard-code
+    command: sdlc-onboard-code
     workspace: false

package/skills/sdlc/workflows/sdlc-build.yaml

@@ -3,7 +3,7 @@ description: "Sub-flow: Implement → Test Gate — TDD code + automated test ve
 
 nodes:
   - id: implement
-    command: implement
+    command: sdlc-implement
     depends_on: []
 
   - id: test-gate

package/skills/sdlc/workflows/sdlc-design.yaml

@@ -3,10 +3,10 @@ description: "Sub-flow: Architecture → SRS — design solution and write detai
 
 nodes:
   - id: architecture
-    command: architecture
+    command: sdlc-architecture
     workspace: false
 
   - id: srs
-    command: srs
+    command: sdlc-srs
     depends_on: [architecture]
     workspace: false

package/skills/sdlc/workflows/sdlc-qa.yaml

@@ -3,15 +3,15 @@ description: "Sub-flow: Review → Feature Complete → Ship — quality gate +
 
 nodes:
   - id: review
-    command: review
+    command: sdlc-review
     workspace: false
 
   - id: complete
-    command: feature-complete
+    command: sdlc-feature-complete
     depends_on: [review]
     workspace: false
 
   - id: ship
-    command: ship
+    command: sdlc-ship
     depends_on: [complete]
     workspace: false

package/skills/sdlc/workflows/sdlc-testcase.yaml

@@ -3,5 +3,5 @@ description: "Sub-flow: Test Design — generate test cases from SRS (tests befo
 
 nodes:
   - id: test-design
-    command: test-design
+    command: sdlc-test-design
     workspace: false

package/skills/sdlc/workflows/sdlc-thinking.yaml

@@ -3,10 +3,10 @@ description: "Sub-flow: Discovery → PRD — understand the problem space befor
 
 nodes:
   - id: discovery
-    command: discovery
+    command: sdlc-discovery
     workspace: false
 
   - id: prd
-    command: prd
+    command: sdlc-prd
     depends_on: [discovery]
     workspace: false