@anhth2/spec-driven-dev-plugin 0.8.0 → 0.9.1

package/commands/report-bug.tmpl

@@ -0,0 +1,131 @@
+# /report-bug — File a Spec-Traced Bug (Tester-Facing)
+
+For **testers**. Produces a structured bug report with full spec context, classifies the likely
+layer, and saves it for handoff to the dev team.
+
+**READ-ONLY on specs and code.** This command never edits PRD, BDD, tech-docs, or source.
+Fixing is the dev's job (`/fix-bug`); writing scenarios is `/propose-scenario`.
+
+Usage: `/report-bug {UC-ID or TICKET} {short description}`
+Example: `/report-bug FT-001 account locks after 6 failed logins, spec says 5`
+
+## Gate
+{{include:steps/gate.md}}
+
+*Note: For this command, the target in Step 1 is a UC-ID / TICKET from `$ARGUMENTS`. Resolve the matching `.feature` file if one exists; if not, continue — a bug can still be filed.*
+
+## Context
+{{include:steps/context-loader.md}}
+
+---
+
+## Step 1 — Resolve Spec Context
+
+Locate the spec chain for the bug's UC/TICKET. Prefer `spec-manifest.yaml` (umbrella/tester setup) if present; else use resolved `paths`.
+
+Gather and store:
+- `prd_path` + current PRD `Version`
+- `bdd_path` (the `.feature` for this UC) + the specific **failing scenario** title, if one matches
+- `tech_doc_path` (if any)
+- `service` / domain
+
+If no `.feature` scenario matches the reported behavior → set `coverage_gap = true` (the behavior is untested by BDD).
+
+## Step 2 — Gather Bug Details
+
+If not already in `$ARGUMENTS`, ask the tester (one compact prompt):
+
+```
+File a bug — answer what you can:
+  1. Where does it occur? (endpoint / screen / flow)
+  2. Steps to reproduce?
+  3. Expected (per spec) vs Actual?
+  4. Error / log / status code?
+  5. Environment? (staging / prod / local)
+```
+
+## Step 3 — Identify the AC Violated
+
+Read the PRD acceptance criteria for this UC. Match the bug to the specific **AC** it violates
+(e.g. `AC3: "5 failed logins → lock 30m"`). Quote it verbatim. If the behavior maps to no AC →
+note "No AC covers this" and treat as a possible PRD gap.
+
+## Step 4 — Classify Likely Layer (BUG_FLOW)
+
+Apply the BUG_FLOW decision table to suggest where the root cause likely is — this routes the bug:
+
+| If… | Likely layer | Route to |
+|------|-------------|----------|
+| Code contradicts a BDD scenario | **Code bug** (Case 1) | Dev → `/fix-bug` |
+| BDD scenario contradicts PRD AC | **BDD bug** (Case 2) | Dev/PO fix BDD |
+| PRD AC is ambiguous / silent | **PRD ambiguity** (Case 3) | PO clarifies PRD |
+| Behavior correct but **no scenario covers it** | **BDD coverage gap** | Tester → `/propose-scenario` |
+| UI ≠ Design Spec | **Design Spec bug** (Case 5) | Dev/Designer |
+| Env / data only | **Environment** (Case 6) | DevOps |
+
+State the classification as a suggestion (dev confirms during `/fix-bug`).
+
+## Step 5 — Write the Report
+
+Assign `BUG-{today YYYYMMDD}-{NN}` (NN = next sequence among existing reports).
+Write to `{paths.bug_reports_dir}/{BUG-ID}.md` (resolved to `{spec_source}/feedback/bug-reports/` in umbrella mode; create dir if needed) using the structure in the Output block, and also print it for pasting into Jira/Slack.
+
+## Step 6 — Handoff (so PO/Dev actually see it)
+
+The report only reaches PO/Dev if it is **committed and pushed to the shared spec repo**. A local file is a dead drop.
+
+Determine the repo that owns `{paths.bug_reports_dir}`:
+- Umbrella mode → the spec submodule at `{spec_source}`
+- Single-service → the current repo
+
+Then commit + push **that** repo:
+
+```bash
+cd {spec_source}              # umbrella: the spec submodule; single-service: omit
+git add feedback/bug-reports/{BUG-ID}.md
+git commit -m "qa(bug): {BUG-ID} — {short description}"
+git push                      # → PO/Dev see it on their next /sync
+```
+
+- If the tester lacks push rights to the spec repo → open a PR / MR instead, or hand the file to whoever owns it. Print this fallback.
+- Print the exact commands if you do not run them automatically.
+
+> PO/Dev are notified through their normal routine: `/sync` lists newly-pulled bug reports.
+
+---
+
+## Output
+
+{{include:steps/report-footer.md}}
+
+```
+🐞 {BUG-ID}  →  {paths.bug_reports_dir}/{BUG-ID}.md  (in shared spec repo)
+
+Feature  : {UC-ID} — {feature name}   |  Service: {service}   |  Severity: {Critical|Major|Minor}
+
+Spec context
+  PRD      : {prd_path} (v{prd_version})
+  BDD      : {bdd_path} → Scenario: "{scenario title}"   {or: ⚠️ no scenario covers this}
+  Tech Doc : {tech_doc_path}
+
+AC violated
+  {AC-N}: "{AC text}"
+
+Expected (per spec) : {expected}
+Actual              : {actual}
+Steps to reproduce  : {1..N}
+Environment         : {env}
+
+Likely layer : {Code | BDD | PRD | Design Spec | Env}  →  {route}
+
+Handoff : {✅ committed + pushed to spec repo | ⚠️ run the git commands above / open a PR}
+
+---
+Status : ✅ Complete (read-only on specs/code — only wrote the feedback file)
+Output Artifacts: created {paths.bug_reports_dir}/{BUG-ID}.md (pushed to shared spec repo)
+Next   :
+  - PO/Dev will see this on their next /sync
+  - Code bug      → dev runs /fix-bug {BUG-ID}
+  - PRD ambiguity → PO (BUG_FLOW Case 3)
+  - Coverage gap  → /propose-scenario {UC-ID}
+```

package/commands/review-code.md

@@ -180,6 +180,37 @@ If `services` section is present:
 - Override `paths.domain_knowledge_dir` → `{spec_source}/specs/domain-knowledge`
 - Override `paths.business_dictionary` → `{spec_source}/specs/domain-knowledge/business-dictionary.md`
 - Override `paths.core_entities` → `{spec_source}/specs/domain-knowledge/core-entities.md`
+- Override `paths.bug_reports_dir` → `{spec_source}/feedback/bug-reports`
+- Override `paths.bdd_proposals_dir` → `{spec_source}/feedback/bdd-proposals`
+
+> **Why under `spec_source`:** tester feedback (`/report-bug`, `/propose-scenario`) must land in the **shared spec repo** so PO/Dev see it when they `/sync`. In single-service mode (no `spec_source`), these default to `feedback/bug-reports` and `feedback/bdd-proposals` at repo root — still shared, same repo.
+
+---
+
+## Step 1.6 — [SERVICE CONVENTIONS] Load service-specific conventions (umbrella mode)
+
+*Skip this step entirely if `active_service` is `"unresolved"` or context is single-service mode.*
+
+When `active_service` has been resolved to a real path in Step 1.5 (e.g., `user-service/`):
+
+**1. Locate service config** — try in priority order:
+- `{active_service}/.agent/project-context.yaml`
+- `{active_service}/project-context.yaml`
+
+**2. If found, override with service-specific values:**
+
+| Variable | Source |
+|----------|--------|
+| `conventions.test_command` | service's `conventions.test_command` |
+| `conventions.build_command` | service's `conventions.build_command` |
+| `paths.trace_dir` | `{active_service}/{service paths.trace_dir}` — default: `{active_service}/.trace` |
+| `paths.specs_dir` | `{active_service}/{service paths.specs_dir}` (if set in service config, else keep Step 1.5 override) |
+
+**3. Store** `service_root = {active_service}` as the working directory anchor for all downstream commands:
+- Shell commands (`/run-tests`, `/generate-tests`) run **from within** `service_root`
+- File write operations (test files, trace TSVs) use paths **relative to** `service_root`
+
+**4. If service config not found** — keep umbrella defaults, still set `service_root = {active_service}` (path anchor is always needed even without a config override).
 
 ---
 
@@ -273,6 +304,25 @@ These two variables (`active_module`, `platform_type`) are the canonical source
 
 ---
 
+## Step 6.7 — [GUARDRAILS] Load Project Lessons (conditional)
+
+*Accumulated mistakes the AI must not repeat in this project. These are added over time via `/learn`
+or accepted during `/review-code`, `/fix-bug`, `/debug`.*
+
+Resolve the lessons file path:
+- Use `paths.lessons_file` if set (may be service-overridden in umbrella mode, Step 1.6)
+- Else default `specs/domain-knowledge/lessons-learned.md`
+- In umbrella/service mode (when `service_root` is set), if `paths.lessons_file` is unset, default to `{service_root}/.agent/project-lessons.md`
+
+If the file exists, read it and store ALL lessons as **ACTIVE GUARDRAILS** for the session:
+- Treat each lesson's **Rule** as a hard constraint — same priority as CLAUDE.md coding standards (Step 3).
+- Before generating or modifying any artifact (PRD, BDD, tech-doc, code, test), check the output against every lesson whose `category` matches the current command AND whose `scope` matches the target (domain / file).
+- If a generated output would violate a lesson → correct it **before** presenting, and note which lesson (`L-NNN`) was applied.
+
+If the file does not exist → skip silently (no lessons captured yet).
+
+---
+
 ## Step 7 — [RECAP] Working Memory Recap (anti-lost-in-middle)
 
 After loading all context, synthesize and output a compact summary block.
@@ -288,7 +338,9 @@ Layers    : {layer order from CLAUDE.md §2, e.g., Controller → Facade → Ser
 Ticket    : {ticket_prefix}-
 Dict      : {loaded — N canonical terms, M banned terms | missing}
 Entities  : {loaded — EntityA, EntityB, EntityC | missing}
+Lessons   : {loaded — N guardrails | none yet}
 Service   : {active_service} ({active_service_module}) | single-service
+Svc Root  : {service_root} — conventions + trace_dir loaded from service config | —
 Status    : {FULL | PARTIAL — missing: CLAUDE.md / business-dict / core-entities | MINIMAL}
 ```
 
@@ -405,6 +457,11 @@ Suggest the logical next command based on workflow phase:
 | /validate-traces        | DRIFT/UNTRACKED → `/generate-code {UC-ID}`; GAP → `/generate-tests {UC-ID}`; all OK → create PR |
 | /fix-bug                | Create PR and link to ticket                  |
 | /debug                  | `/fix-bug {ticket-id}` if fix needed          |
+| /report-bug             | Send to dev (`/fix-bug {BUG-ID}`); if coverage gap → `/propose-scenario {UC-ID}` |
+| /propose-scenario       | Notify PO/Dev to review the proposal in `feedback/bdd-proposals/` |
+| /learn                  | Continue working — lesson applies on next command |
+| /sync                   | `/validate-traces` for full coverage; act on any `📥 tester feedback` surfaced |
+| /update-framework       | Review `git diff .agent/`, commit; `/sync` for project content |
 
 Format the footer as:
 ```
@@ -440,3 +497,99 @@ If NEEDS_FIX ❌:
   - Logic / architecture issue             → /fix-bug {TICKET_ID}
   - Spec mismatch (code ≠ scenario)        → /generate-code {feature-file}  (re-gen affected UC)
 ```
+
+---
+
+## Offer to Record Lessons (optional)
+
+For each **Critical/Major** finding that represents a **repeatable AI mistake** during code generation
+(an architecture/standards violation the AI is likely to make again — NOT a one-off typo or an external cause), ask:
+
+```
+Finding "{issue}" looks like a repeatable mistake.
+Record it as a project lesson so /generate-code won't repeat it? (Y/N)
+```
+
+If `Y` → run the capture procedure below with `category=code-gen`, `source=/review-code {UC-ID}`,
+`scope` = the affected domain or file glob.
+
+# Capture Lesson — Record a Recurring Mistake as a Guardrail
+
+Reusable procedure to persist a "lesson" so the AI does not repeat a mistake in this project.
+Used by `/learn` (manual) and offered by `/review-code`, `/fix-bug`, `/debug` (auto).
+
+> **Project memory, not model training.** A lesson is plain text injected into context at the
+> start of every command (context-loader Step 6.7). Functionally this stops the repeat — the AI
+> sees the guardrail before it generates. No model weights change.
+
+## L1 — Resolve the lessons file
+
+Resolve `lessons_path` in this order:
+1. `paths.lessons_file` from loaded context (may be service-overridden in umbrella mode, Step 1.6)
+2. Default `specs/domain-knowledge/lessons-learned.md` (single-service)
+3. In umbrella/service mode (when `service_root` is set) default `{service_root}/.agent/project-lessons.md`
+
+## L2 — Build the lesson
+
+Gather these fields — from `$ARGUMENTS` (for `/learn`) or from the calling command's findings
+(for `/review-code`, `/fix-bug`, `/debug`):
+
+| Field | Meaning |
+|-------|---------|
+| `category` | one of: `code-gen` \| `bdd` \| `tech-docs` \| `tests` \| `prd` \| `general` |
+| `title` | short phrase naming the mistake |
+| `mistake` | concretely, what the AI did wrong |
+| `rule` | imperative correction — "Always …" / "Never …" — testable, not vague |
+| `scope` | where it applies: a domain, a file glob (e.g. `*Controller.*`), or `all` |
+| `source` | how captured: `/learn` \| `/review-code {UC-ID}` \| `/fix-bug {TICKET}` \| `/debug` |
+
+If `rule` is vague (e.g. "be careful"), rewrite it into a concrete, checkable instruction before saving.
+
+## L3 — De-duplicate
+
+Read existing lessons in `lessons_path`. If one already covers the same mistake:
+- **Refine** that entry (tighten the Rule, widen/narrow Scope, bump Date, append the new Source) — do NOT add a duplicate.
+
+Otherwise assign the next id `L-{NNN}` = (highest existing number + 1), zero-padded to 3 digits.
+
+## L4 — Write
+
+If `lessons_path` does not exist, create it with this header first:
+
+```markdown
+# Project Lessons — Learned Guardrails
+
+> Mistakes the AI must NOT repeat in this project. Loaded by context-loader at the start of
+> every command and treated as hard constraints (same priority as CLAUDE.md coding standards).
+> Add with /learn, or accept the prompt during /review-code, /fix-bug, /debug.
+> Commit this file so the whole team shares the guardrails.
+
+| Category | Applies to |
+|----------|-----------|
+| code-gen | /generate-code output |
+| bdd | /generate-bdd output |
+| tech-docs | /generate-tech-docs output |
+| tests | /generate-tests output |
+| prd | /generate-prd, /refine-prd output |
+| general | every command |
+
+---
+```
+
+Insert the new lesson directly under the `---` separator (**newest first**), in this exact shape:
+
+```markdown
+### L-{NNN} — [{category}] {title}
+- **Date**: {today YYYY-MM-DD}
+- **Scope**: {scope}
+- **Mistake**: {mistake}
+- **Rule**: {rule}
+- **Source**: {source}
+
+```
+
+## L5 — Confirm
+
+Print: `📝 Lesson {id} recorded → {lessons_path}  ([{category}] {title})`
+Then remind: `Commit {lessons_path} so the team shares this guardrail.`
+

package/commands/review-code.tmpl

@@ -85,3 +85,20 @@ If NEEDS_FIX ❌:
   - Logic / architecture issue             → /fix-bug {TICKET_ID}
   - Spec mismatch (code ≠ scenario)        → /generate-code {feature-file}  (re-gen affected UC)
 ```
+
+---
+
+## Offer to Record Lessons (optional)
+
+For each **Critical/Major** finding that represents a **repeatable AI mistake** during code generation
+(an architecture/standards violation the AI is likely to make again — NOT a one-off typo or an external cause), ask:
+
+```
+Finding "{issue}" looks like a repeatable mistake.
+Record it as a project lesson so /generate-code won't repeat it? (Y/N)
+```
+
+If `Y` → run the capture procedure below with `category=code-gen`, `source=/review-code {UC-ID}`,
+`scope` = the affected domain or file glob.
+
+{{include:steps/capture-lesson.md}}

package/commands/review-context.md

@@ -185,6 +185,37 @@ If `services` section is present:
 - Override `paths.domain_knowledge_dir` → `{spec_source}/specs/domain-knowledge`
 - Override `paths.business_dictionary` → `{spec_source}/specs/domain-knowledge/business-dictionary.md`
 - Override `paths.core_entities` → `{spec_source}/specs/domain-knowledge/core-entities.md`
+- Override `paths.bug_reports_dir` → `{spec_source}/feedback/bug-reports`
+- Override `paths.bdd_proposals_dir` → `{spec_source}/feedback/bdd-proposals`
+
+> **Why under `spec_source`:** tester feedback (`/report-bug`, `/propose-scenario`) must land in the **shared spec repo** so PO/Dev see it when they `/sync`. In single-service mode (no `spec_source`), these default to `feedback/bug-reports` and `feedback/bdd-proposals` at repo root — still shared, same repo.
+
+---
+
+## Step 1.6 — [SERVICE CONVENTIONS] Load service-specific conventions (umbrella mode)
+
+*Skip this step entirely if `active_service` is `"unresolved"` or context is single-service mode.*
+
+When `active_service` has been resolved to a real path in Step 1.5 (e.g., `user-service/`):
+
+**1. Locate service config** — try in priority order:
+- `{active_service}/.agent/project-context.yaml`
+- `{active_service}/project-context.yaml`
+
+**2. If found, override with service-specific values:**
+
+| Variable | Source |
+|----------|--------|
+| `conventions.test_command` | service's `conventions.test_command` |
+| `conventions.build_command` | service's `conventions.build_command` |
+| `paths.trace_dir` | `{active_service}/{service paths.trace_dir}` — default: `{active_service}/.trace` |
+| `paths.specs_dir` | `{active_service}/{service paths.specs_dir}` (if set in service config, else keep Step 1.5 override) |
+
+**3. Store** `service_root = {active_service}` as the working directory anchor for all downstream commands:
+- Shell commands (`/run-tests`, `/generate-tests`) run **from within** `service_root`
+- File write operations (test files, trace TSVs) use paths **relative to** `service_root`
+
+**4. If service config not found** — keep umbrella defaults, still set `service_root = {active_service}` (path anchor is always needed even without a config override).
 
 ---
 
@@ -278,6 +309,25 @@ These two variables (`active_module`, `platform_type`) are the canonical source
 
 ---
 
+## Step 6.7 — [GUARDRAILS] Load Project Lessons (conditional)
+
+*Accumulated mistakes the AI must not repeat in this project. These are added over time via `/learn`
+or accepted during `/review-code`, `/fix-bug`, `/debug`.*
+
+Resolve the lessons file path:
+- Use `paths.lessons_file` if set (may be service-overridden in umbrella mode, Step 1.6)
+- Else default `specs/domain-knowledge/lessons-learned.md`
+- In umbrella/service mode (when `service_root` is set), if `paths.lessons_file` is unset, default to `{service_root}/.agent/project-lessons.md`
+
+If the file exists, read it and store ALL lessons as **ACTIVE GUARDRAILS** for the session:
+- Treat each lesson's **Rule** as a hard constraint — same priority as CLAUDE.md coding standards (Step 3).
+- Before generating or modifying any artifact (PRD, BDD, tech-doc, code, test), check the output against every lesson whose `category` matches the current command AND whose `scope` matches the target (domain / file).
+- If a generated output would violate a lesson → correct it **before** presenting, and note which lesson (`L-NNN`) was applied.
+
+If the file does not exist → skip silently (no lessons captured yet).
+
+---
+
 ## Step 7 — [RECAP] Working Memory Recap (anti-lost-in-middle)
 
 After loading all context, synthesize and output a compact summary block.
@@ -293,7 +343,9 @@ Layers    : {layer order from CLAUDE.md §2, e.g., Controller → Facade → Ser
 Ticket    : {ticket_prefix}-
 Dict      : {loaded — N canonical terms, M banned terms | missing}
 Entities  : {loaded — EntityA, EntityB, EntityC | missing}
+Lessons   : {loaded — N guardrails | none yet}
 Service   : {active_service} ({active_service_module}) | single-service
+Svc Root  : {service_root} — conventions + trace_dir loaded from service config | —
 Status    : {FULL | PARTIAL — missing: CLAUDE.md / business-dict / core-entities | MINIMAL}
 ```
 
@@ -511,6 +563,8 @@ findings:
     check_id: "P1"           # P1-P5 for PRD; B1-B6 for BDD
     severity: "critical"     # critical | major | minor
     section: "{section or scenario ID where issue was found}"
+    uc_id: "{UC-ID this finding belongs to — PRD: the UC heading; BDD: @trace.id; \"\" if global}"
+    quote: "{verbatim snippet copied EXACTLY from the reviewed file at the issue location, ≤120 chars}"
     finding: "{clear description of the issue}"
     suggestion: "{specific actionable fix — AI will apply this in --resume if accepted}"
     auto_fixable: true       # true = AI can apply; false = human must write note in Review Board
@@ -524,6 +578,12 @@ summary:
   recommendation: "APPROVED | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the reviewed file at the exact
+> spot the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> Set `uc_id` to the owning Use Case (`@trace.id` for BDD, the UC heading for PRD; `""` if global).
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Post-Analysis Routing
 
 After running all checks and writing the findings file:
@@ -581,6 +641,11 @@ Suggest the logical next command based on workflow phase:
 | /validate-traces        | DRIFT/UNTRACKED → `/generate-code {UC-ID}`; GAP → `/generate-tests {UC-ID}`; all OK → create PR |
 | /fix-bug                | Create PR and link to ticket                  |
 | /debug                  | `/fix-bug {ticket-id}` if fix needed          |
+| /report-bug             | Send to dev (`/fix-bug {BUG-ID}`); if coverage gap → `/propose-scenario {UC-ID}` |
+| /propose-scenario       | Notify PO/Dev to review the proposal in `feedback/bdd-proposals/` |
+| /learn                  | Continue working — lesson applies on next command |
+| /sync                   | `/validate-traces` for full coverage; act on any `📥 tester feedback` surfaced |
+| /update-framework       | Review `git diff .agent/`, commit; `/sync` for project content |
 
 Format the footer as:
 ```

package/commands/review-context.tmpl

@@ -211,6 +211,8 @@ findings:
     check_id: "P1"           # P1-P5 for PRD; B1-B6 for BDD
     severity: "critical"     # critical | major | minor
     section: "{section or scenario ID where issue was found}"
+    uc_id: "{UC-ID this finding belongs to — PRD: the UC heading; BDD: @trace.id; \"\" if global}"
+    quote: "{verbatim snippet copied EXACTLY from the reviewed file at the issue location, ≤120 chars}"
     finding: "{clear description of the issue}"
     suggestion: "{specific actionable fix — AI will apply this in --resume if accepted}"
     auto_fixable: true       # true = AI can apply; false = human must write note in Review Board
@@ -224,6 +226,12 @@ summary:
   recommendation: "APPROVED | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the reviewed file at the exact
+> spot the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> Set `uc_id` to the owning Use Case (`@trace.id` for BDD, the UC heading for PRD; `""` if global).
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Post-Analysis Routing
 
 After running all checks and writing the findings file: