@ngocsangairvds/vsaf 3.0.11 → 3.1.0

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

@@ -1,12 +1,12 @@
 ---
 name: vsaf-ship
-description: Review 2 lớp, ship code, và ghi lại knowledge vào bộ nhớ. Dùng sau /vsaf-build khi code + tests đã pass. Bước cuối cùng của mọi feature.
+description: Review 2 lớp, ship code. Dùng sau /vsaf-build khi code + tests đã pass. Bước cuối cùng của mọi feature.
 ---
 
 # VSAF Ship
 
 ## Mục tiêu
-Đảm bảo code chất lượng, đóng gói feature, và ghi lại toàn bộ knowledge để các session sau kế thừa được.
+Đảm bảo code chất lượng, đóng gói feature, và push PR.
 
 ## Điều kiện tiên quyết
 - Đã chạy `/vsaf-build` với SRS + testcase
@@ -14,39 +14,57 @@ description: Review 2 lớp, ship code, và ghi lại knowledge vào bộ nhớ.
 
 ## Các bước thực hiện
 
-### Bước 1 — Review Layer 1: Methodology (Superpowers)
-- Dùng skill `superpowers:code-review`
+### Bước 1 — Review Layer 1: Code Review
+- **Nếu có Superpowers**:
+  - Dùng `superpowers:code-review` — review code against plan, standards, architecture
+  - Dùng `superpowers:verification-before-completion` — đảm bảo không bỏ sót verification step
+- **Nếu không có Superpowers**: dùng skill `bmad-code-review` (đã có sẵn trong bộ cài)
 - Kiểm tra: code structure, naming, patterns, SOLID principles
 - Fix issues nếu có, commit lại
 
-### Bước 2 — Review Layer 2: Knowledge graph sync
+### Bước 2 — Review Layer 1.5: Adversarial Review
+- Dùng skill `bmad-review-adversarial-general` — cynical attack trên code mới
+  - Tìm: logic flaws, security holes, performance traps, silent failures
+- Dùng skill `bmad-review-edge-case-hunter` — exhaustive boundary analysis
+  - Tìm: unhandled null/empty, off-by-one, concurrent access, resource leaks
+- Triage findings:
+  - **MUST FIX**: fix ngay trước khi ship
+  - **SHOULD FIX**: tạo follow-up task
+  - **NOTED**: ghi nhận, không cần action
+
+### Bước 3 — Review Layer 2: Knowledge graph sync
 - Chạy `gitnexus analyze` để cập nhật call graph
 - Hoặc: `vsaf index`
 - Đây là layer cuối cùng — đảm bảo index reflect đúng code mới
 
-### Bước 3 — Ghi nhớ vào MemPalace
-- Gọi `mcp__mempalace__mempalace_add_drawer` để lưu decisions quan trọng từ feature này
-- Gọi `mcp__mempalace__mempalace_diary_write` để ghi lại session summary
+### Bước 4 — Pre-PR checklist
+- **Nếu có Superpowers**: dùng `superpowers:finishing-a-development-branch` — chạy pre-PR checklist tự động
+- **Nếu không**: kiểm tra thủ công: tests pass, no uncommitted changes, branch up-to-date
 
-### Bước 4 — Push PR
+### Bước 5 — Push PR
 ```bash
 git push origin feature/<name>
 ```
 PR description phải bao gồm:
 - Impact summary (từ GitNexus)
 - Test results summary
+- Adversarial review summary (MUST FIX: 0, SHOULD FIX: N)
+
+### Bước 6 — Retrospective (sau mỗi epic hoặc khi user yêu cầu)
+- **Nếu đây là feature cuối cùng của epic**: dùng skill `bmad-retrospective`
+  - Review: gì đã tốt? gì cần cải thiện? surprise nào?
+  - Cập nhật workflow nếu cần
+- **Nếu không phải cuối epic**: skip, nhắc user chạy retro sau khi epic hoàn thành
 
-### Bước 5 — Output cho user
+### Bước 7 — Output cho user
 ```
 ## Ship Complete: [feature]
 
 ### Reviews
-- Layer 1 (Methodology): PASS
-- Layer 2 (Graph sync):   PASS
-
-### Knowledge saved
-- Diary entry: ✓
-- Decisions: [X entries]
+- Layer 1 (Code Review):       PASS [superpowers / bmad-code-review]
+- Layer 1.5 (Adversarial):     PASS [MUST FIX: 0, SHOULD FIX: N, NOTED: N]
+- Layer 2 (Graph sync):        PASS
+- Pre-PR checklist:             PASS
 
 ### PR
 - Branch: feature/[name]
@@ -56,5 +74,5 @@ Workflow hoàn tất. Chạy /vsaf-plan <next-feature> cho task tiếp theo.
 ```
 
 ## Lưu ý
-- Không ship nếu bất kỳ layer review nào fail
-- `vsaf mine` — chạy weekly, không phải mỗi feature
+- Không ship nếu bất kỳ layer review nào fail hoặc còn MUST FIX
+- Retrospective: chạy sau mỗi epic (3-5 features), không phải mỗi feature

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

@@ -0,0 +1,111 @@
+---
+name: vsaf-sprint
+description: Sprint management — break PRD thành epics/stories, lập sprint plan, tracking progress. Dùng khi cần quản lý nhiều features cùng lúc.
+---
+
+# VSAF Sprint
+
+## Mục tiêu
+Quản lý backlog và sprint cho dự án — từ PRD/SRS chia thành stories, lập plan, track progress, surface risks.
+
+## Input
+`$ARGUMENTS` — hành động cần làm:
+- `plan` — lập sprint plan mới từ PRD/epics
+- `status` — xem trạng thái sprint hiện tại
+- `story <id>` — tạo story file chi tiết cho 1 story
+
+## Khi nào dùng
+- Sau `/vsaf-discover` khi đã có PRD
+- Khi dự án có nhiều features cần ưu tiên
+- Khi cần visibility vào progress tổng thể
+
+## Các bước thực hiện
+
+### Mode: `plan` — Lập sprint plan mới
+
+#### Bước 1 — Break thành Epics + Stories
+- Dùng skill `bmad-create-epics-and-stories` với PRD/SRS làm input
+- Output: danh sách epics, mỗi epic chứa user stories
+- Mỗi story có: description, acceptance criteria, estimated complexity (S/M/L/XL)
+
+#### Bước 2 — Sprint Planning
+- Dùng skill `bmad-sprint-planning` để:
+  - Ưu tiên stories (MoSCoW hoặc WSJF)
+  - Assign stories vào sprint dựa trên capacity
+  - Identify dependencies giữa stories
+- Lưu sprint plan vào `docs/project/planning-artifacts/sprint-plan.md`
+
+#### Bước 3 — Output
+```
+## Sprint Plan: [sprint name/number]
+
+### Capacity: [X story points / N stories]
+
+### Stories in sprint
+| # | Story | Epic | Size | Priority | Depends on |
+|---|-------|------|------|----------|------------|
+| 1 | ...   | ...  | M    | MUST     | -          |
+| 2 | ...   | ...  | L    | MUST     | #1         |
+
+### Deferred to next sprint
+| Story | Reason |
+|-------|--------|
+
+### Next step
+Chạy /vsaf-sprint story <id> để tạo story file chi tiết
+Hoặc: /vsaf-plan <story description> để bắt đầu feature đầu tiên
+```
+
+---
+
+### Mode: `status` — Xem trạng thái sprint
+
+#### Bước 1 — Collect status
+- Dùng skill `bmad-sprint-status` để:
+  - Scan sprint plan file
+  - Check git log cho completed stories
+  - Surface: blocked items, risks, velocity trend
+
+#### Bước 2 — Output
+```
+## Sprint Status: [sprint name]
+
+### Progress: [X/Y stories done] ([Z%])
+### Burndown: [on track / behind / ahead]
+
+### Completed
+- [x] Story #1: ...
+- [x] Story #2: ...
+
+### In Progress
+- [ ] Story #3: ... (blocked by: ...)
+
+### Risks
+- [risk description + mitigation]
+
+### Recommendation
+[Continue / adjust scope / escalate]
+```
+
+---
+
+### Mode: `story <id>` — Tạo story file chi tiết
+
+#### Bước 1 — Tạo story file
+- Dùng skill `bmad-create-story` với story ID từ sprint plan
+- Story file bao gồm: full context, acceptance criteria, technical notes, dependencies
+- Lưu vào `docs/project/planning-artifacts/stories/story-[id].md`
+
+#### Bước 2 — Output
+```
+## Story Created: [story title]
+- File: docs/project/planning-artifacts/stories/story-[id].md
+
+### Next step
+Chạy /vsaf-plan <story description> để plan implementation
+```
+
+## Lưu ý
+- Sprint plan là living document — cập nhật khi có thay đổi
+- Re-run `/vsaf-sprint status` hàng ngày hoặc sau mỗi `/vsaf-ship`
+- Nếu sprint bị delay >20%: dùng `bmad-correct-course` để điều chỉnh scope

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

@@ -19,16 +19,22 @@ Tạo tài liệu testcase coverage đầy đủ từ SRS để làm contract ch
 - Test cases phải cover: happy path, edge cases, error cases, NFRs
 - Nguồn gốc: từ FRs/NFRs trong SRS — KHÔNG dựa trên implementation
 
-### Bước 2 — Đối chiếu coverage
+### Bước 2 — Hunt edge cases (BMAD edge case hunter)
+- Dùng skill `bmad-review-edge-case-hunter` với SRS + testcases đã sinh
+- Tìm: boundary conditions, race conditions, empty/null inputs, overflow, concurrent access
+- Bổ sung test cases cho mọi edge case chưa cover
+- Mục tiêu: không có unhandled edge case nào lọt qua
+
+### Bước 3 — Đối chiếu coverage
 - So sánh test cases với FR/NFR trong SRS
 - Mỗi FR/NFR phải có ít nhất 1 test case tương ứng
 - Ghi nhận gaps nếu có
 
-### Bước 3 — Xuất traceability matrix
+### Bước 4 — Xuất traceability matrix
 - Tạo bảng mapping `FR/NFR -> Testcase ID`
 - Mỗi testcase có: input, expected output, pass/fail criteria
 
-### Bước 4 — Lưu tài liệu testcase
+### Bước 5 — Lưu tài liệu testcase
 - Lưu testcase vào `docs/project/testcases/[feature].md`
 - Format:
 
@@ -47,12 +53,28 @@ Tạo tài liệu testcase coverage đầy đủ từ SRS để làm contract ch
 | ...       | ...   | ...      | [ ]    |
 ```
 
-### Bước 5 — Output cho user
-- Trả về đường dẫn file testcase + coverage summary theo FR/NFR
-- Nêu rõ gaps cần bổ sung trước khi build
+### Bước 6 — Implementation readiness gate (BMAD)
+- Dùng skill `bmad-check-implementation-readiness` để validate toàn bộ artifacts
+- Kiểm tra: SRS đầy đủ? Testcases cover hết FRs/NFRs? Architecture align?
+- Nếu **PASS**: hiển thị `✓ Implementation ready — proceed to /vsaf-build`
+- Nếu **FAIL**: liệt kê gaps cần fix trước khi build, KHÔNG cho tiếp
+
+### Bước 7 — Output cho user
+```
+## Testcase Summary: [feature]
+
+- Total test cases: [N]
+- FR/NFR coverage: [X/Y] ([%])
+- Edge cases found by hunter: [N]
+- Implementation readiness: [PASS / FAIL]
+
+Files:
+- docs/project/testcases/[feature].md
 
 ## Next step
-Chạy `/vsaf-build <path/to/srs> <path/to/testcases>` để implement theo testcase đã chuẩn hoá.
+[Nếu PASS]: Chạy /vsaf-build <path/to/srs> <path/to/testcases>
+[Nếu FAIL]: Fix gaps listed above, then re-run /vsaf-test
+```
 
 ## Lưu ý
 - Không đánh dấu implementation done ở bước này

package/README.md

@@ -10,6 +10,9 @@ every decision. $20/month total.
 
 ```
 ┌──────────────────────────────────────────────────────────────────────┐
+│  DISCOVERY         BMAD (agents)                                     │
+│                    PM · Analyst · domain/market/tech research        │
+├──────────────────────────────────────────────────────────────────────┤
 │  PLANNING          BMAD (agents)                                     │
 │                    Analyst · Architect · Brainstorming · QA          │
 ├──────────────────────────────────────────────────────────────────────┤
@@ -21,6 +24,9 @@ every decision. $20/month total.
 ├──────────────────────────────────────────────────────────────────────┤
 │  IMPLEMENTATION    Claude Code + Superpowers                         │
 │                    TDD execution, code review                        │
+├──────────────────────────────────────────────────────────────────────┤
+│  KNOWLEDGE         Graphify + BMAD (tech writer, editors)            │
+│                    wiki, docs sync, distillation                     │
 └──────────────────────────────────────────────────────────────────────┘
 ```
 
@@ -95,26 +101,56 @@ Run `npx @ngocsangairvds/vsaf@latest --help` for the full list. Highlights:
 
 Main skill commands inside Claude Code:
 
+- `/vsaf-discover <product/domain>` — product discovery *(new)*
+- `/vsaf-sprint plan|status|story` — sprint management *(new)*
 - `/vsaf-onboard`
 - `/vsaf-plan <feature>`
 - `/vsaf-doc`
 - `/vsaf-test <path/to/srs>`
 - `/vsaf-build <path/to/srs> <path/to/testcases>`
 - `/vsaf-ship`
+- `/vsaf-docs` — documentation sync *(new)*
 
 ## Workflow
 
-Every feature follows an **SRS-first cycle**:
+Full product lifecycle:
 
 ```
-/vsaf-onboard → /vsaf-plan → /vsaf-doc → /vsaf-test → /vsaf-build → /vsaf-ship
+/vsaf-discover → /vsaf-sprint plan → [per feature in sprint]:
+  /vsaf-onboard → /vsaf-plan → /vsaf-doc → /vsaf-test → /vsaf-build → /vsaf-ship
+→ /vsaf-docs → /vsaf-sprint status → next sprint
 ```
 
-Bug fixes (Quick Flow) may use mini-SRS + mini-testcases, but still require
-`gitnexus_impact` before editing symbols and `gitnexus_detect_changes` before commit.
+Every feature follows an **SRS-first cycle**. Bug fixes (Quick Flow) may use
+mini-SRS + mini-testcases, but still require `gitnexus_impact` before editing
+symbols and `gitnexus_detect_changes` before commit.
 
 ### Flow breakdown
 
+#### `/vsaf-discover <product/domain>` — Product discovery *(new)*
+| Step | Tool | Does |
+|------|------|------|
+| 1 | **MemPalace** `mempalace_search` | Checks for prior research |
+| 2 | **BMAD** `bmad-domain-research` | Deep dive into domain/industry terminology, rules, patterns |
+| 3 | **BMAD** `bmad-market-research` | Competition landscape, customer needs, market trends |
+| 4 | **BMAD** `bmad-technical-research` | Tech stack options, feasibility, build-vs-buy |
+| 5 | **BMAD** `bmad-product-brief` | Synthesises findings into product brief |
+| 6 | **BMAD** `bmad-prfaq` | Working Backwards — stress-tests product concept |
+| 7 | **BMAD** `bmad-agent-pm` + `bmad-create-prd` | PM creates PRD from brief; `bmad-validate-prd` checks quality; `bmad-edit-prd` fixes issues |
+| 8 | **BMAD** `bmad-party-mode` | Multi-agent roundtable: PM + Analyst + Architect review |
+| 9 | **MemPalace** `mempalace_add_drawer` | Saves market insights + product decisions |
+| → | Output | Research artifacts, product brief, validated PRD, open questions |
+
+#### `/vsaf-sprint plan|status|story` — Sprint management *(new)*
+| Mode | Tool | Does |
+|------|------|------|
+| **plan** | **BMAD** `bmad-create-epics-and-stories` | Breaks PRD into epics + prioritised user stories |
+| **plan** | **BMAD** `bmad-sprint-planning` | Assigns stories to sprint, identifies dependencies |
+| **plan** | **MemPalace** `mempalace_add_drawer` | Saves sprint decisions, priorities, trade-offs |
+| **status** | **BMAD** `bmad-sprint-status` | Progress %, burndown, blocked items, risks |
+| **story** | **BMAD** `bmad-create-story` | Creates detailed story file with full context for implementation |
+| → | Output | Sprint plan, status dashboard, or story file |
+
 #### `/vsaf-onboard` — Understand the codebase
 | Step | Tool | Does |
 |------|------|------|
@@ -130,44 +166,72 @@ Bug fixes (Quick Flow) may use mini-SRS + mini-testcases, but still require
 | 3 | **GitNexus** `mcp__gitnexus__impact` + `query` | Blast radius — how many modules touched, risk level |
 | 4 | **Graphify** `/graphify path A B` *(if needed)* | Traces dependency path between two services |
 | 5 | **BMAD** `bmad-agent-architect` (Winston) | Proposes architecture approach, compares alternatives |
+| 5b | **BMAD** `bmad-create-architecture` *(if HIGH risk / >3 modules)* | Formal ADR → `docs/project/planning-artifacts/adr-[feature].md` |
 | 6 | **BMAD** `bmad-brainstorming` | Creative exploration — min. 20 alternatives / risk angles |
-| → | Output | Scope, impact report, chosen approach, rejected alternatives |
+| 7 | **BMAD** `bmad-advanced-elicitation` | Pre-mortem + red team — challenges chosen approach, finds failure modes |
+| → | Output | Scope, impact, approach, pre-mortem findings, rejected alternatives |
 
 #### `/vsaf-doc` — Write the SRS
 | Step | Tool | Does |
 |------|------|------|
+| 0 | *(Claude)* | Detects mode: **CREATE** (new SRS) or **EDIT** (modify existing) |
 | 1 | **MemPalace** `mempalace_search` | Checks for old decisions to reference in SRS |
-| 2 | *(Claude)* | Writes SRS with FRs/NFRs/acceptance criteria + traceability IDs → `docs/project/srs/` |
-| 3 | *(Claude)* | Writes implement notes: affected modules, technical constraints |
-| 4 | **MemPalace** `mempalace_add_drawer` | Persists chosen approach + rejected alternatives |
-| → | Output | `docs/project/srs/[feature].md` ready for testcase generation |
+| 2a | **BMAD** `bmad-create-prd` *or* *(Claude)* | **CREATE mode**: writes SRS/PRD with FRs/NFRs + traceability IDs |
+| 2b | **BMAD** `bmad-edit-prd` | **EDIT mode**: modifies existing SRS in-place, preserves traceability IDs, flags testcase impact |
+| 3 | **BMAD** `bmad-validate-prd` | Validates SRS quality; if FAIL in EDIT mode → `bmad-edit-prd` fixes again |
+| 4 | *(Claude)* | Writes implement notes: affected modules, technical constraints |
+| 5 | **MemPalace** `mempalace_add_drawer` | Persists chosen approach + rejected alternatives |
+| → | Output | Validated `docs/project/srs/[feature].md` + testcase impact report |
 
 #### `/vsaf-test <path/to/srs>` — Generate testcases
 | Step | Tool | Does |
 |------|------|------|
 | 1 | **BMAD** `bmad-qa-generate-e2e-tests` | Derives unit / integration / edge-case tests from SRS FRs/NFRs |
-| 2 | *(Claude)* | Validates every FR/NFR has ≥ 1 test, records gaps |
-| 3 | *(Claude)* | Builds FR/NFR → Testcase ID traceability matrix |
+| 2 | **BMAD** `bmad-review-edge-case-hunter` | Finds unhandled boundaries, race conditions, null/empty cases — adds tests |
+| 3 | *(Claude)* | Validates every FR/NFR has ≥ 1 test, builds traceability matrix |
 | 4 | *(Claude)* | Saves to `docs/project/testcases/[feature].md` |
-| → | Output | Testcase contract — used as implementation guardrails |
+| 5 | **BMAD** `bmad-check-implementation-readiness` | **Quality gate** — blocks build if SRS/testcase/architecture gaps found |
+| → | Output | Testcase contract + implementation readiness verdict (PASS/FAIL) |
 
 #### `/vsaf-build <path/to/srs> <path/to/testcases>` — Implement with TDD
 | Step | Tool | Does |
 |------|------|------|
+| 0 | **Superpowers** check | Detects plugin. If yes → uses write-plan, execute-plan, TDD, debugging. If no → warns + fallback |
 | 1 | **MemPalace** `mempalace_search` | Last check — no old decisions conflict with implementation |
 | 2 | *(Claude)* | Reads SRS + testcases, confirms FR/NFR → testcase mapping |
-| 3 | **Claude Code** (TDD loop) | RED → GREEN → REFACTOR per testcase group |
-| 3b | **GitNexus** `mcp__gitnexus__detect_changes` | Verifies only intended files changed before each commit |
+| 3 | **Superpowers** `write-plan` *or* *(Claude)* | Generates atomic task list from SRS + testcases |
+| 4 | **Superpowers** `execute-plan` + `test-driven-development` *or* **Claude Code** | TDD loop per task. Large plans (20+): `subagent-driven-development` |
+| 4b | **GitNexus** `mcp__gitnexus__detect_changes` | Verifies only intended files changed before each commit |
+| 4.5 | **BMAD** `bmad-checkpoint-preview` *(every 3-5 tasks)* | Human-in-the-loop review — summarise progress, flag issues, ask user to continue |
+| 5 | **Superpowers** `systematic-debugging` *or* manual | On failure: structured hypothesis → experiment → conclusion |
+| 5b | **BMAD** `bmad-correct-course` *(if scope drift detected)* | Assesses impact of scope change, proposes adjusted plan vs re-plan |
 | → | Output | Working code, all tests passing, 1 commit per task |
 
 #### `/vsaf-ship` — Review, sync, and record
 | Step | Tool | Does |
 |------|------|------|
-| 1 | **Superpowers** `superpowers:code-review` | Layer 1 — structure, naming, SOLID, patterns |
-| 2 | **GitNexus** `gitnexus analyze` / `vsaf index` | Layer 2 — updates call graph to reflect new code |
-| 3 | **MemPalace** `mempalace_add_drawer` + `diary_write` | Saves decisions + session summary for future sessions |
-| 4 | *(git)* | Push branch, open PR with impact summary + test results |
-| → | Output | Shipped feature, updated graph, persistent knowledge |
+| 1 | **Superpowers** `code-review` + `verification-before-completion` *or* **BMAD** `bmad-code-review` | Layer 1 — code quality, patterns, SOLID |
+| 2 | **BMAD** `bmad-review-adversarial-general` + `bmad-review-edge-case-hunter` | Layer 1.5 — cynical attack + boundary analysis. Triage: MUST FIX / SHOULD FIX / NOTED |
+| 3 | **GitNexus** `gitnexus analyze` / `vsaf index` | Layer 2 — updates call graph to reflect new code |
+| 4 | **Superpowers** `finishing-a-development-branch` *or* manual | Pre-PR checklist |
+| 5 | **MemPalace** `mempalace_add_drawer` + `diary_write` | Saves decisions, adversarial findings, session summary |
+| 6 | *(git)* | Push branch, open PR with impact + test + adversarial summary |
+| 7 | **BMAD** `bmad-retrospective` *(end of epic only)* | Lessons learned → MemPalace. What went well / what to improve |
+| → | Output | Shipped feature, updated graph, persistent knowledge, follow-up tasks |
+
+#### `/vsaf-docs` — Documentation & knowledge sync *(new)*
+| Step | Tool | Does |
+|------|------|------|
+| 1 | **GitNexus** `query` + **MemPalace** `search` | Scans codebase + decisions, finds stale docs |
+| 2 | **BMAD** `bmad-document-project` | Generates/updates project documentation from code |
+| 3 | **BMAD** `bmad-generate-project-context` | Creates `project-context.md` — AI agent instructions |
+| 4 | **BMAD** `bmad-agent-tech-writer` (Paige) | Reviews docs for clarity, completeness, consistency |
+| 5 | **BMAD** `bmad-editorial-review-prose` + `bmad-editorial-review-structure` | Polish prose + restructure for readability |
+| 6 | **BMAD** `bmad-distillator` | Compresses long docs into LLM-optimised format |
+| 7 | **BMAD** `bmad-index-docs` | Generates `index.md` for each docs folder |
+| 8 | **Graphify** `/graphify . --wiki` | Builds agent-crawlable wiki from codebase |
+| 9 | **MemPalace** `diary_write` | Records what was updated/replaced |
+| → | Output | Updated docs, project context, wiki, doc indexes |
 
 ### Generated docs path convention
 
@@ -187,22 +251,23 @@ Bug fixes (Quick Flow) may use mini-SRS + mini-testcases, but still require
 
 See [1-setup-guide.md § Your First Project](docs/onboarding/1-setup-guide.md#5-your-first-project--a-walkthrough)
 for a walkthrough, or [2-workflow-guide.md § JWT Demo](docs/onboarding/2-workflow-guide.md#4-full-sdlc-demo)
-for a full command-by-command example.
+for a full code-by-code example.
 
 ## Tools
 
 | Tool | What It Does | Cost |
 |---|---|---|
 | **Claude Code** | AI coding agent — everything else plugs into it | $20/mo |
-| **BMAD Method** | AI agents for planning: Analyst, Architect, Brainstorming, QA | Free |
-| **Superpowers** | Methodology engine: code review | Free |
+| **BMAD Method** | AI agents for full lifecycle: PM, Analyst, Architect, QA, Tech Writer, Code Review + 40 skills | Free |
+| **Superpowers** | Claude Code plugin: plan execution, TDD, debugging, code review, pre-PR checklist *(optional — BMAD/manual fallback)* | Free |
 | **GitNexus** | Code knowledge graph via MCP — impact analysis, dependency queries | Free |
 | **MemPalace** | Knowledge base — verbatim storage of decisions, temporal knowledge graph | Free |
-| **Graphify** | Any input → knowledge graph → clustered communities, dependency tracing between services | Free |
+| **Graphify** | Any input → knowledge graph → clustered communities, dependency tracing, wiki | Free |
 
 ---
 
-**Core principles:** Onboard first. SRS before implementation. Testcases derived from SRS.
-Impact analysis before touching any symbol. Run `gitnexus_detect_changes` before commit.
-2-layer review before every PR. Re-index after every merge. Mine decisions weekly and after major decisions.
+**Core principles:** Discover before planning. Onboard first. SRS before implementation.
+Testcases derived from SRS. Impact analysis before touching any symbol.
+Run `gitnexus_detect_changes` before commit. 2-layer review before every PR.
+Re-index after every merge. Mine decisions weekly. Sync docs every sprint.
 MemPalace = decisions. Not CLAUDE.md.