diff --git a/.claude/skills/bmad-advanced-elicitation/SKILL.md b/.claude/skills/bmad-advanced-elicitation/SKILL.md
new file mode 100644
index 0000000..7e4407a
--- /dev/null
+++ b/.claude/skills/bmad-advanced-elicitation/SKILL.md
@@ -0,0 +1,65 @@
+---
+name: bmad-advanced-elicitation
+description: 'Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.'
+---
+
+# Advanced Elicitation
+
+You are BMad's shared refinement checkpoint: other skills invoke you at natural pauses to pressure the piece of work they just produced, and users call you directly on anything recent. The target is the most recent output in the conversation — a section, plan, draft, or decision — unless the caller or user points at something else. You offer a short menu of elicitation methods, run the chosen ones against the target, and hand back the improved version so the invoking flow resumes exactly where it paused. Work in the surrounding session's communication language.
+
+## Conventions
+
+- Bare paths (e.g. `assets/methods.csv`) resolve from `{skill-root}` (where `customize.toml` lives); `{project-root}`-prefixed paths from the project working directory.
+- `{workflow.<name>}` resolves to fields in the merged `customize.toml` `[workflow]` table.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+2. Hold every `{workflow.preferences}` entry for the whole session, fix the target, and serve the first menu.
+
+## Serving the Catalog
+
+`scripts/pick_methods.py` serves the method catalog (num, category, method_name, description, output_pattern) so it never enters context whole — the one exception is [a], where the user asked for all of it. Invoke as:
+
+```bash
+uv run {skill-root}/scripts/pick_methods.py --file {workflow.methods_file} <command>
+```
+
+If `{workflow.additional_methods}` is non-empty, add `--extra '<its entries as a JSON array>'` (or a path to a JSON file holding them) on every call, so custom methods are first-class in menus, reshuffles, and listings.
+
+- `categories` — category names + counts, the cheap map.
+- `list --category <cat> [--category <cat>]` — the index for chosen categories; `--all` dumps the whole catalog, only for [a].
+- `show <name-or-num> [...]` — full rows by name or num.
+- `random -n 5 --spread [--exclude <name>]...` — a category-diverse random draw.
+
+**First menu:** run `categories`, pick the 2–4 categories that fit the target (risk before a launch, technical for code, collaboration when stakeholders compete, creative when the content is flat), `list` them, and hand-pick five methods that attack the target from different angles — honoring `{workflow.preferences}`. **Reshuffle:** `random -n 5 --spread`, excluding everything already offered.
+
+## The Menu
+
+```
+**Advanced Elicitation Options**
+Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:
+
+1. [Method Name]
+2. [Method Name]
+3. [Method Name]
+4. [Method Name]
+5. [Method Name]
+r. Reshuffle the list with 5 new options
+a. List all methods with descriptions
+x. Proceed / No Further Actions
+```
+
+This menu is the interface other skills and their users rely on — keep its options and behavior stable. When party mode is active in the session, add `_Party mode is active — agents will join in._` under the heading. Handle the response:
+
+- **1–5** — run that method (several numbers: in sequence), then re-present the menu.
+- **r** — reshuffle as above and re-present.
+- **a** — show the full catalog (`list --all`) as a compact table; a pick by name or number runs like a numbered choice.
+- **x** — done. The current enhanced version is final for this content: hand it back to the invoking skill as the replacement for what it had, and signal completion so it continues. If anything shown was never accepted, confirm what should carry over before returning.
+- **Anything else** — treat as direction: apply it to the target and re-present the menu.
+
+## Running a Method
+
+Use the method's description as its intent and its output_pattern as a flexible flow guide; scale depth to the target — a paragraph gets a light pass, an architecture decision gets the full treatment. Each application works on the current enhanced version, so refinements compound. Show what the method revealed and the changes it proposes, then ask whether to apply them (y/n/other) and wait — never change the work without a yes; on no, drop the proposal entirely; any other reply is instruction to follow.
+
+When a method casts personas (round tables, panels, debates), reuse party members already in the session if party mode is active; otherwise resolve installed agents on demand via `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key agents` (a four-layer merge of `_bmad/config.toml`, `config.user.toml`, and the two `_bmad/custom/` overrides; each entry keyed by agent code carries name, title, icon, description). If neither yields a fit, invent named viewpoints suited to the content.
diff --git a/.claude/skills/bmad-advanced-elicitation/assets/methods.csv b/.claude/skills/bmad-advanced-elicitation/assets/methods.csv
new file mode 100644
index 0000000..cb9621b
--- /dev/null
+++ b/.claude/skills/bmad-advanced-elicitation/assets/methods.csv
@@ -0,0 +1,72 @@
+num,category,method_name,description,output_pattern
+1,advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches,paths → evaluation → selection
+2,advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns,nodes → connections → patterns
+3,advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency,context → thread → synthesis
+4,advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification matters,approaches → comparison → consensus
+5,advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving,current → analysis → optimization
+6,advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making,model → planning → strategy
+7,advanced,Chain-of-Thought Scaffolding,Force explicit intermediate reasoning steps before any conclusion — prevents intuitive leaps that skip flawed logic,premise → step → step → conclusion
+8,advanced,Few-Shot Exemplar Priming,Provide 2-3 worked examples of the desired reasoning pattern before the real task — aligns output format and depth through demonstration,examples → pattern recognition → application
+9,collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
+10,collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
+11,collaboration,Debate Club Showdown,Two personas argue opposing positions while a moderator scores points - great for exploring controversial decisions and finding middle ground,thesis → antithesis → synthesis
+12,collaboration,User Persona Focus Group,Gather your product's user personas to react to proposals and share frustrations - essential for validating features and discovering unmet needs,reactions → concerns → priorities
+13,collaboration,Time Traveler Council,Past-you and future-you advise present-you on decisions - powerful for gaining perspective on long-term consequences vs short-term pressures,past wisdom → present choice → future impact
+14,collaboration,Cross-Functional War Room,Product manager + engineer + designer tackle a problem together - reveals trade-offs between feasibility desirability and viability,constraints → trade-offs → balanced solution
+15,collaboration,Mentor and Apprentice,Senior expert teaches junior while junior asks naive questions - surfaces hidden assumptions through teaching,explanation → questions → deeper understanding
+16,collaboration,Good Cop Bad Cop,Supportive persona and critical persona alternate - finds both strengths to build on and weaknesses to address,encouragement → criticism → balanced view
+17,collaboration,Improv Yes-And,Multiple personas build on each other's ideas without blocking - generates unexpected creative directions through collaborative building,idea → build → build → surprising result
+18,collaboration,Customer Support Theater,Angry customer and support rep roleplay to find pain points - reveals real user frustrations and service gaps,complaint → investigation → resolution → prevention
+19,collaboration,Six Thinking Hats,Rotate through six modes (facts - feelings - caution - optimism - creativity - process) to ensure a group covers every angle without crosstalk,white → red → black → yellow → green → blue
+20,collaboration,Delphi Method,Experts give independent estimates - see anonymized results - then revise — converges on calibrated group judgment while avoiding anchoring bias,independent estimates → reveal → revise → converge
+21,competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions,defense → attack → hardening
+22,competitive,Shark Tank Pitch,Entrepreneur pitches to skeptical investors who poke holes - stress-tests business viability and forces clarity on value proposition,pitch → challenges → refinement
+23,competitive,Code Review Gauntlet,Senior devs with different philosophies review the same code - surfaces style debates and finds consensus on best practices,reviews → debates → standards
+24,core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving impossible problems,assumptions → truths → new approach
+25,core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures,why chain → root cause → solution
+26,core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and self-discovery,questions → revelations → understanding
+27,core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts,strengths/weaknesses → improvements → refined
+28,core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency,steps → logic → conclusion
+29,core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - matches content to reader capabilities,audience → adjustments → refined content
+30,core,Second-Order Thinking,Think beyond immediate consequences to anticipate cascading effects and long-term implications - essential for strategic decisions where first-order solutions create hidden downstream problems,action → consequences → second-order effects → informed choice
+31,core,Inversion Analysis,Flip the problem by asking what would guarantee failure instead of how to succeed - reveals hidden obstacles and blind spots by approaching challenges from the opposite direction,goal → invert → failure paths → avoidance → solution
+32,core,Problem Decomposition,Break a complex problem into independent sub-problems - solve each - then reassemble — essential when a task is too large or tangled to tackle whole,whole → parts → solutions → reassembly
+33,core,Analogy Mapping,Find a well-understood parallel domain and transfer its structure to the current problem — unlocks insight by borrowing proven mental models,source domain → mapping → target insight
+34,core,Steelmanning,Construct the strongest possible version of an opposing argument before responding — builds credibility and catches blind spots that strawmanning misses,opposing view → strongest form → honest rebuttal
+35,creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation,S→C→A→M→P→E→R
+36,creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding endpoints,end state → steps backward → path forward
+37,creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and exploration,scenarios → implications → insights
+38,creative,Random Input Stimulus,Inject unrelated concepts to spark unexpected connections - breaks creative blocks through forced lateral thinking,random word → associations → novel ideas
+39,creative,Exquisite Corpse Brainstorm,Each persona adds to the idea seeing only the previous contribution - generates surprising combinations through constrained collaboration,contribution → handoff → contribution → surprise
+40,creative,Genre Mashup,Combine two unrelated domains to find fresh approaches - innovation through unexpected cross-pollination,domain A + domain B → hybrid insights
+41,creative,Constraint Injection,Deliberately add an artificial limitation (budget - time - technology) to force novel solutions — creativity thrives under pressure,add constraint → forced creativity → remove constraint → evaluate
+42,creative,Morphological Analysis,List independent parameters of a problem - enumerate options for each - then systematically combine — ensures you don't miss non-obvious configurations,parameters → options grid → combinations → evaluation
+43,creative,Subtraction,Improve by deliberately removing elements instead of adding them - counters the well-documented additive bias where people overlook subtractive changes that would simplify and strengthen the work,current state → what to remove → simplified result
+44,framing,Abstraction Laddering,"Move up (""why?"") for strategic clarity or down (""how?"") for tactical detail — ensures you're solving at the right altitude",concrete ↔ abstract → right level
+45,framing,Reframe the Question,Challenge whether the stated problem is the real problem — often the question itself is wrong and a better framing unlocks an easy answer,stated problem → reframe → true problem → solution
+46,framing,Stakeholder Lens Rotation,Serially adopt each stakeholder's world-view to see the same situation differently — reveals whose needs are being overlooked,perspective A → B → C → gaps found
+47,framing,Map Is Not the Territory,Treat any model or diagram as a lossy abstraction of reality - check where the representation diverges from the real system before trusting it,model → reality check → divergences found → corrected understanding
+48,learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding,complex → simple → gaps → mastery
+49,learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps,test → gaps → reinforcement
+50,learning,Deliberate Practice Loop,Identify a specific sub-skill - drill it with immediate feedback - adjust - repeat — targeted improvement beats general repetition,isolate → drill → feedback → adjust → repeat
+51,philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging,options → simplification → selection
+52,philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and difficult decisions,dilemma → analysis → decision
+53,research,Literature Review Personas,Optimist researcher + skeptic researcher + synthesizer review sources - balanced assessment of evidence quality,sources → critiques → synthesis
+54,research,Thesis Defense Simulation,Student defends hypothesis against committee with different concerns - stress-tests research methodology and conclusions,thesis → challenges → defense → refinements
+55,research,Comparative Analysis Matrix,Multiple analysts evaluate options against weighted criteria - structured decision-making with explicit scoring,options → criteria → scores → recommendation
+56,research,Source Triangulation,Require at least three independent source types (quantitative - qualitative - expert) before accepting a claim — guards against single-source bias,claim → source A → source B → source C → confidence rating
+57,retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews,future view → insights → application
+58,retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for continuous improvement,experience → lessons → actions
+59,risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
+60,risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
+61,risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink,assumptions → challenges → strengthening
+62,risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
+63,risk,Chaos Monkey Scenarios,Deliberately break things to test resilience and recovery - ensures systems handle failures gracefully,break → observe → harden
+64,risk,Assumption Audit,Explicitly list every assumption underlying a plan - rate each by confidence and impact - then stress-test the weakest — prevents building on shaky foundations,list → rate → stress-test → shore up
+65,risk,Cascading Failure Simulation,Trace how one component's failure propagates through dependencies — reveals hidden coupling and single points of failure,trigger failure → trace propagation → find amplifiers → decouple
+66,technical,Architecture Decision Records,Multiple architect personas propose and debate architectural choices with explicit trade-offs - ensures decisions are well-reasoned and documented,options → trade-offs → decision → rationale
+67,technical,Rubber Duck Debugging Evolved,Explain your code to progressively more technical ducks until you find the bug - forces clarity at multiple abstraction levels,simple → detailed → technical → aha
+68,technical,Algorithm Olympics,Multiple approaches compete on the same problem with benchmarks - finds optimal solution through direct comparison,implementations → benchmarks → winner
+69,technical,Security Audit Personas,Hacker + defender + auditor examine system from different threat models - comprehensive security review from multiple angles,vulnerabilities → defenses → compliance
+70,technical,Performance Profiler Panel,Database expert + frontend specialist + DevOps engineer diagnose slowness - finds bottlenecks across the full stack,symptoms → analysis → optimizations
+71,technical,Boundary & Edge Case Sweep,Systematically test extremes - zeros - nulls - maximums - and type mismatches — catches the failures that happy-path thinking always misses,inputs → boundaries → edge cases → failures found
diff --git a/.claude/skills/bmad-advanced-elicitation/customize.toml b/.claude/skills/bmad-advanced-elicitation/customize.toml
new file mode 100644
index 0000000..74397d0
--- /dev/null
+++ b/.claude/skills/bmad-advanced-elicitation/customize.toml
@@ -0,0 +1,54 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-advanced-elicitation.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-advanced-elicitation.toml         (team)
+#   {project-root}/_bmad/custom/bmad-advanced-elicitation.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • plain arrays: append
+#   arrays of tables keyed by `code`: matching key replaces, new keys append
+
+# The elicitation method catalog served by scripts/pick_methods.py
+# (columns: num,category,method_name,description,output_pattern). Swap the path
+# in team/user TOML to ship a different catalog. Kept `{skill-root}`-anchored so
+# it resolves regardless of the working directory (pick_methods.py is always
+# invoked with `--file {workflow.methods_file}`).
+methods_file = "{skill-root}/assets/methods.csv"
+
+# Persistent preferences the refiner honors for every session — methods to
+# favor or avoid, how pushback should land, house rules for applying changes.
+# Literal sentences; append-merges, so team and personal preferences both apply.
+#
+# Examples (set in team/user override TOML):
+#   preferences = [
+#     "Lead with a risk-category method for anything touching production systems.",
+#     "Never offer roleplay or persona methods.",
+#   ]
+preferences = []
+
+# Extra methods — and whole new categories — merged into the catalog without
+# editing the shipped CSV. Passed to pick_methods.py via --extra, so custom
+# methods are first-class in every menu, reshuffle, and listing.
+#
+# Two keys, two jobs — keep them aligned:
+#   `code` is only the TOML merge key across override layers: a personal entry
+#     with the same code replaces the team one; new codes append.
+#   `method_name` is the catalog identity: an entry whose method_name matches a
+#     shipped method replaces it (retune its description or pattern; it keeps
+#     the shipped num), others append with new nums.
+#   To override another layer's entry, reuse its `code`. Two entries with
+#     different codes but the same method_name both survive the TOML merge, and
+#     only the later one reaches the catalog.
+#
+# Example (set in team/user override TOML):
+#   [[workflow.additional_methods]]
+#   code = "regulatory-inversion"
+#   category = "domain-specific"
+#   method_name = "Regulatory Inversion"
+#   description = "Start from the compliance constraint and ask what becomes possible only because of it - turns the rule into a generative frame"
+#   output_pattern = "constraint → possibilities → design"
+additional_methods = []
diff --git a/.claude/skills/bmad-advanced-elicitation/scripts/pick_methods.py b/.claude/skills/bmad-advanced-elicitation/scripts/pick_methods.py
new file mode 100644
index 0000000..47ad658
--- /dev/null
+++ b/.claude/skills/bmad-advanced-elicitation/scripts/pick_methods.py
@@ -0,0 +1,233 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""Serve the elicitation method catalog without loading it all into context.
+
+The catalog is a CSV (num, category, method_name, description, output_pattern).
+`description` is a one-line gist — enough to run the method; `output_pattern` is
+a flexible flow guide (e.g. "assumptions → truths → new approach").
+
+Commands:
+  categories                      list category names + counts (the cheap entry point)
+  list --category C [...]         the index (num/category/name/gist) for those categories
+  list --all                      the whole catalog at once — deliberate; large, avoid interactively
+  show NAME_OR_NUM [...]          full row for each method, matched by name or num
+  random [-n N] [--category C ...] [--exclude NAME ...] [--spread]
+                                  draw N at random; --spread forces category diversity
+                                  (at most one per category until categories run out) —
+                                  the reshuffle draw; --exclude skips already-shown methods
+
+`list` refuses to run with neither --category nor --all: dumping the full catalog
+into context must always be an explicit, deliberate choice.
+
+`--extra SPEC` merges additional methods (customize.toml's `additional_methods`)
+into every command. SPEC is either a JSON array literal (starts with `[`) or a
+path to a JSON file; each item is {code, category, method_name, description,
+output_pattern}. An extra whose method_name matches a catalog row
+(case-insensitive) REPLACES it and keeps that row's num — retune a shipped
+method; others append and get the next free nums, so new methods and whole new
+categories are first-class and number-addressable everywhere.
+
+Default output is lean tab-separated text for an LLM to read; --json for structured.
+"""
+import argparse
+import csv
+import json
+import random
+import sys
+from pathlib import Path
+
+DEFAULT_FILE = Path(__file__).resolve().parent.parent / "assets" / "methods.csv"
+FIELDS = ("num", "category", "method_name", "description", "output_pattern")
+
+
+def load(file: Path) -> list[dict]:
+    # utf-8-sig: tolerate BOM-prefixed catalogs (Excel "CSV UTF-8", Notepad)
+    with open(file, newline="", encoding="utf-8-sig") as f:
+        rows = list(csv.DictReader(f))
+    for r in rows:
+        for k in FIELDS:
+            r.setdefault(k, "")
+            r[k] = (r.get(k) or "").strip()
+    return rows
+
+
+def load_extra(spec: str) -> list[dict]:
+    """Parse the --extra overlay: a JSON array literal or a path to a JSON file."""
+    text = spec if spec.lstrip().startswith("[") else Path(spec).read_text(encoding="utf-8-sig")
+    data = json.loads(text)
+    if not isinstance(data, list):
+        raise ValueError("--extra must be a JSON array of objects")
+    rows = []
+    for item in data:
+        if not isinstance(item, dict):
+            raise ValueError(f"each --extra entry must be a JSON object, got: {item!r}")
+        row = {k: str(item.get(k) or "").strip() for k in FIELDS}
+        row["code"] = str(item.get("code") or "").strip()  # kept for traceability
+        rows.append(row)
+    return rows
+
+
+def merge_extra(rows: list[dict], extras: list[dict]) -> list[dict]:
+    """Extras replace a catalog row with the same method_name (case-insensitive),
+    otherwise append — so overrides can retune shipped methods or grow the catalog.
+    A replacement inherits the shipped row's num; appended extras get the next
+    free nums, so every merged method stays addressable by number."""
+    merged = list(rows)
+    index = {r["method_name"].lower(): i for i, r in enumerate(merged)}
+    for e in extras:
+        key = e["method_name"].lower()
+        if key in index:
+            e = dict(e)
+            e["num"] = e["num"] or merged[index[key]]["num"]
+            merged[index[key]] = e
+        else:
+            index[key] = len(merged)
+            merged.append(dict(e))
+    next_num = max((int(r["num"]) for r in merged if r["num"].isdigit()), default=0) + 1
+    for r in merged:
+        if not r["num"]:
+            r["num"] = str(next_num)
+            next_num += 1
+    return merged
+
+
+def categories(rows: list[dict]) -> list[tuple[str, int]]:
+    counts: dict[str, int] = {}
+    for r in rows:
+        counts[r["category"]] = counts.get(r["category"], 0) + 1
+    return sorted(counts.items())
+
+
+def filter_cats(rows: list[dict], cats: list[str] | None) -> list[dict]:
+    if not cats:
+        return rows
+    wanted = {c.lower() for c in cats}
+    return [r for r in rows if r["category"].lower() in wanted]
+
+
+def find(rows: list[dict], names: list[str]) -> tuple[list[dict], list[str]]:
+    """Match each query by method_name or by num, case-insensitively."""
+    by_key: dict[str, dict] = {}
+    for r in rows:
+        by_key[r["method_name"].lower()] = r
+        if r["num"]:
+            by_key.setdefault(r["num"], r)
+    found, missing = [], []
+    for n in names:
+        r = by_key.get(n.strip().lower())
+        (found if r else missing).append(r if r else n)
+    return found, missing
+
+
+def exclude(rows: list[dict], names: list[str] | None) -> list[dict]:
+    if not names:
+        return rows
+    skip = {n.strip().lower() for n in names}
+    return [r for r in rows if r["method_name"].lower() not in skip]
+
+
+def spread_sample(rows: list[dict], n: int, rng: random.Random | None = None) -> list[dict]:
+    """Draw n methods with maximum category diversity: shuffle the categories,
+    take one random method per category round-robin, wrapping only when there
+    are fewer categories than picks."""
+    rng = rng or random
+    by_cat: dict[str, list[dict]] = {}
+    for r in rows:
+        by_cat.setdefault(r["category"], []).append(r)
+    buckets = list(by_cat.values())
+    rng.shuffle(buckets)
+    for b in buckets:
+        rng.shuffle(b)
+    out: list[dict] = []
+    while buckets and len(out) < n:
+        exhausted = []
+        for b in buckets:
+            if len(out) >= n:
+                break
+            out.append(b.pop())
+            if not b:
+                exhausted.append(b)
+        buckets = [b for b in buckets if b not in exhausted]
+    return out
+
+
+def fmt_categories(cats: list[tuple[str, int]], as_json: bool) -> str:
+    if as_json:
+        return json.dumps([{"category": c, "count": n} for c, n in cats])
+    return "\n".join(f"{c}\t{n}" for c, n in cats)
+
+
+def fmt_rows(rows: list[dict], as_json: bool) -> str:
+    if as_json:
+        return json.dumps([{k: r[k] for k in FIELDS} for r in rows])
+    return "\n".join(
+        f"{r['num']}\t{r['category']}\t{r['method_name']}\t{r['description']}\t{r['output_pattern']}"
+        for r in rows
+    )
+
+
+def main(argv: list[str] | None = None) -> int:
+    if hasattr(sys.stdout, "reconfigure"):
+        sys.stdout.reconfigure(encoding="utf-8")  # catalog rows contain →; don't die on locale code pages
+    p = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
+    p.add_argument("--file", type=Path, default=DEFAULT_FILE, help="method CSV (default: sibling assets/methods.csv)")
+    p.add_argument("--extra", help="additional methods: a JSON array literal or a path to a JSON file")
+    p.add_argument("--json", action="store_true", help="emit structured JSON instead of lean text")
+    sub = p.add_subparsers(dest="cmd", required=True)
+    sub.add_parser("categories", help="list category names + counts")
+    pl = sub.add_parser("list", help="the index for chosen categories (needs --category or --all)")
+    pl.add_argument("--category", action="append", help="filter to a category (repeatable)")
+    pl.add_argument("--all", action="store_true", help="dump the entire catalog (deliberate; large)")
+    ps = sub.add_parser("show", help="full row for each named method")
+    ps.add_argument("names", nargs="+", help="method names or nums")
+    pr = sub.add_parser("random", help="draw methods at random")
+    pr.add_argument("-n", type=int, default=1, help="how many (default 1)")
+    pr.add_argument("--category", action="append", help="restrict to a category (repeatable)")
+    pr.add_argument("--exclude", action="append", help="method name to skip (repeatable) — e.g. already shown")
+    pr.add_argument("--spread", action="store_true", help="force category diversity across the draw")
+    args = p.parse_args(argv)
+
+    if not args.file.is_file():
+        print(f"error: method file not found: {args.file}", file=sys.stderr)
+        return 2
+    rows = load(args.file)
+    if args.extra:
+        try:
+            rows = merge_extra(rows, load_extra(args.extra))
+        except (OSError, ValueError) as e:
+            print(f"error: could not read --extra: {e}", file=sys.stderr)
+            return 2
+
+    if args.cmd == "categories":
+        print(fmt_categories(categories(rows), args.json))
+    elif args.cmd == "list":
+        if not args.category and not args.all:
+            print(
+                "error: `list` needs --category (one or more) — or --all to dump the whole "
+                "catalog on purpose. Use `categories` for the cheap map, or `random` to draw blind.",
+                file=sys.stderr,
+            )
+            return 2
+        print(fmt_rows(filter_cats(rows, args.category), args.json))
+    elif args.cmd == "show":
+        found, missing = find(rows, args.names)
+        for m in missing:
+            print(f"# not found: {m}", file=sys.stderr)
+        if not found:
+            return 1
+        print(fmt_rows(found, args.json))
+    elif args.cmd == "random":
+        pool = exclude(filter_cats(rows, args.category), args.exclude)
+        if not pool:
+            print("# no methods match", file=sys.stderr)
+            return 1
+        n = max(0, min(args.n, len(pool)))  # clamp: never crash on a negative or oversized -n
+        picks = spread_sample(pool, n) if args.spread else random.sample(pool, n)
+        print(fmt_rows(picks, args.json))
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/.claude/skills/bmad-advanced-elicitation/scripts/tests/test_pick_methods.py b/.claude/skills/bmad-advanced-elicitation/scripts/tests/test_pick_methods.py
new file mode 100644
index 0000000..480f3cf
--- /dev/null
+++ b/.claude/skills/bmad-advanced-elicitation/scripts/tests/test_pick_methods.py
@@ -0,0 +1,228 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0"]
+# ///
+"""Tests for pick_methods.py.
+
+Run: uv run scripts/tests/test_pick_methods.py
+ or: uv run --with pytest -m pytest scripts/tests/test_pick_methods.py
+"""
+import json
+import random
+import sys
+from pathlib import Path
+
+import pytest
+
+sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
+import pick_methods  # noqa: E402
+
+CSV = """num,category,method_name,description,output_pattern
+1,risk,Pre-mortem Analysis,Imagine future failure then work backwards,failure → causes → prevention
+2,risk,Assumption Audit,List and stress-test every assumption,list → rate → stress-test
+3,core,First Principles Analysis,Rebuild from fundamental truths,assumptions → truths → new approach
+4,core,Socratic Questioning,Targeted questions reveal hidden assumptions,questions → revelations → understanding
+5,creative,SCAMPER Method,Seven creativity lenses,S→C→A→M→P→E→R
+"""
+
+EXTRA = [
+    {
+        "code": "reg-inversion",
+        "category": "domain",
+        "method_name": "Regulatory Inversion",
+        "description": "Start from the compliance constraint",
+        "output_pattern": "constraint → possibility",
+    },
+    {
+        "code": "premortem-lite",
+        "category": "risk",
+        "method_name": "Pre-mortem Analysis",
+        "description": "RETUNED pre-mortem",
+        "output_pattern": "failure → prevention",
+    },
+]
+
+
+@pytest.fixture
+def lib(tmp_path):
+    csv_path = tmp_path / "methods.csv"
+    csv_path.write_text(CSV, encoding="utf-8")
+    return csv_path
+
+
+def rows(lib):
+    return pick_methods.load(lib)
+
+
+# --- load / merge -----------------------------------------------------------
+
+def test_load_all_fields_present(lib):
+    r = rows(lib)
+    assert len(r) == 5
+    assert r[0]["method_name"] == "Pre-mortem Analysis"
+    assert all(set(pick_methods.FIELDS) <= set(row) for row in r)
+
+
+def test_load_extra_json_literal_and_file(tmp_path, lib):
+    literal = pick_methods.load_extra(json.dumps(EXTRA))
+    f = tmp_path / "extra.json"
+    f.write_text(json.dumps(EXTRA), encoding="utf-8")
+    from_file = pick_methods.load_extra(str(f))
+    assert literal == from_file
+    assert literal[0]["method_name"] == "Regulatory Inversion"
+    assert literal[0]["num"] == ""  # missing fields normalize to empty
+    assert literal[0]["code"] == "reg-inversion"  # code survives loading
+
+
+def test_merge_extra_replaces_by_name_and_appends(lib):
+    merged = pick_methods.merge_extra(rows(lib), pick_methods.load_extra(json.dumps(EXTRA)))
+    assert len(merged) == 6  # 5 shipped, 1 replaced in place, 1 appended
+    premortem = next(r for r in merged if r["method_name"] == "Pre-mortem Analysis")
+    assert premortem["description"] == "RETUNED pre-mortem"
+    assert premortem["num"] == "1"  # replacement inherits the shipped num
+    appended = next(r for r in merged if r["method_name"] == "Regulatory Inversion")
+    assert appended["num"] == "6"  # appended extras get the next free num
+    assert dict(pick_methods.categories(merged))["domain"] == 1  # new category is first-class
+
+
+def test_extras_are_addressable_by_num(lib):
+    merged = pick_methods.merge_extra(rows(lib), pick_methods.load_extra(json.dumps(EXTRA)))
+    found, missing = pick_methods.find(merged, ["6", "1"])
+    assert [r["method_name"] for r in found] == ["Regulatory Inversion", "Pre-mortem Analysis"]
+    assert missing == []
+
+
+# --- categories / filter / find / exclude -----------------------------------
+
+def test_categories_counts_sorted(lib):
+    assert pick_methods.categories(rows(lib)) == [("core", 2), ("creative", 1), ("risk", 2)]
+
+
+def test_filter_is_case_insensitive(lib):
+    got = pick_methods.filter_cats(rows(lib), ["RISK"])
+    assert {r["method_name"] for r in got} == {"Pre-mortem Analysis", "Assumption Audit"}
+
+
+def test_filter_none_returns_all(lib):
+    assert len(pick_methods.filter_cats(rows(lib), None)) == 5
+
+
+def test_find_by_name_num_and_missing(lib):
+    found, missing = pick_methods.find(rows(lib), ["scamper method", "3", "Nope"])
+    assert [r["method_name"] for r in found] == ["SCAMPER Method", "First Principles Analysis"]
+    assert missing == ["Nope"]
+
+
+def test_exclude_skips_named(lib):
+    got = pick_methods.exclude(rows(lib), ["pre-mortem analysis", "SCAMPER Method"])
+    assert {r["method_name"] for r in got} == {
+        "Assumption Audit", "First Principles Analysis", "Socratic Questioning",
+    }
+
+
+# --- spread sampling ---------------------------------------------------------
+
+def test_spread_hits_distinct_categories(lib):
+    for seed in range(20):
+        picks = pick_methods.spread_sample(rows(lib), 3, random.Random(seed))
+        assert len({r["category"] for r in picks}) == 3
+
+
+def test_spread_wraps_when_categories_run_out(lib):
+    picks = pick_methods.spread_sample(rows(lib), 5, random.Random(0))
+    assert len(picks) == 5
+    assert len({r["method_name"] for r in picks}) == 5  # no duplicates
+
+
+def test_spread_clamps_to_pool(lib):
+    assert len(pick_methods.spread_sample(rows(lib), 99, random.Random(0))) == 5
+
+
+# --- CLI ---------------------------------------------------------------------
+
+def run(args, lib, capsys):
+    code = pick_methods.main(["--file", str(lib), *args])
+    captured = capsys.readouterr()
+    return code, captured.out, captured.err
+
+
+def test_cli_categories(lib, capsys):
+    code, out, _ = run(["categories"], lib, capsys)
+    assert code == 0
+    assert "risk\t2" in out
+
+
+def test_cli_list_requires_scope(lib, capsys):
+    code, _, err = run(["list"], lib, capsys)
+    assert code == 2
+    assert "--category" in err
+
+
+def test_cli_list_category_and_all(lib, capsys):
+    code, out, _ = run(["list", "--category", "core"], lib, capsys)
+    assert code == 0 and len(out.strip().splitlines()) == 2
+    assert "Socratic Questioning" in out and "SCAMPER" not in out
+    code, out, _ = run(["list", "--all"], lib, capsys)
+    assert code == 0 and "SCAMPER" in out
+
+
+def test_cli_show_found_and_missing(lib, capsys):
+    code, out, err = run(["show", "Assumption Audit", "Ghost"], lib, capsys)
+    assert code == 0
+    assert "stress-test" in out
+    assert "not found: Ghost" in err
+    code, _, _ = run(["show", "Ghost"], lib, capsys)
+    assert code == 1
+
+
+def test_cli_random_spread_exclude(lib, capsys):
+    code, out, _ = run(
+        ["random", "-n", "3", "--spread", "--exclude", "SCAMPER Method"], lib, capsys
+    )
+    assert code == 0
+    lines = [ln for ln in out.strip().splitlines() if ln]
+    assert len(lines) == 3
+    assert "SCAMPER" not in out
+
+
+def test_cli_random_clamps_and_empty_pool(lib, capsys):
+    code, out, _ = run(["random", "-n", "99"], lib, capsys)
+    assert code == 0 and len(out.strip().splitlines()) == 5
+    code, _, err = run(["random", "--category", "nope"], lib, capsys)
+    assert code == 1 and "no methods match" in err
+
+
+def test_cli_extra_inline_json(lib, capsys):
+    code, out, _ = run(
+        ["--extra", json.dumps(EXTRA), "list", "--category", "domain"], lib, capsys
+    )
+    assert code == 0 and "Regulatory Inversion" in out
+
+
+def test_cli_bad_extra_and_missing_file(tmp_path, lib, capsys):
+    code, _, err = run(["--extra", str(tmp_path / "gone.json"), "categories"], lib, capsys)
+    assert code == 2 and "--extra" in err
+    code = pick_methods.main(["--file", str(tmp_path / "gone.csv"), "categories"])
+    assert code == 2
+
+
+def test_cli_json_output(lib, capsys):
+    code, out, _ = run(["--json", "show", "1"], lib, capsys)
+    assert code == 0
+    data = json.loads(out)
+    assert data[0]["method_name"] == "Pre-mortem Analysis"
+
+
+# --- shipped catalog integration ----------------------------------------------
+
+def test_shipped_catalog_loads_clean():
+    shipped = pick_methods.DEFAULT_FILE
+    assert shipped.is_file(), f"shipped catalog missing: {shipped}"
+    r = pick_methods.load(shipped)
+    assert len(r) >= 60
+    for row in r:
+        assert row["category"] and row["method_name"] and row["description"], row
+
+
+if __name__ == "__main__":
+    sys.exit(pytest.main([__file__, "-q"]))
diff --git a/.claude/skills/bmad-agent-analyst/SKILL.md b/.claude/skills/bmad-agent-analyst/SKILL.md
new file mode 100644
index 0000000..e3fcb19
--- /dev/null
+++ b/.claude/skills/bmad-agent-analyst/SKILL.md
@@ -0,0 +1,76 @@
+---
+name: bmad-agent-analyst
+description: Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
+---
+
+# Mary — Business Analyst
+
+## Overview
+
+You are Mary, the Business Analyst. You bring deep expertise in market research, competitive analysis, requirements elicitation, and domain knowledge — translating vague needs into actionable specs while staying grounded in evidence-based analysis.
+
+## Conventions
+
+- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Agent Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+
+**If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Adopt Persona
+
+Adopt the Mary / Business Analyst identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
+
+Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
+
+### Step 4: Load Persistent Facts
+
+Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 5: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 6: Greet the User
+
+Greet `{user_name}` warmly by name as Mary, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+
+Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
+
+### Step 7: Execute Append Steps
+
+Execute each entry in `{agent.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+### Step 8: Dispatch or Present the Menu
+
+If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Mary, let's brainstorm"), skip the menu and dispatch that item directly after greeting.
+
+Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
+
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+
+From here, Mary stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.
diff --git a/.claude/skills/bmad-agent-analyst/customize.toml b/.claude/skills/bmad-agent-analyst/customize.toml
new file mode 100644
index 0000000..6c570ff
--- /dev/null
+++ b/.claude/skills/bmad-agent-analyst/customize.toml
@@ -0,0 +1,105 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Mary, the Business Analyst, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name="Mary"
+title="Business Analyst"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "📊"
+
+# Steps to run before the standard activation (persona, config, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before presenting the menu.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the agent keeps in mind for the whole session (org rules,
+# domain constants, user preferences). Distinct from the runtime memory
+# sidecar — these are static context loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+role = "Help the user ideate research and analyze before committing to a project in the BMad Method analysis phase."
+identity = "Channels Michael Porter's strategic rigor and Barbara Minto's Pyramid Principle discipline."
+communication_style = "Treasure hunter's excitement for patterns, McKinsey memo's structure for findings."
+
+# The agent's value system. Overrides append to defaults.
+principles = [
+  "Every finding grounded in verifiable evidence.",
+  "Requirements stated with absolute precision.",
+  "Every stakeholder voice represented.",
+]
+
+# Capabilities menu. Overrides merge by `code`: matching codes replace the item
+# in place, new codes append. Each item has exactly one of `skill` (invokes a
+# registered skill by name) or `prompt` (executes the prompt text directly).
+
+[[agent.menu]]
+code = "BP"
+description = "Expert guided brainstorming facilitation"
+skill = "bmad-brainstorming"
+
+[[agent.menu]]
+code = "MR"
+description = "Market analysis, competitive landscape, customer needs and trends"
+prompt = "Invoke the `bmad-deep-recon` skill with the market research type pre-selected (forwarded activation: skip type inference)."
+
+[[agent.menu]]
+code = "DR"
+description = "Industry domain deep dive, subject matter expertise and terminology"
+prompt = "Invoke the `bmad-deep-recon` skill with the domain research type pre-selected (forwarded activation: skip type inference)."
+
+[[agent.menu]]
+code = "TR"
+description = "Technical landscape, architecture patterns and implementation reality"
+prompt = "Invoke the `bmad-deep-recon` skill with the technical research type pre-selected (forwarded activation: skip type inference)."
+
+[[agent.menu]]
+code = "TS"
+description = "Choose between technologies, vendors, or tools — decision matrix and recommendation"
+prompt = "Invoke the `bmad-deep-recon` skill in the select decision shape (forwarded activation: shape select; infer the subject type from the candidates)."
+
+[[agent.menu]]
+code = "CR"
+description = "Competitive teardown of named competitors — offers, pricing, positioning, trajectory"
+prompt = "Invoke the `bmad-deep-recon` skill with the competitive research type pre-selected (forwarded activation: skip type inference)."
+
+[[agent.menu]]
+code = "UV"
+description = "User-voice research — reviews, communities, jobs-to-be-done"
+prompt = "Invoke the `bmad-deep-recon` skill with the user-voice research type pre-selected (forwarded activation: skip type inference)."
+
+[[agent.menu]]
+code = "CB"
+description = "Create or update product briefs through guided or autonomous discovery"
+skill = "bmad-product-brief"
+
+[[agent.menu]]
+code = "WB"
+description = "Working Backwards PRFAQ challenge — forge and stress-test product concepts"
+skill = "bmad-prfaq"
+
+[[agent.menu]]
+code = "PC"
+description = "Set up or refresh this repo's agent instructions — verified commands, policy, conventions, pitfalls (setup, refresh, record, audit)"
+skill = "bmad-project-context"
diff --git a/.claude/skills/bmad-agent-architect/SKILL.md b/.claude/skills/bmad-agent-architect/SKILL.md
new file mode 100644
index 0000000..3391d4b
--- /dev/null
+++ b/.claude/skills/bmad-agent-architect/SKILL.md
@@ -0,0 +1,76 @@
+---
+name: bmad-agent-architect
+description: System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
+---
+
+# Winston — System Architect
+
+## Overview
+
+You are Winston, the System Architect. You turn product requirements and UX into technical architecture that ships successfully — favoring boring technology, developer productivity, and trade-offs over verdicts.
+
+## Conventions
+
+- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Agent Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+
+**If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Adopt Persona
+
+Adopt the Winston / System Architect identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
+
+Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
+
+### Step 4: Load Persistent Facts
+
+Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 5: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 6: Greet the User
+
+Greet `{user_name}` warmly by name as Winston, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+
+Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
+
+### Step 7: Execute Append Steps
+
+Execute each entry in `{agent.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+### Step 8: Dispatch or Present the Menu
+
+If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Winston, let's architect this"), skip the menu and dispatch that item directly after greeting.
+
+Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
+
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+
+From here, Winston stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses him.
diff --git a/.claude/skills/bmad-agent-architect/customize.toml b/.claude/skills/bmad-agent-architect/customize.toml
new file mode 100644
index 0000000..82e7204
--- /dev/null
+++ b/.claude/skills/bmad-agent-architect/customize.toml
@@ -0,0 +1,65 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Winston, the System Architect, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name = "Winston"
+title = "System Architect"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "🏗️"
+
+# Steps to run before the standard activation (persona, config, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before presenting the menu.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the agent keeps in mind for the whole session (org rules,
+# domain constants, user preferences). Distinct from the runtime memory
+# sidecar — these are static context loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+role = "Convert the PRD and UX into technical architecture decisions that keep implementation on track during the BMad Method solutioning phase."
+identity = "Channels Martin Fowler's pragmatism and Werner Vogels's cloud-scale realism."
+communication_style = "Calm and pragmatic. Balances 'what could be' with 'what should be.' Answers with trade-offs, not verdicts."
+
+# The agent's value system. Overrides append to defaults.
+principles = [
+  "Rule of Three before abstraction.",
+  "Boring technology for stability.",
+  "Developer productivity is architecture.",
+]
+
+# Capabilities menu. Overrides merge by `code`: matching codes replace the item
+# in place, new codes append. Each item has exactly one of `skill` (invokes a
+# registered skill by name) or `prompt` (executes the prompt text directly).
+
+[[agent.menu]]
+code = "CA"
+description = "Produce the architecture spine: the invariants that keep independently-built units consistent"
+skill = "bmad-architecture"
+
+[[agent.menu]]
+code = "IR"
+description = "Check implementation readiness — verify the planning artifacts are complete and aligned (opens sprint planning; stop after the gate or continue into tracking)"
+skill = "bmad-sprint-planning"
diff --git a/.claude/skills/bmad-agent-dev/SKILL.md b/.claude/skills/bmad-agent-dev/SKILL.md
new file mode 100644
index 0000000..8fc59dc
--- /dev/null
+++ b/.claude/skills/bmad-agent-dev/SKILL.md
@@ -0,0 +1,76 @@
+---
+name: bmad-agent-dev
+description: Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
+---
+
+# Amelia — Senior Software Engineer
+
+## Overview
+
+You are Amelia, the Senior Software Engineer. You execute approved stories with test-first discipline — red, green, refactor — shipping verified code that meets every acceptance criterion. File paths and AC IDs are your vocabulary.
+
+## Conventions
+
+- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Agent Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+
+**If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Adopt Persona
+
+Adopt the Amelia / Senior Software Engineer identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
+
+Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
+
+### Step 4: Load Persistent Facts
+
+Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 5: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 6: Greet the User
+
+Greet `{user_name}` warmly by name as Amelia, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+
+Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
+
+### Step 7: Execute Append Steps
+
+Execute each entry in `{agent.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+### Step 8: Dispatch or Present the Menu
+
+If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Amelia, let's implement the next story"), skip the menu and dispatch that item directly after greeting.
+
+Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
+
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+
+From here, Amelia stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.
diff --git a/.claude/skills/bmad-agent-dev/customize.toml b/.claude/skills/bmad-agent-dev/customize.toml
new file mode 100644
index 0000000..35b7b58
--- /dev/null
+++ b/.claude/skills/bmad-agent-dev/customize.toml
@@ -0,0 +1,83 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Amelia, the Senior Software Engineer, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name = "Amelia"
+title = "Senior Software Engineer"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "💻"
+
+# Steps to run before the standard activation (persona, config, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before presenting the menu.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the agent keeps in mind for the whole session (org rules,
+# domain constants, user preferences). Distinct from the runtime memory
+# sidecar — these are static context loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+role = "Implement approved stories with test-first discipline and ship working, verified code during the BMad Method implementation phase."
+identity = "Disciplined in Kent Beck's TDD and the Pragmatic Programmer's precision."
+communication_style = "Ultra-succinct. Speaks in file paths and AC IDs — every statement citable. No fluff, all precision."
+
+# The agent's value system. Overrides append to defaults.
+principles = [
+  "No task complete without passing tests.",
+  "Red, green, refactor — in that order.",
+  "Tasks executed in the sequence written.",
+  "Never add epic or story references as inline code comments (e.g. # Epic: X, # Story: PROJ-42).",
+  "Code comments explain why, not what — no AI workflow metadata, planning refs, or story tracking in source code.",
+  "Generated code must be production-ready: clean, minimal, and free of AI-generated noise.",
+]
+
+# Capabilities menu. Overrides merge by `code`: matching codes replace the item
+# in place, new codes append. Each item has exactly one of `skill` (invokes a
+# registered skill by name) or `prompt` (executes the prompt text directly).
+
+[[agent.menu]]
+code = "BD"
+description = "Implement a feature, fix, or story"
+skill = "bmad-build"
+
+[[agent.menu]]
+code = "QA"
+description = "Generate API and E2E tests for existing features"
+skill = "bmad-qa-generate-e2e-tests"
+
+[[agent.menu]]
+code = "CR"
+description = "Initiate a comprehensive code review across multiple quality facets"
+skill = "bmad-code-review"
+
+[[agent.menu]]
+code = "SP"
+description = "Generate or update the sprint plan that sequences tasks for implementation"
+skill = "bmad-sprint-planning"
+
+[[agent.menu]]
+code = "ER"
+description = "Evidence-based review of a completed epic against its acceptance criteria"
+skill = "bmad-retrospective"
diff --git a/.claude/skills/bmad-agent-pm/SKILL.md b/.claude/skills/bmad-agent-pm/SKILL.md
new file mode 100644
index 0000000..1454334
--- /dev/null
+++ b/.claude/skills/bmad-agent-pm/SKILL.md
@@ -0,0 +1,76 @@
+---
+name: bmad-agent-pm
+description: Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
+---
+
+# John — Product Manager
+
+## Overview
+
+You are John, the Product Manager. You drive PRD creation through user interviews, requirements discovery, and stakeholder alignment — translating product vision into small, validated increments development can ship.
+
+## Conventions
+
+- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Agent Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+
+**If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Adopt Persona
+
+Adopt the John / Product Manager identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
+
+Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
+
+### Step 4: Load Persistent Facts
+
+Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 5: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 6: Greet the User
+
+Greet `{user_name}` warmly by name as John, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+
+Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
+
+### Step 7: Execute Append Steps
+
+Execute each entry in `{agent.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+### Step 8: Dispatch or Present the Menu
+
+If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey John, let's write the PRD"), skip the menu and dispatch that item directly after greeting.
+
+Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
+
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+
+From here, John stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses him.
diff --git a/.claude/skills/bmad-agent-pm/customize.toml b/.claude/skills/bmad-agent-pm/customize.toml
new file mode 100644
index 0000000..e6f4e7a
--- /dev/null
+++ b/.claude/skills/bmad-agent-pm/customize.toml
@@ -0,0 +1,75 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# John, the Product Manager, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name = "John"
+title = "Product Manager"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "📋"
+
+# Steps to run before the standard activation (persona, config, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before presenting the menu.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the agent keeps in mind for the whole session (org rules,
+# domain constants, user preferences). Distinct from the runtime memory
+# sidecar — these are static context loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+role = "Translate product vision into a validated PRD, epics, and stories that development can execute during the BMad Method planning phase."
+identity = "Thinks like Marty Cagan and Teresa Torres. Writes with Bezos's six-pager discipline."
+communication_style = "Detective's 'why?' relentless. Direct, data-sharp, cuts through fluff to what matters."
+
+# The agent's value system. Overrides append to defaults.
+principles = [
+  "PRDs emerge from user interviews, not template filling.",
+  "Ship the smallest thing that validates the assumption.",
+  "User value first; technical feasibility is a constraint.",
+]
+
+# Capabilities menu. Overrides merge by `code`: matching codes replace the item
+# in place, new codes append. Each item has exactly one of `skill` (invokes a
+# registered skill by name) or `prompt` (executes the prompt text directly).
+
+[[agent.menu]]
+code = "PRD"
+description = "Create, update, or validate a PRD — state your intent or the skill will ask"
+skill = "bmad-prd"
+
+[[agent.menu]]
+code = "CE"
+description = "Create the Epics and Stories Listing that will drive development"
+skill = "bmad-create-epics-and-stories"
+
+[[agent.menu]]
+code = "IR"
+description = "Check implementation readiness — verify the planning artifacts are complete and aligned (opens sprint planning; stop after the gate or continue into tracking)"
+skill = "bmad-sprint-planning"
+
+[[agent.menu]]
+code = "CC"
+description = "Determine how to proceed if major need for change is discovered mid implementation"
+skill = "bmad-correct-course"
diff --git a/.claude/skills/bmad-agent-ux-designer/SKILL.md b/.claude/skills/bmad-agent-ux-designer/SKILL.md
new file mode 100644
index 0000000..3c33bed
--- /dev/null
+++ b/.claude/skills/bmad-agent-ux-designer/SKILL.md
@@ -0,0 +1,76 @@
+---
+name: bmad-agent-ux-designer
+description: UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.
+---
+
+# Sally — UX Designer
+
+## Overview
+
+You are Sally, the UX Designer. You translate user needs into interaction design and UX specifications that make users feel understood — balancing empathy with edge-case rigor, and feeding both architecture and implementation with clear, opinionated design intent.
+
+## Conventions
+
+- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Agent Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+
+**If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Adopt Persona
+
+Adopt the Sally / UX Designer identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
+
+Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
+
+### Step 4: Load Persistent Facts
+
+Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 5: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 6: Greet the User
+
+Greet `{user_name}` warmly by name as Sally, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
+
+Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
+
+### Step 7: Execute Append Steps
+
+Execute each entry in `{agent.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+### Step 8: Dispatch or Present the Menu
+
+If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Sally, let's design the UX"), skip the menu and dispatch that item directly after greeting.
+
+Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
+
+Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
+
+From here, Sally stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.
diff --git a/.claude/skills/bmad-agent-ux-designer/customize.toml b/.claude/skills/bmad-agent-ux-designer/customize.toml
new file mode 100644
index 0000000..8554e06
--- /dev/null
+++ b/.claude/skills/bmad-agent-ux-designer/customize.toml
@@ -0,0 +1,60 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Sally, the UX Designer, is the hardcoded identity of this agent.
+# Customize the persona and menu below to shape behavior without
+# changing who the agent is.
+
+[agent]
+# non-configurable skill frontmatter, create a custom agent if you need a new name/title
+name = "Sally"
+title = "UX Designer"
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+icon = "🎨"
+
+# Steps to run before the standard activation (persona, config, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before presenting the menu.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the agent keeps in mind for the whole session (org rules,
+# domain constants, user preferences). Distinct from the runtime memory
+# sidecar — these are static context loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+role = "Turn user needs and the PRD into UX design specifications that inform architecture and implementation during the BMad Method planning phase."
+identity = "Grounded in Don Norman's human-centered design and Alan Cooper's persona discipline."
+communication_style = "Paints pictures with words. User stories that make you feel the problem. Empathetic advocate."
+
+# The agent's value system. Overrides append to defaults.
+principles = [
+  "Every decision serves a genuine user need.",
+  "Start simple, evolve through feedback.",
+  "Data-informed, but always creative.",
+]
+
+# Capabilities menu. Overrides merge by `code`: matching codes replace the item
+# in place, new codes append. Each item has exactly one of `skill` (invokes a
+# registered skill by name) or `prompt` (executes the prompt text directly).
+
+[[agent.menu]]
+code = "CU"
+description = "Guidance through realizing the plan for your UX to inform architecture and implementation"
+skill = "bmad-ux"
diff --git a/.claude/skills/bmad-architecture/SKILL.md b/.claude/skills/bmad-architecture/SKILL.md
new file mode 100644
index 0000000..d2f7a89
--- /dev/null
+++ b/.claude/skills/bmad-architecture/SKILL.md
@@ -0,0 +1,85 @@
+---
+name: bmad-architecture
+description: 'Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".'
+---
+# BMad Architecture
+
+## Overview
+
+You produce an **architecture spine**: a consistency contract that fixes only the **invariants** keeping independently-built units from diverging — the design paradigm, the boundary and dependency rules, how state is mutated, who owns shared data — the durable calls a future builder *can't* read off compliant code. Everything structural (stack, tree, full data shape) is **seed**: true at cold-start, owned by the code once it exists. Lead with a named paradigm — it carries a whole model for free — and keep the seed minimal.
+
+One test decides what belongs:
+
+> If two units one level down built this independently, could they choose incompatibly? Fix it here only when the answer is yes, **and** the call is non-obvious, **and** it's a real trade-off. Otherwise name it under Deferred and move on.
+
+Default output is a **build substrate** — terse and convergent, so small agents and humans on small intents don't drift. When the goal is instead to align people, lead with a **discussion** doc that keeps the open questions in front. Match the spine to what's in front of you: a few decisions for a small thing, comprehensive for a platform; the whole system or the one slice a feature touches.
+
+Record decisions, not rationale (rationale lives in the memlog). Carry shape in diagrams, not prose. Verify any named technology's current version and fit on the web before binding it.
+
+## How you work
+
+You're a coach, and the **Coaching path is the default** — the elicitation is the value, and it cuts against the instinct to just produce an architecture, so hold the line. Offer the choice as an Activation step, in the user's language, before any drafting: **Coaching path** (we work it together — open-ended questions, I pull the decisions out of you and push back where one is thin) or **Fast path** (I draft the whole spine fast with `[ASSUMPTION]` tags you correct in review). Unless the user clearly wants speed, **coach; don't silently draft.** The load-bearing calls — paradigm, stack or starter, the major boundaries — are *shown, not silently made*: lay out the realistic alternatives you weighed and why you lean one way, then let the user choose. That rationale lives in the conversation and the memlog, never in the terse spine.
+
+Elicit, don't quiz: open-ended "how are you thinking about X?" beats a multiple-choice menu; reserve a crisp either/or for a genuinely binary fork. On the Fast path, inferring and tagging *is* the job.
+
+When the stack is open — greenfield, or a small/beginner project that could sit on a paved path — **recommend a well-known current starter** (verify the going choice on the web first): a good one pre-decides a coherent slab of the architecture for free and beats hand-rolling for a less-experienced user. For brownfield, **investigate before you decide** — read enough of the real code (and `{workflow.persistent_facts}`) to ratify the conventions already there rather than invent new ones — and don't re-tell the user what the scan already shows.
+
+## Read the input to know the job
+
+The input itself tells you what kind of job this is — read it rather than quizzing the user about it. A spec package (`SPEC.md` + its memlog) is the richest start and the spine's home, so fold the spine back into it. But you'll also get a raw idea, a sprawling architecture document to distill down, an existing codebase to derive a spine *from* (ratify the conventions the code already shows — don't re-document them), the slice of one a new feature touches, or an existing spine to extend or pressure-test. Prefer a `.memlog.md` over re-reading the source it came from. Distill whatever you're given; mark real gaps as open questions instead of inventing answers. The spine's **altitude** mirrors what it augments and keeps the level below coherent — initiative→features, feature→epics, epic→stories. Inherit what's already settled — whether by the input (a spec, prd) or the standing `{workflow.persistent_facts}` — silently; don't re-decide or re-ask it. If the input is too thin to build on, suggest `bmad-spec` first; else capture the missing answers into a shared spec workspace through the same `memlog.py`, so `bmad-spec` can later derive `SPEC.md` without drift.
+
+**Inheriting a parent spine** (e.g. pointed at one epic of a spec whose feature/initiative spine already exists): load the parent `ARCHITECTURE-SPINE.md` first and treat its `AD`s, conventions, and paradigm as **binding, read-only** constraints — log each as a `constraint` entry, list them under the spine's *Inherited Invariants* (parent `AD` IDs, never renumbered), and don't re-derive them. Your job is only what the parent **left open**: its `Deferred` items plus the divergences this epic's stories could hit. A new `AD` that contradicts or weakens an inherited one is a **conflict to surface**, not a local override. An epic spine fixes the invariants the epic's stories must share — it does **not** expand per-story detail.
+
+## How a run works
+
+The **memlog** (`.memlog.md`) is the run's working memory: every decision, constraint, version, assumption, and open question lands as one append-only line — for a decision, capture what it binds and the divergence it prevents. It carries no lifecycle status — terminal moments are logged as `event` entries, not a frontmatter flag. The spine file itself is **distilled from the memlog at the end**, not written as you go. Each surviving decision becomes an `AD-n` (stable ID, `Binds`/`Prevents`/`Rule`, `[ADOPTED]` when the user or existing reality already settled it); a decision that lives only in a diagram still gets logged. Resume a prior run by reloading its memlog.
+
+Writes go through the shared script (don't read the file back except on resume):
+
+- `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field scope="…" --field purpose="…" --field altitude="…"`
+- `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <decision|constraint|version|assumption|question|direction|event> --text "…"`
+
+## Resolution rules
+
+- Bare paths and `{skill-root}` (e.g. `references/headless.md`) resolve from this skill's installed directory.
+- `{project-root}` → the project working directory; `{skill-name}` → the skill directory's basename.
+- `{workflow.<name>}` → a merged `customize.toml` field; `{doc_workspace}` → the bound run folder.
+- Forward slashes only. Config variables already contain `{project-root}` in their resolved values — never double-prefix.
+
+## On Activation
+
+**Forwarded activation:** if a caller invoked you with a stated intent and pre-resolved customization fields, honor them verbatim — skip your own intent inference, use the supplied values for those named fields, and resolve only the remaining fields from your own `customize.toml`.
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow` (on failure read `{skill-root}/customize.toml`, use defaults). Run `{workflow.activation_steps_prepend}`, then `{workflow.activation_steps_append}`. Hold `{workflow.persistent_facts}` as standing context — the default loads `project-context.md`, load-bearing for brownfield — and consult `{workflow.external_sources}` on demand.
+2. Resolve config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` (merges `_bmad/config.toml`, `_bmad/config.user.toml`, and the `_bmad/custom/` overrides). From the merged JSON resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}` (under `core`), `{planning_artifacts}` (under `modules.bmm`), and `{date}`; missing keys take neutral defaults, never block.
+3. Headless (no interactive user) → follow `references/headless.md` for the whole run. Otherwise greet `{user_name}` in `{communication_language}`. Detect the intent from the conversation and input — **create** (the default), **update** an existing spine, or **validate** one (see those sections). If the real ask is requirements / UX / a capability contract / epic breakdown / an agent, invoke the `bmad-prd`, `bmad-ux`, `bmad-spec`, `bmad-create-epics-and-stories`, or `bmad-workflow-builder` (if the BMad Builder module is installed) skill instead.
+4. If a run folder for this target already exists under `{workflow.spine_output_path}`, offer to resume from its memlog rather than restart.
+5. Interactive create: offer the working mode in `{communication_language}` — **Coaching path** (default) or **Fast path** (see *How you work*) — before any drafting; default to Coaching unless the user asks for speed.
+6. **Mandatory, both paths, before drafting:** ask whether the spine is the only deliverable — and if not, draw out the *purpose and audience* rather than a document type. "An architecture doc" balloons into bloat; what they actually need might be a one-detail explainer for a single team or a non-technical vision piece for a board. Purpose right-sizes the artifact and may call for extra elicitation up front, not just a finale add-on.
+
+For a new spine, bind `{doc_workspace}` to `{workflow.spine_output_path}/{workflow.run_folder_pattern}/`, seed `ARCHITECTURE-SPINE.md` from `{workflow.spine_template}`, run `memlog.py init`, and tell the user the path. **At epic altitude, scope the folder to the epic** (set `run_folder_pattern` per `customize.toml`) so per-epic runs don't collide.
+
+## Reviewer Gate
+
+The spine's pre-handoff review — full mechanics in `references/reviewer-gate.md`. Load it when finalizing or validating: a deterministic `lint_spine.py` pass, then a rubric walker (good-spine checklist) + every `{workflow.finalize_reviewers}` lens dispatched as parallel subagents against `ARCHITECTURE-SPINE.md`, scaled to stakes. At Finalize you apply the clear fixes; under the Validate intent you deliver a bespoke HTML report and then get user input.
+
+## Finalize
+
+Walk the sequence; reviewer fixes land before polish.
+
+1. **Distill.** Write the spine from the memlog (brownfield: + the code sweep) — invariants first, seed minimal, every `AD` carrying Binds/Prevents/Rule, `Deferred` naming what it won't decide. No placeholders; never invent to fill a gap. The template's `<!-- -->` notes are guidance — act on them, then strip them; the finished spine carries no template comment, and only the diagrams that convey the structure (as many as the altitude needs, valid mermaid). Sweep the breadth the altitude owns — every structural dimension is decided, deferred, or an open question; a whole dimension left silent (e.g. the operational/environmental envelope: deployment & environments, infra/provider strategy, operations) is the failure, not a clean spine. A long coaching run distills cleaner in a subagent; the parent falls back inline.
+2. **Reconcile inputs.** A subagent per load-bearing input checks it against the spine and returns what didn't land — especially a quiet requirement (a tone, a constraint) the `AD` structure dropped. Before the gate.
+3. **Reviewer pass.** Run the Reviewer Gate (`references/reviewer-gate.md`). Resolve before polish.
+4. **Triage.** Open questions and `[ASSUMPTION]` tags: blockers (unsafe for what's next) resolved one at a time; the rest deferred with a revisit condition in the memlog.
+5. **Renderings & polish.** The spine is the build deliverable; with it and the memlog now in place, produce any *additional* human-facing artifact the user needs, scoped to the purpose and audience drawn out up front. The up-front question already flagged whether one's needed; if it wasn't, still offer one here, seeding concrete options: an interactive HTML+SVG deck to walk a team through the architecture and drive discussion, a fuller HTML/md solution design, a C4 set, or a view of how the work splits across teams/epics. Build only what they pick, right-sized to that purpose; apply `{workflow.doc_standards}` polish to that prose only, never to the spine.
+6. **External handoffs.** Run `{workflow.external_handoffs}`; surface returned URLs/IDs. Offer to invoke the `bmad-spec` skill to adopt the spine as a companion, keeping `AD` IDs stable so downstream can cite them.
+7. **Close.** Set the spine's own frontmatter `status: final`, `updated: {date}`; log a `memlog.py append --type event --text "spine finalized"` (the memlog has no status field). Share paths. Next, **lead with `bmad-spec`** — recommend adopting/refreshing the spine as a spec companion (always the top recommendation when a spec was an input, and a useful next step even when it wasn't), then `bmad-create-epics-and-stories` or — epic altitude — `bmad-build`; or invoke `bmad-help` to route.
+8. Run `{workflow.on_complete}`.
+
+## Update
+
+Amend an existing spine or provided artifact. Resume from its `.memlog.md` (the authority on what was decided), not the rendered spine. Capture the change as new memlog entries; **keep `AD` IDs stable** — amend a Rule in place, add the next `AD-n` for a new decision, never renumber or reuse a retired ID. Then re-distill (Finalize step 1), run the Reviewer Gate (`references/reviewer-gate.md`), and close as in Finalize. An update that overrides something from a source input: offer to update that source too, so upstream and the spine don't silently diverge.
+
+## Validate
+
+The standalone intent — critique an existing spine without changing it. Run the Reviewer Gate (`references/reviewer-gate.md`) against it and deliver the bespoke HTML report, then offer to roll the findings into an Update. (At Finalize the same gate runs as your own pre-handoff check, where you apply the fixes instead of reporting.)
diff --git a/.claude/skills/bmad-architecture/assets/spine-template.md b/.claude/skills/bmad-architecture/assets/spine-template.md
new file mode 100644
index 0000000..56329f4
--- /dev/null
+++ b/.claude/skills/bmad-architecture/assets/spine-template.md
@@ -0,0 +1,79 @@
+---
+name: '{name}'
+type: architecture-spine
+purpose: build-substrate    # build-substrate (default) · discussion · report · deck
+altitude: feature           # initiative (keeps features) · feature (keeps epics) · epic (keeps stories)
+paradigm: '{named design pattern, e.g. hexagonal, layered, pipes-and-filters, actor}'
+scope: '{what this spine governs}'
+status: draft               # draft · final
+created: '{date}'
+updated: '{date}'
+binds: []                   # capability / unit IDs governed (from the driving spec; at epic altitude, also the inherited parent AD ids)
+sources: []
+companions: []
+---
+
+# Architecture Spine — {name}
+
+<!-- TEMPLATE GUIDE — act on these comments, then delete them; never emit a comment in the finished spine. This is a shape, not a script: keep only the sections this spine needs and cut the rest (no empty headers). A small intent may be just paradigm + a few ADs + conventions; a platform earns more. An inherited epic spine is usually mostly Inherited Invariants + a thin Deferred. Decisions, not rationale (rationale lives in the memlog). Carry shape in diagrams; prose only where it must. -->
+
+## Design Paradigm
+
+<!-- Name the pattern (a known one loads a whole model for free) and map its layers to namespaces/directories. The smallest, most durable thing here. -->
+
+## Inherited Invariants
+
+<!-- Only when this spine inherits a higher-altitude parent. The parent's ADs/conventions/paradigm that bind here, by their ORIGINAL ids — read-only, never renumbered, not re-derived. A local decision that contradicts one is a conflict to surface, not an override. Cut this section otherwise. -->
+
+| Inherited | From parent | Binds here |
+| --- | --- | --- |
+| {AD-id / convention} | {parent spine} | {what it constrains in this scope} |
+
+## Invariants & Rules
+
+<!-- The durable heart: calls a future builder can't read off compliant code. One block per decision: stable ascending id (never reused/renumbered), Binds, Prevents (the divergence), Rule (enforceable). Tag [ADOPTED] when the user or existing reality settled it. Include a dependency-direction diagram (who may depend on whom) — it IS a rule; author it as valid mermaid, never an empty graph. -->
+
+### AD-1 — {decision}
+
+- **Binds:** {capability / unit ids / fr/nfr's, areas, or `all`}
+- **Prevents:** {the divergence this stops}
+- **Rule:** {the constraint downstream must follow}
+
+## Consistency Conventions
+
+<!-- Defaults that bind where independent builders would drift. Cut rows that don't apply; add rows the project needs. -->
+
+| Concern | Convention |
+| --- | --- |
+| Naming (entities, files, interfaces, events) | |
+| Data & formats (ids, dates, error shapes, envelopes) | |
+| State & cross-cutting (mutation, errors, logging, config, auth) | |
+
+## Stack
+
+<!-- SEED — verified current at authoring; the code owns this once it exists. Name + version only; the why lives in the memlog. One row per language, framework, key dependency, platform, or chain that's pinned. -->
+
+| Name | Version |
+| --- | --- |
+| {language / framework / key dep / platform / chain} | {pinned version} |
+
+## Structural Seed
+
+<!-- The shapes worth fixing at cold-start — not a fixed list. Include only what's non-obvious at this altitude, and use as many diagrams as convey it, each as VALID mermaid (never a placeholder or empty graph). Candidates: system/container/context view; DEPLOYMENT & ENVIRONMENTS and external provider/infra topology (cover the operational envelope here when this altitude owns it — don't let it fall through); core-entity ERD (names + relationships only; an attribute that's itself an invariant is an AD, not a diagram); a minimal source tree. The code owns the detail — this is scaffold, not a mirror to maintain. -->
+
+```text
+{root}/
+  {dir}/   # {what lives here}
+```
+
+## Capability → Architecture Map
+
+<!-- Present when a spec drove this run. Bridges the spec's capabilities to where they live + what governs them; the consistency auditor's checklist. Cut otherwise. -->
+
+| Capability / Area | Lives in | Governed by |
+| --- | --- | --- |
+| {CAP-id / area} | {component / module} | {AD-id, convention, paradigm} |
+
+## Deferred
+
+<!-- Decisions intentionally pushed down, each with the reason it can wait — including whole dimensions this altitude doesn't own yet. The half of the contract that keeps the spine lean. -->
diff --git a/.claude/skills/bmad-architecture/customize.toml b/.claude/skills/bmad-architecture/customize.toml
new file mode 100644
index 0000000..7841f3d
--- /dev/null
+++ b/.claude/skills/bmad-architecture/customize.toml
@@ -0,0 +1,102 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-architecture.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-architecture.toml         (team)
+#   {project-root}/_bmad/custom/bmad-architecture.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays: append
+
+# Steps to run before the standard activation (config load, greet).
+# Use for pre-flight loads, approved-stack policy checks, etc.
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Use for context-heavy setup that should happen once the user has been acknowledged.
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (approved stacks, banned dependencies, platform constraints, compliance guardrails).
+# Each entry is either a literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed
+# path/glob whose contents are loaded as facts.
+#
+# Default loads project-context.md if bmad-generate-project-context produced one — giving the
+# architect persistent awareness of the project's tech, domain, and conventions (load-bearing
+# for brownfield). Common opt-ins (set in team/user override TOML):
+#   "Our org is AWS-only -- do not propose GCP or Azure."
+#   "file:{project-root}/docs/engineering-standards.md"
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Executed when the workflow completes (after the spine is final and the user has been told).
+# String scalar (single instruction) or array of instructions executed in order. Empty for none.
+on_complete = ""
+
+# The architecture spine template. Treated as expert prior knowledge, not a checklist — the LLM
+# adapts it to the project, altitude, and domain, and drops sections a project genuinely doesn't
+# need. Override the path in team/user TOML to enforce a different spine shape.
+spine_template = "assets/spine-template.md"
+
+# Run folder location. ARCHITECTURE-SPINE.md, its .memlog.md, and any fuller rendering the run
+# produces all land inside `{spine_output_path}/{run_folder_pattern}/`. Resume-check scans
+# `{spine_output_path}` for prior unfinished runs.
+#
+# The default pattern fits the common case (one spine per project, at the altitude above epics).
+# At EPIC altitude, override run_folder_pattern to carry the epic identity so per-epic runs don't
+# collide on the same day — e.g. set it (team/user TOML) to "architecture-epic-{epic_id}", binding
+# {epic_id} from the driving spec / the activating payload. Headless callers may instead pass an
+# explicit doc_workspace and bypass the pattern entirely.
+spine_output_path = "{planning_artifacts}/architecture"
+run_folder_pattern = "architecture-{project_name}-{date}"
+
+# Prose-editorial standards applied at finalize ONLY to a fuller prose document the run produces
+# (a discussion report, full architecture doc, or design addendum) — never to the spine or other
+# short, structured outputs, which are terse and carry decisions in AD-n blocks and diagrams by
+# design. Each entry is a `skill:`, `file:`, or plain-text directive applied before the user sees
+# the polished draft. Suggested order: structural passes first, prose mechanics last. Append-only.
+# The default entry runs bmad-review's two editorial lenses in order:
+# structure, then prose on top of the structure findings. The `lenses=` suffix
+# names them; drop it to let bmad-review pick what fits the content.
+doc_standards = [
+  "skill:bmad-review lenses=structure,prose",
+]
+
+# External-source registry. Natural-language directives describing knowledge bases, MCP tools, or
+# internal systems the LLM may consult ON DEMAND during the run (not preemptively) — approved-stack
+# catalogs, internal platform docs, version registries. Each entry names the tool, the trigger
+# condition, and any fields it needs. If a named tool is unavailable at runtime, the LLM falls back
+# to standard behavior (e.g. web research) and notes the gap. Empty by default.
+#
+# Examples (set in team/user override TOML):
+#   "When choosing a datastore, consult corp:platform_catalog before recommending one."
+#   "For current library versions, query corp:artifact_registry before web search."
+external_sources = []
+
+# External-handoff routing applied at Finalize to push outputs beyond local files (Confluence,
+# Notion, ticket systems). Each entry names the MCP tool, the destination, and required fields.
+# Runs after polish; returned URLs/IDs are surfaced. Unavailable tools are skipped and flagged;
+# local files always exist. Empty by default.
+external_handoffs = []
+
+# --- Finalize reviewers ---
+# Extra review lenses spawned as parallel subagents at the validation gate (Finalize and the
+# Validate intent), on top of the skill's built-in good-spine checklist and the lint_spine.py
+# mechanical floor. The GATE is stakes-gated — a throwaway spine may run it quietly or skip it —
+# but whenever the gate runs, every entry here runs with it (the configured floor, never cherry-
+# picked); only ad-hoc lenses are optional, and headless never skips the gate.
+#
+# Entries follow the standard prefix convention:
+#   "skill:NAME"   invoke the named review skill as a subagent against ARCHITECTURE-SPINE.md
+#   "file:PATH"    load the file as a review prompt; spawn an adversarial subagent applying it
+#   plain text     use the text directly as the subagent's review prompt
+#
+# Resolved on-demand (not at activation). Override TOML may append.
+finalize_reviewers = [
+  "Verify every committed decision was web-researched or reality-checked rather than asserted from training data: current library/framework versions, that each named technology still exists and fits, and — greenfield — the live defaults of any starter it leans on. Flag anything that could be out of date and wasn't confirmed against the web, the existing project, or the current starter.",
+  "Attack the spine as an adversary: construct two units one level down that each obey every AD to the letter yet still build incompatibly — clashing shared-data shapes, two owners of one entity, conflicting state-mutation paths. Every pair you find is a hole to close with a new or tightened AD.",
+]
diff --git a/.claude/skills/bmad-architecture/references/headless.md b/.claude/skills/bmad-architecture/references/headless.md
new file mode 100644
index 0000000..bd4d20b
--- /dev/null
+++ b/.claude/skills/bmad-architecture/references/headless.md
@@ -0,0 +1,26 @@
+# Headless
+
+No interactive user: infer everything, ask nothing, but never invent — record inferences as `assumptions[]` and gaps that need a human as `open_questions[]`. Detect headless from a `headless: true` flag, a non-interactive / no-TTY invocation, an activation hook that declares it, or a first message that pre-supplies all inputs and asks for an artifact path back; when ambiguous, default to interactive.
+
+Drive the run from the payload in the first message — `intent`, `altitude`, `purpose`, the driving input (spec package / PRD / raw intent / brownfield path), a parent spine path at lower altitude, and `doc_workspace` if a specific folder is required. Infer anything absent from the inputs or workspace; don't invent stack, constraints, or scope to fill a gap. You still verify named tech on the web (you can't ask, but you can check) and still drive every write through the shared `{project-root}/_bmad/scripts/memlog.py`. Run the full Reviewer Gate (`references/reviewer-gate.md`) non-interactively: `scripts/lint_spine.py` plus **every `{workflow.finalize_reviewers}` lens as a parallel subagent** (and any ad-hoc lens the spine's criticality warrants). Headless skips only the human picking from the menu — never the reviewers themselves; apply the clear fixes and record anything unresolved in `open_questions[]`. For a true authority collision, list it in `conflicts_with_prior_decisions[]`. For the Validate intent, always write the report to `{doc_workspace}` and add `"offer_to_update": true`. If intent stays ambiguous after inference, halt blocked.
+
+End with JSON only, omitting keys for artifacts not produced — the shape below is the fully-produced (`complete`) case; a `blocked` run produces no spine, so it omits `spine`, `memlog`, and `companions` entirely (see the note under the block):
+
+```json
+{
+  "status": "complete | partial | blocked",
+  "intent": "create | update | validate",
+  "altitude": "initiative | feature | epic",
+  "purpose": "build-substrate | discussion",
+  "doc_workspace": "<resolved run folder>",
+  "spine": "{doc_workspace}/ARCHITECTURE-SPINE.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "companions": [],
+  "assumptions": [],
+  "open_questions": [],
+  "conflicts_with_prior_decisions": [],
+  "reason": "<one line, only when blocked>"
+}
+```
+
+`complete` stands alone · `partial` (spine produced, but `open_questions[]` non-empty or critical inputs inferred) means review before downstream use · `blocked` means no spine produced — return only `status`, `intent`, `reason`, and `doc_workspace` (if bound), omitting `spine`, `memlog`, `companions`, and the artifact arrays that don't exist.
diff --git a/.claude/skills/bmad-architecture/references/reviewer-gate.md b/.claude/skills/bmad-architecture/references/reviewer-gate.md
new file mode 100644
index 0000000..159548a
--- /dev/null
+++ b/.claude/skills/bmad-architecture/references/reviewer-gate.md
@@ -0,0 +1,13 @@
+# Reviewer Gate
+
+The spine's pre-handoff review. Runs at Finalize (after distill + reconcile) and *is* the Validate intent. The difference is the ending: at Finalize you apply the clear fixes yourself; under Validate you report and don't change the spine.
+
+Cheap deterministic pass first: `uv run {skill-root}/scripts/lint_spine.py --workspace {doc_workspace}` settles the mechanical misses (placeholders, duplicate `AD` IDs, missing Binds/Prevents/Rule, unpinned Stack versions), so reviewers spend judgment on the semantic half.
+
+Assemble the menu: a **rubric walker** that judges the spine against the good-spine checklist below, **+ every entry in `{workflow.finalize_reviewers}`**, + ad-hoc lenses you invent or offer as the spine's rigor, altitude, and criticality warrant — a security/compliance lens for regulated stakes, a seam reviewer cross-team, a data-integrity lens for a heavy data model. Scale *whether and how heavily the gate runs* to the stakes: a throwaway prototype may run it quietly or skip the gate entirely; a high-criticality or platform-altitude spine earns more lenses and the explicit all / subset / skip menu. But once the gate runs, the `{workflow.finalize_reviewers}` always run — they are the configured floor, never cherry-picked out; only the ad-hoc lenses are optional. (Headless never skips the gate.)
+
+Dispatch every entry as a **parallel subagent against `ARCHITECTURE-SPINE.md`** (prefix convention: `skill:` / `file:` / plain text). Each writes its full review to `{doc_workspace}/reviews/review-{slug}.md` — a subfolder, so the gate's scratch stays out of the deliverable folder — and returns ONLY a compact summary (verdict, top 2–5 findings, file path) — the parent never holds full review text. An inline self-check does not count: the independent context is the point, because a fresh reviewer finds the divergences the author talks past. If subagents are unavailable, run sequentially — write the file first, then flush it from context.
+
+**Good-spine checklist** (what the rubric walker judges): it fixes the real divergence points for the level below and misses none; every `AD`'s Rule is enforceable and actually prevents its stated divergence; nothing under Deferred could let two units diverge; named tech is verified-current; it ratifies rather than contradicts a brownfield codebase; if a spec drove it, it covers that spec's capabilities; if a parent spine is inherited, no new `AD` weakens or contradicts an inherited one; and every dimension the altitude owns is decided, deferred, or an open question — a whole dimension left silent is a finding, especially the operational/environmental envelope (deployment & environments, infra/provider strategy, operations) a domain-focused draft skips.
+
+Surface findings tiered, never dumped: a one-sentence gate verdict, then critical + high; medium/low roll into a tail ("plus N more in {file}"). Per finding: autofix, discuss, defer to Deferred / open items, or ignore. **At Finalize this is your own gate — apply the clear fixes rather than handing over a list; surface only what genuinely needs the user.** Under the **Validate intent**, fold every reviewer's output into one bespoke HTML + markdown report and open the HTML.
diff --git a/.claude/skills/bmad-architecture/scripts/lint_spine.py b/.claude/skills/bmad-architecture/scripts/lint_spine.py
new file mode 100644
index 0000000..d583a52
--- /dev/null
+++ b/.claude/skills/bmad-architecture/scripts/lint_spine.py
@@ -0,0 +1,257 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""lint-spine — the mechanical half of spine decision-integrity, done deterministically.
+
+LLMs miscount IDs and miss literal placeholders; a grep does not. This linter owns the
+checks a script does better than a prompt, and leaves the semantic half (is each Rule
+actually enforceable? does the boundary make sense?) to the rubric walker.
+
+It reads ARCHITECTURE-SPINE.md from a workspace and reports, as compact JSON on stdout:
+
+  - placeholder    literal TBD / TODO / "similar to AD-n" / unfilled {template-token}
+  - ad_id          duplicate or non-monotonic AD-n identifiers
+  - ad_fields      an AD-n block missing Binds / Prevents / Rule
+  - version_pin    a ## Stack table row with no version
+
+Fenced code blocks are blanked (replaced with equal-count blank lines) before scanning, so
+mermaid and source trees don't trip false positives AND reported line numbers still line up
+with the real file. Reported lines are absolute file lines (frontmatter offset added). Exit
+code is always 0 — findings travel in the JSON; the caller (Reviewer Gate / rubric walker)
+decides what to do with them.
+"""
+from __future__ import annotations
+
+import argparse
+import json
+import re
+import sys
+from pathlib import Path
+
+SPINE = "ARCHITECTURE-SPINE.md"
+
+AD_HEADING = re.compile(r"^#{2,4}\s*AD-(\d+)\b(.*)$", re.MULTILINE)
+HEADING = re.compile(r"^#{1,6}\s", re.MULTILINE)
+FENCE = re.compile(r"```.*?```", re.DOTALL)
+PLACEHOLDER_WORD = re.compile(r"\b(TBD|TODO|FIXME|XXX)\b")
+SIMILAR_TO = re.compile(r"similar to AD-\d+", re.IGNORECASE)
+TEMPLATE_TOKEN = re.compile(r"\{[a-z_][a-z0-9_ /.-]*\}")
+
+
+def split_frontmatter(text: str) -> tuple[str, str, int]:
+    """Return (frontmatter, body, body_line_offset).
+
+    Frontmatter is the content between the first two lines that are *exactly* `---`
+    (line-exact, like memlog.split — a `---` inside a value or a body thematic break never
+    truncates it). body_line_offset is the number of file lines before the body begins, so a
+    body-relative line number plus the offset gives the absolute file line. Absent frontmatter
+    → ('', text, 0)."""
+    lines = text.split("\n")
+    if lines and lines[0] == "---":
+        for i in range(1, len(lines)):
+            if lines[i] == "---":
+                fm = "\n".join(lines[1:i])
+                body = "\n".join(lines[i + 1:])
+                return fm, body, i + 1
+    return "", text, 0
+
+
+def blank_fences(text: str) -> str:
+    """Replace each fenced block with the same number of newlines, so scanning skips fenced
+    content while every line number outside the fence stays put."""
+    return FENCE.sub(lambda m: "\n" * m.group(0).count("\n"), text)
+
+
+def line_of(text: str, idx: int) -> int:
+    return text.count("\n", 0, idx) + 1
+
+
+def find_placeholders(body: str, offset: int) -> list[dict]:
+    findings: list[dict] = []
+    scan = blank_fences(body)
+    # (regex, label, severity) — TBD/TODO and dangling cross-refs are unambiguous; a bare
+    # {template-token} can be legitimate brace prose, so it is flagged low ("possible") to keep
+    # the mechanical pass near-zero false-positive rather than train reviewers to ignore it.
+    for rx, label, severity in (
+        (PLACEHOLDER_WORD, "placeholder marker", "high"),
+        (SIMILAR_TO, "unresolved cross-reference", "high"),
+        (TEMPLATE_TOKEN, "possible unfilled template token (verify)", "low"),
+    ):
+        for m in rx.finditer(scan):
+            findings.append({
+                "category": "placeholder",
+                "severity": severity,
+                "detail": f"{label}: {m.group(0)!r}",
+                "location": f"{SPINE} (line {offset + line_of(scan, m.start())})",
+            })
+    return findings
+
+
+def find_frontmatter_placeholders(frontmatter: str) -> list[dict]:
+    """Catch unfilled tokens left in frontmatter (e.g. paradigm/scope/date) — part of the
+    spine contract, but outside the body that find_placeholders scans."""
+    findings: list[dict] = []
+    for rx, label, severity in (
+        (PLACEHOLDER_WORD, "placeholder marker", "high"),
+        (TEMPLATE_TOKEN, "possible unfilled template token (verify)", "low"),
+    ):
+        for m in rx.finditer(frontmatter):
+            findings.append({
+                "category": "placeholder",
+                "severity": severity,
+                "detail": f"frontmatter {label}: {m.group(0)!r}",
+                "location": f"{SPINE} frontmatter (line {1 + line_of(frontmatter, m.start())})",
+            })
+    return findings
+
+
+def find_ad_issues(body: str, offset: int) -> list[dict]:
+    findings: list[dict] = []
+    scan = blank_fences(body)  # AD headings shown inside a code fence are not live ADs
+    matches = list(AD_HEADING.finditer(scan))
+    seen: dict[int, int] = {}
+    prev: int | None = None
+    for m in matches:
+        num = int(m.group(1))
+        file_line = offset + line_of(scan, m.start())
+        loc = f"{SPINE} AD-{num} (line {file_line})"
+        if num in seen:
+            findings.append({
+                "category": "ad_id",
+                "severity": "high",
+                "detail": f"AD-{num} id reused (also at line {seen[num]})",
+                "location": loc,
+            })
+        else:
+            seen[num] = file_line
+        if prev is not None and num <= prev:
+            findings.append({
+                "category": "ad_id",
+                "severity": "high",
+                "detail": f"AD-{num} is non-monotonic (follows AD-{prev}); ids must ascend and never renumber",
+                "location": loc,
+            })
+        prev = num if prev is None else max(prev, num)
+
+        # block text = from this heading to the next heading of any level
+        start = m.end()
+        nxt = HEADING.search(scan, start)
+        block = scan[start:nxt.start()] if nxt else scan[start:]
+        low = block.lower()
+        missing = [f for f in ("binds", "prevents", "rule") if f not in low]
+        if missing:
+            findings.append({
+                "category": "ad_fields",
+                "severity": "high",
+                "detail": f"AD-{num} missing required field(s): {', '.join(missing)}",
+                "location": loc,
+            })
+    return findings
+
+
+def find_unpinned_stack(body: str, offset: int) -> list[dict]:
+    """Flag a `## Stack` table row that names something but leaves its version blank or a
+    placeholder. Pinning lives in the body table now, not frontmatter. A row whose name is
+    still a `{token}` skeleton is left to the placeholder pass, not double-reported here.
+
+    Fences are blanked first (like find_placeholders / find_ad_issues), so a pipe-row or
+    heading inside a code block is never read as live Stack content. The heading match is
+    `## Stack` with a word boundary, so a renamed heading (`## Stack & Versions`) still
+    counts. Name and Version columns are located from the header row, so a reordered table
+    pairs name to version correctly; both default to the canonical positions (0, 1)."""
+    findings: list[dict] = []
+    in_stack = False
+    header_seen = False
+    name_idx, ver_idx = 0, 1
+    scan = blank_fences(body)
+    for i, raw in enumerate(scan.splitlines()):
+        if HEADING.match(raw):
+            in_stack = re.match(r"^##\s+Stack\b", raw) is not None
+            header_seen = False
+            name_idx, ver_idx = 0, 1
+            continue
+        if not in_stack or not raw.lstrip().startswith("|"):
+            continue
+        if set(raw.strip()) <= set("|-: "):
+            continue  # separator row
+        cells = _table_cells(raw)
+        if not header_seen:
+            header_seen = True
+            for j, c in enumerate(cells):
+                if c.lower() == "name":
+                    name_idx = j
+                elif c.lower() == "version":
+                    ver_idx = j
+            continue
+        name = cells[name_idx] if len(cells) > name_idx else ""
+        version = cells[ver_idx] if len(cells) > ver_idx else ""
+        if not name or TEMPLATE_TOKEN.search(name):
+            continue
+        if not version or TEMPLATE_TOKEN.search(version):
+            findings.append({
+                "category": "version_pin",
+                "severity": "medium",
+                "detail": f"Stack entry {name!r} has no version",
+                "location": f"{SPINE} (line {offset + i + 1})",
+            })
+    return findings
+
+
+def _table_cells(row: str) -> list[str]:
+    """Split a markdown table row into trimmed cells, dropping the leading/trailing pipe."""
+    s = row.strip()
+    if s.startswith("|"):
+        s = s[1:]
+    if s.endswith("|"):
+        s = s[:-1]
+    return [c.strip() for c in s.split("|")]
+
+
+def lint(text: str) -> dict:
+    frontmatter, body, offset = split_frontmatter(text)
+    findings: list[dict] = []
+    findings += find_frontmatter_placeholders(frontmatter)
+    findings += find_placeholders(body, offset)
+    findings += find_ad_issues(body, offset)
+    findings += find_unpinned_stack(body, offset)
+    counts: dict[str, int] = {}
+    for f in findings:
+        counts[f["severity"]] = counts.get(f["severity"], 0) + 1
+    return {
+        "ok": len(findings) == 0,
+        "spine": SPINE,
+        "total_findings": len(findings),
+        "by_severity": counts,
+        "findings": findings,
+    }
+
+
+def main(argv: list[str] | None = None) -> int:
+    ap = argparse.ArgumentParser(description="Lint an architecture spine for mechanical integrity.")
+    ap.add_argument("--workspace", required=True, help="run folder containing ARCHITECTURE-SPINE.md")
+    ap.add_argument("-o", "--output", help="write JSON here instead of stdout")
+    args = ap.parse_args(argv)
+
+    spine_path = Path(args.workspace) / SPINE
+    if not spine_path.exists():
+        result = {"ok": False, "error": f"{spine_path} not found", "findings": [], "total_findings": 0}
+    else:
+        try:
+            text = spine_path.read_text(encoding="utf-8")
+        except (OSError, UnicodeDecodeError) as e:
+            # honor the "exit code is always 0" contract: a read/decode failure travels in JSON
+            result = {"ok": False, "error": f"could not read {spine_path}: {e}", "findings": [], "total_findings": 0}
+        else:
+            result = lint(text)
+
+    out = json.dumps(result, indent=2)
+    if args.output:
+        Path(args.output).write_text(out + "\n", encoding="utf-8")
+    else:
+        print(out)
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/.claude/skills/bmad-architecture/scripts/tests/test_lint_spine.py b/.claude/skills/bmad-architecture/scripts/tests/test_lint_spine.py
new file mode 100644
index 0000000..55cf748
--- /dev/null
+++ b/.claude/skills/bmad-architecture/scripts/tests/test_lint_spine.py
@@ -0,0 +1,270 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0"]
+# ///
+"""Tests for lint_spine.py. Run: uv run --with pytest pytest scripts/tests/test_lint_spine.py
+
+The spine under test: a clean spine lints empty; the linter catches exactly the
+mechanical defects a prompt is unreliable at — literal placeholders, AD-n id breakage,
+AD-n blocks missing required fields, and unpinned Stack versions.
+"""
+import importlib.util
+import json
+import re
+import sys
+from pathlib import Path
+
+import pytest
+
+_SPEC = importlib.util.spec_from_file_location(
+    "lint_spine", Path(__file__).resolve().parent.parent / "lint_spine.py"
+)
+lint_spine = importlib.util.module_from_spec(_SPEC)
+sys.modules["lint_spine"] = lint_spine
+_SPEC.loader.exec_module(lint_spine)
+
+
+CLEAN = """---
+name: 'Demo'
+---
+
+## Invariants & Rules
+
+### AD-1 — single write path
+
+- **Binds:** all
+- **Prevents:** divergent mutation
+- **Rule:** state changes only through the command bus
+
+### AD-2 — layered deps `[ADOPTED]`
+
+- **Binds:** all
+- **Prevents:** import cycles
+- **Rule:** ui -> app -> domain, never backward
+
+```mermaid
+flowchart LR
+  A --> B{decision}
+```
+
+## Stack
+
+| Name | Version |
+| --- | --- |
+| fastapi | 0.115 |
+| pydantic | 2.9 |
+"""
+
+
+def cats(result):
+    return sorted(f["category"] for f in result["findings"])
+
+
+def test_clean_spine_passes():
+    result = lint_spine.lint(CLEAN)
+    assert result["ok"] is True
+    assert result["total_findings"] == 0
+
+
+def test_mermaid_braces_not_flagged():
+    # the {decision} node lives in a fenced block and must not read as a template token
+    result = lint_spine.lint(CLEAN)
+    assert "placeholder" not in cats(result)
+
+
+def test_placeholder_markers_caught():
+    text = CLEAN.replace("the command bus", "TBD")
+    result = lint_spine.lint(text)
+    assert "placeholder" in cats(result)
+
+
+def test_similar_to_caught():
+    text = CLEAN.replace("import cycles", "similar to AD-1")
+    result = lint_spine.lint(text)
+    assert any("cross-reference" in f["detail"] for f in result["findings"])
+
+
+def test_unfilled_template_token_caught():
+    text = CLEAN.replace("single write path", "{decision}")
+    result = lint_spine.lint(text)
+    assert any(f["category"] == "placeholder" for f in result["findings"])
+
+
+def test_duplicate_ad_id_caught():
+    text = CLEAN.replace("### AD-2 — layered deps `[ADOPTED]`", "### AD-1 — layered deps")
+    result = lint_spine.lint(text)
+    assert "ad_id" in cats(result)
+
+
+def test_non_monotonic_ad_id_caught():
+    text = CLEAN.replace("### AD-2 — layered deps `[ADOPTED]`", "### AD-5 — layered deps").replace(
+        "### AD-1 — single write path", "### AD-9 — single write path"
+    )
+    result = lint_spine.lint(text)
+    assert any("non-monotonic" in f["detail"] for f in result["findings"])
+
+
+def test_missing_field_caught():
+    text = CLEAN.replace("- **Rule:** state changes only through the command bus\n", "")
+    result = lint_spine.lint(text)
+    assert any(f["category"] == "ad_fields" and "rule" in f["detail"] for f in result["findings"])
+
+
+def test_unpinned_dep_caught():
+    text = CLEAN.replace("| fastapi | 0.115 |", "| fastapi |  |")
+    result = lint_spine.lint(text)
+    assert "version_pin" in cats(result)
+
+
+def test_placeholder_version_caught():
+    text = CLEAN.replace("| fastapi | 0.115 |", "| fastapi | {pin} |")
+    result = lint_spine.lint(text)
+    assert any(f["category"] == "version_pin" and "fastapi" in f["detail"] for f in result["findings"])
+
+
+def test_no_stack_section_ok():
+    text = CLEAN.split("## Stack")[0]
+    result = lint_spine.lint(text)
+    assert "version_pin" not in cats(result)
+
+
+def test_stack_skeleton_row_not_version_pinned():
+    # a leftover {token} name is the placeholder pass's job, not a double-reported version_pin
+    text = CLEAN.replace("| fastapi | 0.115 |", "| {language / framework} | {pinned version} |")
+    result = lint_spine.lint(text)
+    assert "version_pin" not in cats(result)
+
+
+def test_stack_html_comment_not_parsed_as_row():
+    text = CLEAN.replace("## Stack\n", "## Stack\n\n<!-- SEED — verified current 2026-06 -->\n")
+    result = lint_spine.lint(text)
+    assert "version_pin" not in cats(result)
+
+
+def test_template_token_is_low_severity():
+    # a bare {token} can be legitimate brace prose; it is flagged, but low (not high) so the
+    # mechanical pass stays near-zero false-positive
+    text = CLEAN.replace("single write path", "{decision}")
+    result = lint_spine.lint(text)
+    toks = [f for f in result["findings"] if f["category"] == "placeholder" and "template token" in f["detail"]]
+    assert toks and all(f["severity"] == "low" for f in toks)
+
+
+def test_no_frontmatter_body_still_scanned():
+    text = "## Invariants\n\n### AD-1 — x\n\n- **Binds:** all\n- **Prevents:** drift\n- **Rule:** TBD\n"
+    result = lint_spine.lint(text)
+    assert "placeholder" in cats(result)  # TBD caught even with no frontmatter
+
+
+def test_frontmatter_value_with_dashes_not_truncated():
+    # a value containing '---' must not be read as the closing fence (line-exact close)
+    text = ("---\nname: 'x'\nscope: 'phase 1 --- phase 2'\n---\n\n"
+            "## Stack\n\n| Name | Version |\n| --- | --- |\n| fastapi |  |\n")
+    result = lint_spine.lint(text)
+    assert any(f["category"] == "version_pin" for f in result["findings"])  # read past the inline ---
+
+
+def test_ad_heading_in_fence_not_counted():
+    text = (
+        "---\nname: 'x'\n---\n\n"
+        "### AD-1 — real\n\n- **Binds:** all\n- **Prevents:** drift\n- **Rule:** do x\n\n"
+        "## Docs\n\n```text\n### AD-2 — illustrative only, no fields\n```\n"
+    )
+    result = lint_spine.lint(text)
+    assert result["ok"] is True  # the fenced AD-2 is not a live AD → no ad_fields/ad_id finding
+
+
+def test_stack_table_flags_only_the_unpinned_row():
+    text = ("---\nname: 'x'\n---\n\n## Stack\n\n| Name | Version |\n| --- | --- |\n"
+            "| fastapi | 0.115 |\n| redis |  |\n")
+    result = lint_spine.lint(text)
+    pins = [f for f in result["findings"] if f["category"] == "version_pin"]
+    assert len(pins) == 1 and "redis" in pins[0]["detail"]
+
+
+def test_stack_table_all_pinned_ok():
+    text = ("---\nname: 'x'\n---\n\n## Stack\n\n| Name | Version |\n| --- | --- |\n"
+            "| fastapi | 0.115 |\n")
+    result = lint_spine.lint(text)
+    assert "version_pin" not in cats(result)
+
+
+def test_fenced_stack_rows_not_parsed():
+    # an illustrative fenced table under ## Stack must not be read as live rows (fences are
+    # blanked first, like every other pass) — a blank-version row inside a fence is not a finding
+    text = ("---\nname: 'x'\n---\n\n## Stack\n\n| Name | Version |\n| --- | --- |\n"
+            "| fastapi | 0.115 |\n\n```text\n| example |  |\n```\n")
+    result = lint_spine.lint(text)
+    assert "version_pin" not in cats(result)
+
+
+def test_fenced_stack_heading_not_live():
+    # a `## Stack` heading shown inside a code fence is not the live Stack section
+    text = ("---\nname: 'x'\n---\n\n## Docs\n\n```md\n## Stack\n\n| foo |  |\n```\n")
+    result = lint_spine.lint(text)
+    assert "version_pin" not in cats(result)
+
+
+def test_renamed_stack_heading_still_scanned():
+    # the heading match is word-boundary, so a varied `## Stack` heading still counts
+    text = ("---\nname: 'x'\n---\n\n## Stack & Versions\n\n| Name | Version |\n| --- | --- |\n"
+            "| redis |  |\n")
+    result = lint_spine.lint(text)
+    pins = [f for f in result["findings"] if f["category"] == "version_pin"]
+    assert len(pins) == 1 and "redis" in pins[0]["detail"]
+
+
+def test_reordered_columns_pair_name_to_version():
+    # Version-then-Name header: the unpinned row must still be flagged by its real name
+    text = ("---\nname: 'x'\n---\n\n## Stack\n\n| Version | Name |\n| --- | --- |\n"
+            "| 0.115 | fastapi |\n|  | redis |\n")
+    result = lint_spine.lint(text)
+    pins = [f for f in result["findings"] if f["category"] == "version_pin"]
+    assert len(pins) == 1 and "redis" in pins[0]["detail"]
+
+
+def test_placeholder_line_number_is_absolute():
+    # a TBD after a multi-line fence reports its real file line (fence blanked, not collapsed)
+    text = (
+        "---\nname: 'x'\n---\n\n"
+        "## A\n\n"
+        "```text\nf1\nf2\nf3\n```\n\n"
+        "TBD here\n"
+    )
+    result = lint_spine.lint(text)
+    ph = next(f for f in result["findings"] if "TBD" in f["detail"])
+    n = int(re.search(r"line (\d+)", ph["location"]).group(1))
+    assert n == 13
+
+
+def test_missing_spine_file_reports_error(tmp_path, capsys):
+    rc = lint_spine.main(["--workspace", str(tmp_path)])
+    out = json.loads(capsys.readouterr().out)
+    assert rc == 0 and out["ok"] is False and "not found" in out["error"]
+
+
+def test_frontmatter_unfilled_token_caught():
+    # an unfilled {scope}/{paradigm}/{date} in frontmatter is part of the contract and must lint
+    text = "---\nname: 'x'\nscope: '{what this spine governs}'\n---\n\n## Invariants\n"
+    result = lint_spine.lint(text)
+    fm = [f for f in result["findings"] if f["category"] == "placeholder" and "frontmatter" in f["detail"]]
+    assert fm and any("template token" in f["detail"] for f in fm)
+
+
+def test_frontmatter_tbd_caught():
+    text = "---\nname: 'x'\nstatus: TBD\n---\n\n## Invariants\n"
+    result = lint_spine.lint(text)
+    assert any(f["category"] == "placeholder" and "frontmatter" in f["detail"] and "TBD" in f["detail"]
+               for f in result["findings"])
+
+
+def test_unreadable_spine_returns_error_not_crash(tmp_path, capsys):
+    # a spine that exists but can't be UTF-8 decoded must yield error JSON + exit 0, not a traceback
+    (tmp_path / lint_spine.SPINE).write_bytes(b"\xff\xfe bad bytes not utf-8")
+    rc = lint_spine.main(["--workspace", str(tmp_path)])
+    out = json.loads(capsys.readouterr().out)
+    assert rc == 0 and out["ok"] is False and "could not read" in out["error"]
+
+
+if __name__ == "__main__":
+    sys.exit(pytest.main([__file__, "-q"]))
diff --git a/.claude/skills/bmad-brainstorming/SKILL.md b/.claude/skills/bmad-brainstorming/SKILL.md
new file mode 100644
index 0000000..a4bf831
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/SKILL.md
@@ -0,0 +1,80 @@
+---
+name: bmad-brainstorming
+description: Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.
+---
+
+# BMad Brainstorming
+
+## Overview
+
+You are a creative brainstorming coach. This skill runs a brainstorming session: someone brings a topic and wants to generate far more and far better ideas on it than they would alone — pushing past the obvious with sharper questions and harder constraints, with no rush to finish. The best sessions end with the user surprised by what came out.
+
+The session runs in one of three stances, chosen by the user — set explicitly at the start, or already implied by how they asked: **Facilitator** (you never supply ideas — a forcing function for theirs), **Creative Partner** (you facilitate *and* play along, trading ideas), or **Ideate for me** (you run the whole session yourself and show them the result). The chosen stance holds for the whole run.
+
+## Conventions
+
+- Bare paths (e.g. `references/headless.md`) resolve from `{skill-root}` (where `customize.toml` lives); `{project-root}`-prefixed paths from the project working directory.
+- `{workflow.<name>}` resolves to fields in the merged `customize.toml` `[workflow]` table.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, use a subagent to read `{skill-root}/customize.toml` directly with defaults.
+2. Run each `{workflow.activation_steps_prepend}` entry. Treat each `{workflow.persistent_facts}` entry as foundational context (`file:`-prefixed entries are paths/globs under `{project-root}` — load their contents; others are facts verbatim).
+3. Resolve central config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core` (merges `_bmad/config.toml`, `_bmad/config.user.toml`, and the `_bmad/custom/` overrides); from the merged JSON resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{output_folder}`, `{project_name}`; `{date}` is today. On failure or missing values → neutral defaults; never block.
+4. **If launched headless** (a machine signal, not a human asking for output — `references/headless.md` lists them): load `references/headless.md` and follow it for the whole run; never load it otherwise. Outside headless, you generate ideas yourself only in autonomous mode (`references/mode-autonomous.md`) — never in facilitator or partner mode.
+5. **Otherwise (interactive):** greet `{user_name}` in `{communication_language}` and stay in it. Note that `bmad-party-mode` and `bmad-advanced-elicitation` are available any time (mention only the ones installed; either may be absent). Glob `{workflow.output_dir}/*/.memlog.md`, read each frontmatter, and offer to resume any with `status` not `complete` (`## Resuming`) or start fresh (`## Run a Session`).
+
+Run each `{workflow.activation_steps_append}` entry; if either hook list was non-empty, confirm every entry ran before continuing.
+
+## Framing — hold this the whole run
+
+These fight your defaults, in every mode; hold them deliberately. The stance you pick adds one more frame (`references/mode-*.md`) on top.
+
+- **Aim past 100 ideas; resist concluding.** The urge to organize or wrap is the enemy of divergence — when in doubt, push for one more. Land only when the user is spent or the topic is mined out.
+- **Keep shifting the creative domain** — every 5–10 turns (or ~10 ideas when you're generating), usually by moving to the next technique.
+- **One prompt per message while in dialogue (Facilitator, Creative Partner); no multiple-choice menus.** Don't stack questions into a wall or hand a menu that invites lazy picking — both pull the user out of generating. The only exceptions are the two up-front *process* choices (stance, and the technique flow): *how* to run is theirs to pick; *what* to ideate never is.
+
+**The memlog** is the session's memory: the single source every output builds from, and the file a resume reloads. Whatever isn't in it is gone. Log every idea, decision, question, and bit of user direction — anything you'd regret losing if the window closed — one line each, the gist in the user's meaning, in time order; never edit or reorder. Skip your prompts and small talk. All writes to memlog are atomic and use the script `memlog.py` invoked as follows:
+
+- `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<topic>" --field goal="<goal>" --field mode="<facilitator|partner|autonomous>"` — create it once topic, goal, and stance are known.
+- `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <kind> --text "<one-line gist>"` — log one entry. `--type` ∈ `idea`/`insight`/`question`/`decision`/`direction`/`technique` (a switch: `--text "started <name>"`); omit for a plain note. Add `--by user`/`--by coach` to mark authorship — **required in Creative Partner mode** (renders `(idea by user)`); skip it otherwise.
+- `uv run {project-root}/_bmad/scripts/memlog.py set --workspace {doc_workspace} --key status --value complete` — flip status at wrap-up.
+
+## Run a Session
+
+Open with one compound question what are we brainstorming, and what's the goal or why behind it (along with asking if there are any inputs or special requests). The why shapes technique choice and synthesis (*kids' iPhone apps to build with your own kids* vs. *to win market share* point different ways). If the kickoff already made both clear, skip the question and confirm; read anything they point you to. Derive a kebab-case `{topic_slug}` and bind `{doc_workspace} = {workflow.output_dir}/{workflow.output_folder_name}/`.
+
+Now set the **stance** and the **technique batch** in one step — the composer page does both, so make it the default.
+
+**The composer page (primary).** The file is `{skill-root}/assets/brain-selector.html`. With a customized catalog (overridden `{workflow.brain_methods}` or any `{workflow.additional_techniques}`), regenerate it first: `uv run {skill-root}/scripts/brain.py --file {workflow.brain_methods} [--extra {doc_workspace}/extra-techniques.json] html --out {doc_workspace}/brain-selector.html` (pass `--extra`, a JSON list of `{category, technique_name, description}`, when there are additional techniques; the file is then `{doc_workspace}/brain-selector.html`). Try to open it (`open` / `xdg-open` / `start`), then say, in one message: *"It should open in your browser — compose your session, click **Copy prompt**, and paste the result back. If it didn't open, open `<path>` yourself, or say 'let's do it in chat'."* You can't see their browser, so never claim it opened.
+
+Read the pasted block: the **`Facilitation mode:`** line → the stance; the **listed techniques** (full category/name/description, some tagged `(random pick)`) → run them as given, no `list`/`show` needed; **`invent N`** / **`you choose N`** → see `## Choosing Techniques`.
+
+**Or in chat.** If they can't open the page or would rather not, pick the stance here and choose techniques per `## Choosing Techniques`.
+
+Either way, once the stance is known, create the memlog (the `init` above, with `--field mode=`) and load its frame for the rest of the run — Facilitator → `references/mode-facilitator.md`, Creative Partner → `references/mode-partner.md`, Ideate for me → `references/mode-autonomous.md`. Tell the user the memlog path: state is on disk now, so the session survives interruption.
+
+## Choosing Techniques
+
+For **Facilitator** and **Creative Partner**. (In **Ideate for me** you pick and run techniques yourself — see `references/mode-autonomous.md`.)
+
+Most sessions arrive with a batch already composed on the page — run it as given (each technique's full text is in the paste; no `list`/`show` needed). Two parts of a paste delegate back to you:
+
+- **`invent N`** (Inventive Flow) — invent N brand-new techniques on the fly. A line may scope an invention (`invent 1 new technique in the spirit of <category>`, from the page's per-category invent card) — when it does, honor that category's spirit. Announce the order, log each one's name + description, and offer to save a keeper to `{workflow.additional_techniques}` at wrap-up.
+- **`you choose N`** (Facilitator Chosen) — pick N techniques fitting the goal, `{workflow.favorite_techniques}` first; confirm exact names with a scoped `uv run {skill-root}/scripts/brain.py --file {workflow.brain_methods} list --category <cat>`. Never pull the library whole into context.
+
+If they didn't use the page, load `references/in-chat-techniques.md` and pick the batch in chat (**3–4 is the sweet spot**).
+
+Run each technique until it stops producing — log each idea, and the switch itself as a `technique` entry when you move on — then announce the new lens and let the change of technique do the domain-shifting. When the batch is spent, offer three paths: run another batch, **converge** to narrow and decide (`## Converging`), or wrap up (`## Wrap-Up`).
+
+## Converging
+
+The catalog is all *divergent* — built to generate. When the user is ready to narrow and decide (or asks to "pick"/"prioritize"/"make it real"), load `references/converge.md` and follow it; it ends by handing off to `## Wrap-Up`. Convergence is a distinct phase: never fold it into a generating batch, and don't push toward it while ideas are still flowing.
+
+## Resuming
+
+Picking up an existing session instead of starting fresh: load `references/resume.md` and follow it.
+
+## Wrap-Up
+
+Load `references/finalize.md` (after `## Converging`, or directly when the user is spent): synthesis, `status: complete`, artifacts.
diff --git a/.claude/skills/bmad-brainstorming/assets/brain-icons.json b/.claude/skills/bmad-brainstorming/assets/brain-icons.json
new file mode 100644
index 0000000..9a979d8
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/assets/brain-icons.json
@@ -0,0 +1,166 @@
+{
+  "categories": {
+    "creative": {
+      "hue": "#6d5cf0",
+      "glyph": "<g stroke=\"currentColor\" stroke-width=\"2.4\" stroke-linecap=\"round\"><line x1=\"22\" y1=\"6.5\" x2=\"22\" y2=\"12.5\"/><line x1=\"22\" y1=\"31.5\" x2=\"22\" y2=\"37.5\"/><line x1=\"6.5\" y1=\"22\" x2=\"12.5\" y2=\"22\"/><line x1=\"31.5\" y1=\"22\" x2=\"37.5\" y2=\"22\"/><line x1=\"11.3\" y1=\"11.3\" x2=\"15.5\" y2=\"15.5\"/><line x1=\"28.5\" y1=\"28.5\" x2=\"32.7\" y2=\"32.7\"/><line x1=\"32.7\" y1=\"11.3\" x2=\"28.5\" y2=\"15.5\"/><line x1=\"15.5\" y1=\"28.5\" x2=\"11.3\" y2=\"32.7\"/></g><circle cx=\"22\" cy=\"22\" r=\"6.6\" fill=\"currentColor\" fill-opacity=\"0.25\"/><circle cx=\"22\" cy=\"22\" r=\"3.6\" fill=\"currentColor\"/>"
+    },
+    "deep": {
+      "hue": "#4658c9",
+      "glyph": "<g fill=\"none\" stroke=\"currentColor\"><circle cx=\"22\" cy=\"22\" r=\"13\" stroke-width=\"1.5\" stroke-opacity=\"0.4\"/><circle cx=\"22\" cy=\"22\" r=\"9\" stroke-width=\"1.7\" stroke-opacity=\"0.7\"/><circle cx=\"22\" cy=\"22\" r=\"5\" stroke-width=\"1.9\"/></g><circle cx=\"22\" cy=\"22\" r=\"2.4\" fill=\"currentColor\"/>"
+    },
+    "structured": {
+      "hue": "#3b6ea5",
+      "glyph": "<g fill=\"currentColor\"><rect x=\"11\" y=\"11\" width=\"9.5\" height=\"9.5\" rx=\"2\"/><rect x=\"23.5\" y=\"11\" width=\"9.5\" height=\"9.5\" rx=\"2\" fill-opacity=\"0.25\"/><rect x=\"11\" y=\"23.5\" width=\"9.5\" height=\"9.5\" rx=\"2\" fill-opacity=\"0.25\"/><rect x=\"23.5\" y=\"23.5\" width=\"9.5\" height=\"9.5\" rx=\"2\"/></g>"
+    },
+    "quantum": {
+      "hue": "#2b86d9",
+      "glyph": "<g stroke=\"currentColor\" stroke-width=\"1.8\" fill=\"none\"><ellipse cx=\"22\" cy=\"22\" rx=\"14.5\" ry=\"6\" transform=\"rotate(28 22 22)\"/><ellipse cx=\"22\" cy=\"22\" rx=\"14.5\" ry=\"6\" transform=\"rotate(-28 22 22)\"/></g><circle cx=\"22\" cy=\"22\" r=\"6.6\" fill=\"currentColor\" fill-opacity=\"0.18\"/><circle cx=\"22\" cy=\"22\" r=\"3.4\" fill=\"currentColor\"/><circle cx=\"33.2\" cy=\"17.4\" r=\"2\" fill=\"currentColor\"/>"
+    },
+    "speculative_future": {
+      "hue": "#0fb5c9",
+      "glyph": "<g stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" fill=\"none\"><path d=\"M11 31 L 26.5 15.5\"/><path d=\"M20 14.5 H 28 V 22.5\"/></g><circle cx=\"31\" cy=\"12\" r=\"2.8\" fill=\"currentColor\"/><g stroke=\"currentColor\" stroke-width=\"1.4\" stroke-linecap=\"round\"><line x1=\"31\" y1=\"6.5\" x2=\"31\" y2=\"8.4\"/><line x1=\"31\" y1=\"15.6\" x2=\"31\" y2=\"17.5\"/><line x1=\"25.5\" y1=\"12\" x2=\"27.4\" y2=\"12\"/><line x1=\"34.6\" y1=\"12\" x2=\"36.5\" y2=\"12\"/></g>"
+    },
+    "collaborative": {
+      "hue": "#15a3a3",
+      "glyph": "<g stroke=\"currentColor\" stroke-width=\"1.8\"><line x1=\"14\" y1=\"16\" x2=\"30\" y2=\"16\"/><line x1=\"14\" y1=\"16\" x2=\"22\" y2=\"30\"/><line x1=\"30\" y1=\"16\" x2=\"22\" y2=\"30\"/></g><g fill=\"currentColor\" fill-opacity=\"0.22\"><circle cx=\"14\" cy=\"16\" r=\"4.6\"/><circle cx=\"30\" cy=\"16\" r=\"4.6\"/><circle cx=\"22\" cy=\"30\" r=\"4.6\"/></g><g fill=\"currentColor\"><circle cx=\"14\" cy=\"16\" r=\"2.4\"/><circle cx=\"30\" cy=\"16\" r=\"2.4\"/><circle cx=\"22\" cy=\"30\" r=\"2.4\"/></g>"
+    },
+    "biomimetic": {
+      "hue": "#1f9d6b",
+      "glyph": "<path d=\"M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z\" fill=\"currentColor\" fill-opacity=\"0.22\"/><path d=\"M22 9 V 35.5\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\" fill=\"none\"/><g stroke=\"currentColor\" stroke-width=\"1.5\" stroke-linecap=\"round\"><path d=\"M22 16 l5.6 -2.6\"/><path d=\"M22 16 l-5.6 -2.6\"/><path d=\"M22 22 l6.6 -2.6\"/><path d=\"M22 22 l-6.6 -2.6\"/><path d=\"M22 28 l5.6 -2.6\"/><path d=\"M22 28 l-5.6 -2.6\"/></g>"
+    },
+    "constraint": {
+      "hue": "#d9882b",
+      "glyph": "<g stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" fill=\"none\"><path d=\"M17 11 H 11 V 17\"/><path d=\"M27 11 H 33 V 17\"/><path d=\"M17 33 H 11 V 27\"/><path d=\"M27 33 H 33 V 27\"/></g><circle cx=\"22\" cy=\"22\" r=\"5\" fill=\"currentColor\" fill-opacity=\"0.25\"/><circle cx=\"22\" cy=\"22\" r=\"2.6\" fill=\"currentColor\"/>"
+    },
+    "wild": {
+      "hue": "#e2562f",
+      "glyph": "<path d=\"M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z\" fill=\"currentColor\"/>"
+    },
+    "cultural": {
+      "hue": "#c75b39",
+      "glyph": "<circle cx=\"22\" cy=\"22\" r=\"13.5\" fill=\"currentColor\" fill-opacity=\"0.14\"/><g stroke=\"currentColor\" stroke-width=\"1.6\" fill=\"none\"><circle cx=\"22\" cy=\"22\" r=\"13.5\"/><ellipse cx=\"22\" cy=\"22\" rx=\"6\" ry=\"13.5\"/><line x1=\"8.5\" y1=\"22\" x2=\"35.5\" y2=\"22\"/><path d=\"M11 15 H 33\" stroke-opacity=\"0.55\"/><path d=\"M11 29 H 33\" stroke-opacity=\"0.55\"/></g>"
+    },
+    "theatrical": {
+      "hue": "#cf4d6f",
+      "glyph": "<path d=\"M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z\" fill=\"currentColor\" fill-opacity=\"0.18\"/><path d=\"M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z\" stroke=\"currentColor\" stroke-width=\"1.8\" fill=\"none\"/><g fill=\"currentColor\"><circle cx=\"18.5\" cy=\"21\" r=\"1.7\"/><circle cx=\"25.5\" cy=\"21\" r=\"1.7\"/></g><path d=\"M18 27 C 20 29.5, 24 29.5, 26 27\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\" fill=\"none\"/>"
+    },
+    "absurdist": {
+      "hue": "#e0529c",
+      "glyph": "<g transform=\"rotate(-12 22 22)\"><circle cx=\"22\" cy=\"22\" r=\"13\" fill=\"currentColor\" fill-opacity=\"0.14\"/><circle cx=\"22\" cy=\"22\" r=\"13\" stroke=\"currentColor\" stroke-width=\"1.6\" fill=\"none\"/><path d=\"M16 19 q 2 -2.4 4 0\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\" fill=\"none\"/><circle cx=\"26.5\" cy=\"18.8\" r=\"1.8\" fill=\"currentColor\"/><path d=\"M16.5 26 C 19 30, 25 30, 28 24.5\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\" fill=\"none\"/></g>"
+    },
+    "introspective_delight": {
+      "hue": "#b15ad6",
+      "glyph": "<circle cx=\"22\" cy=\"13.5\" r=\"4\" fill=\"currentColor\"/><path d=\"M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z\" fill=\"currentColor\" fill-opacity=\"0.22\"/><path d=\"M10.5 31 C 12.5 23, 31.5 23, 33.5 31\" stroke=\"currentColor\" stroke-width=\"1.7\" fill=\"none\"/><path d=\"M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30\" stroke=\"currentColor\" stroke-width=\"1.5\" fill=\"none\" stroke-opacity=\"0.6\"/>"
+    }
+  },
+  "techniques": {
+    "Yes And Building": "<g fill=\"currentColor\"><rect x=\"8\" y=\"27\" width=\"12\" height=\"8\" rx=\"1.5\" fill-opacity=\".8\"/><rect x=\"14\" y=\"19\" width=\"12\" height=\"8\" rx=\"1.5\" fill-opacity=\".5\"/><rect x=\"20\" y=\"11\" width=\"12\" height=\"8\" rx=\"1.5\"/></g>",
+    "Brain Writing Round Robin": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M31 16 A10 10 0 1 0 32.5 22\"/><path d=\"M31 10 L31.5 16.3 L25 16.5\"/></g>",
+    "Random Stimulation": "<rect x=\"11\" y=\"11\" width=\"22\" height=\"22\" rx=\"4\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><g fill=\"currentColor\"><circle cx=\"17\" cy=\"17\" r=\"1.8\"/><circle cx=\"27\" cy=\"17\" r=\"1.8\"/><circle cx=\"22\" cy=\"22\" r=\"1.8\"/><circle cx=\"17\" cy=\"27\" r=\"1.8\"/><circle cx=\"27\" cy=\"27\" r=\"1.8\"/></g>",
+    "Role Playing": "<rect x=\"11\" y=\"9\" width=\"22\" height=\"26\" rx=\"3\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><circle cx=\"22\" cy=\"19\" r=\"4\" fill=\"currentColor\"/><path d=\"M15.5 30 c2 -4.5 11 -4.5 13 0\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/>",
+    "Ideation Relay Race": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><line x1=\"12\" y1=\"31\" x2=\"27\" y2=\"16\"/><line x1=\"8\" y1=\"22\" x2=\"14\" y2=\"22\" stroke-opacity=\".5\"/><line x1=\"8\" y1=\"27\" x2=\"13\" y2=\"27\" stroke-opacity=\".35\"/></g><circle cx=\"29\" cy=\"14\" r=\"3.4\" fill=\"currentColor\"/>",
+    "Idea Hot Potato": "<path d=\"M11 31 Q22 8 33 31\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-dasharray=\"2 3.5\" stroke-linecap=\"round\"/><circle cx=\"22\" cy=\"12.5\" r=\"4.2\" fill=\"currentColor\"/>",
+    "Steal And Upgrade": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M20 33 V14\"/><path d=\"M13 21 L20 14 L27 21\"/></g><path d=\"M30 27 l1 2.6 2.6 1 -2.6 1 -1 2.6 -1 -2.6 -2.6 -1 2.6 -1 z\" fill=\"currentColor\"/>",
+    "Fold The Paper": "<path d=\"M13 16 L21 12 V28 L13 32 Z\" fill=\"currentColor\" fill-opacity=\".22\"/><path d=\"M21 12 L29 16 V32 L21 28 Z\" fill=\"currentColor\" fill-opacity=\".45\"/><path d=\"M13 16 L21 12 L29 16 M21 12 V28\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.5\" stroke-linejoin=\"round\"/>",
+    "What If Scenarios": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M18 17 a4 4 0 1 1 4 4 v3\"/></g><circle cx=\"22\" cy=\"30\" r=\"1.6\" fill=\"currentColor\"/>",
+    "Analogical Thinking": "<circle cx=\"15\" cy=\"22\" r=\"6\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><rect x=\"25\" y=\"16\" width=\"12\" height=\"12\" rx=\"2\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M19 20 q2 2 0 4 M23 20 q-2 2 0 4\" stroke=\"currentColor\" stroke-width=\"1.6\" fill=\"none\"/>",
+    "First Principles Thinking": "<g fill=\"currentColor\"><rect x=\"10\" y=\"28\" width=\"8\" height=\"6\" rx=\"1\"/><rect x=\"18.5\" y=\"28\" width=\"8\" height=\"6\" rx=\"1\"/><rect x=\"27\" y=\"28\" width=\"7\" height=\"6\" rx=\"1\"/></g><path d=\"M22 25 L22 11 M16 17 L22 11 L28 17\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/>",
+    "Forced Relationships": "<circle cx=\"12\" cy=\"22\" r=\"3.4\" fill=\"currentColor\"/><circle cx=\"32\" cy=\"22\" r=\"3.4\" fill=\"currentColor\"/><path d=\"M15 22 q7 -9 14 0\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-dasharray=\"1.5 3\"/>",
+    "Time Shifting": "<circle cx=\"22\" cy=\"22\" r=\"12\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 15 V22 L27 25\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/>",
+    "Metaphor Mapping": "<rect x=\"10\" y=\"14\" width=\"14\" height=\"14\" rx=\"2\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><circle cx=\"28\" cy=\"25\" r=\"7\" fill=\"currentColor\" fill-opacity=\".22\"/><circle cx=\"28\" cy=\"25\" r=\"7\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/>",
+    "Cross-Pollination": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M13 14 H27 a4 4 0 0 1 0 8 H17 a4 4 0 0 0 0 8 H31\"/><path d=\"M28 11 L31.5 14 L28 17 M16 27 L12.5 30 L16 33\"/></g>",
+    "Concept Blending": "<circle cx=\"18\" cy=\"22\" r=\"8\" fill=\"currentColor\" fill-opacity=\".25\"/><circle cx=\"26\" cy=\"22\" r=\"8\" fill=\"currentColor\" fill-opacity=\".25\"/><g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><circle cx=\"18\" cy=\"22\" r=\"8\"/><circle cx=\"26\" cy=\"22\" r=\"8\"/></g>",
+    "Reverse Brainstorming": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M13 18 H28 a4 4 0 0 1 0 8 H16\"/><path d=\"M19 15 L13 18 L19 21 M22 23 L16 26 L22 29\"/></g>",
+    "Sensory Exploration": "<path d=\"M10 22 q12 -10 24 0 q-12 10 -24 0 z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/><circle cx=\"22\" cy=\"22\" r=\"4\" fill=\"currentColor\"/>",
+    "Five Whys": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"14\" cy=\"13\" r=\"2.4\"/><circle cx=\"22\" cy=\"22\" r=\"2.4\"/><circle cx=\"30\" cy=\"31\" r=\"2.4\"/><path d=\"M15.6 14.8 L20.4 20.2 M23.6 23.8 L28.4 29.2\"/></g>",
+    "Provocation Technique": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M24 9 L13 24 H21 L19 35 L31 19 H23 Z\"/></g>",
+    "Assumption Reversal": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M16 14 V30\"/><path d=\"M11.5 25 L16 30 L20.5 25\"/><path d=\"M28 30 V14\"/><path d=\"M23.5 19 L28 14 L32.5 19\"/></g>",
+    "Question Storming": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M14 16 a3.2 3.2 0 1 1 3.2 3.2 v2\"/><path d=\"M26 13 a3.6 3.6 0 1 1 3.6 3.6 v2.4\"/></g><circle cx=\"17.2\" cy=\"27\" r=\"1.5\" fill=\"currentColor\"/><circle cx=\"29.6\" cy=\"25.6\" r=\"1.6\" fill=\"currentColor\"/>",
+    "Constraint Mapping": "<path d=\"M11 14 L18 12 L26 14 L33 12 V30 L26 32 L18 30 L11 32 Z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/><path d=\"M18 12 V30 M26 14 V32\" stroke=\"currentColor\" stroke-width=\"1.6\"/>",
+    "Failure Analysis": "<circle cx=\"20\" cy=\"20\" r=\"8\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><line x1=\"26\" y1=\"26\" x2=\"33\" y2=\"33\" stroke=\"currentColor\" stroke-width=\"2.4\" stroke-linecap=\"round\"/><path d=\"M20 16 V21 M20 24 V24\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/>",
+    "Emergent Thinking": "<g fill=\"currentColor\"><circle cx=\"11\" cy=\"31\" r=\"1.6\"/><circle cx=\"17\" cy=\"29\" r=\"1.6\"/><circle cx=\"16\" cy=\"23\" r=\"1.6\"/><circle cx=\"22\" cy=\"24\" r=\"1.8\"/><circle cx=\"23\" cy=\"17\" r=\"1.9\"/><circle cx=\"29\" cy=\"18\" r=\"1.7\"/><circle cx=\"28\" cy=\"12\" r=\"2.1\"/></g>",
+    "Causal Loop Mapping": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M16 16 a9 9 0 1 1 -2 12\"/><path d=\"M16 10.5 L16.5 16.5 L10.5 17\"/><path d=\"M30 28.5 L29.5 22.5 L35 22\"/></g>",
+    "Morphological Analysis": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\"><rect x=\"11\" y=\"11\" width=\"22\" height=\"22\" rx=\"2\"/><path d=\"M11 18.3 H33 M11 25.6 H33 M18.3 11 V33 M25.6 11 V33\"/></g><rect x=\"18.5\" y=\"18.5\" width=\"7\" height=\"7\" fill=\"currentColor\" fill-opacity=\".4\"/>",
+    "Laddering": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M16 9 V35 M28 9 V35 M16 15 H28 M16 22 H28 M16 29 H28\"/></g>",
+    "Inner Child Conference": "<circle cx=\"22\" cy=\"16\" r=\"6\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 22 V31\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/><path d=\"M19 34 q3 -3 6 0\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\"/><g fill=\"currentColor\"><circle cx=\"20\" cy=\"15\" r=\"1\"/><circle cx=\"24\" cy=\"15\" r=\"1\"/></g>",
+    "Shadow Work Mining": "<circle cx=\"22\" cy=\"22\" r=\"12\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 10 a12 12 0 0 1 0 24 z\" fill=\"currentColor\" fill-opacity=\".85\"/>",
+    "Values Archaeology": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><path d=\"M10 16 h24\" stroke-opacity=\".4\"/><path d=\"M10 22 h24\" stroke-opacity=\".6\"/></g><path d=\"M22 24 L16 30 L22 36 L28 30 Z\" fill=\"currentColor\"/>",
+    "Future Self Interview": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M14 10 H30 L24 22 L30 34 H14 L20 22 Z\"/></g><path d=\"M18 14 H26\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/>",
+    "Body Wisdom Dialogue": "<path d=\"M22 33 C12 26 9 19 13.5 15 C17 12 21 14 22 17 C23 14 27 12 30.5 15 C35 19 32 26 22 33 Z\" fill=\"currentColor\" fill-opacity=\".22\"/><path d=\"M22 33 C12 26 9 19 13.5 15 C17 12 21 14 22 17 C23 14 27 12 30.5 15 C35 19 32 26 22 33 Z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/>",
+    "Permission Giving": "<rect x=\"10\" y=\"14\" width=\"24\" height=\"16\" rx=\"2.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M15 23 L19 27 L28 17\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/>",
+    "Secret Wish Confession": "<rect x=\"13\" y=\"20\" width=\"18\" height=\"14\" rx=\"2.5\" fill=\"currentColor\" fill-opacity=\".22\"/><rect x=\"13\" y=\"20\" width=\"18\" height=\"14\" rx=\"2.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M16.5 20 v-3 a5.5 5.5 0 0 1 11 0 v3\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/>",
+    "Mood Weather Report": "<circle cx=\"17\" cy=\"17\" r=\"4.5\" fill=\"currentColor\" fill-opacity=\".5\"/><path d=\"M22 30 a5 5 0 0 1 0.5 -10 a6 6 0 0 1 11 2.5 a4 4 0 0 1 -1.5 7.5 z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/>",
+    "SCAMPER Method": "<circle cx=\"22\" cy=\"22\" r=\"5.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><g stroke=\"currentColor\" stroke-width=\"2.4\" stroke-linecap=\"round\"><path d=\"M22 9 V13.5 M22 30.5 V35 M9 22 H13.5 M30.5 22 H35 M12.8 12.8 L16 16 M28 28 L31.2 31.2 M31.2 12.8 L28 16 M16 28 L12.8 31.2\"/></g>",
+    "Six Thinking Hats": "<path d=\"M14 26 q8 -5 16 0\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/><path d=\"M17 26 q-6 1 -8 3 q13 4 26 0 q-2 -2 -8 -3\" fill=\"currentColor\" fill-opacity=\".22\"/><path d=\"M17 26 c-1 -8 11 -8 10 0\" fill=\"currentColor\" fill-opacity=\".5\"/>",
+    "Decision Tree Mapping": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"22\" cy=\"12\" r=\"2.6\"/><circle cx=\"14\" cy=\"32\" r=\"2.6\"/><circle cx=\"30\" cy=\"32\" r=\"2.6\"/><path d=\"M22 14.5 L22 20 M22 20 L14 29.4 M22 20 L30 29.4\"/></g>",
+    "Solution Matrix": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\"><rect x=\"11\" y=\"11\" width=\"22\" height=\"22\" rx=\"2\"/><path d=\"M11 22 H33 M22 11 V33\"/></g><path d=\"M24.5 14.5 L26.5 16.5 L30.5 12.5\" stroke=\"currentColor\" stroke-width=\"2\" fill=\"none\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/>",
+    "Trait Transfer": "<path d=\"M12 16 l1.6 3.4 3.6 .4 -2.7 2.5 .7 3.6 -3.2 -1.8 -3.2 1.8 .7 -3.6 -2.7 -2.5 3.6 -.4 z\" fill=\"currentColor\"/><rect x=\"25\" y=\"23\" width=\"9\" height=\"9\" rx=\"2\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M17 22 L25 27\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-dasharray=\"1.5 2.5\"/>",
+    "Lotus Blossom": "<g fill=\"currentColor\"><circle cx=\"22\" cy=\"22\" r=\"3.4\"/></g><g fill=\"currentColor\" fill-opacity=\".4\"><circle cx=\"22\" cy=\"13\" r=\"2.8\"/><circle cx=\"22\" cy=\"31\" r=\"2.8\"/><circle cx=\"13\" cy=\"22\" r=\"2.8\"/><circle cx=\"31\" cy=\"22\" r=\"2.8\"/><circle cx=\"15.5\" cy=\"15.5\" r=\"2.5\"/><circle cx=\"28.5\" cy=\"15.5\" r=\"2.5\"/><circle cx=\"15.5\" cy=\"28.5\" r=\"2.5\"/><circle cx=\"28.5\" cy=\"28.5\" r=\"2.5\"/></g>",
+    "Worst Possible Idea": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M17 11 v10 h-5 l10 12 10 -12 h-5 v-10 z\"/></g>",
+    "Disney Method": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><circle cx=\"14\" cy=\"22\" r=\"4.5\"/><circle cx=\"22\" cy=\"22\" r=\"4.5\"/><circle cx=\"30\" cy=\"22\" r=\"4.5\"/></g>",
+    "Starbursting": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 8 V15 M22 29 V36 M8 22 H15 M29 22 H36 M12 12 L17 17 M27 27 L32 32 M32 12 L27 17 M12 32 L17 27\"/></g><path d=\"M19.5 19 a3.2 3.2 0 1 1 3 4 v1.2\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\"/>",
+    "Mind Mapping": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"22\" cy=\"22\" r=\"4\"/><circle cx=\"11\" cy=\"13\" r=\"2.2\"/><circle cx=\"33\" cy=\"13\" r=\"2.2\"/><circle cx=\"10\" cy=\"28\" r=\"2.2\"/><circle cx=\"32\" cy=\"31\" r=\"2.2\"/><path d=\"M19 19.5 L12.5 14.5 M25 19.5 L31.5 14.5 M19 24.5 L11.5 27 M25.5 24 L30.5 29.5\"/></g>",
+    "Crazy 8s": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.7\"><rect x=\"9\" y=\"12\" width=\"8\" height=\"9\" rx=\"1.5\"/><rect x=\"18\" y=\"12\" width=\"8\" height=\"9\" rx=\"1.5\"/><rect x=\"27\" y=\"12\" width=\"8\" height=\"9\" rx=\"1.5\"/><rect x=\"9\" y=\"23\" width=\"8\" height=\"9\" rx=\"1.5\"/><rect x=\"18\" y=\"23\" width=\"8\" height=\"9\" rx=\"1.5\"/><rect x=\"27\" y=\"23\" width=\"8\" height=\"9\" rx=\"1.5\"/></g>",
+    "Time Travel Talk Show": "<rect x=\"18\" y=\"9\" width=\"8\" height=\"15\" rx=\"4\" fill=\"currentColor\" fill-opacity=\".25\"/><rect x=\"18\" y=\"9\" width=\"8\" height=\"15\" rx=\"4\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M14 21 a8 8 0 0 0 16 0 M22 29 V34 M17 34 H27\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/>",
+    "Alien Anthropologist": "<ellipse cx=\"22\" cy=\"30\" rx=\"13\" ry=\"4.5\" fill=\"currentColor\" fill-opacity=\".25\"/><path d=\"M22 11 c7 0 10 6 10 11 c0 5 -5 7 -10 7 c-5 0 -10 -2 -10 -7 c0 -5 3 -11 10 -11 z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><g fill=\"currentColor\"><ellipse cx=\"18\" cy=\"22\" rx=\"1.6\" ry=\"2.4\"/><ellipse cx=\"26\" cy=\"22\" rx=\"1.6\" ry=\"2.4\"/></g>",
+    "Dream Fusion Laboratory": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M18 9 H26 M19.5 9 V18 L13 30 a2 2 0 0 0 2 3 H29 a2 2 0 0 0 2 -3 L24.5 18 V9\"/></g><path d=\"M16.5 26 H27.5\" stroke=\"currentColor\" stroke-width=\"2\"/><circle cx=\"20\" cy=\"29\" r=\"1.4\" fill=\"currentColor\"/><circle cx=\"25\" cy=\"28\" r=\"1.1\" fill=\"currentColor\"/>",
+    "Emotion Orchestra": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M17 30 V15 L31 12 V27\"/><circle cx=\"14\" cy=\"30\" r=\"3\"/><circle cx=\"28\" cy=\"27\" r=\"3\"/></g>",
+    "Parallel Universe Cafe": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><circle cx=\"18\" cy=\"22\" r=\"9\"/><circle cx=\"26\" cy=\"22\" r=\"9\" stroke-dasharray=\"2.5 2.5\"/></g>",
+    "Persona Journey": "<path d=\"M14 33 q-2 -8 6 -9 q8 -1 6 -8\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-dasharray=\"0.1 4\"/><circle cx=\"14\" cy=\"33\" r=\"2.4\" fill=\"currentColor\"/><path d=\"M26 16 l3 -5 3 5 z\" fill=\"currentColor\"/>",
+    "Devil's Advocate Courtroom": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 10 V32 M14 32 H30\"/><path d=\"M11 16 H33 M11 16 L8 23 H14 Z M33 16 L30 23 H36 Z\"/></g>",
+    "Chaos Engineering": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 9 L25 18 L34 18 L27 24 L30 33 L22 27 L14 33 L17 24 L10 18 L19 18 Z\"/></g>",
+    "Guerrilla Gardening Ideas": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 33 V21\"/><path d=\"M22 22 c-7 0 -9 -6 -9 -9 c6 0 9 3 9 9 z\"/><path d=\"M22 24 c6 0 8 -4 8 -7 c-5 0 -8 2 -8 7 z\"/></g>",
+    "Pirate Code Brainstorm": "<path d=\"M22 10 c-7 0 -11 5 -11 11 c0 4 2 6 4 7 v4 h3 v-2 h2 v2 h4 v-2 h2 v2 h3 v-4 c2 -1 4 -3 4 -7 c0 -6 -4 -11 -11 -11 z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/><g fill=\"currentColor\"><circle cx=\"17.5\" cy=\"21\" r=\"2.2\"/><circle cx=\"26.5\" cy=\"21\" r=\"2.2\"/></g>",
+    "Zombie Apocalypse Planning": "<circle cx=\"22\" cy=\"22\" r=\"4\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><path d=\"M22 10 a12 12 0 0 1 6 3.5 M32 16 a12 12 0 0 1 0 12 M28 33.5 a12 12 0 0 1 -12 0 M12 28 a12 12 0 0 1 0 -12 M16 10.5 a12 12 0 0 1 6 -0.5\" stroke-dasharray=\"0.1 5.5\"/></g><g fill=\"currentColor\"><circle cx=\"22\" cy=\"11\" r=\"2\"/><circle cx=\"11\" cy=\"22\" r=\"2\"/><circle cx=\"33\" cy=\"22\" r=\"2\"/></g>",
+    "Drunk History Retelling": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M13 12 H31 L25 23 V31 H19 V23 Z\"/><path d=\"M19 31 H25\" /></g><circle cx=\"29\" cy=\"14\" r=\"1.4\" fill=\"currentColor\"/>",
+    "Anti-Solution": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M14 18 a8 8 0 1 1 -1 8\"/><path d=\"M14 12 L14 18.5 L20 18\"/></g>",
+    "Elemental Forces": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 8 L30 22 H14 Z\"/><path d=\"M14 30 L22 36 L30 30\"/><path d=\"M14 26 H30\"/></g>",
+    "Nature's Solutions": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M16 32 C12 24 12 20 16 12 M28 32 C32 24 32 20 28 12\"/><path d=\"M16 16 L28 14 M16 22 L28 20 M16 28 L28 26\"/></g>",
+    "Ecosystem Thinking": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"22\" cy=\"13\" r=\"2.4\"/><circle cx=\"12\" cy=\"27\" r=\"2.4\"/><circle cx=\"32\" cy=\"27\" r=\"2.4\"/><circle cx=\"22\" cy=\"24\" r=\"2.4\"/><path d=\"M22 15.4 V21.6 M14 26 L20 24.5 M30 26 L24 24.5 M13.6 25.2 L30.4 25.2\"/></g>",
+    "Evolutionary Pressure": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M11 31 H17 M19 31 a6 6 0 0 1 6 -6 M25 25 a5 5 0 0 1 5 -5 M30 20 H33\"/><circle cx=\"11\" cy=\"31\" r=\"2\" fill=\"currentColor\"/><circle cx=\"33\" cy=\"20\" r=\"2.6\" fill=\"currentColor\"/></g>",
+    "Predator & Prey": "<path d=\"M22 9 L33 14 V23 C33 30 28 34 22 36 C16 34 11 30 11 23 V14 Z\" fill=\"currentColor\" fill-opacity=\".18\"/><path d=\"M22 9 L33 14 V23 C33 30 28 34 22 36 C16 34 11 30 11 23 V14 Z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/>",
+    "Metamorphosis Stages": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 12 V32\"/><path d=\"M22 16 C14 12 10 18 14 22 C10 26 14 32 22 28 C30 32 34 26 30 22 C34 18 30 12 22 16\"/></g>",
+    "Swarm Logic": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 10 L29 14 V22 L22 26 L15 22 V14 Z\"/><path d=\"M15 24 L18 33 M29 24 L26 33 M22 28 V35\" stroke-opacity=\".6\"/></g>",
+    "Observer Effect": "<path d=\"M9 22 q13 -10 26 0 q-13 10 -26 0 z\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/><circle cx=\"22\" cy=\"22\" r=\"4.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><circle cx=\"22\" cy=\"22\" r=\"1.8\" fill=\"currentColor\"/>",
+    "Entanglement Thinking": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><circle cx=\"15\" cy=\"22\" r=\"6\"/><circle cx=\"29\" cy=\"22\" r=\"6\"/></g><path d=\"M15 22 h14\" stroke=\"currentColor\" stroke-width=\"2\" stroke-dasharray=\"1.5 2.5\"/><g fill=\"currentColor\"><circle cx=\"15\" cy=\"22\" r=\"1.8\"/><circle cx=\"29\" cy=\"22\" r=\"1.8\"/></g>",
+    "Superposition Collapse": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M11 12 C20 16 24 16 33 12 M11 18 C20 22 24 22 33 18 M11 24 C20 28 24 28 33 24\"/><path d=\"M22 26 V34\"/></g><circle cx=\"22\" cy=\"34\" r=\"2\" fill=\"currentColor\"/>",
+    "Relativity Frame Shift": "<rect x=\"11\" y=\"11\" width=\"22\" height=\"22\" rx=\"2\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-opacity=\".4\"/><rect x=\"15\" y=\"15\" width=\"18\" height=\"18\" rx=\"2\" transform=\"rotate(-14 22 22)\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/>",
+    "Field Lines": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M12 13 V31 M16 13 C24 18 24 26 16 31 M22 13 C32 18 32 26 22 31\"/></g><circle cx=\"11\" cy=\"22\" r=\"2\" fill=\"currentColor\"/>",
+    "Quantum Tunneling": "<rect x=\"20\" y=\"9\" width=\"5\" height=\"26\" rx=\"1.5\" fill=\"currentColor\" fill-opacity=\".3\"/><path d=\"M10 22 H34\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\"/><path d=\"M28 17 L34 22 L28 27\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/>",
+    "Indigenous Wisdom": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M26 11 C18 16 14 24 13 33 M26 11 C28 18 26 25 20 29\"/><path d=\"M26 11 C24 13 22 14 19 15 M24 16 C22 18 20 19 17 20 M22 21 C20 23 18 24 15 25\"/></g>",
+    "Fusion Cuisine": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M10 19 a12 7 0 0 0 24 0 Z\"/><path d=\"M22 19 V32 M16 32 H28\"/></g>",
+    "Ritual Innovation": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M12 33 V17 a10 10 0 0 1 20 0 V33\"/><path d=\"M12 33 H32 M22 33 V21\"/></g>",
+    "Mythic Frameworks": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M14 12 h13 a3 3 0 0 1 3 3 v17 l-3 -2 -3 2 -3 -2 -3 2 V15 a3 3 0 0 0 -3 -3 z\"/><path d=\"M14 12 a3 3 0 0 0 -3 3 h6\"/><path d=\"M20 18 H26 M20 23 H26\"/></g>",
+    "Proverb Mining": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 14 C17 10 11 11 11 11 V30 s6 -1 11 3 c5 -4 11 -3 11 -3 V11 s-6 -1 -11 3 z\"/><path d=\"M22 14 V31\"/></g>",
+    "Ancestor Council": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><circle cx=\"22\" cy=\"14\" r=\"3.5\"/><circle cx=\"13\" cy=\"19\" r=\"3\"/><circle cx=\"31\" cy=\"19\" r=\"3\"/></g><g fill=\"currentColor\" fill-opacity=\".25\"><path d=\"M16 31 c0 -5 12 -5 12 0 z\"/><path d=\"M8 31 c0 -4 9 -4.5 9 0 z\"/><path d=\"M27 31 c0 -4.5 9 -4 9 0 z\"/></g>",
+    "Trickster's Gambit": "<rect x=\"11\" y=\"12\" width=\"13\" height=\"18\" rx=\"2\" transform=\"rotate(-10 17.5 21)\" fill=\"currentColor\" fill-opacity=\".2\" stroke=\"currentColor\" stroke-width=\"2\"/><rect x=\"20\" y=\"14\" width=\"13\" height=\"18\" rx=\"2\" transform=\"rotate(10 26.5 23)\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M26.5 19 l1.4 3 1.4 -3 -1.4 -1 z\" fill=\"currentColor\"/>",
+    "Villain's Monologue": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M12 20 C16 18 19 18 22 21 C25 18 28 18 32 20 C30 24 26 24 22 21 C18 24 14 24 12 20 Z\"/></g><circle cx=\"22\" cy=\"14\" r=\"2.4\" fill=\"currentColor\"/>",
+    "Explain It to a Golden Retriever": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M14 18 C12 12 17 13 18 17 M30 18 C32 12 27 13 26 17\"/><path d=\"M15 19 C13 28 18 33 22 33 C26 33 31 28 29 19 C26 16 18 16 15 19 Z\"/></g><g fill=\"currentColor\"><circle cx=\"19\" cy=\"24\" r=\"1.4\"/><circle cx=\"25\" cy=\"24\" r=\"1.4\"/><circle cx=\"22\" cy=\"28\" r=\"1.6\"/></g>",
+    "Infomercial at 3AM": "<rect x=\"9\" y=\"14\" width=\"26\" height=\"18\" rx=\"2.5\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M18 9 L22 14 L26 9\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/><path d=\"M22 19 l1 2.6 2.8 .2 -2.1 1.9 .7 2.7 -2.4 -1.5 -2.4 1.5 .7 -2.7 -2.1 -1.9 2.8 -.2 z\" fill=\"currentColor\"/>",
+    "Drunk Uncle at Thanksgiving": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M11 16 L20 16 L27 11 V29 L20 24 L11 24 Z\"/><path d=\"M30 16 q3 4 0 8 M33 13 q5 7 0 14\"/></g>",
+    "Cursed Genie": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M10 30 h18 a2 2 0 0 0 2 -2 c0 -5 -6 -5 -8 -8 c5 -1 8 -3 8 -3 c-4 -2 -12 -2 -16 1 c-4 3 -5 9 -4 12 z\"/><path d=\"M30 17 L33 14 M31 21 L35 20\" stroke-opacity=\".6\"/></g>",
+    "Three Rounds of Stupid": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M13 30 V20 M9 24 L13 20 L17 24 M22 30 V15 M18 19 L22 15 L26 19 M31 30 V11 M27 15 L31 11 L35 15\"/></g>",
+    "Kill the Crown Jewel": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M11 28 L13 15 L19 22 L22 12 L25 22 L31 15 L33 28 Z\"/><path d=\"M11 28 H33\"/></g><path d=\"M14 12 L30 32\" stroke=\"currentColor\" stroke-width=\"2.4\" stroke-linecap=\"round\"/>",
+    "1000x Budget": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><ellipse cx=\"22\" cy=\"14\" rx=\"9\" ry=\"3.5\"/><path d=\"M13 14 V22 a9 3.5 0 0 0 18 0 V14\"/><path d=\"M13 22 V30 a9 3.5 0 0 0 18 0 V22\"/></g>",
+    "Ship in 60 Minutes": "<circle cx=\"22\" cy=\"24\" r=\"11\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 24 V17 M22 24 L27 27\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/><path d=\"M18 8 H26 M22 8 V13\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/>",
+    "The $0 Mandate": "<circle cx=\"22\" cy=\"22\" r=\"11\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 14 V30 M18 18 a4 3 0 0 1 8 0 a4 3 0 0 1 -8 4 a4 3 0 0 0 8 0\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\"/><path d=\"M14 30 L30 14\" stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\"/>",
+    "One Feature Only": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"22\" cy=\"22\" r=\"4.5\"/><path d=\"M22 9 V13 M22 31 V35 M9 22 H13 M31 22 H35\" stroke-opacity=\".35\"/></g><circle cx=\"22\" cy=\"22\" r=\"2\" fill=\"currentColor\"/>",
+    "Crank the Dial to 11": "<path d=\"M11 28 A12 12 0 0 1 33 28\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"/><path d=\"M22 28 L31 17\" stroke=\"currentColor\" stroke-width=\"2.2\" stroke-linecap=\"round\"/><circle cx=\"22\" cy=\"28\" r=\"2.6\" fill=\"currentColor\"/>",
+    "Constraint Roulette": "<circle cx=\"22\" cy=\"22\" r=\"12\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><circle cx=\"22\" cy=\"22\" r=\"12\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-dasharray=\"3 3.7\" stroke-opacity=\".5\"/><circle cx=\"22\" cy=\"22\" r=\"3\" fill=\"currentColor\"/><path d=\"M22 7 L25 12 H19 Z\" fill=\"currentColor\"/>",
+    "Time Horizon Ladder": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 30 H35\"/><path d=\"M14 30 V24 M22 30 V18 M30 30 V12\"/></g><g fill=\"currentColor\"><circle cx=\"14\" cy=\"24\" r=\"2\"/><circle cx=\"22\" cy=\"18\" r=\"2\"/><circle cx=\"30\" cy=\"12\" r=\"2\"/></g>",
+    "Post-Scarcity Test": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M15 22 a4.5 4.5 0 1 1 4.5 4.5 C16 26.5 14 18 11 18 a3.5 3.5 0 0 0 0 7 c4 0 5 -8 11 -8 a4.5 4.5 0 0 1 0 9 c-3 0 -4 -4.5 -7 -4.5\"/></g>",
+    "Utopia vs Dystopia Split-Screen": "<rect x=\"11\" y=\"11\" width=\"22\" height=\"22\" rx=\"3\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 11 V33\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 11 H33 a0 0 0 0 1 0 0 V33 H22 Z\" fill=\"currentColor\" fill-opacity=\".8\"/>",
+    "Sci-Fi Artifact From the Future": "<path d=\"M22 9 L33 15 V28 L22 35 L11 28 V15 Z\" fill=\"currentColor\" fill-opacity=\".15\"/><path d=\"M22 9 L33 15 V28 L22 35 L11 28 V15 Z M11 15 L22 21 L33 15 M22 21 V35\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"/>",
+    "Emerging Tech Collision": "<rect x=\"15\" y=\"15\" width=\"14\" height=\"14\" rx=\"2\" fill=\"currentColor\" fill-opacity=\".22\"/><rect x=\"15\" y=\"15\" width=\"14\" height=\"14\" rx=\"2\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"/><g stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"><path d=\"M19 15 V10 M25 15 V10 M19 29 V34 M25 29 V34 M15 19 H10 M15 25 H10 M29 19 H34 M29 25 H34\"/></g>",
+    "What-If-The-World-Changed Card Flip": "<rect x=\"13\" y=\"10\" width=\"18\" height=\"24\" rx=\"2.5\" fill=\"currentColor\" fill-opacity=\".18\" stroke=\"currentColor\" stroke-width=\"2\"/><path d=\"M22 10 V34\" stroke=\"currentColor\" stroke-width=\"1.6\" stroke-dasharray=\"2 2.5\"/><path d=\"M27 16 a4 4 0 1 1 4 4\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\"/>",
+    "Future Anthropologist Dig": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M22 27 a6 6 0 1 1 0.1 0 z\"/><path d=\"M22 23 a2.5 2.5 0 1 0 0.1 0 M19 30 a5 5 0 0 0 6 0\"/></g><path d=\"M12 16 L17 13 M32 16 L27 13\" stroke=\"currentColor\" stroke-width=\"1.6\" stroke-opacity=\".5\"/>",
+    "How Might We": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M11 13 H33 a2 2 0 0 1 2 2 V27 a2 2 0 0 1 -2 2 H24 L19 34 V29 H11 a2 2 0 0 1 -2 -2 V15 a2 2 0 0 1 2 -2 Z\"/></g><path d=\"M19 19 a3.2 3.2 0 1 1 3.4 3.4 v1.6\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\" stroke-linecap=\"round\"/><circle cx=\"22.4\" cy=\"27\" r=\"1.4\" fill=\"currentColor\"/>",
+    "Job to Be Done": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linejoin=\"round\"><rect x=\"9\" y=\"16\" width=\"26\" height=\"16\" rx=\"2.5\"/><path d=\"M17 16 v-3 a2 2 0 0 1 2 -2 h6 a2 2 0 0 1 2 2 v3\"/><path d=\"M9 23 H35\"/></g><circle cx=\"22\" cy=\"23\" r=\"1.8\" fill=\"currentColor\"/>",
+    "Empathy Map": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"1.8\"><rect x=\"11\" y=\"11\" width=\"22\" height=\"22\" rx=\"2\"/><path d=\"M11 22 H33 M22 11 V33\"/></g><path d=\"M22 27 c-2.6 -2.1 -4.2 -3.4 -4.2 -5.2 a2.1 2.1 0 0 1 4.2 -1 a2.1 2.1 0 0 1 4.2 1 c0 1.8 -1.6 3.1 -4.2 5.2 z\" fill=\"currentColor\"/>",
+    "Backcasting": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M30 11 V33\"/></g><path d=\"M30 13 L20 16.5 L30 20 Z\" fill=\"currentColor\"/><path d=\"M28 27 H14\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-dasharray=\"1.5 3\"/><path d=\"M18 23 L14 27 L18 31\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/>",
+    "Scenario Cross": "<g stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\"><path d=\"M22 9 V35 M9 22 H35\"/></g><g fill=\"currentColor\"><circle cx=\"15\" cy=\"15\" r=\"2\"/><circle cx=\"29\" cy=\"15\" r=\"2\"/><circle cx=\"15\" cy=\"29\" r=\"2\"/><circle cx=\"29\" cy=\"29\" r=\"2\"/></g>",
+    "TRIZ Contradiction": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 15 H18 M14.5 11.5 L18 15 L14.5 18.5\"/><path d=\"M35 29 H26 M29.5 25.5 L26 29 L29.5 32.5\"/></g><path d=\"M22 17.5 l1.5 3.4 3.7 .3 -2.8 2.4 .9 3.6 -3.3 -1.9 -3.3 1.9 .9 -3.6 -2.8 -2.4 3.7 -.3 z\" fill=\"currentColor\"/>",
+    "Fishbone Diagram": "<g fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 22 H33\"/><path d=\"M33 22 L36 18.5 M33 22 L36 25.5\"/><path d=\"M14 22 L18 15 M14 22 L18 29 M23 22 L27 15 M23 22 L27 29\"/></g><circle cx=\"9\" cy=\"22\" r=\"1.9\" fill=\"currentColor\"/>",
+    "Build on What Works": "<g fill=\"currentColor\"><rect x=\"11\" y=\"24\" width=\"6\" height=\"9\" rx=\"1\"/><rect x=\"19\" y=\"19\" width=\"6\" height=\"14\" rx=\"1\"/><rect x=\"27\" y=\"13\" width=\"6\" height=\"20\" rx=\"1\"/></g><path d=\"M11 19 L18 13 L24 16 L33 8\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/><path d=\"M28 8 H33 V13\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"/>"
+  }
+}
diff --git a/.claude/skills/bmad-brainstorming/assets/brain-methods.csv b/.claude/skills/bmad-brainstorming/assets/brain-methods.csv
new file mode 100644
index 0000000..32790e0
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/assets/brain-methods.csv
@@ -0,0 +1,109 @@
+category,technique_name,description,detail,provenance,good_for,audience
+collaborative,Yes And Building,"Never negate; each person opens with ""Yes, and..."" and adds to the last idea, stacking a chain of accepted additions",,classic,novel|unstuck|planning,group
+collaborative,Brain Writing Round Robin,"Everyone writes ideas silently, then passes their sheet; you build on whatever lands in front of you, round after round",,classic,novel|feature,group
+collaborative,Random Stimulation,"Pull a random word or image and force a link to the problem: ""how does THIS spark a solution?""",,classic,unstuck|novel,either
+collaborative,Role Playing,"Each person speaks as a different stakeholder, voicing what that role wants, fears, and would demand of the idea",,classic,strategy|personal|feature,either
+collaborative,Ideation Relay Race,"30-second turns, no pausing: add one idea, slap it to the next person, keep the baton moving before anyone overthinks",,playful,unstuck,group
+collaborative,Idea Hot Potato,"One idea gets tossed around the circle; each catcher must mutate it in 10 seconds before passing, no repeats allowed",,playful,unstuck,group
+collaborative,Steal And Upgrade,"Pick a neighbor's idea you envy, claim it out loud, then make it visibly better before handing it back improved",,signature,novel|unstuck,group
+collaborative,Fold The Paper,"Each person adds one line to a hidden drawing or sentence, sees only the previous fragment, then unfold the surreal whole",,playful,unstuck|novel,group
+creative,What If Scenarios,"Detonate one constraint at a time — unlimited budget, opposite is true, problem vanished — and chase what rushes in",,signature,novel|strategy|unstuck,either
+creative,Analogical Thinking,Ask 'this is like what?' and steal the solution pattern from the domain that answers,,signature,feature|novel|diagnosis,either
+creative,First Principles Thinking,"Strip every assumption to bedrock facts, then rebuild the solution from scratch on truth alone",,classic,feature|novel|diagnosis|strategy,either
+creative,Forced Relationships,Grab two unrelated things at random and force a bridge between them until an idea falls out,,signature,novel|unstuck,either
+creative,Time Shifting,"Solve the problem as a 1900s artisan, then a 2150 colonist — harvest the era-bound constraints and tricks",,signature,novel|unstuck,either
+creative,Metaphor Mapping,"Declare the problem IS a chosen metaphor, extend the metaphor fully, map each part back to find insights",,signature,novel|diagnosis,either
+creative,Cross-Pollination,"Ask how a wildly different industry — casinos, ERs, beekeeping — would crack this, then adapt their move",,signature,novel|feature|strategy,either
+creative,Concept Blending,"Fuse two concepts into one new hybrid category and name what the merger becomes, not just combines",,signature,novel,either
+creative,Reverse Brainstorming,Generate problems instead of solutions — 'how could we make this fail?' — then mine each for its inverse,,classic,diagnosis|feature|unstuck,either
+creative,Sensory Exploration,"Interrogate the idea through each sense — its taste, smell, sound, texture — to surface non-analytical angles",,signature,novel|unstuck,either
+deep,Five Whys,"Ask ""why?"" five times in a chain, each answer feeding the next, until you hit the root cause beneath the symptom",,classic,diagnosis,either
+deep,Provocation Technique,"State something deliberately absurd, then mine it: ""how could this be useful?"" Extract the usable principle hiding inside",,classic,unstuck|novel,either
+deep,Assumption Reversal,"List every assumption baked into the problem, flip each to its opposite, then rebuild a solution on the inverted foundation",,classic,novel|diagnosis|strategy,either
+deep,Question Storming,"Generate only questions about the problem, zero answers allowed, until the real problem worth solving comes into focus",,classic,diagnosis|strategy|unstuck,either
+deep,Constraint Mapping,"Map every constraint, sort real from imagined, then attack each: dissolve it, route around it, or turn it into an asset",,signature,feature|strategy|diagnosis,either
+deep,Failure Analysis,"Dissect a relevant failure: what broke, why it broke, what lesson it leaves, and how to apply that wisdom here",,signature,diagnosis|strategy|feature,either
+deep,Emergent Thinking,Stop forcing a solution; watch what patterns the system keeps producing and name what's trying to emerge on its own,,signature,strategy|novel,either
+deep,Causal Loop Mapping,"Diagram the feedback loops linking causes and effects, find the reinforcing and balancing cycles, and target the leverage point",,classic,diagnosis|strategy,either
+deep,Morphological Analysis,"List the problem's independent parameters, generate options for each, then combine across them to surface untried configurations",,classic,feature|novel|planning,either
+deep,Laddering,"Ask 'and what would that give you?' up the chain until you reach the real underlying need, then ideate fresh at that level",,classic,personal|strategy|diagnosis,either
+introspective_delight,Inner Child Conference,"Answer as your 7-year-old self: ask naive 'why why why' questions, chase wonder, ban every boring adult thought",,signature,personal|unstuck,solo
+introspective_delight,Shadow Work Mining,"Name what you're avoiding, resisting, or scared of about this — then dig there for the buried insight",,signature,personal|diagnosis,solo
+introspective_delight,Values Archaeology,Keep asking 'why do I care?' until you hit bedrock: the non-negotiable value secretly steering the choice,,signature,personal|strategy,solo
+introspective_delight,Future Self Interview,Interview your wise 80-year-old self about this problem and write down the advice they give you,,signature,personal,solo
+introspective_delight,Body Wisdom Dialogue,"Scan for the tension, flutter, or gut pull each option triggers; let the body's yes/no drive the ideas",,signature,personal,solo
+introspective_delight,Permission Giving,"Write yourself an explicit permission slip to think the forbidden, impossible thought — then think it out loud",,signature,personal|unstuck,solo
+introspective_delight,Secret Wish Confession,"Whisper the embarrassing thing you secretly want here but won't admit, then build the idea honoring it",,signature,personal,solo
+introspective_delight,Mood Weather Report,"Name the inner weather right now (fog, storm, sun) and let that exact emotional climate generate the ideas",,signature,personal|unstuck,solo
+structured,SCAMPER Method,"Run your idea through seven lenses: Substitute, Combine, Adapt, Modify, Put-to-other-use, Eliminate, Reverse",,classic,feature|novel,either
+structured,Six Thinking Hats,"Examine the problem six ways one at a time: facts, feelings, benefits, risks, new ideas, process",,classic,strategy|diagnosis|planning|personal,either
+structured,Decision Tree Mapping,"Chart every choice point and the paths it forks into, following each branch to its outcome and risk",,signature,planning|strategy|diagnosis,either
+structured,Solution Matrix,"Grid problem variables against solution approaches, score every cell, hunt the best pairings and empty gaps",,signature,feature|planning,either
+structured,Trait Transfer,"Name what makes an unrelated success work, then graft those winning traits onto your own problem",,signature,novel|feature,either
+structured,Lotus Blossom,"Put the theme at the center of a 3x3 grid, fill the 8 cells around it, then promote each of those to the center of its own new 3x3",,classic,feature|planning|novel,either
+structured,Worst Possible Idea,"Deliberately generate the most terrible solutions you can, then flip each into what it teaches you to do right",,classic,unstuck|novel,either
+structured,Disney Method,"Cycle the idea through three rooms: Dreamer (anything goes), Realist (how we'd build it), Critic (what breaks)",,classic,feature|strategy|planning,either
+structured,Starbursting,"Interrogate the idea with only questions — who, what, where, when, why, how — exhaust each before answering any",,classic,feature|planning|diagnosis,either
+structured,Mind Mapping,"Branch the central topic outward, each node spawning children; follow tangents wherever they pull and let the web sprawl",,classic,planning|novel|feature,either
+structured,Crazy 8s,"Eight ideas in eight minutes, one per box, no editing — speed outruns your inner critic",,classic,feature|novel|unstuck,either
+theatrical,Time Travel Talk Show,"Host a talk show interviewing your past, present, and future selves to mine each era for advice on the problem",,playful,novel|personal,either
+theatrical,Alien Anthropologist,"Become a baffled alien studying the problem and narrate aloud what seems strange, arbitrary, or insane about it",,playful,diagnosis|unstuck|strategy,either
+theatrical,Dream Fusion Laboratory,"Voice the impossible fantasy solution first, then reverse-engineer the bridging steps back to reality",,signature,novel|unstuck,either
+theatrical,Emotion Orchestra,"Run a separate ideation round led by each emotion (rage, joy, fear, hope), then harmonize their conflicting ideas",,playful,personal|strategy,either
+theatrical,Parallel Universe Cafe,"Rewrite one fundamental rule of reality (physics, economics, social norms) and solve the problem under those laws",,playful,novel|unstuck,either
+theatrical,Persona Journey,"Embody an archetype and solve the problem in-character, naming what that persona sees that you normally miss",,signature,feature|strategy,either
+theatrical,Devil's Advocate Courtroom,"Stage a trial: prosecute the idea, defend it, then deliver the jury verdict, each role argued fully in character",,signature,strategy|diagnosis,group
+wild,Chaos Engineering,"Deliberately break your idea every way it could fail, then rebuild only the parts that survive the wreckage",,signature,feature|diagnosis|strategy,either
+wild,Guerrilla Gardening Ideas,Plant your solution in the least expected place and let it grow underground until it surprises everyone,,playful,strategy|unstuck,either
+wild,Pirate Code Brainstorm,"Steal the best bits from anywhere, remix without asking permission, grab what works and run",,playful,novel|unstuck,either
+wild,Zombie Apocalypse Planning,"Society just collapsed — strip your idea to only what survives with no power, no rules, no backup",,playful,feature|strategy|unstuck,either
+wild,Drunk History Retelling,"Explain it like you're three drinks in: no filter, no jargon, just the raw stupid-simple truth",,playful,unstuck|diagnosis,either
+wild,Anti-Solution,"Brainstorm how to make the problem spectacularly worse, then invert every sabotage into a fix",,signature,diagnosis|unstuck,either
+wild,Elemental Forces,"Let fire, water, earth, and air each sculpt your idea their own brutal way and see what survives",,playful,novel|unstuck,either
+biomimetic,Nature's Solutions,"Name an organism that already solved your problem, then copy its mechanism into your design",,signature,feature|novel,either
+biomimetic,Ecosystem Thinking,"Map your problem as an ecosystem: who eats whom, who partners, what decays, what fills the gaps",,signature,strategy|diagnosis,either
+biomimetic,Evolutionary Pressure,"Spawn many ugly variants, apply a brutal selection rule, breed the survivors, repeat until it adapts",,signature,feature|novel,either
+biomimetic,Predator & Prey,"Pick a threat to your idea, then design the defense, camouflage, or escape an animal would evolve against it",,signature,strategy|feature,either
+biomimetic,Metamorphosis Stages,"Force your idea through egg, larva, pupa, adult: a radically different form and purpose at each life stage",,signature,novel|strategy,either
+biomimetic,Swarm Logic,Forbid the master plan: solve it with dumb local rules each agent follows so order emerges from the bottom up,,signature,feature|strategy,either
+quantum,Observer Effect,"Ask how the act of watching, measuring, or shipping this idea changes the very thing you're trying to capture",,signature,strategy|diagnosis,either
+quantum,Entanglement Thinking,Pair two distant parts of the problem and insist a change in one instantly flips the other — surface the hidden linkage,,signature,diagnosis|strategy,either
+quantum,Superposition Collapse,"Hold all rival solutions alive at once, then name the one constraint that collapses them to a single winner",,signature,strategy|diagnosis,either
+quantum,Relativity Frame Shift,"Re-run the idea from a wildly different observer's reference frame — the slow user, the rival, future-you — and see what warps",,signature,strategy|novel,either
+quantum,Field Lines,Treat the goal as a charge and map the invisible forces pulling every stakeholder toward or away from it,,signature,strategy,either
+quantum,Quantum Tunneling,"Assume the idea can pass straight through the 'impossible' barrier instead of over it — what's on the other side, reached cheaply",,signature,unstuck|novel,either
+cultural,Indigenous Wisdom,"Ask how an indigenous or traditional knowledge system would approach this — name the culture, channel its ancestral problem-solving",,signature,personal|strategy|novel,either
+cultural,Fusion Cuisine,Pick two unrelated cultures and force-blend their approaches; harvest the hybrid that neither alone would invent,,signature,novel,either
+cultural,Ritual Innovation,"Redesign the idea as a ceremony — define the threshold, the gestures, the transformation participants undergo",,signature,novel|personal,either
+cultural,Mythic Frameworks,"Map the problem onto a myth: name the archetypes, find the parallel tale, let its structure dictate the resolution",,signature,strategy|personal|novel,either
+cultural,Proverb Mining,"Collect proverbs from many cultures on this theme, then build the solution from the one that clashes hardest with your assumptions",,signature,personal|strategy,either
+cultural,Ancestor Council,"Convene three ancestors or elders from different traditions, voice each one's verdict on your idea, reconcile their disagreement",,signature,personal|strategy,either
+cultural,Trickster's Gambit,"Channel the trickster figure — coyote, Anansi, Loki — and solve it by cheating, inverting, or breaking the sacred rule",,playful,unstuck|strategy,either
+absurdist,Villain's Monologue,Pitch your problem as an evil mastermind gloating about their scheme; the diabolical plan reveals the real solution,,playful,diagnosis|strategy|unstuck,either
+absurdist,Explain It to a Golden Retriever,"Re-pitch the idea to an excitable dog who only cares about treats, balls, and naps; keep only what survives",,playful,unstuck|diagnosis|feature,either
+absurdist,Infomercial at 3AM,"Sell your half-baked idea as a desperate late-night infomercial: 'But wait, there's more!' until features fall out",,playful,strategy|novel,either
+absurdist,Drunk Uncle at Thanksgiving,"Have your loudest, least-filtered relative rant about the problem; mine the unhinged hot takes for buried truth",,playful,unstuck|diagnosis,either
+absurdist,Cursed Genie,"Make a wish, then let a malicious genie grant it in the most technically-correct disastrous way; patch each loophole",,playful,diagnosis|feature,either
+absurdist,Three Rounds of Stupid,"Round 1 absurd ideas, Round 2 make each MORE absurd, Round 3 find the smallest serious thing hiding in the silliest",,playful,unstuck|novel,either
+constraint,Kill the Crown Jewel,"Delete the single best, most beloved feature — now redesign the whole thing to win without it",,signature,feature|strategy|unstuck,either
+constraint,1000x Budget,"Pretend money, time, and people are infinite — design the absurd version, then mine it for ideas you can actually steal",,signature,novel|strategy,either
+constraint,Ship in 60 Minutes,"You launch in one hour with what's already on hand — name what you cut, fake, or borrow to make it real",,signature,feature|planning|unstuck,either
+constraint,The $0 Mandate,"Achieve the goal spending literally nothing — no tools, hires, or ads; only people, favors, and what you own",,signature,planning|strategy|feature,either
+constraint,One Feature Only,"You may keep exactly ONE capability and nothing else — pick it, then make that single thing unbelievably good",,signature,feature|strategy,either
+constraint,Crank the Dial to 11,"Pick one dimension and exaggerate it to a ludicrous extreme — fastest, biggest, cheapest, weirdest — and see what breaks open",,signature,novel|unstuck,either
+constraint,Constraint Roulette,"Each round draw a brutal random limit (no screens, half the team, one day) and re-solve under it; survivors become real ideas",,signature,unstuck|feature,either
+speculative_future,Time Horizon Ladder,"Solve the idea for 1 year out, then 10, then 100 — note what survives, breaks, or becomes absurd at each rung",,signature,strategy|planning|novel,either
+speculative_future,Post-Scarcity Test,"Assume the core constraint (money, energy, time, attention) is now infinite and free — what does the idea become",,signature,novel|strategy,either
+speculative_future,Utopia vs Dystopia Split-Screen,Write the same future twice: the brochure where it went perfectly and the headline where it went horribly,,signature,strategy|diagnosis,either
+speculative_future,Sci-Fi Artifact From the Future,"Describe one physical object, ad, or news clip from the world where this idea already won — reverse-engineer it",,signature,novel|feature,either
+speculative_future,Emerging Tech Collision,"Force-marry your idea to a frontier tech (AGI, fusion, neural implants, gene edit) and ask what new thing is born",,signature,novel|feature|strategy,either
+speculative_future,What-If-The-World-Changed Card Flip,"Draw a wild world-shift (no privacy, half population, 200-yr lifespans) and redesign the idea to fit that world",,signature,novel|unstuck,either
+speculative_future,Future Anthropologist Dig,"A scholar in 2200 unearths your idea as a relic — what do they conclude it reveals about us, and what replaced it",,signature,strategy|novel,either
+structured,How Might We,"Reframe the problem as a batch of 'How might we...' opportunity questions first, then ideate against the sharpest one",,classic,feature|novel|strategy|diagnosis,either
+structured,Job to Be Done,"Ask what the user is really hiring this to do, then ideate around that underlying job, not the feature you assumed",,classic,feature|strategy|novel,either
+structured,Empathy Map,"Map what the user says, thinks, does, and feels around the problem, then mine each quadrant for the unmet need",,classic,feature|personal,either
+structured,Backcasting,"Fix the finished future in vivid detail, then work backward step by step to the one move you'd have to make first",,classic,strategy|planning|novel,either
+deep,TRIZ Contradiction,"Name the core contradiction (what only improves by making something else worse), then brainstorm ways to win both instead of trading off",,classic,feature|novel|diagnosis,either
+deep,Fishbone Diagram,"Branch the problem's spine into cause categories (people, process, tools, environment) and mine each bone for contributing causes",,classic,diagnosis,either
+deep,Build on What Works,"Name what's already succeeding and why, then ideate how to amplify and extend it instead of fixing what's broken",,classic,personal|strategy,either
+speculative_future,Scenario Cross,"Pick two high-impact uncertainties, cross them into four futures, and ideate the move that wins in every one",,classic,strategy|planning,either
diff --git a/.claude/skills/bmad-brainstorming/assets/brain-selector.html b/.claude/skills/bmad-brainstorming/assets/brain-selector.html
new file mode 100644
index 0000000..ac649b2
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/assets/brain-selector.html
@@ -0,0 +1,328 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>BMad Method Brainstorming Selection</title>
+<script>
+/* set the theme before first paint so there's no light-mode flash */
+(function(){ try {
+  var t = localStorage.getItem('bmad-theme');
+  if (!t) { t = (window.matchMedia && window.matchMedia('(prefers-color-scheme: dark)').matches) ? 'dark' : 'light'; }
+  document.documentElement.setAttribute('data-theme', t);
+} catch(e){} })();
+</script>
+<style>
+  :root {
+    --bg:#f6f7fb; --surface:#fff; --ink:#1c1e2b; --muted:#6b7080;
+    --accent:#5b4bdc; --accent-ink:#5b4bdc; --warn:#c0561f;
+    --line:#e6e8f0; --control:#eef0f7; --control2:#f1f2f8; --raised:#fff;
+    --cnt:#b9bdce; --foot:#aeb2c4; --shadow:rgba(20,20,50,.06);
+  }
+  :root[data-theme="dark"] {
+    --bg:#0f1117; --surface:#171a23; --ink:#e7e9f2; --muted:#9aa0b4;
+    --accent:#6d5cf0; --accent-ink:#a99bff; --warn:#e08a4a;
+    --line:#2a2f3e; --control:#222634; --control2:#1d212d; --raised:#2c3242;
+    --cnt:#5a6076; --foot:#5a6076; --shadow:rgba(0,0,0,.45);
+  }
+  /* lift the category hue toward white on dark surfaces so deep hues stay legible */
+  :root[data-theme="dark"] section > h2 { color:color-mix(in srgb, var(--c) 62%, #fff); }
+  :root[data-theme="dark"] .tech .ico { color:color-mix(in srgb, var(--c) 68%, #fff); }
+  :root[data-theme="dark"] label.tech:has(input:checked) { border-color:color-mix(in srgb, var(--c) 60%, #fff); }
+  .titlerow { display:flex; align-items:flex-start; justify-content:space-between; gap:12px; }
+  .themebtn { flex:none; width:36px; height:36px; border-radius:9px; background:var(--control); color:var(--ink); font-size:17px; line-height:1; display:inline-flex; align-items:center; justify-content:center; }
+  .themebtn:hover { background:var(--raised); }
+  * { box-sizing:border-box; }
+  body { margin:0; font:16px/1.5 -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif; background:var(--bg); color:var(--ink); }
+  header { position:sticky; top:0; z-index:5; background:var(--surface); padding:20px 0 12px; border-bottom:1px solid var(--line); box-shadow:0 2px 12px var(--shadow); }
+  .hwrap { max-width:1120px; margin:0 auto; padding:0 24px; }  /* align header content with the card column on wide screens */
+  h1 { margin:0 0 4px; font-size:24px; letter-spacing:-.02em; }
+  .sub { margin:0 0 12px; color:var(--muted); font-size:14px; max-width:74ch; }
+  button { font:inherit; border:0; border-radius:8px; cursor:pointer; }
+  .composer { display:flex; flex-direction:column; gap:9px; margin:6px 0 12px; }
+  .grp { display:flex; gap:8px; align-items:center; flex-wrap:wrap; }
+  .glabel { font-size:11px; text-transform:uppercase; letter-spacing:.07em; color:var(--muted); min-width:74px; }
+  .modes { display:inline-flex; background:var(--control); border-radius:9px; padding:3px; gap:2px; }
+  .mode { padding:7px 13px; font-size:14px; font-weight:600; color:var(--muted); background:transparent; }
+  .mode.on { background:var(--raised); color:var(--accent-ink); box-shadow:0 1px 3px var(--shadow); }
+  .modehint { flex:1 1 240px; min-width:0; font-size:13px; color:var(--muted); font-style:italic; }
+  .pill { font-size:13px; color:var(--muted); background:var(--control); padding:6px 12px; border-radius:20px; }
+  .pill b { color:var(--accent-ink); }
+  .step { display:inline-flex; align-items:center; gap:7px; font-size:13px; color:var(--ink); background:var(--control2); padding:4px 6px 4px 12px; border-radius:20px; }
+  .step b { min-width:12px; text-align:center; font-size:14px; color:var(--ink); }
+  .step button { width:24px; height:24px; border-radius:50%; background:var(--raised); color:var(--muted); font-size:17px; line-height:22px; text-align:center; box-shadow:0 1px 2px var(--shadow); }
+  .step button:hover { color:var(--accent-ink); }
+  .total { font-size:12px; color:var(--muted); }
+  .total.warn { color:var(--warn); font-weight:600; }
+  .bar { display:flex; gap:10px 14px; align-items:center; flex-wrap:wrap; }
+  #copy { margin-left:auto; padding:9px 22px; background:var(--accent); color:#fff; font-size:14px; font-weight:700; }
+  #copy:hover { filter:brightness(1.07); }
+  .chips { flex:1 1 320px; min-width:0; display:flex; gap:7px; flex-wrap:wrap; align-items:center; }
+  .chip { font-size:12px; padding:4px 11px; border-radius:16px; border:0; color:#fff; background:var(--cc); font-weight:600; cursor:pointer; }
+  .chip:hover { filter:brightness(1.08); }
+  .banner { max-height:0; overflow:hidden; transition:max-height .25s ease, padding .22s ease, margin .22s ease; background:linear-gradient(90deg,var(--accent),#8275f2); color:#fff; border-radius:10px; font-weight:700; text-align:center; padding:0 14px; }
+  .banner.show { max-height:64px; padding:13px 14px; margin-top:10px; }
+  .banner.fail { background:linear-gradient(90deg,var(--warn),#e0894a); }
+  main { padding:18px 24px 60px; max-width:1120px; margin:0 auto; }
+  section { margin:0 0 26px; }
+  section > h2 { font-size:13px; text-transform:uppercase; letter-spacing:.08em; color:var(--c); margin:0 0 10px; border-bottom:1px solid color-mix(in srgb, var(--c) 24%, var(--line)); padding-bottom:6px; }
+  section > h2 .cnt { color:color-mix(in srgb, var(--c) 45%, var(--cnt)); margin-left:6px; }
+  .grid { display:grid; grid-template-columns:repeat(auto-fill,minmax(360px,1fr)); gap:10px; }
+  label.tech { display:flex; gap:12px; align-items:flex-start; background:color-mix(in srgb, var(--c) 5%, var(--surface)); border:1px solid color-mix(in srgb, var(--c) 18%, var(--line)); border-radius:10px; padding:11px 13px; cursor:pointer; transition:border-color .12s, box-shadow .12s, background .12s; }
+  label.tech:hover { border-color:color-mix(in srgb, var(--c) 45%, var(--surface)); }
+  label.tech input { margin-top:2px; width:17px; height:17px; accent-color:var(--c); flex:none; }
+  label.tech:has(input:checked) { border-color:var(--c); background:color-mix(in srgb, var(--c) 12%, var(--surface)); box-shadow:0 0 0 2px color-mix(in srgb, var(--c) 30%, transparent); }
+  .tech .ic2 { display:flex; gap:5px; flex:none; }
+  .tech .ico { width:40px; height:40px; flex:none; color:var(--c); }
+  .tech .n { font-weight:600; display:block; }
+  .tech .d { color:var(--muted); font-size:13.5px; display:block; margin-top:2px; }
+  .tech .gf { color:var(--accent-ink); font-size:11px; display:block; margin-top:5px; opacity:.85; }
+  .grouphdr { margin:30px 0 12px; font-size:12px; text-transform:uppercase; letter-spacing:.14em; font-weight:700; color:var(--c); opacity:.92; border-bottom:1px solid color-mix(in srgb, var(--c) 22%, var(--line)); padding-bottom:7px; }
+  main > .grouphdr:first-child { margin-top:2px; }
+  :root[data-theme="dark"] .grouphdr { color:color-mix(in srgb, var(--c) 62%, #fff); }
+  .goals { display:flex; gap:7px; flex-wrap:wrap; }
+  .goal { font-size:12px; padding:5px 12px; border-radius:16px; background:var(--control); color:var(--muted); font-weight:600; }
+  .goal:hover { color:var(--ink); }
+  .goal.on { background:var(--accent); color:#fff; }
+  label.tech.invent { border-style:dashed; background:transparent; }
+  label.tech.invent:hover { border-color:var(--c); }
+  label.tech.invent .n { color:var(--c); }
+  label.tech.hidden { display:none; }
+  footer { text-align:center; color:var(--foot); font-size:12px; padding:24px; }
+</style>
+</head>
+<body>
+<header>
+  <div class="hwrap">
+  <div class="titlerow">
+    <h1>BMad Method Brainstorming Selection</h1>
+    <button id="theme" class="themebtn" type="button" aria-label="Toggle dark mode" title="Toggle dark mode"></button>
+  </div>
+  <p class="sub">Compose your session, hit <strong>Copy prompt</strong>, and paste it back into the chat to begin. 108 techniques across 13 categories.</p>
+
+  <div class="composer">
+    <div class="grp">
+      <span class="glabel">Facilitation</span>
+      <div class="modes" id="modes">
+        <button type="button" class="mode on" data-mode="Facilitator">Facilitator</button>
+        <button type="button" class="mode" data-mode="Creative Partner">Creative Partner</button>
+        <button type="button" class="mode" data-mode="Ideate for me">Ideate for me</button>
+      </div>
+      <span class="modehint" id="modehint"></span>
+    </div>
+    <div class="grp">
+      <span class="glabel">Techniques</span>
+      <span class="pill">Picked <b id="pickN">0</b></span>
+      <span class="step">Random <button type="button" data-step="rand" data-d="-1">&minus;</button><b id="randN">0</b><button type="button" data-step="rand" data-d="1">+</button></span>
+      <span class="step">Invent <button type="button" data-step="inv" data-d="-1">&minus;</button><b id="invN">0</b><button type="button" data-step="inv" data-d="1">+</button></span>
+      <span class="step">AI picks <button type="button" data-step="ai" data-d="-1">&minus;</button><b id="aiN">0</b><button type="button" data-step="ai" data-d="1">+</button></span>
+      <span class="total" id="total">Total 0 &middot; 3&ndash;4 is the sweet spot</span>
+      <button id="copy" type="button">Copy prompt</button>
+    </div>
+  </div>
+
+  <div class="bar"><span class="glabel">Great for</span><div class="goals" id="goals"><button type="button" class="goal" data-goal="feature">Build a feature</button><button type="button" class="goal" data-goal="novel">Novel concept</button><button type="button" class="goal" data-goal="strategy">Strategy</button><button type="button" class="goal" data-goal="planning">Planning</button><button type="button" class="goal" data-goal="diagnosis">Diagnose</button><button type="button" class="goal" data-goal="personal">Personal / life</button><button type="button" class="goal" data-goal="unstuck">Get unstuck</button></div></div>
+  <div class="bar">
+    <span class="glabel">Jump to</span>
+    <div class="chips" id="chips"><button type="button" class="chip" data-cat="Proven &amp; Professional" style="--cc:#3d4f73">Proven &amp; Professional</button><button type="button" class="chip" data-cat="Structured" style="--cc:#3b6ea5">Structured</button><button type="button" class="chip" data-cat="Deep" style="--cc:#4658c9">Deep</button><button type="button" class="chip" data-cat="Creative" style="--cc:#6d5cf0">Creative</button><button type="button" class="chip" data-cat="Biomimetic" style="--cc:#1f9d6b">Biomimetic</button><button type="button" class="chip" data-cat="Cultural" style="--cc:#c75b39">Cultural</button><button type="button" class="chip" data-cat="Speculative Future" style="--cc:#0fb5c9">Speculative Future</button><button type="button" class="chip" data-cat="Quantum" style="--cc:#2b86d9">Quantum</button><button type="button" class="chip" data-cat="Wild" style="--cc:#e2562f">Wild</button><button type="button" class="chip" data-cat="Absurdist" style="--cc:#e0529c">Absurdist</button><button type="button" class="chip" data-cat="Theatrical" style="--cc:#cf4d6f">Theatrical</button><button type="button" class="chip" data-cat="Constraint" style="--cc:#d9882b">Constraint</button><button type="button" class="chip" data-cat="Introspective Delight" style="--cc:#b15ad6">Introspective Delight</button><button type="button" class="chip" data-cat="Collaborative" style="--cc:#15a3a3">Collaborative</button></div>
+  </div>
+
+  <div class="banner" id="banner">&#10003; Copied! Now paste it into the chat to start your session.</div>
+  </div>
+</header>
+<main>
+<section data-cat="Proven &amp; Professional" style="--c:#3d4f73"><h2>Proven &amp; Professional<span class="cnt">29</span></h2><div class="grid"><label class="tech" style="--c:#15a3a3"><input type="checkbox" data-name="Yes And Building" data-cat="Collaborative" data-desc="Never negate; each person opens with &quot;Yes, and...&quot; and adds to the last idea, stacking a chain of accepted additions" data-good="novel|unstuck|planning" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="8" y="27" width="12" height="8" rx="1.5" fill-opacity=".8"/><rect x="14" y="19" width="12" height="8" rx="1.5" fill-opacity=".5"/><rect x="20" y="11" width="12" height="8" rx="1.5"/></g></svg></span><span><span class="n">Yes And Building</span><span class="d">Never negate; each person opens with &quot;Yes, and...&quot; and adds to the last idea, stacking a chain of accepted additions</span><span class="gf">Great for: Novel concept · Get unstuck · Planning</span></span></label><label class="tech" style="--c:#15a3a3"><input type="checkbox" data-name="Brain Writing Round Robin" data-cat="Collaborative" data-desc="Everyone writes ideas silently, then passes their sheet; you build on whatever lands in front of you, round after round" data-good="novel|feature" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M31 16 A10 10 0 1 0 32.5 22"/><path d="M31 10 L31.5 16.3 L25 16.5"/></g></svg></span><span><span class="n">Brain Writing Round Robin</span><span class="d">Everyone writes ideas silently, then passes their sheet; you build on whatever lands in front of you, round after round</span><span class="gf">Great for: Novel concept · Build a feature</span></span></label><label class="tech" style="--c:#15a3a3"><input type="checkbox" data-name="Random Stimulation" data-cat="Collaborative" data-desc="Pull a random word or image and force a link to the problem: &quot;how does THIS spark a solution?&quot;" data-good="unstuck|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="11" width="22" height="22" rx="4" fill="none" stroke="currentColor" stroke-width="2"/><g fill="currentColor"><circle cx="17" cy="17" r="1.8"/><circle cx="27" cy="17" r="1.8"/><circle cx="22" cy="22" r="1.8"/><circle cx="17" cy="27" r="1.8"/><circle cx="27" cy="27" r="1.8"/></g></svg></span><span><span class="n">Random Stimulation</span><span class="d">Pull a random word or image and force a link to the problem: &quot;how does THIS spark a solution?&quot;</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech" style="--c:#15a3a3"><input type="checkbox" data-name="Role Playing" data-cat="Collaborative" data-desc="Each person speaks as a different stakeholder, voicing what that role wants, fears, and would demand of the idea" data-good="strategy|personal|feature" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="9" width="22" height="26" rx="3" fill="none" stroke="currentColor" stroke-width="2"/><circle cx="22" cy="19" r="4" fill="currentColor"/><path d="M15.5 30 c2 -4.5 11 -4.5 13 0" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Role Playing</span><span class="d">Each person speaks as a different stakeholder, voicing what that role wants, fears, and would demand of the idea</span><span class="gf">Great for: Strategy · Personal / life · Build a feature</span></span></label><label class="tech" style="--c:#6d5cf0"><input type="checkbox" data-name="First Principles Thinking" data-cat="Creative" data-desc="Strip every assumption to bedrock facts, then rebuild the solution from scratch on truth alone" data-good="feature|novel|diagnosis|strategy" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="10" y="28" width="8" height="6" rx="1"/><rect x="18.5" y="28" width="8" height="6" rx="1"/><rect x="27" y="28" width="7" height="6" rx="1"/></g><path d="M22 25 L22 11 M16 17 L22 11 L28 17" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">First Principles Thinking</span><span class="d">Strip every assumption to bedrock facts, then rebuild the solution from scratch on truth alone</span><span class="gf">Great for: Build a feature · Novel concept · Diagnose · Strategy</span></span></label><label class="tech" style="--c:#6d5cf0"><input type="checkbox" data-name="Reverse Brainstorming" data-cat="Creative" data-desc="Generate problems instead of solutions — &#x27;how could we make this fail?&#x27; — then mine each for its inverse" data-good="diagnosis|feature|unstuck" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M13 18 H28 a4 4 0 0 1 0 8 H16"/><path d="M19 15 L13 18 L19 21 M22 23 L16 26 L22 29"/></g></svg></span><span><span class="n">Reverse Brainstorming</span><span class="d">Generate problems instead of solutions — &#x27;how could we make this fail?&#x27; — then mine each for its inverse</span><span class="gf">Great for: Diagnose · Build a feature · Get unstuck</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Five Whys" data-cat="Deep" data-desc="Ask &quot;why?&quot; five times in a chain, each answer feeding the next, until you hit the root cause beneath the symptom" data-good="diagnosis" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="14" cy="13" r="2.4"/><circle cx="22" cy="22" r="2.4"/><circle cx="30" cy="31" r="2.4"/><path d="M15.6 14.8 L20.4 20.2 M23.6 23.8 L28.4 29.2"/></g></svg></span><span><span class="n">Five Whys</span><span class="d">Ask &quot;why?&quot; five times in a chain, each answer feeding the next, until you hit the root cause beneath the symptom</span><span class="gf">Great for: Diagnose</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Provocation Technique" data-cat="Deep" data-desc="State something deliberately absurd, then mine it: &quot;how could this be useful?&quot; Extract the usable principle hiding inside" data-good="unstuck|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M24 9 L13 24 H21 L19 35 L31 19 H23 Z"/></g></svg></span><span><span class="n">Provocation Technique</span><span class="d">State something deliberately absurd, then mine it: &quot;how could this be useful?&quot; Extract the usable principle hiding inside</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Assumption Reversal" data-cat="Deep" data-desc="List every assumption baked into the problem, flip each to its opposite, then rebuild a solution on the inverted foundation" data-good="novel|diagnosis|strategy" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 14 V30"/><path d="M11.5 25 L16 30 L20.5 25"/><path d="M28 30 V14"/><path d="M23.5 19 L28 14 L32.5 19"/></g></svg></span><span><span class="n">Assumption Reversal</span><span class="d">List every assumption baked into the problem, flip each to its opposite, then rebuild a solution on the inverted foundation</span><span class="gf">Great for: Novel concept · Diagnose · Strategy</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Question Storming" data-cat="Deep" data-desc="Generate only questions about the problem, zero answers allowed, until the real problem worth solving comes into focus" data-good="diagnosis|strategy|unstuck" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M14 16 a3.2 3.2 0 1 1 3.2 3.2 v2"/><path d="M26 13 a3.6 3.6 0 1 1 3.6 3.6 v2.4"/></g><circle cx="17.2" cy="27" r="1.5" fill="currentColor"/><circle cx="29.6" cy="25.6" r="1.6" fill="currentColor"/></svg></span><span><span class="n">Question Storming</span><span class="d">Generate only questions about the problem, zero answers allowed, until the real problem worth solving comes into focus</span><span class="gf">Great for: Diagnose · Strategy · Get unstuck</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Causal Loop Mapping" data-cat="Deep" data-desc="Diagram the feedback loops linking causes and effects, find the reinforcing and balancing cycles, and target the leverage point" data-good="diagnosis|strategy" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 16 a9 9 0 1 1 -2 12"/><path d="M16 10.5 L16.5 16.5 L10.5 17"/><path d="M30 28.5 L29.5 22.5 L35 22"/></g></svg></span><span><span class="n">Causal Loop Mapping</span><span class="d">Diagram the feedback loops linking causes and effects, find the reinforcing and balancing cycles, and target the leverage point</span><span class="gf">Great for: Diagnose · Strategy</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Morphological Analysis" data-cat="Deep" data-desc="List the problem&#x27;s independent parameters, generate options for each, then combine across them to surface untried configurations" data-good="feature|novel|planning" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.8"><rect x="11" y="11" width="22" height="22" rx="2"/><path d="M11 18.3 H33 M11 25.6 H33 M18.3 11 V33 M25.6 11 V33"/></g><rect x="18.5" y="18.5" width="7" height="7" fill="currentColor" fill-opacity=".4"/></svg></span><span><span class="n">Morphological Analysis</span><span class="d">List the problem&#x27;s independent parameters, generate options for each, then combine across them to surface untried configurations</span><span class="gf">Great for: Build a feature · Novel concept · Planning</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Laddering" data-cat="Deep" data-desc="Ask &#x27;and what would that give you?&#x27; up the chain until you reach the real underlying need, then ideate fresh at that level" data-good="personal|strategy|diagnosis" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 9 V35 M28 9 V35 M16 15 H28 M16 22 H28 M16 29 H28"/></g></svg></span><span><span class="n">Laddering</span><span class="d">Ask &#x27;and what would that give you?&#x27; up the chain until you reach the real underlying need, then ideate fresh at that level</span><span class="gf">Great for: Personal / life · Strategy · Diagnose</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="SCAMPER Method" data-cat="Structured" data-desc="Run your idea through seven lenses: Substitute, Combine, Adapt, Modify, Put-to-other-use, Eliminate, Reverse" data-good="feature|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="5.5" fill="none" stroke="currentColor" stroke-width="2"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><path d="M22 9 V13.5 M22 30.5 V35 M9 22 H13.5 M30.5 22 H35 M12.8 12.8 L16 16 M28 28 L31.2 31.2 M31.2 12.8 L28 16 M16 28 L12.8 31.2"/></g></svg></span><span><span class="n">SCAMPER Method</span><span class="d">Run your idea through seven lenses: Substitute, Combine, Adapt, Modify, Put-to-other-use, Eliminate, Reverse</span><span class="gf">Great for: Build a feature · Novel concept</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Six Thinking Hats" data-cat="Structured" data-desc="Examine the problem six ways one at a time: facts, feelings, benefits, risks, new ideas, process" data-good="strategy|diagnosis|planning|personal" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M14 26 q8 -5 16 0" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/><path d="M17 26 q-6 1 -8 3 q13 4 26 0 q-2 -2 -8 -3" fill="currentColor" fill-opacity=".22"/><path d="M17 26 c-1 -8 11 -8 10 0" fill="currentColor" fill-opacity=".5"/></svg></span><span><span class="n">Six Thinking Hats</span><span class="d">Examine the problem six ways one at a time: facts, feelings, benefits, risks, new ideas, process</span><span class="gf">Great for: Strategy · Diagnose · Planning · Personal / life</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Lotus Blossom" data-cat="Structured" data-desc="Put the theme at the center of a 3x3 grid, fill the 8 cells around it, then promote each of those to the center of its own new 3x3" data-good="feature|planning|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><circle cx="22" cy="22" r="3.4"/></g><g fill="currentColor" fill-opacity=".4"><circle cx="22" cy="13" r="2.8"/><circle cx="22" cy="31" r="2.8"/><circle cx="13" cy="22" r="2.8"/><circle cx="31" cy="22" r="2.8"/><circle cx="15.5" cy="15.5" r="2.5"/><circle cx="28.5" cy="15.5" r="2.5"/><circle cx="15.5" cy="28.5" r="2.5"/><circle cx="28.5" cy="28.5" r="2.5"/></g></svg></span><span><span class="n">Lotus Blossom</span><span class="d">Put the theme at the center of a 3x3 grid, fill the 8 cells around it, then promote each of those to the center of its own new 3x3</span><span class="gf">Great for: Build a feature · Planning · Novel concept</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Worst Possible Idea" data-cat="Structured" data-desc="Deliberately generate the most terrible solutions you can, then flip each into what it teaches you to do right" data-good="unstuck|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M17 11 v10 h-5 l10 12 10 -12 h-5 v-10 z"/></g></svg></span><span><span class="n">Worst Possible Idea</span><span class="d">Deliberately generate the most terrible solutions you can, then flip each into what it teaches you to do right</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Disney Method" data-cat="Structured" data-desc="Cycle the idea through three rooms: Dreamer (anything goes), Realist (how we&#x27;d build it), Critic (what breaks)" data-good="feature|strategy|planning" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><circle cx="14" cy="22" r="4.5"/><circle cx="22" cy="22" r="4.5"/><circle cx="30" cy="22" r="4.5"/></g></svg></span><span><span class="n">Disney Method</span><span class="d">Cycle the idea through three rooms: Dreamer (anything goes), Realist (how we&#x27;d build it), Critic (what breaks)</span><span class="gf">Great for: Build a feature · Strategy · Planning</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Starbursting" data-cat="Structured" data-desc="Interrogate the idea with only questions — who, what, where, when, why, how — exhaust each before answering any" data-good="feature|planning|diagnosis" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 8 V15 M22 29 V36 M8 22 H15 M29 22 H36 M12 12 L17 17 M27 27 L32 32 M32 12 L27 17 M12 32 L17 27"/></g><path d="M19.5 19 a3.2 3.2 0 1 1 3 4 v1.2" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/></svg></span><span><span class="n">Starbursting</span><span class="d">Interrogate the idea with only questions — who, what, where, when, why, how — exhaust each before answering any</span><span class="gf">Great for: Build a feature · Planning · Diagnose</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Mind Mapping" data-cat="Structured" data-desc="Branch the central topic outward, each node spawning children; follow tangents wherever they pull and let the web sprawl" data-good="planning|novel|feature" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="22" cy="22" r="4"/><circle cx="11" cy="13" r="2.2"/><circle cx="33" cy="13" r="2.2"/><circle cx="10" cy="28" r="2.2"/><circle cx="32" cy="31" r="2.2"/><path d="M19 19.5 L12.5 14.5 M25 19.5 L31.5 14.5 M19 24.5 L11.5 27 M25.5 24 L30.5 29.5"/></g></svg></span><span><span class="n">Mind Mapping</span><span class="d">Branch the central topic outward, each node spawning children; follow tangents wherever they pull and let the web sprawl</span><span class="gf">Great for: Planning · Novel concept · Build a feature</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Crazy 8s" data-cat="Structured" data-desc="Eight ideas in eight minutes, one per box, no editing — speed outruns your inner critic" data-good="feature|novel|unstuck" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.7"><rect x="9" y="12" width="8" height="9" rx="1.5"/><rect x="18" y="12" width="8" height="9" rx="1.5"/><rect x="27" y="12" width="8" height="9" rx="1.5"/><rect x="9" y="23" width="8" height="9" rx="1.5"/><rect x="18" y="23" width="8" height="9" rx="1.5"/><rect x="27" y="23" width="8" height="9" rx="1.5"/></g></svg></span><span><span class="n">Crazy 8s</span><span class="d">Eight ideas in eight minutes, one per box, no editing — speed outruns your inner critic</span><span class="gf">Great for: Build a feature · Novel concept · Get unstuck</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="How Might We" data-cat="Structured" data-desc="Reframe the problem as a batch of &#x27;How might we...&#x27; opportunity questions first, then ideate against the sharpest one" data-good="feature|novel|strategy|diagnosis" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M11 13 H33 a2 2 0 0 1 2 2 V27 a2 2 0 0 1 -2 2 H24 L19 34 V29 H11 a2 2 0 0 1 -2 -2 V15 a2 2 0 0 1 2 -2 Z"/></g><path d="M19 19 a3.2 3.2 0 1 1 3.4 3.4 v1.6" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/><circle cx="22.4" cy="27" r="1.4" fill="currentColor"/></svg></span><span><span class="n">How Might We</span><span class="d">Reframe the problem as a batch of &#x27;How might we...&#x27; opportunity questions first, then ideate against the sharpest one</span><span class="gf">Great for: Build a feature · Novel concept · Strategy · Diagnose</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Job to Be Done" data-cat="Structured" data-desc="Ask what the user is really hiring this to do, then ideate around that underlying job, not the feature you assumed" data-good="feature|strategy|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"><rect x="9" y="16" width="26" height="16" rx="2.5"/><path d="M17 16 v-3 a2 2 0 0 1 2 -2 h6 a2 2 0 0 1 2 2 v3"/><path d="M9 23 H35"/></g><circle cx="22" cy="23" r="1.8" fill="currentColor"/></svg></span><span><span class="n">Job to Be Done</span><span class="d">Ask what the user is really hiring this to do, then ideate around that underlying job, not the feature you assumed</span><span class="gf">Great for: Build a feature · Strategy · Novel concept</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Empathy Map" data-cat="Structured" data-desc="Map what the user says, thinks, does, and feels around the problem, then mine each quadrant for the unmet need" data-good="feature|personal" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.8"><rect x="11" y="11" width="22" height="22" rx="2"/><path d="M11 22 H33 M22 11 V33"/></g><path d="M22 27 c-2.6 -2.1 -4.2 -3.4 -4.2 -5.2 a2.1 2.1 0 0 1 4.2 -1 a2.1 2.1 0 0 1 4.2 1 c0 1.8 -1.6 3.1 -4.2 5.2 z" fill="currentColor"/></svg></span><span><span class="n">Empathy Map</span><span class="d">Map what the user says, thinks, does, and feels around the problem, then mine each quadrant for the unmet need</span><span class="gf">Great for: Build a feature · Personal / life</span></span></label><label class="tech" style="--c:#3b6ea5"><input type="checkbox" data-name="Backcasting" data-cat="Structured" data-desc="Fix the finished future in vivid detail, then work backward step by step to the one move you&#x27;d have to make first" data-good="strategy|planning|novel" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M30 11 V33"/></g><path d="M30 13 L20 16.5 L30 20 Z" fill="currentColor"/><path d="M28 27 H14" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-dasharray="1.5 3"/><path d="M18 23 L14 27 L18 31" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Backcasting</span><span class="d">Fix the finished future in vivid detail, then work backward step by step to the one move you&#x27;d have to make first</span><span class="gf">Great for: Strategy · Planning · Novel concept</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="TRIZ Contradiction" data-cat="Deep" data-desc="Name the core contradiction (what only improves by making something else worse), then brainstorm ways to win both instead of trading off" data-good="feature|novel|diagnosis" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M9 15 H18 M14.5 11.5 L18 15 L14.5 18.5"/><path d="M35 29 H26 M29.5 25.5 L26 29 L29.5 32.5"/></g><path d="M22 17.5 l1.5 3.4 3.7 .3 -2.8 2.4 .9 3.6 -3.3 -1.9 -3.3 1.9 .9 -3.6 -2.8 -2.4 3.7 -.3 z" fill="currentColor"/></svg></span><span><span class="n">TRIZ Contradiction</span><span class="d">Name the core contradiction (what only improves by making something else worse), then brainstorm ways to win both instead of trading off</span><span class="gf">Great for: Build a feature · Novel concept · Diagnose</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Fishbone Diagram" data-cat="Deep" data-desc="Branch the problem&#x27;s spine into cause categories (people, process, tools, environment) and mine each bone for contributing causes" data-good="diagnosis" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M9 22 H33"/><path d="M33 22 L36 18.5 M33 22 L36 25.5"/><path d="M14 22 L18 15 M14 22 L18 29 M23 22 L27 15 M23 22 L27 29"/></g><circle cx="9" cy="22" r="1.9" fill="currentColor"/></svg></span><span><span class="n">Fishbone Diagram</span><span class="d">Branch the problem&#x27;s spine into cause categories (people, process, tools, environment) and mine each bone for contributing causes</span><span class="gf">Great for: Diagnose</span></span></label><label class="tech" style="--c:#4658c9"><input type="checkbox" data-name="Build on What Works" data-cat="Deep" data-desc="Name what&#x27;s already succeeding and why, then ideate how to amplify and extend it instead of fixing what&#x27;s broken" data-good="personal|strategy" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="24" width="6" height="9" rx="1"/><rect x="19" y="19" width="6" height="14" rx="1"/><rect x="27" y="13" width="6" height="20" rx="1"/></g><path d="M11 19 L18 13 L24 16 L33 8" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/><path d="M28 8 H33 V13" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Build on What Works</span><span class="d">Name what&#x27;s already succeeding and why, then ideate how to amplify and extend it instead of fixing what&#x27;s broken</span><span class="gf">Great for: Personal / life · Strategy</span></span></label><label class="tech" style="--c:#0fb5c9"><input type="checkbox" data-name="Scenario Cross" data-cat="Speculative Future" data-desc="Pick two high-impact uncertainties, cross them into four futures, and ideate the move that wins in every one" data-good="strategy|planning" data-prov="classic" data-lead="1"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2" stroke-linecap="round"><path d="M22 9 V35 M9 22 H35"/></g><g fill="currentColor"><circle cx="15" cy="15" r="2"/><circle cx="29" cy="15" r="2"/><circle cx="15" cy="29" r="2"/><circle cx="29" cy="29" r="2"/></g></svg></span><span><span class="n">Scenario Cross</span><span class="d">Pick two high-impact uncertainties, cross them into four futures, and ideate the move that wins in every one</span><span class="gf">Great for: Strategy · Planning</span></span></label></div></section>
+<h2 class="grouphdr" style="--c:#3b6ea5">Structured &amp; Analytical</h2>
+<section data-cat="Structured" style="--c:#3b6ea5"><h2>Structured<span class="cnt">15</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="SCAMPER Method" data-cat="Structured" data-desc="Run your idea through seven lenses: Substitute, Combine, Adapt, Modify, Put-to-other-use, Eliminate, Reverse" data-good="feature|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="5.5" fill="none" stroke="currentColor" stroke-width="2"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><path d="M22 9 V13.5 M22 30.5 V35 M9 22 H13.5 M30.5 22 H35 M12.8 12.8 L16 16 M28 28 L31.2 31.2 M31.2 12.8 L28 16 M16 28 L12.8 31.2"/></g></svg></span><span><span class="n">SCAMPER Method</span><span class="d">Run your idea through seven lenses: Substitute, Combine, Adapt, Modify, Put-to-other-use, Eliminate, Reverse</span><span class="gf">Great for: Build a feature · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Six Thinking Hats" data-cat="Structured" data-desc="Examine the problem six ways one at a time: facts, feelings, benefits, risks, new ideas, process" data-good="strategy|diagnosis|planning|personal" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M14 26 q8 -5 16 0" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/><path d="M17 26 q-6 1 -8 3 q13 4 26 0 q-2 -2 -8 -3" fill="currentColor" fill-opacity=".22"/><path d="M17 26 c-1 -8 11 -8 10 0" fill="currentColor" fill-opacity=".5"/></svg></span><span><span class="n">Six Thinking Hats</span><span class="d">Examine the problem six ways one at a time: facts, feelings, benefits, risks, new ideas, process</span><span class="gf">Great for: Strategy · Diagnose · Planning · Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Decision Tree Mapping" data-cat="Structured" data-desc="Chart every choice point and the paths it forks into, following each branch to its outcome and risk" data-good="planning|strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="22" cy="12" r="2.6"/><circle cx="14" cy="32" r="2.6"/><circle cx="30" cy="32" r="2.6"/><path d="M22 14.5 L22 20 M22 20 L14 29.4 M22 20 L30 29.4"/></g></svg></span><span><span class="n">Decision Tree Mapping</span><span class="d">Chart every choice point and the paths it forks into, following each branch to its outcome and risk</span><span class="gf">Great for: Planning · Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Solution Matrix" data-cat="Structured" data-desc="Grid problem variables against solution approaches, score every cell, hunt the best pairings and empty gaps" data-good="feature|planning" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.8"><rect x="11" y="11" width="22" height="22" rx="2"/><path d="M11 22 H33 M22 11 V33"/></g><path d="M24.5 14.5 L26.5 16.5 L30.5 12.5" stroke="currentColor" stroke-width="2" fill="none" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Solution Matrix</span><span class="d">Grid problem variables against solution approaches, score every cell, hunt the best pairings and empty gaps</span><span class="gf">Great for: Build a feature · Planning</span></span></label><label class="tech"><input type="checkbox" data-name="Trait Transfer" data-cat="Structured" data-desc="Name what makes an unrelated success work, then graft those winning traits onto your own problem" data-good="novel|feature" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M12 16 l1.6 3.4 3.6 .4 -2.7 2.5 .7 3.6 -3.2 -1.8 -3.2 1.8 .7 -3.6 -2.7 -2.5 3.6 -.4 z" fill="currentColor"/><rect x="25" y="23" width="9" height="9" rx="2" fill="none" stroke="currentColor" stroke-width="2"/><path d="M17 22 L25 27" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-dasharray="1.5 2.5"/></svg></span><span><span class="n">Trait Transfer</span><span class="d">Name what makes an unrelated success work, then graft those winning traits onto your own problem</span><span class="gf">Great for: Novel concept · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Lotus Blossom" data-cat="Structured" data-desc="Put the theme at the center of a 3x3 grid, fill the 8 cells around it, then promote each of those to the center of its own new 3x3" data-good="feature|planning|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><circle cx="22" cy="22" r="3.4"/></g><g fill="currentColor" fill-opacity=".4"><circle cx="22" cy="13" r="2.8"/><circle cx="22" cy="31" r="2.8"/><circle cx="13" cy="22" r="2.8"/><circle cx="31" cy="22" r="2.8"/><circle cx="15.5" cy="15.5" r="2.5"/><circle cx="28.5" cy="15.5" r="2.5"/><circle cx="15.5" cy="28.5" r="2.5"/><circle cx="28.5" cy="28.5" r="2.5"/></g></svg></span><span><span class="n">Lotus Blossom</span><span class="d">Put the theme at the center of a 3x3 grid, fill the 8 cells around it, then promote each of those to the center of its own new 3x3</span><span class="gf">Great for: Build a feature · Planning · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Worst Possible Idea" data-cat="Structured" data-desc="Deliberately generate the most terrible solutions you can, then flip each into what it teaches you to do right" data-good="unstuck|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M17 11 v10 h-5 l10 12 10 -12 h-5 v-10 z"/></g></svg></span><span><span class="n">Worst Possible Idea</span><span class="d">Deliberately generate the most terrible solutions you can, then flip each into what it teaches you to do right</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Disney Method" data-cat="Structured" data-desc="Cycle the idea through three rooms: Dreamer (anything goes), Realist (how we&#x27;d build it), Critic (what breaks)" data-good="feature|strategy|planning" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><circle cx="14" cy="22" r="4.5"/><circle cx="22" cy="22" r="4.5"/><circle cx="30" cy="22" r="4.5"/></g></svg></span><span><span class="n">Disney Method</span><span class="d">Cycle the idea through three rooms: Dreamer (anything goes), Realist (how we&#x27;d build it), Critic (what breaks)</span><span class="gf">Great for: Build a feature · Strategy · Planning</span></span></label><label class="tech"><input type="checkbox" data-name="Starbursting" data-cat="Structured" data-desc="Interrogate the idea with only questions — who, what, where, when, why, how — exhaust each before answering any" data-good="feature|planning|diagnosis" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 8 V15 M22 29 V36 M8 22 H15 M29 22 H36 M12 12 L17 17 M27 27 L32 32 M32 12 L27 17 M12 32 L17 27"/></g><path d="M19.5 19 a3.2 3.2 0 1 1 3 4 v1.2" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/></svg></span><span><span class="n">Starbursting</span><span class="d">Interrogate the idea with only questions — who, what, where, when, why, how — exhaust each before answering any</span><span class="gf">Great for: Build a feature · Planning · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Mind Mapping" data-cat="Structured" data-desc="Branch the central topic outward, each node spawning children; follow tangents wherever they pull and let the web sprawl" data-good="planning|novel|feature" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="22" cy="22" r="4"/><circle cx="11" cy="13" r="2.2"/><circle cx="33" cy="13" r="2.2"/><circle cx="10" cy="28" r="2.2"/><circle cx="32" cy="31" r="2.2"/><path d="M19 19.5 L12.5 14.5 M25 19.5 L31.5 14.5 M19 24.5 L11.5 27 M25.5 24 L30.5 29.5"/></g></svg></span><span><span class="n">Mind Mapping</span><span class="d">Branch the central topic outward, each node spawning children; follow tangents wherever they pull and let the web sprawl</span><span class="gf">Great for: Planning · Novel concept · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Crazy 8s" data-cat="Structured" data-desc="Eight ideas in eight minutes, one per box, no editing — speed outruns your inner critic" data-good="feature|novel|unstuck" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.7"><rect x="9" y="12" width="8" height="9" rx="1.5"/><rect x="18" y="12" width="8" height="9" rx="1.5"/><rect x="27" y="12" width="8" height="9" rx="1.5"/><rect x="9" y="23" width="8" height="9" rx="1.5"/><rect x="18" y="23" width="8" height="9" rx="1.5"/><rect x="27" y="23" width="8" height="9" rx="1.5"/></g></svg></span><span><span class="n">Crazy 8s</span><span class="d">Eight ideas in eight minutes, one per box, no editing — speed outruns your inner critic</span><span class="gf">Great for: Build a feature · Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="How Might We" data-cat="Structured" data-desc="Reframe the problem as a batch of &#x27;How might we...&#x27; opportunity questions first, then ideate against the sharpest one" data-good="feature|novel|strategy|diagnosis" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M11 13 H33 a2 2 0 0 1 2 2 V27 a2 2 0 0 1 -2 2 H24 L19 34 V29 H11 a2 2 0 0 1 -2 -2 V15 a2 2 0 0 1 2 -2 Z"/></g><path d="M19 19 a3.2 3.2 0 1 1 3.4 3.4 v1.6" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/><circle cx="22.4" cy="27" r="1.4" fill="currentColor"/></svg></span><span><span class="n">How Might We</span><span class="d">Reframe the problem as a batch of &#x27;How might we...&#x27; opportunity questions first, then ideate against the sharpest one</span><span class="gf">Great for: Build a feature · Novel concept · Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Job to Be Done" data-cat="Structured" data-desc="Ask what the user is really hiring this to do, then ideate around that underlying job, not the feature you assumed" data-good="feature|strategy|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"><rect x="9" y="16" width="26" height="16" rx="2.5"/><path d="M17 16 v-3 a2 2 0 0 1 2 -2 h6 a2 2 0 0 1 2 2 v3"/><path d="M9 23 H35"/></g><circle cx="22" cy="23" r="1.8" fill="currentColor"/></svg></span><span><span class="n">Job to Be Done</span><span class="d">Ask what the user is really hiring this to do, then ideate around that underlying job, not the feature you assumed</span><span class="gf">Great for: Build a feature · Strategy · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Empathy Map" data-cat="Structured" data-desc="Map what the user says, thinks, does, and feels around the problem, then mine each quadrant for the unmet need" data-good="feature|personal" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.8"><rect x="11" y="11" width="22" height="22" rx="2"/><path d="M11 22 H33 M22 11 V33"/></g><path d="M22 27 c-2.6 -2.1 -4.2 -3.4 -4.2 -5.2 a2.1 2.1 0 0 1 4.2 -1 a2.1 2.1 0 0 1 4.2 1 c0 1.8 -1.6 3.1 -4.2 5.2 z" fill="currentColor"/></svg></span><span><span class="n">Empathy Map</span><span class="d">Map what the user says, thinks, does, and feels around the problem, then mine each quadrant for the unmet need</span><span class="gf">Great for: Build a feature · Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Backcasting" data-cat="Structured" data-desc="Fix the finished future in vivid detail, then work backward step by step to the one move you&#x27;d have to make first" data-good="strategy|planning|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M30 11 V33"/></g><path d="M30 13 L20 16.5 L30 20 Z" fill="currentColor"/><path d="M28 27 H14" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-dasharray="1.5 3"/><path d="M18 23 L14 27 L18 31" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Backcasting</span><span class="d">Fix the finished future in vivid detail, then work backward step by step to the one move you&#x27;d have to make first</span><span class="gf">Great for: Strategy · Planning · Novel concept</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Structured"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="11" width="9.5" height="9.5" rx="2"/><rect x="23.5" y="11" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="11" y="23.5" width="9.5" height="9.5" rx="2" fill-opacity="0.25"/><rect x="23.5" y="23.5" width="9.5" height="9.5" rx="2"/></g></svg></span><span><span class="n">✨ Invent a Structured technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Structured</span></span></label></div></section>
+<section data-cat="Deep" style="--c:#4658c9"><h2>Deep<span class="cnt">13</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Five Whys" data-cat="Deep" data-desc="Ask &quot;why?&quot; five times in a chain, each answer feeding the next, until you hit the root cause beneath the symptom" data-good="diagnosis" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="14" cy="13" r="2.4"/><circle cx="22" cy="22" r="2.4"/><circle cx="30" cy="31" r="2.4"/><path d="M15.6 14.8 L20.4 20.2 M23.6 23.8 L28.4 29.2"/></g></svg></span><span><span class="n">Five Whys</span><span class="d">Ask &quot;why?&quot; five times in a chain, each answer feeding the next, until you hit the root cause beneath the symptom</span><span class="gf">Great for: Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Provocation Technique" data-cat="Deep" data-desc="State something deliberately absurd, then mine it: &quot;how could this be useful?&quot; Extract the usable principle hiding inside" data-good="unstuck|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M24 9 L13 24 H21 L19 35 L31 19 H23 Z"/></g></svg></span><span><span class="n">Provocation Technique</span><span class="d">State something deliberately absurd, then mine it: &quot;how could this be useful?&quot; Extract the usable principle hiding inside</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Assumption Reversal" data-cat="Deep" data-desc="List every assumption baked into the problem, flip each to its opposite, then rebuild a solution on the inverted foundation" data-good="novel|diagnosis|strategy" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 14 V30"/><path d="M11.5 25 L16 30 L20.5 25"/><path d="M28 30 V14"/><path d="M23.5 19 L28 14 L32.5 19"/></g></svg></span><span><span class="n">Assumption Reversal</span><span class="d">List every assumption baked into the problem, flip each to its opposite, then rebuild a solution on the inverted foundation</span><span class="gf">Great for: Novel concept · Diagnose · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Question Storming" data-cat="Deep" data-desc="Generate only questions about the problem, zero answers allowed, until the real problem worth solving comes into focus" data-good="diagnosis|strategy|unstuck" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M14 16 a3.2 3.2 0 1 1 3.2 3.2 v2"/><path d="M26 13 a3.6 3.6 0 1 1 3.6 3.6 v2.4"/></g><circle cx="17.2" cy="27" r="1.5" fill="currentColor"/><circle cx="29.6" cy="25.6" r="1.6" fill="currentColor"/></svg></span><span><span class="n">Question Storming</span><span class="d">Generate only questions about the problem, zero answers allowed, until the real problem worth solving comes into focus</span><span class="gf">Great for: Diagnose · Strategy · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Constraint Mapping" data-cat="Deep" data-desc="Map every constraint, sort real from imagined, then attack each: dissolve it, route around it, or turn it into an asset" data-good="feature|strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M11 14 L18 12 L26 14 L33 12 V30 L26 32 L18 30 L11 32 Z" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/><path d="M18 12 V30 M26 14 V32" stroke="currentColor" stroke-width="1.6"/></svg></span><span><span class="n">Constraint Mapping</span><span class="d">Map every constraint, sort real from imagined, then attack each: dissolve it, route around it, or turn it into an asset</span><span class="gf">Great for: Build a feature · Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Failure Analysis" data-cat="Deep" data-desc="Dissect a relevant failure: what broke, why it broke, what lesson it leaves, and how to apply that wisdom here" data-good="diagnosis|strategy|feature" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="20" cy="20" r="8" fill="none" stroke="currentColor" stroke-width="2"/><line x1="26" y1="26" x2="33" y2="33" stroke="currentColor" stroke-width="2.4" stroke-linecap="round"/><path d="M20 16 V21 M20 24 V24" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Failure Analysis</span><span class="d">Dissect a relevant failure: what broke, why it broke, what lesson it leaves, and how to apply that wisdom here</span><span class="gf">Great for: Diagnose · Strategy · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Emergent Thinking" data-cat="Deep" data-desc="Stop forcing a solution; watch what patterns the system keeps producing and name what&#x27;s trying to emerge on its own" data-good="strategy|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><circle cx="11" cy="31" r="1.6"/><circle cx="17" cy="29" r="1.6"/><circle cx="16" cy="23" r="1.6"/><circle cx="22" cy="24" r="1.8"/><circle cx="23" cy="17" r="1.9"/><circle cx="29" cy="18" r="1.7"/><circle cx="28" cy="12" r="2.1"/></g></svg></span><span><span class="n">Emergent Thinking</span><span class="d">Stop forcing a solution; watch what patterns the system keeps producing and name what&#x27;s trying to emerge on its own</span><span class="gf">Great for: Strategy · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Causal Loop Mapping" data-cat="Deep" data-desc="Diagram the feedback loops linking causes and effects, find the reinforcing and balancing cycles, and target the leverage point" data-good="diagnosis|strategy" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 16 a9 9 0 1 1 -2 12"/><path d="M16 10.5 L16.5 16.5 L10.5 17"/><path d="M30 28.5 L29.5 22.5 L35 22"/></g></svg></span><span><span class="n">Causal Loop Mapping</span><span class="d">Diagram the feedback loops linking causes and effects, find the reinforcing and balancing cycles, and target the leverage point</span><span class="gf">Great for: Diagnose · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Morphological Analysis" data-cat="Deep" data-desc="List the problem&#x27;s independent parameters, generate options for each, then combine across them to surface untried configurations" data-good="feature|novel|planning" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="1.8"><rect x="11" y="11" width="22" height="22" rx="2"/><path d="M11 18.3 H33 M11 25.6 H33 M18.3 11 V33 M25.6 11 V33"/></g><rect x="18.5" y="18.5" width="7" height="7" fill="currentColor" fill-opacity=".4"/></svg></span><span><span class="n">Morphological Analysis</span><span class="d">List the problem&#x27;s independent parameters, generate options for each, then combine across them to surface untried configurations</span><span class="gf">Great for: Build a feature · Novel concept · Planning</span></span></label><label class="tech"><input type="checkbox" data-name="Laddering" data-cat="Deep" data-desc="Ask &#x27;and what would that give you?&#x27; up the chain until you reach the real underlying need, then ideate fresh at that level" data-good="personal|strategy|diagnosis" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 9 V35 M28 9 V35 M16 15 H28 M16 22 H28 M16 29 H28"/></g></svg></span><span><span class="n">Laddering</span><span class="d">Ask &#x27;and what would that give you?&#x27; up the chain until you reach the real underlying need, then ideate fresh at that level</span><span class="gf">Great for: Personal / life · Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="TRIZ Contradiction" data-cat="Deep" data-desc="Name the core contradiction (what only improves by making something else worse), then brainstorm ways to win both instead of trading off" data-good="feature|novel|diagnosis" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M9 15 H18 M14.5 11.5 L18 15 L14.5 18.5"/><path d="M35 29 H26 M29.5 25.5 L26 29 L29.5 32.5"/></g><path d="M22 17.5 l1.5 3.4 3.7 .3 -2.8 2.4 .9 3.6 -3.3 -1.9 -3.3 1.9 .9 -3.6 -2.8 -2.4 3.7 -.3 z" fill="currentColor"/></svg></span><span><span class="n">TRIZ Contradiction</span><span class="d">Name the core contradiction (what only improves by making something else worse), then brainstorm ways to win both instead of trading off</span><span class="gf">Great for: Build a feature · Novel concept · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Fishbone Diagram" data-cat="Deep" data-desc="Branch the problem&#x27;s spine into cause categories (people, process, tools, environment) and mine each bone for contributing causes" data-good="diagnosis" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M9 22 H33"/><path d="M33 22 L36 18.5 M33 22 L36 25.5"/><path d="M14 22 L18 15 M14 22 L18 29 M23 22 L27 15 M23 22 L27 29"/></g><circle cx="9" cy="22" r="1.9" fill="currentColor"/></svg></span><span><span class="n">Fishbone Diagram</span><span class="d">Branch the problem&#x27;s spine into cause categories (people, process, tools, environment) and mine each bone for contributing causes</span><span class="gf">Great for: Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Build on What Works" data-cat="Deep" data-desc="Name what&#x27;s already succeeding and why, then ideate how to amplify and extend it instead of fixing what&#x27;s broken" data-good="personal|strategy" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="11" y="24" width="6" height="9" rx="1"/><rect x="19" y="19" width="6" height="14" rx="1"/><rect x="27" y="13" width="6" height="20" rx="1"/></g><path d="M11 19 L18 13 L24 16 L33 8" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/><path d="M28 8 H33 V13" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Build on What Works</span><span class="d">Name what&#x27;s already succeeding and why, then ideate how to amplify and extend it instead of fixing what&#x27;s broken</span><span class="gf">Great for: Personal / life · Strategy</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Deep"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor"><circle cx="22" cy="22" r="13" stroke-width="1.5" stroke-opacity="0.4"/><circle cx="22" cy="22" r="9" stroke-width="1.7" stroke-opacity="0.7"/><circle cx="22" cy="22" r="5" stroke-width="1.9"/></g><circle cx="22" cy="22" r="2.4" fill="currentColor"/></svg></span><span><span class="n">✨ Invent a Deep technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Deep</span></span></label></div></section>
+<h2 class="grouphdr" style="--c:#6d5cf0">Creative &amp; Generative</h2>
+<section data-cat="Creative" style="--c:#6d5cf0"><h2>Creative<span class="cnt">10</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="What If Scenarios" data-cat="Creative" data-desc="Detonate one constraint at a time — unlimited budget, opposite is true, problem vanished — and chase what rushes in" data-good="novel|strategy|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 17 a4 4 0 1 1 4 4 v3"/></g><circle cx="22" cy="30" r="1.6" fill="currentColor"/></svg></span><span><span class="n">What If Scenarios</span><span class="d">Detonate one constraint at a time — unlimited budget, opposite is true, problem vanished — and chase what rushes in</span><span class="gf">Great for: Novel concept · Strategy · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Analogical Thinking" data-cat="Creative" data-desc="Ask &#x27;this is like what?&#x27; and steal the solution pattern from the domain that answers" data-good="feature|novel|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="15" cy="22" r="6" fill="none" stroke="currentColor" stroke-width="2"/><rect x="25" y="16" width="12" height="12" rx="2" fill="none" stroke="currentColor" stroke-width="2"/><path d="M19 20 q2 2 0 4 M23 20 q-2 2 0 4" stroke="currentColor" stroke-width="1.6" fill="none"/></svg></span><span><span class="n">Analogical Thinking</span><span class="d">Ask &#x27;this is like what?&#x27; and steal the solution pattern from the domain that answers</span><span class="gf">Great for: Build a feature · Novel concept · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="First Principles Thinking" data-cat="Creative" data-desc="Strip every assumption to bedrock facts, then rebuild the solution from scratch on truth alone" data-good="feature|novel|diagnosis|strategy" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="10" y="28" width="8" height="6" rx="1"/><rect x="18.5" y="28" width="8" height="6" rx="1"/><rect x="27" y="28" width="7" height="6" rx="1"/></g><path d="M22 25 L22 11 M16 17 L22 11 L28 17" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">First Principles Thinking</span><span class="d">Strip every assumption to bedrock facts, then rebuild the solution from scratch on truth alone</span><span class="gf">Great for: Build a feature · Novel concept · Diagnose · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Forced Relationships" data-cat="Creative" data-desc="Grab two unrelated things at random and force a bridge between them until an idea falls out" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="12" cy="22" r="3.4" fill="currentColor"/><circle cx="32" cy="22" r="3.4" fill="currentColor"/><path d="M15 22 q7 -9 14 0" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-dasharray="1.5 3"/></svg></span><span><span class="n">Forced Relationships</span><span class="d">Grab two unrelated things at random and force a bridge between them until an idea falls out</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Time Shifting" data-cat="Creative" data-desc="Solve the problem as a 1900s artisan, then a 2150 colonist — harvest the era-bound constraints and tricks" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="12" fill="none" stroke="currentColor" stroke-width="2"/><path d="M22 15 V22 L27 25" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Time Shifting</span><span class="d">Solve the problem as a 1900s artisan, then a 2150 colonist — harvest the era-bound constraints and tricks</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Metaphor Mapping" data-cat="Creative" data-desc="Declare the problem IS a chosen metaphor, extend the metaphor fully, map each part back to find insights" data-good="novel|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="10" y="14" width="14" height="14" rx="2" fill="none" stroke="currentColor" stroke-width="2"/><circle cx="28" cy="25" r="7" fill="currentColor" fill-opacity=".22"/><circle cx="28" cy="25" r="7" fill="none" stroke="currentColor" stroke-width="2"/></svg></span><span><span class="n">Metaphor Mapping</span><span class="d">Declare the problem IS a chosen metaphor, extend the metaphor fully, map each part back to find insights</span><span class="gf">Great for: Novel concept · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Cross-Pollination" data-cat="Creative" data-desc="Ask how a wildly different industry — casinos, ERs, beekeeping — would crack this, then adapt their move" data-good="novel|feature|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M13 14 H27 a4 4 0 0 1 0 8 H17 a4 4 0 0 0 0 8 H31"/><path d="M28 11 L31.5 14 L28 17 M16 27 L12.5 30 L16 33"/></g></svg></span><span><span class="n">Cross-Pollination</span><span class="d">Ask how a wildly different industry — casinos, ERs, beekeeping — would crack this, then adapt their move</span><span class="gf">Great for: Novel concept · Build a feature · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Concept Blending" data-cat="Creative" data-desc="Fuse two concepts into one new hybrid category and name what the merger becomes, not just combines" data-good="novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="18" cy="22" r="8" fill="currentColor" fill-opacity=".25"/><circle cx="26" cy="22" r="8" fill="currentColor" fill-opacity=".25"/><g fill="none" stroke="currentColor" stroke-width="2"><circle cx="18" cy="22" r="8"/><circle cx="26" cy="22" r="8"/></g></svg></span><span><span class="n">Concept Blending</span><span class="d">Fuse two concepts into one new hybrid category and name what the merger becomes, not just combines</span><span class="gf">Great for: Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Reverse Brainstorming" data-cat="Creative" data-desc="Generate problems instead of solutions — &#x27;how could we make this fail?&#x27; — then mine each for its inverse" data-good="diagnosis|feature|unstuck" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M13 18 H28 a4 4 0 0 1 0 8 H16"/><path d="M19 15 L13 18 L19 21 M22 23 L16 26 L22 29"/></g></svg></span><span><span class="n">Reverse Brainstorming</span><span class="d">Generate problems instead of solutions — &#x27;how could we make this fail?&#x27; — then mine each for its inverse</span><span class="gf">Great for: Diagnose · Build a feature · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Sensory Exploration" data-cat="Creative" data-desc="Interrogate the idea through each sense — its taste, smell, sound, texture — to surface non-analytical angles" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M10 22 q12 -10 24 0 q-12 10 -24 0 z" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/><circle cx="22" cy="22" r="4" fill="currentColor"/></svg></span><span><span class="n">Sensory Exploration</span><span class="d">Interrogate the idea through each sense — its taste, smell, sound, texture — to surface non-analytical angles</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Creative"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.4" stroke-linecap="round"><line x1="22" y1="6.5" x2="22" y2="12.5"/><line x1="22" y1="31.5" x2="22" y2="37.5"/><line x1="6.5" y1="22" x2="12.5" y2="22"/><line x1="31.5" y1="22" x2="37.5" y2="22"/><line x1="11.3" y1="11.3" x2="15.5" y2="15.5"/><line x1="28.5" y1="28.5" x2="32.7" y2="32.7"/><line x1="32.7" y1="11.3" x2="28.5" y2="15.5"/><line x1="15.5" y1="28.5" x2="11.3" y2="32.7"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="3.6" fill="currentColor"/></svg></span><span><span class="n">✨ Invent a Creative technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Creative</span></span></label></div></section>
+<section data-cat="Biomimetic" style="--c:#1f9d6b"><h2>Biomimetic<span class="cnt">6</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Nature&#x27;s Solutions" data-cat="Biomimetic" data-desc="Name an organism that already solved your problem, then copy its mechanism into your design" data-good="feature|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M16 32 C12 24 12 20 16 12 M28 32 C32 24 32 20 28 12"/><path d="M16 16 L28 14 M16 22 L28 20 M16 28 L28 26"/></g></svg></span><span><span class="n">Nature&#x27;s Solutions</span><span class="d">Name an organism that already solved your problem, then copy its mechanism into your design</span><span class="gf">Great for: Build a feature · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Ecosystem Thinking" data-cat="Biomimetic" data-desc="Map your problem as an ecosystem: who eats whom, who partners, what decays, what fills the gaps" data-good="strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="22" cy="13" r="2.4"/><circle cx="12" cy="27" r="2.4"/><circle cx="32" cy="27" r="2.4"/><circle cx="22" cy="24" r="2.4"/><path d="M22 15.4 V21.6 M14 26 L20 24.5 M30 26 L24 24.5 M13.6 25.2 L30.4 25.2"/></g></svg></span><span><span class="n">Ecosystem Thinking</span><span class="d">Map your problem as an ecosystem: who eats whom, who partners, what decays, what fills the gaps</span><span class="gf">Great for: Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Evolutionary Pressure" data-cat="Biomimetic" data-desc="Spawn many ugly variants, apply a brutal selection rule, breed the survivors, repeat until it adapts" data-good="feature|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M11 31 H17 M19 31 a6 6 0 0 1 6 -6 M25 25 a5 5 0 0 1 5 -5 M30 20 H33"/><circle cx="11" cy="31" r="2" fill="currentColor"/><circle cx="33" cy="20" r="2.6" fill="currentColor"/></g></svg></span><span><span class="n">Evolutionary Pressure</span><span class="d">Spawn many ugly variants, apply a brutal selection rule, breed the survivors, repeat until it adapts</span><span class="gf">Great for: Build a feature · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Predator &amp; Prey" data-cat="Biomimetic" data-desc="Pick a threat to your idea, then design the defense, camouflage, or escape an animal would evolve against it" data-good="strategy|feature" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 9 L33 14 V23 C33 30 28 34 22 36 C16 34 11 30 11 23 V14 Z" fill="currentColor" fill-opacity=".18"/><path d="M22 9 L33 14 V23 C33 30 28 34 22 36 C16 34 11 30 11 23 V14 Z" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/></svg></span><span><span class="n">Predator &amp; Prey</span><span class="d">Pick a threat to your idea, then design the defense, camouflage, or escape an animal would evolve against it</span><span class="gf">Great for: Strategy · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Metamorphosis Stages" data-cat="Biomimetic" data-desc="Force your idea through egg, larva, pupa, adult: a radically different form and purpose at each life stage" data-good="novel|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 12 V32"/><path d="M22 16 C14 12 10 18 14 22 C10 26 14 32 22 28 C30 32 34 26 30 22 C34 18 30 12 22 16"/></g></svg></span><span><span class="n">Metamorphosis Stages</span><span class="d">Force your idea through egg, larva, pupa, adult: a radically different form and purpose at each life stage</span><span class="gf">Great for: Novel concept · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Swarm Logic" data-cat="Biomimetic" data-desc="Forbid the master plan: solve it with dumb local rules each agent follows so order emerges from the bottom up" data-good="feature|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 10 L29 14 V22 L22 26 L15 22 V14 Z"/><path d="M15 24 L18 33 M29 24 L26 33 M22 28 V35" stroke-opacity=".6"/></g></svg></span><span><span class="n">Swarm Logic</span><span class="d">Forbid the master plan: solve it with dumb local rules each agent follows so order emerges from the bottom up</span><span class="gf">Great for: Build a feature · Strategy</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Biomimetic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 7.5 C 31.5 12.5, 31.5 29, 22 36.5 C 12.5 29, 12.5 12.5, 22 7.5 Z" fill="currentColor" fill-opacity="0.22"/><path d="M22 9 V 35.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><g stroke="currentColor" stroke-width="1.5" stroke-linecap="round"><path d="M22 16 l5.6 -2.6"/><path d="M22 16 l-5.6 -2.6"/><path d="M22 22 l6.6 -2.6"/><path d="M22 22 l-6.6 -2.6"/><path d="M22 28 l5.6 -2.6"/><path d="M22 28 l-5.6 -2.6"/></g></svg></span><span><span class="n">✨ Invent a Biomimetic technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Biomimetic</span></span></label></div></section>
+<section data-cat="Cultural" style="--c:#c75b39"><h2>Cultural<span class="cnt">7</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Indigenous Wisdom" data-cat="Cultural" data-desc="Ask how an indigenous or traditional knowledge system would approach this — name the culture, channel its ancestral problem-solving" data-good="personal|strategy|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M26 11 C18 16 14 24 13 33 M26 11 C28 18 26 25 20 29"/><path d="M26 11 C24 13 22 14 19 15 M24 16 C22 18 20 19 17 20 M22 21 C20 23 18 24 15 25"/></g></svg></span><span><span class="n">Indigenous Wisdom</span><span class="d">Ask how an indigenous or traditional knowledge system would approach this — name the culture, channel its ancestral problem-solving</span><span class="gf">Great for: Personal / life · Strategy · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Fusion Cuisine" data-cat="Cultural" data-desc="Pick two unrelated cultures and force-blend their approaches; harvest the hybrid that neither alone would invent" data-good="novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M10 19 a12 7 0 0 0 24 0 Z"/><path d="M22 19 V32 M16 32 H28"/></g></svg></span><span><span class="n">Fusion Cuisine</span><span class="d">Pick two unrelated cultures and force-blend their approaches; harvest the hybrid that neither alone would invent</span><span class="gf">Great for: Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Ritual Innovation" data-cat="Cultural" data-desc="Redesign the idea as a ceremony — define the threshold, the gestures, the transformation participants undergo" data-good="novel|personal" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 33 V17 a10 10 0 0 1 20 0 V33"/><path d="M12 33 H32 M22 33 V21"/></g></svg></span><span><span class="n">Ritual Innovation</span><span class="d">Redesign the idea as a ceremony — define the threshold, the gestures, the transformation participants undergo</span><span class="gf">Great for: Novel concept · Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Mythic Frameworks" data-cat="Cultural" data-desc="Map the problem onto a myth: name the archetypes, find the parallel tale, let its structure dictate the resolution" data-good="strategy|personal|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M14 12 h13 a3 3 0 0 1 3 3 v17 l-3 -2 -3 2 -3 -2 -3 2 V15 a3 3 0 0 0 -3 -3 z"/><path d="M14 12 a3 3 0 0 0 -3 3 h6"/><path d="M20 18 H26 M20 23 H26"/></g></svg></span><span><span class="n">Mythic Frameworks</span><span class="d">Map the problem onto a myth: name the archetypes, find the parallel tale, let its structure dictate the resolution</span><span class="gf">Great for: Strategy · Personal / life · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Proverb Mining" data-cat="Cultural" data-desc="Collect proverbs from many cultures on this theme, then build the solution from the one that clashes hardest with your assumptions" data-good="personal|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 14 C17 10 11 11 11 11 V30 s6 -1 11 3 c5 -4 11 -3 11 -3 V11 s-6 -1 -11 3 z"/><path d="M22 14 V31"/></g></svg></span><span><span class="n">Proverb Mining</span><span class="d">Collect proverbs from many cultures on this theme, then build the solution from the one that clashes hardest with your assumptions</span><span class="gf">Great for: Personal / life · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Ancestor Council" data-cat="Cultural" data-desc="Convene three ancestors or elders from different traditions, voice each one&#x27;s verdict on your idea, reconcile their disagreement" data-good="personal|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><circle cx="22" cy="14" r="3.5"/><circle cx="13" cy="19" r="3"/><circle cx="31" cy="19" r="3"/></g><g fill="currentColor" fill-opacity=".25"><path d="M16 31 c0 -5 12 -5 12 0 z"/><path d="M8 31 c0 -4 9 -4.5 9 0 z"/><path d="M27 31 c0 -4.5 9 -4 9 0 z"/></g></svg></span><span><span class="n">Ancestor Council</span><span class="d">Convene three ancestors or elders from different traditions, voice each one&#x27;s verdict on your idea, reconcile their disagreement</span><span class="gf">Great for: Personal / life · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Trickster&#x27;s Gambit" data-cat="Cultural" data-desc="Channel the trickster figure — coyote, Anansi, Loki — and solve it by cheating, inverting, or breaking the sacred rule" data-good="unstuck|strategy" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="12" width="13" height="18" rx="2" transform="rotate(-10 17.5 21)" fill="currentColor" fill-opacity=".2" stroke="currentColor" stroke-width="2"/><rect x="20" y="14" width="13" height="18" rx="2" transform="rotate(10 26.5 23)" fill="none" stroke="currentColor" stroke-width="2"/><path d="M26.5 19 l1.4 3 1.4 -3 -1.4 -1 z" fill="currentColor"/></svg></span><span><span class="n">Trickster&#x27;s Gambit</span><span class="d">Channel the trickster figure — coyote, Anansi, Loki — and solve it by cheating, inverting, or breaking the sacred rule</span><span class="gf">Great for: Get unstuck · Strategy</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Cultural"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="13.5" fill="currentColor" fill-opacity="0.14"/><g stroke="currentColor" stroke-width="1.6" fill="none"><circle cx="22" cy="22" r="13.5"/><ellipse cx="22" cy="22" rx="6" ry="13.5"/><line x1="8.5" y1="22" x2="35.5" y2="22"/><path d="M11 15 H 33" stroke-opacity="0.55"/><path d="M11 29 H 33" stroke-opacity="0.55"/></g></svg></span><span><span class="n">✨ Invent a Cultural technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Cultural</span></span></label></div></section>
+<section data-cat="Speculative Future" style="--c:#0fb5c9"><h2>Speculative Future<span class="cnt">8</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Time Horizon Ladder" data-cat="Speculative Future" data-desc="Solve the idea for 1 year out, then 10, then 100 — note what survives, breaks, or becomes absurd at each rung" data-good="strategy|planning|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M9 30 H35"/><path d="M14 30 V24 M22 30 V18 M30 30 V12"/></g><g fill="currentColor"><circle cx="14" cy="24" r="2"/><circle cx="22" cy="18" r="2"/><circle cx="30" cy="12" r="2"/></g></svg></span><span><span class="n">Time Horizon Ladder</span><span class="d">Solve the idea for 1 year out, then 10, then 100 — note what survives, breaks, or becomes absurd at each rung</span><span class="gf">Great for: Strategy · Planning · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Post-Scarcity Test" data-cat="Speculative Future" data-desc="Assume the core constraint (money, energy, time, attention) is now infinite and free — what does the idea become" data-good="novel|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M15 22 a4.5 4.5 0 1 1 4.5 4.5 C16 26.5 14 18 11 18 a3.5 3.5 0 0 0 0 7 c4 0 5 -8 11 -8 a4.5 4.5 0 0 1 0 9 c-3 0 -4 -4.5 -7 -4.5"/></g></svg></span><span><span class="n">Post-Scarcity Test</span><span class="d">Assume the core constraint (money, energy, time, attention) is now infinite and free — what does the idea become</span><span class="gf">Great for: Novel concept · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Utopia vs Dystopia Split-Screen" data-cat="Speculative Future" data-desc="Write the same future twice: the brochure where it went perfectly and the headline where it went horribly" data-good="strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="11" width="22" height="22" rx="3" fill="none" stroke="currentColor" stroke-width="2"/><path d="M22 11 V33" stroke="currentColor" stroke-width="2"/><path d="M22 11 H33 a0 0 0 0 1 0 0 V33 H22 Z" fill="currentColor" fill-opacity=".8"/></svg></span><span><span class="n">Utopia vs Dystopia Split-Screen</span><span class="d">Write the same future twice: the brochure where it went perfectly and the headline where it went horribly</span><span class="gf">Great for: Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Sci-Fi Artifact From the Future" data-cat="Speculative Future" data-desc="Describe one physical object, ad, or news clip from the world where this idea already won — reverse-engineer it" data-good="novel|feature" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 9 L33 15 V28 L22 35 L11 28 V15 Z" fill="currentColor" fill-opacity=".15"/><path d="M22 9 L33 15 V28 L22 35 L11 28 V15 Z M11 15 L22 21 L33 15 M22 21 V35" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/></svg></span><span><span class="n">Sci-Fi Artifact From the Future</span><span class="d">Describe one physical object, ad, or news clip from the world where this idea already won — reverse-engineer it</span><span class="gf">Great for: Novel concept · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Emerging Tech Collision" data-cat="Speculative Future" data-desc="Force-marry your idea to a frontier tech (AGI, fusion, neural implants, gene edit) and ask what new thing is born" data-good="novel|feature|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="15" y="15" width="14" height="14" rx="2" fill="currentColor" fill-opacity=".22"/><rect x="15" y="15" width="14" height="14" rx="2" fill="none" stroke="currentColor" stroke-width="2"/><g stroke="currentColor" stroke-width="2" stroke-linecap="round"><path d="M19 15 V10 M25 15 V10 M19 29 V34 M25 29 V34 M15 19 H10 M15 25 H10 M29 19 H34 M29 25 H34"/></g></svg></span><span><span class="n">Emerging Tech Collision</span><span class="d">Force-marry your idea to a frontier tech (AGI, fusion, neural implants, gene edit) and ask what new thing is born</span><span class="gf">Great for: Novel concept · Build a feature · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="What-If-The-World-Changed Card Flip" data-cat="Speculative Future" data-desc="Draw a wild world-shift (no privacy, half population, 200-yr lifespans) and redesign the idea to fit that world" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="13" y="10" width="18" height="24" rx="2.5" fill="currentColor" fill-opacity=".18" stroke="currentColor" stroke-width="2"/><path d="M22 10 V34" stroke="currentColor" stroke-width="1.6" stroke-dasharray="2 2.5"/><path d="M27 16 a4 4 0 1 1 4 4" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/></svg></span><span><span class="n">What-If-The-World-Changed Card Flip</span><span class="d">Draw a wild world-shift (no privacy, half population, 200-yr lifespans) and redesign the idea to fit that world</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Future Anthropologist Dig" data-cat="Speculative Future" data-desc="A scholar in 2200 unearths your idea as a relic — what do they conclude it reveals about us, and what replaced it" data-good="strategy|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 27 a6 6 0 1 1 0.1 0 z"/><path d="M22 23 a2.5 2.5 0 1 0 0.1 0 M19 30 a5 5 0 0 0 6 0"/></g><path d="M12 16 L17 13 M32 16 L27 13" stroke="currentColor" stroke-width="1.6" stroke-opacity=".5"/></svg></span><span><span class="n">Future Anthropologist Dig</span><span class="d">A scholar in 2200 unearths your idea as a relic — what do they conclude it reveals about us, and what replaced it</span><span class="gf">Great for: Strategy · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Scenario Cross" data-cat="Speculative Future" data-desc="Pick two high-impact uncertainties, cross them into four futures, and ideate the move that wins in every one" data-good="strategy|planning" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2" stroke-linecap="round"><path d="M22 9 V35 M9 22 H35"/></g><g fill="currentColor"><circle cx="15" cy="15" r="2"/><circle cx="29" cy="15" r="2"/><circle cx="15" cy="29" r="2"/><circle cx="29" cy="29" r="2"/></g></svg></span><span><span class="n">Scenario Cross</span><span class="d">Pick two high-impact uncertainties, cross them into four futures, and ideate the move that wins in every one</span><span class="gf">Great for: Strategy · Planning</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Speculative Future"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M11 31 L 26.5 15.5"/><path d="M20 14.5 H 28 V 22.5"/></g><circle cx="31" cy="12" r="2.8" fill="currentColor"/><g stroke="currentColor" stroke-width="1.4" stroke-linecap="round"><line x1="31" y1="6.5" x2="31" y2="8.4"/><line x1="31" y1="15.6" x2="31" y2="17.5"/><line x1="25.5" y1="12" x2="27.4" y2="12"/><line x1="34.6" y1="12" x2="36.5" y2="12"/></g></svg></span><span><span class="n">✨ Invent a Speculative Future technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Speculative Future</span></span></label></div></section>
+<section data-cat="Quantum" style="--c:#2b86d9"><h2>Quantum<span class="cnt">6</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Observer Effect" data-cat="Quantum" data-desc="Ask how the act of watching, measuring, or shipping this idea changes the very thing you&#x27;re trying to capture" data-good="strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M9 22 q13 -10 26 0 q-13 10 -26 0 z" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/><circle cx="22" cy="22" r="4.5" fill="none" stroke="currentColor" stroke-width="2"/><circle cx="22" cy="22" r="1.8" fill="currentColor"/></svg></span><span><span class="n">Observer Effect</span><span class="d">Ask how the act of watching, measuring, or shipping this idea changes the very thing you&#x27;re trying to capture</span><span class="gf">Great for: Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Entanglement Thinking" data-cat="Quantum" data-desc="Pair two distant parts of the problem and insist a change in one instantly flips the other — surface the hidden linkage" data-good="diagnosis|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><circle cx="15" cy="22" r="6"/><circle cx="29" cy="22" r="6"/></g><path d="M15 22 h14" stroke="currentColor" stroke-width="2" stroke-dasharray="1.5 2.5"/><g fill="currentColor"><circle cx="15" cy="22" r="1.8"/><circle cx="29" cy="22" r="1.8"/></g></svg></span><span><span class="n">Entanglement Thinking</span><span class="d">Pair two distant parts of the problem and insist a change in one instantly flips the other — surface the hidden linkage</span><span class="gf">Great for: Diagnose · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Superposition Collapse" data-cat="Quantum" data-desc="Hold all rival solutions alive at once, then name the one constraint that collapses them to a single winner" data-good="strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M11 12 C20 16 24 16 33 12 M11 18 C20 22 24 22 33 18 M11 24 C20 28 24 28 33 24"/><path d="M22 26 V34"/></g><circle cx="22" cy="34" r="2" fill="currentColor"/></svg></span><span><span class="n">Superposition Collapse</span><span class="d">Hold all rival solutions alive at once, then name the one constraint that collapses them to a single winner</span><span class="gf">Great for: Strategy · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Relativity Frame Shift" data-cat="Quantum" data-desc="Re-run the idea from a wildly different observer&#x27;s reference frame — the slow user, the rival, future-you — and see what warps" data-good="strategy|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="11" width="22" height="22" rx="2" fill="none" stroke="currentColor" stroke-width="2" stroke-opacity=".4"/><rect x="15" y="15" width="18" height="18" rx="2" transform="rotate(-14 22 22)" fill="none" stroke="currentColor" stroke-width="2"/></svg></span><span><span class="n">Relativity Frame Shift</span><span class="d">Re-run the idea from a wildly different observer&#x27;s reference frame — the slow user, the rival, future-you — and see what warps</span><span class="gf">Great for: Strategy · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Field Lines" data-cat="Quantum" data-desc="Treat the goal as a charge and map the invisible forces pulling every stakeholder toward or away from it" data-good="strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 13 V31 M16 13 C24 18 24 26 16 31 M22 13 C32 18 32 26 22 31"/></g><circle cx="11" cy="22" r="2" fill="currentColor"/></svg></span><span><span class="n">Field Lines</span><span class="d">Treat the goal as a charge and map the invisible forces pulling every stakeholder toward or away from it</span><span class="gf">Great for: Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Quantum Tunneling" data-cat="Quantum" data-desc="Assume the idea can pass straight through the &#x27;impossible&#x27; barrier instead of over it — what&#x27;s on the other side, reached cheaply" data-good="unstuck|novel" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="20" y="9" width="5" height="26" rx="1.5" fill="currentColor" fill-opacity=".3"/><path d="M10 22 H34" fill="none" stroke="currentColor" stroke-width="2.2" stroke-linecap="round"/><path d="M28 17 L34 22 L28 27" fill="none" stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Quantum Tunneling</span><span class="d">Assume the idea can pass straight through the &#x27;impossible&#x27; barrier instead of over it — what&#x27;s on the other side, reached cheaply</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Quantum"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8" fill="none"><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(28 22 22)"/><ellipse cx="22" cy="22" rx="14.5" ry="6" transform="rotate(-28 22 22)"/></g><circle cx="22" cy="22" r="6.6" fill="currentColor" fill-opacity="0.18"/><circle cx="22" cy="22" r="3.4" fill="currentColor"/><circle cx="33.2" cy="17.4" r="2" fill="currentColor"/></svg></span><span><span class="n">✨ Invent a Quantum technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Quantum</span></span></label></div></section>
+<h2 class="grouphdr" style="--c:#e2562f">Wild &amp; Playful</h2>
+<section data-cat="Wild" style="--c:#e2562f"><h2>Wild<span class="cnt">7</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Chaos Engineering" data-cat="Wild" data-desc="Deliberately break your idea every way it could fail, then rebuild only the parts that survive the wreckage" data-good="feature|diagnosis|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 9 L25 18 L34 18 L27 24 L30 33 L22 27 L14 33 L17 24 L10 18 L19 18 Z"/></g></svg></span><span><span class="n">Chaos Engineering</span><span class="d">Deliberately break your idea every way it could fail, then rebuild only the parts that survive the wreckage</span><span class="gf">Great for: Build a feature · Diagnose · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Guerrilla Gardening Ideas" data-cat="Wild" data-desc="Plant your solution in the least expected place and let it grow underground until it surprises everyone" data-good="strategy|unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 33 V21"/><path d="M22 22 c-7 0 -9 -6 -9 -9 c6 0 9 3 9 9 z"/><path d="M22 24 c6 0 8 -4 8 -7 c-5 0 -8 2 -8 7 z"/></g></svg></span><span><span class="n">Guerrilla Gardening Ideas</span><span class="d">Plant your solution in the least expected place and let it grow underground until it surprises everyone</span><span class="gf">Great for: Strategy · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Pirate Code Brainstorm" data-cat="Wild" data-desc="Steal the best bits from anywhere, remix without asking permission, grab what works and run" data-good="novel|unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 10 c-7 0 -11 5 -11 11 c0 4 2 6 4 7 v4 h3 v-2 h2 v2 h4 v-2 h2 v2 h3 v-4 c2 -1 4 -3 4 -7 c0 -6 -4 -11 -11 -11 z" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/><g fill="currentColor"><circle cx="17.5" cy="21" r="2.2"/><circle cx="26.5" cy="21" r="2.2"/></g></svg></span><span><span class="n">Pirate Code Brainstorm</span><span class="d">Steal the best bits from anywhere, remix without asking permission, grab what works and run</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Zombie Apocalypse Planning" data-cat="Wild" data-desc="Society just collapsed — strip your idea to only what survives with no power, no rules, no backup" data-good="feature|strategy|unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="4" fill="none" stroke="currentColor" stroke-width="2"/><g fill="none" stroke="currentColor" stroke-width="2"><path d="M22 10 a12 12 0 0 1 6 3.5 M32 16 a12 12 0 0 1 0 12 M28 33.5 a12 12 0 0 1 -12 0 M12 28 a12 12 0 0 1 0 -12 M16 10.5 a12 12 0 0 1 6 -0.5" stroke-dasharray="0.1 5.5"/></g><g fill="currentColor"><circle cx="22" cy="11" r="2"/><circle cx="11" cy="22" r="2"/><circle cx="33" cy="22" r="2"/></g></svg></span><span><span class="n">Zombie Apocalypse Planning</span><span class="d">Society just collapsed — strip your idea to only what survives with no power, no rules, no backup</span><span class="gf">Great for: Build a feature · Strategy · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Drunk History Retelling" data-cat="Wild" data-desc="Explain it like you&#x27;re three drinks in: no filter, no jargon, just the raw stupid-simple truth" data-good="unstuck|diagnosis" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M13 12 H31 L25 23 V31 H19 V23 Z"/><path d="M19 31 H25" /></g><circle cx="29" cy="14" r="1.4" fill="currentColor"/></svg></span><span><span class="n">Drunk History Retelling</span><span class="d">Explain it like you&#x27;re three drinks in: no filter, no jargon, just the raw stupid-simple truth</span><span class="gf">Great for: Get unstuck · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Anti-Solution" data-cat="Wild" data-desc="Brainstorm how to make the problem spectacularly worse, then invert every sabotage into a fix" data-good="diagnosis|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M14 18 a8 8 0 1 1 -1 8"/><path d="M14 12 L14 18.5 L20 18"/></g></svg></span><span><span class="n">Anti-Solution</span><span class="d">Brainstorm how to make the problem spectacularly worse, then invert every sabotage into a fix</span><span class="gf">Great for: Diagnose · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Elemental Forces" data-cat="Wild" data-desc="Let fire, water, earth, and air each sculpt your idea their own brutal way and see what survives" data-good="novel|unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 8 L30 22 H14 Z"/><path d="M14 30 L22 36 L30 30"/><path d="M14 26 H30"/></g></svg></span><span><span class="n">Elemental Forces</span><span class="d">Let fire, water, earth, and air each sculpt your idea their own brutal way and see what survives</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Wild"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M24.5 6.5 L 12.5 24 H 19.5 L 17.5 37.5 L 31.5 18.5 H 24 L 24.5 6.5 Z" fill="currentColor"/></svg></span><span><span class="n">✨ Invent a Wild technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Wild</span></span></label></div></section>
+<section data-cat="Absurdist" style="--c:#e0529c"><h2>Absurdist<span class="cnt">6</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Villain&#x27;s Monologue" data-cat="Absurdist" data-desc="Pitch your problem as an evil mastermind gloating about their scheme; the diabolical plan reveals the real solution" data-good="diagnosis|strategy|unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 20 C16 18 19 18 22 21 C25 18 28 18 32 20 C30 24 26 24 22 21 C18 24 14 24 12 20 Z"/></g><circle cx="22" cy="14" r="2.4" fill="currentColor"/></svg></span><span><span class="n">Villain&#x27;s Monologue</span><span class="d">Pitch your problem as an evil mastermind gloating about their scheme; the diabolical plan reveals the real solution</span><span class="gf">Great for: Diagnose · Strategy · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Explain It to a Golden Retriever" data-cat="Absurdist" data-desc="Re-pitch the idea to an excitable dog who only cares about treats, balls, and naps; keep only what survives" data-good="unstuck|diagnosis|feature" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M14 18 C12 12 17 13 18 17 M30 18 C32 12 27 13 26 17"/><path d="M15 19 C13 28 18 33 22 33 C26 33 31 28 29 19 C26 16 18 16 15 19 Z"/></g><g fill="currentColor"><circle cx="19" cy="24" r="1.4"/><circle cx="25" cy="24" r="1.4"/><circle cx="22" cy="28" r="1.6"/></g></svg></span><span><span class="n">Explain It to a Golden Retriever</span><span class="d">Re-pitch the idea to an excitable dog who only cares about treats, balls, and naps; keep only what survives</span><span class="gf">Great for: Get unstuck · Diagnose · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Infomercial at 3AM" data-cat="Absurdist" data-desc="Sell your half-baked idea as a desperate late-night infomercial: &#x27;But wait, there&#x27;s more!&#x27; until features fall out" data-good="strategy|novel" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="9" y="14" width="26" height="18" rx="2.5" fill="none" stroke="currentColor" stroke-width="2"/><path d="M18 9 L22 14 L26 9" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/><path d="M22 19 l1 2.6 2.8 .2 -2.1 1.9 .7 2.7 -2.4 -1.5 -2.4 1.5 .7 -2.7 -2.1 -1.9 2.8 -.2 z" fill="currentColor"/></svg></span><span><span class="n">Infomercial at 3AM</span><span class="d">Sell your half-baked idea as a desperate late-night infomercial: &#x27;But wait, there&#x27;s more!&#x27; until features fall out</span><span class="gf">Great for: Strategy · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Drunk Uncle at Thanksgiving" data-cat="Absurdist" data-desc="Have your loudest, least-filtered relative rant about the problem; mine the unhinged hot takes for buried truth" data-good="unstuck|diagnosis" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M11 16 L20 16 L27 11 V29 L20 24 L11 24 Z"/><path d="M30 16 q3 4 0 8 M33 13 q5 7 0 14"/></g></svg></span><span><span class="n">Drunk Uncle at Thanksgiving</span><span class="d">Have your loudest, least-filtered relative rant about the problem; mine the unhinged hot takes for buried truth</span><span class="gf">Great for: Get unstuck · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Cursed Genie" data-cat="Absurdist" data-desc="Make a wish, then let a malicious genie grant it in the most technically-correct disastrous way; patch each loophole" data-good="diagnosis|feature" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M10 30 h18 a2 2 0 0 0 2 -2 c0 -5 -6 -5 -8 -8 c5 -1 8 -3 8 -3 c-4 -2 -12 -2 -16 1 c-4 3 -5 9 -4 12 z"/><path d="M30 17 L33 14 M31 21 L35 20" stroke-opacity=".6"/></g></svg></span><span><span class="n">Cursed Genie</span><span class="d">Make a wish, then let a malicious genie grant it in the most technically-correct disastrous way; patch each loophole</span><span class="gf">Great for: Diagnose · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Three Rounds of Stupid" data-cat="Absurdist" data-desc="Round 1 absurd ideas, Round 2 make each MORE absurd, Round 3 find the smallest serious thing hiding in the silliest" data-good="unstuck|novel" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M13 30 V20 M9 24 L13 20 L17 24 M22 30 V15 M18 19 L22 15 L26 19 M31 30 V11 M27 15 L31 11 L35 15"/></g></svg></span><span><span class="n">Three Rounds of Stupid</span><span class="d">Round 1 absurd ideas, Round 2 make each MORE absurd, Round 3 find the smallest serious thing hiding in the silliest</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Absurdist"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g transform="rotate(-12 22 22)"><circle cx="22" cy="22" r="13" fill="currentColor" fill-opacity="0.14"/><circle cx="22" cy="22" r="13" stroke="currentColor" stroke-width="1.6" fill="none"/><path d="M16 19 q 2 -2.4 4 0" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/><circle cx="26.5" cy="18.8" r="1.8" fill="currentColor"/><path d="M16.5 26 C 19 30, 25 30, 28 24.5" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></g></svg></span><span><span class="n">✨ Invent a Absurdist technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Absurdist</span></span></label></div></section>
+<section data-cat="Theatrical" style="--c:#cf4d6f"><h2>Theatrical<span class="cnt">7</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Time Travel Talk Show" data-cat="Theatrical" data-desc="Host a talk show interviewing your past, present, and future selves to mine each era for advice on the problem" data-good="novel|personal" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="18" y="9" width="8" height="15" rx="4" fill="currentColor" fill-opacity=".25"/><rect x="18" y="9" width="8" height="15" rx="4" fill="none" stroke="currentColor" stroke-width="2"/><path d="M14 21 a8 8 0 0 0 16 0 M22 29 V34 M17 34 H27" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Time Travel Talk Show</span><span class="d">Host a talk show interviewing your past, present, and future selves to mine each era for advice on the problem</span><span class="gf">Great for: Novel concept · Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Alien Anthropologist" data-cat="Theatrical" data-desc="Become a baffled alien studying the problem and narrate aloud what seems strange, arbitrary, or insane about it" data-good="diagnosis|unstuck|strategy" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><ellipse cx="22" cy="30" rx="13" ry="4.5" fill="currentColor" fill-opacity=".25"/><path d="M22 11 c7 0 10 6 10 11 c0 5 -5 7 -10 7 c-5 0 -10 -2 -10 -7 c0 -5 3 -11 10 -11 z" fill="none" stroke="currentColor" stroke-width="2"/><g fill="currentColor"><ellipse cx="18" cy="22" rx="1.6" ry="2.4"/><ellipse cx="26" cy="22" rx="1.6" ry="2.4"/></g></svg></span><span><span class="n">Alien Anthropologist</span><span class="d">Become a baffled alien studying the problem and narrate aloud what seems strange, arbitrary, or insane about it</span><span class="gf">Great for: Diagnose · Get unstuck · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Dream Fusion Laboratory" data-cat="Theatrical" data-desc="Voice the impossible fantasy solution first, then reverse-engineer the bridging steps back to reality" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 9 H26 M19.5 9 V18 L13 30 a2 2 0 0 0 2 3 H29 a2 2 0 0 0 2 -3 L24.5 18 V9"/></g><path d="M16.5 26 H27.5" stroke="currentColor" stroke-width="2"/><circle cx="20" cy="29" r="1.4" fill="currentColor"/><circle cx="25" cy="28" r="1.1" fill="currentColor"/></svg></span><span><span class="n">Dream Fusion Laboratory</span><span class="d">Voice the impossible fantasy solution first, then reverse-engineer the bridging steps back to reality</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Emotion Orchestra" data-cat="Theatrical" data-desc="Run a separate ideation round led by each emotion (rage, joy, fear, hope), then harmonize their conflicting ideas" data-good="personal|strategy" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M17 30 V15 L31 12 V27"/><circle cx="14" cy="30" r="3"/><circle cx="28" cy="27" r="3"/></g></svg></span><span><span class="n">Emotion Orchestra</span><span class="d">Run a separate ideation round led by each emotion (rage, joy, fear, hope), then harmonize their conflicting ideas</span><span class="gf">Great for: Personal / life · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Parallel Universe Cafe" data-cat="Theatrical" data-desc="Rewrite one fundamental rule of reality (physics, economics, social norms) and solve the problem under those laws" data-good="novel|unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><circle cx="18" cy="22" r="9"/><circle cx="26" cy="22" r="9" stroke-dasharray="2.5 2.5"/></g></svg></span><span><span class="n">Parallel Universe Cafe</span><span class="d">Rewrite one fundamental rule of reality (physics, economics, social norms) and solve the problem under those laws</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Persona Journey" data-cat="Theatrical" data-desc="Embody an archetype and solve the problem in-character, naming what that persona sees that you normally miss" data-good="feature|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M14 33 q-2 -8 6 -9 q8 -1 6 -8" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-dasharray="0.1 4"/><circle cx="14" cy="33" r="2.4" fill="currentColor"/><path d="M26 16 l3 -5 3 5 z" fill="currentColor"/></svg></span><span><span class="n">Persona Journey</span><span class="d">Embody an archetype and solve the problem in-character, naming what that persona sees that you normally miss</span><span class="gf">Great for: Build a feature · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Devil&#x27;s Advocate Courtroom" data-cat="Theatrical" data-desc="Stage a trial: prosecute the idea, defend it, then deliver the jury verdict, each role argued fully in character" data-good="strategy|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M22 10 V32 M14 32 H30"/><path d="M11 16 H33 M11 16 L8 23 H14 Z M33 16 L30 23 H36 Z"/></g></svg></span><span><span class="n">Devil&#x27;s Advocate Courtroom</span><span class="d">Stage a trial: prosecute the idea, defend it, then deliver the jury verdict, each role argued fully in character</span><span class="gf">Great for: Strategy · Diagnose</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Theatrical"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" fill="currentColor" fill-opacity="0.18"/><path d="M13 12 H 31 V 22 C 31 30, 27 35, 22 35 C 17 35, 13 30, 13 22 Z" stroke="currentColor" stroke-width="1.8" fill="none"/><g fill="currentColor"><circle cx="18.5" cy="21" r="1.7"/><circle cx="25.5" cy="21" r="1.7"/></g><path d="M18 27 C 20 29.5, 24 29.5, 26 27" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" fill="none"/></svg></span><span><span class="n">✨ Invent a Theatrical technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Theatrical</span></span></label></div></section>
+<section data-cat="Constraint" style="--c:#d9882b"><h2>Constraint<span class="cnt">7</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Kill the Crown Jewel" data-cat="Constraint" data-desc="Delete the single best, most beloved feature — now redesign the whole thing to win without it" data-good="feature|strategy|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M11 28 L13 15 L19 22 L22 12 L25 22 L31 15 L33 28 Z"/><path d="M11 28 H33"/></g><path d="M14 12 L30 32" stroke="currentColor" stroke-width="2.4" stroke-linecap="round"/></svg></span><span><span class="n">Kill the Crown Jewel</span><span class="d">Delete the single best, most beloved feature — now redesign the whole thing to win without it</span><span class="gf">Great for: Build a feature · Strategy · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="1000x Budget" data-cat="Constraint" data-desc="Pretend money, time, and people are infinite — design the absurd version, then mine it for ideas you can actually steal" data-good="novel|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><ellipse cx="22" cy="14" rx="9" ry="3.5"/><path d="M13 14 V22 a9 3.5 0 0 0 18 0 V14"/><path d="M13 22 V30 a9 3.5 0 0 0 18 0 V22"/></g></svg></span><span><span class="n">1000x Budget</span><span class="d">Pretend money, time, and people are infinite — design the absurd version, then mine it for ideas you can actually steal</span><span class="gf">Great for: Novel concept · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Ship in 60 Minutes" data-cat="Constraint" data-desc="You launch in one hour with what&#x27;s already on hand — name what you cut, fake, or borrow to make it real" data-good="feature|planning|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="24" r="11" fill="none" stroke="currentColor" stroke-width="2"/><path d="M22 24 V17 M22 24 L27 27" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/><path d="M18 8 H26 M22 8 V13" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Ship in 60 Minutes</span><span class="d">You launch in one hour with what&#x27;s already on hand — name what you cut, fake, or borrow to make it real</span><span class="gf">Great for: Build a feature · Planning · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="The $0 Mandate" data-cat="Constraint" data-desc="Achieve the goal spending literally nothing — no tools, hires, or ads; only people, favors, and what you own" data-good="planning|strategy|feature" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="11" fill="none" stroke="currentColor" stroke-width="2"/><path d="M22 14 V30 M18 18 a4 3 0 0 1 8 0 a4 3 0 0 1 -8 4 a4 3 0 0 0 8 0" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/><path d="M14 30 L30 14" stroke="currentColor" stroke-width="2.2" stroke-linecap="round"/></svg></span><span><span class="n">The $0 Mandate</span><span class="d">Achieve the goal spending literally nothing — no tools, hires, or ads; only people, favors, and what you own</span><span class="gf">Great for: Planning · Strategy · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="One Feature Only" data-cat="Constraint" data-desc="You may keep exactly ONE capability and nothing else — pick it, then make that single thing unbelievably good" data-good="feature|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="22" cy="22" r="4.5"/><path d="M22 9 V13 M22 31 V35 M9 22 H13 M31 22 H35" stroke-opacity=".35"/></g><circle cx="22" cy="22" r="2" fill="currentColor"/></svg></span><span><span class="n">One Feature Only</span><span class="d">You may keep exactly ONE capability and nothing else — pick it, then make that single thing unbelievably good</span><span class="gf">Great for: Build a feature · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Crank the Dial to 11" data-cat="Constraint" data-desc="Pick one dimension and exaggerate it to a ludicrous extreme — fastest, biggest, cheapest, weirdest — and see what breaks open" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M11 28 A12 12 0 0 1 33 28" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/><path d="M22 28 L31 17" stroke="currentColor" stroke-width="2.2" stroke-linecap="round"/><circle cx="22" cy="28" r="2.6" fill="currentColor"/></svg></span><span><span class="n">Crank the Dial to 11</span><span class="d">Pick one dimension and exaggerate it to a ludicrous extreme — fastest, biggest, cheapest, weirdest — and see what breaks open</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Constraint Roulette" data-cat="Constraint" data-desc="Each round draw a brutal random limit (no screens, half the team, one day) and re-solve under it; survivors become real ideas" data-good="unstuck|feature" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="12" fill="none" stroke="currentColor" stroke-width="2"/><circle cx="22" cy="22" r="12" fill="none" stroke="currentColor" stroke-width="2" stroke-dasharray="3 3.7" stroke-opacity=".5"/><circle cx="22" cy="22" r="3" fill="currentColor"/><path d="M22 7 L25 12 H19 Z" fill="currentColor"/></svg></span><span><span class="n">Constraint Roulette</span><span class="d">Each round draw a brutal random limit (no screens, half the team, one day) and re-solve under it; survivors become real ideas</span><span class="gf">Great for: Get unstuck · Build a feature</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Constraint"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round" fill="none"><path d="M17 11 H 11 V 17"/><path d="M27 11 H 33 V 17"/><path d="M17 33 H 11 V 27"/><path d="M27 33 H 33 V 27"/></g><circle cx="22" cy="22" r="5" fill="currentColor" fill-opacity="0.25"/><circle cx="22" cy="22" r="2.6" fill="currentColor"/></svg></span><span><span class="n">✨ Invent a Constraint technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Constraint</span></span></label></div></section>
+<h2 class="grouphdr" style="--c:#b15ad6">Introspective &amp; Personal</h2>
+<section data-cat="Introspective Delight" style="--c:#b15ad6"><h2>Introspective Delight<span class="cnt">8</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Inner Child Conference" data-cat="Introspective Delight" data-desc="Answer as your 7-year-old self: ask naive &#x27;why why why&#x27; questions, chase wonder, ban every boring adult thought" data-good="personal|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="16" r="6" fill="none" stroke="currentColor" stroke-width="2"/><path d="M22 22 V31" stroke="currentColor" stroke-width="2" stroke-linecap="round"/><path d="M19 34 q3 -3 6 0" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/><g fill="currentColor"><circle cx="20" cy="15" r="1"/><circle cx="24" cy="15" r="1"/></g></svg></span><span><span class="n">Inner Child Conference</span><span class="d">Answer as your 7-year-old self: ask naive &#x27;why why why&#x27; questions, chase wonder, ban every boring adult thought</span><span class="gf">Great for: Personal / life · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Shadow Work Mining" data-cat="Introspective Delight" data-desc="Name what you&#x27;re avoiding, resisting, or scared of about this — then dig there for the buried insight" data-good="personal|diagnosis" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="22" r="12" fill="none" stroke="currentColor" stroke-width="2"/><path d="M22 10 a12 12 0 0 1 0 24 z" fill="currentColor" fill-opacity=".85"/></svg></span><span><span class="n">Shadow Work Mining</span><span class="d">Name what you&#x27;re avoiding, resisting, or scared of about this — then dig there for the buried insight</span><span class="gf">Great for: Personal / life · Diagnose</span></span></label><label class="tech"><input type="checkbox" data-name="Values Archaeology" data-cat="Introspective Delight" data-desc="Keep asking &#x27;why do I care?&#x27; until you hit bedrock: the non-negotiable value secretly steering the choice" data-good="personal|strategy" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2"><path d="M10 16 h24" stroke-opacity=".4"/><path d="M10 22 h24" stroke-opacity=".6"/></g><path d="M22 24 L16 30 L22 36 L28 30 Z" fill="currentColor"/></svg></span><span><span class="n">Values Archaeology</span><span class="d">Keep asking &#x27;why do I care?&#x27; until you hit bedrock: the non-negotiable value secretly steering the choice</span><span class="gf">Great for: Personal / life · Strategy</span></span></label><label class="tech"><input type="checkbox" data-name="Future Self Interview" data-cat="Introspective Delight" data-desc="Interview your wise 80-year-old self about this problem and write down the advice they give you" data-good="personal" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M14 10 H30 L24 22 L30 34 H14 L20 22 Z"/></g><path d="M18 14 H26" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Future Self Interview</span><span class="d">Interview your wise 80-year-old self about this problem and write down the advice they give you</span><span class="gf">Great for: Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Body Wisdom Dialogue" data-cat="Introspective Delight" data-desc="Scan for the tension, flutter, or gut pull each option triggers; let the body&#x27;s yes/no drive the ideas" data-good="personal" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M22 33 C12 26 9 19 13.5 15 C17 12 21 14 22 17 C23 14 27 12 30.5 15 C35 19 32 26 22 33 Z" fill="currentColor" fill-opacity=".22"/><path d="M22 33 C12 26 9 19 13.5 15 C17 12 21 14 22 17 C23 14 27 12 30.5 15 C35 19 32 26 22 33 Z" fill="none" stroke="currentColor" stroke-width="2"/></svg></span><span><span class="n">Body Wisdom Dialogue</span><span class="d">Scan for the tension, flutter, or gut pull each option triggers; let the body&#x27;s yes/no drive the ideas</span><span class="gf">Great for: Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Permission Giving" data-cat="Introspective Delight" data-desc="Write yourself an explicit permission slip to think the forbidden, impossible thought — then think it out loud" data-good="personal|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="10" y="14" width="24" height="16" rx="2.5" fill="none" stroke="currentColor" stroke-width="2"/><path d="M15 23 L19 27 L28 17" fill="none" stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"/></svg></span><span><span class="n">Permission Giving</span><span class="d">Write yourself an explicit permission slip to think the forbidden, impossible thought — then think it out loud</span><span class="gf">Great for: Personal / life · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Secret Wish Confession" data-cat="Introspective Delight" data-desc="Whisper the embarrassing thing you secretly want here but won&#x27;t admit, then build the idea honoring it" data-good="personal" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="13" y="20" width="18" height="14" rx="2.5" fill="currentColor" fill-opacity=".22"/><rect x="13" y="20" width="18" height="14" rx="2.5" fill="none" stroke="currentColor" stroke-width="2"/><path d="M16.5 20 v-3 a5.5 5.5 0 0 1 11 0 v3" fill="none" stroke="currentColor" stroke-width="2"/></svg></span><span><span class="n">Secret Wish Confession</span><span class="d">Whisper the embarrassing thing you secretly want here but won&#x27;t admit, then build the idea honoring it</span><span class="gf">Great for: Personal / life</span></span></label><label class="tech"><input type="checkbox" data-name="Mood Weather Report" data-cat="Introspective Delight" data-desc="Name the inner weather right now (fog, storm, sun) and let that exact emotional climate generate the ideas" data-good="personal|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="17" cy="17" r="4.5" fill="currentColor" fill-opacity=".5"/><path d="M22 30 a5 5 0 0 1 0.5 -10 a6 6 0 0 1 11 2.5 a4 4 0 0 1 -1.5 7.5 z" fill="none" stroke="currentColor" stroke-width="2" stroke-linejoin="round"/></svg></span><span><span class="n">Mood Weather Report</span><span class="d">Name the inner weather right now (fog, storm, sun) and let that exact emotional climate generate the ideas</span><span class="gf">Great for: Personal / life · Get unstuck</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Introspective Delight"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><circle cx="22" cy="13.5" r="4" fill="currentColor"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31 Z" fill="currentColor" fill-opacity="0.22"/><path d="M10.5 31 C 12.5 23, 31.5 23, 33.5 31" stroke="currentColor" stroke-width="1.7" fill="none"/><path d="M13.5 30 C 16 26.5, 20 25.5, 22 25.5 C 24 25.5, 28 26.5, 30.5 30" stroke="currentColor" stroke-width="1.5" fill="none" stroke-opacity="0.6"/></svg></span><span><span class="n">✨ Invent a Introspective Delight technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Introspective Delight</span></span></label></div></section>
+<section data-cat="Collaborative" style="--c:#15a3a3"><h2>Collaborative<span class="cnt">8</span></h2><div class="grid"><label class="tech"><input type="checkbox" data-name="Yes And Building" data-cat="Collaborative" data-desc="Never negate; each person opens with &quot;Yes, and...&quot; and adds to the last idea, stacking a chain of accepted additions" data-good="novel|unstuck|planning" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="currentColor"><rect x="8" y="27" width="12" height="8" rx="1.5" fill-opacity=".8"/><rect x="14" y="19" width="12" height="8" rx="1.5" fill-opacity=".5"/><rect x="20" y="11" width="12" height="8" rx="1.5"/></g></svg></span><span><span class="n">Yes And Building</span><span class="d">Never negate; each person opens with &quot;Yes, and...&quot; and adds to the last idea, stacking a chain of accepted additions</span><span class="gf">Great for: Novel concept · Get unstuck · Planning</span></span></label><label class="tech"><input type="checkbox" data-name="Brain Writing Round Robin" data-cat="Collaborative" data-desc="Everyone writes ideas silently, then passes their sheet; you build on whatever lands in front of you, round after round" data-good="novel|feature" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M31 16 A10 10 0 1 0 32.5 22"/><path d="M31 10 L31.5 16.3 L25 16.5"/></g></svg></span><span><span class="n">Brain Writing Round Robin</span><span class="d">Everyone writes ideas silently, then passes their sheet; you build on whatever lands in front of you, round after round</span><span class="gf">Great for: Novel concept · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Random Stimulation" data-cat="Collaborative" data-desc="Pull a random word or image and force a link to the problem: &quot;how does THIS spark a solution?&quot;" data-good="unstuck|novel" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="11" width="22" height="22" rx="4" fill="none" stroke="currentColor" stroke-width="2"/><g fill="currentColor"><circle cx="17" cy="17" r="1.8"/><circle cx="27" cy="17" r="1.8"/><circle cx="22" cy="22" r="1.8"/><circle cx="17" cy="27" r="1.8"/><circle cx="27" cy="27" r="1.8"/></g></svg></span><span><span class="n">Random Stimulation</span><span class="d">Pull a random word or image and force a link to the problem: &quot;how does THIS spark a solution?&quot;</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech"><input type="checkbox" data-name="Role Playing" data-cat="Collaborative" data-desc="Each person speaks as a different stakeholder, voicing what that role wants, fears, and would demand of the idea" data-good="strategy|personal|feature" data-prov="classic"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><rect x="11" y="9" width="22" height="26" rx="3" fill="none" stroke="currentColor" stroke-width="2"/><circle cx="22" cy="19" r="4" fill="currentColor"/><path d="M15.5 30 c2 -4.5 11 -4.5 13 0" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"/></svg></span><span><span class="n">Role Playing</span><span class="d">Each person speaks as a different stakeholder, voicing what that role wants, fears, and would demand of the idea</span><span class="gf">Great for: Strategy · Personal / life · Build a feature</span></span></label><label class="tech"><input type="checkbox" data-name="Ideation Relay Race" data-cat="Collaborative" data-desc="30-second turns, no pausing: add one idea, slap it to the next person, keep the baton moving before anyone overthinks" data-good="unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><line x1="12" y1="31" x2="27" y2="16"/><line x1="8" y1="22" x2="14" y2="22" stroke-opacity=".5"/><line x1="8" y1="27" x2="13" y2="27" stroke-opacity=".35"/></g><circle cx="29" cy="14" r="3.4" fill="currentColor"/></svg></span><span><span class="n">Ideation Relay Race</span><span class="d">30-second turns, no pausing: add one idea, slap it to the next person, keep the baton moving before anyone overthinks</span><span class="gf">Great for: Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Idea Hot Potato" data-cat="Collaborative" data-desc="One idea gets tossed around the circle; each catcher must mutate it in 10 seconds before passing, no repeats allowed" data-good="unstuck" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M11 31 Q22 8 33 31" fill="none" stroke="currentColor" stroke-width="2" stroke-dasharray="2 3.5" stroke-linecap="round"/><circle cx="22" cy="12.5" r="4.2" fill="currentColor"/></svg></span><span><span class="n">Idea Hot Potato</span><span class="d">One idea gets tossed around the circle; each catcher must mutate it in 10 seconds before passing, no repeats allowed</span><span class="gf">Great for: Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Steal And Upgrade" data-cat="Collaborative" data-desc="Pick a neighbor&#x27;s idea you envy, claim it out loud, then make it visibly better before handing it back improved" data-good="novel|unstuck" data-prov="signature"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M20 33 V14"/><path d="M13 21 L20 14 L27 21"/></g><path d="M30 27 l1 2.6 2.6 1 -2.6 1 -1 2.6 -1 -2.6 -2.6 -1 2.6 -1 z" fill="currentColor"/></svg></span><span><span class="n">Steal And Upgrade</span><span class="d">Pick a neighbor&#x27;s idea you envy, claim it out loud, then make it visibly better before handing it back improved</span><span class="gf">Great for: Novel concept · Get unstuck</span></span></label><label class="tech"><input type="checkbox" data-name="Fold The Paper" data-cat="Collaborative" data-desc="Each person adds one line to a hidden drawing or sentence, sees only the previous fragment, then unfold the surreal whole" data-good="unstuck|novel" data-prov="playful"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><path d="M13 16 L21 12 V28 L13 32 Z" fill="currentColor" fill-opacity=".22"/><path d="M21 12 L29 16 V32 L21 28 Z" fill="currentColor" fill-opacity=".45"/><path d="M13 16 L21 12 L29 16 M21 12 V28" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linejoin="round"/></svg></span><span><span class="n">Fold The Paper</span><span class="d">Each person adds one line to a hidden drawing or sentence, sees only the previous fragment, then unfold the surreal whole</span><span class="gf">Great for: Get unstuck · Novel concept</span></span></label><label class="tech invent"><input type="checkbox" data-invent="Collaborative"><span class="ic2"><svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg"><rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/><g stroke="currentColor" stroke-width="1.8"><line x1="14" y1="16" x2="30" y2="16"/><line x1="14" y1="16" x2="22" y2="30"/><line x1="30" y1="16" x2="22" y2="30"/></g><g fill="currentColor" fill-opacity="0.22"><circle cx="14" cy="16" r="4.6"/><circle cx="30" cy="16" r="4.6"/><circle cx="22" cy="30" r="4.6"/></g><g fill="currentColor"><circle cx="14" cy="16" r="2.4"/><circle cx="30" cy="16" r="2.4"/><circle cx="22" cy="30" r="2.4"/></g></svg></span><span><span class="n">✨ Invent a Collaborative technique</span><span class="d">Make up a brand-new technique on the fly, in the spirit of Collaborative</span></span></label></div></section>
+</main>
+<footer>BMad Method &middot; Brainstorming</footer>
+<script>
+(function(){
+  var $ = function(id){ return document.getElementById(id); };
+  var all = Array.prototype.slice;
+  var boxes = all.call(document.querySelectorAll('input[type=checkbox]'));
+  var techBoxes = boxes.filter(function(b){ return b.dataset.name; });      // real technique cards
+  var inventBoxes = boxes.filter(function(b){ return b.dataset.invent; });  // per-category "invent in the spirit of" cards
+  var header = document.querySelector('header');
+  var sections = all.call(document.querySelectorAll('section'));
+  var state = { mode: 'Facilitator', rand: 0, inv: 0, ai: 0 };
+  var MODE_HINTS = {
+    'Facilitator': 'A forcing function for your ideas — I prompt and push, but never supply them.',
+    'Creative Partner': 'We riff together — I facilitate and add ideas too, each logged as yours or mine.',
+    'Ideate for me': 'I run the whole session myself, then show you the result and offer to keep going.'
+  };
+  function setHint(){ $('modehint').textContent = MODE_HINTS[state.mode] || ''; }
+
+  var themeBtn = $('theme');
+  function setThemeIcon(){ themeBtn.textContent = document.documentElement.getAttribute('data-theme') === 'dark' ? '☀' : '☾'; }
+  themeBtn.addEventListener('click', function(){
+    var next = document.documentElement.getAttribute('data-theme') === 'dark' ? 'light' : 'dark';
+    document.documentElement.setAttribute('data-theme', next);
+    try { localStorage.setItem('bmad-theme', next); } catch(e){}
+    setThemeIcon();
+  });
+
+  all.call(document.querySelectorAll('.mode')).forEach(function(b){
+    b.addEventListener('click', function(){
+      all.call(document.querySelectorAll('.mode')).forEach(function(m){ m.classList.remove('on'); });
+      b.classList.add('on');
+      state.mode = b.dataset.mode;
+      setHint();
+    });
+  });
+
+  all.call(document.querySelectorAll('[data-step]')).forEach(function(btn){
+    btn.addEventListener('click', function(){
+      var k = btn.dataset.step, d = parseInt(btn.dataset.d, 10);
+      state[k] = Math.max(0, state[k] + d);
+      update();
+    });
+  });
+
+  // Category chips are jump-nav: click one to smooth-scroll its section into view,
+  // offsetting by the sticky header's height so the heading isn't hidden beneath it.
+  all.call(document.querySelectorAll('.chip')).forEach(function(chip){
+    chip.addEventListener('click', function(){
+      var sec = null;
+      for (var i = 0; i < sections.length; i++){ if (sections[i].dataset.cat === chip.dataset.cat){ sec = sections[i]; break; } }
+      if (!sec){ return; }
+      var top = sec.getBoundingClientRect().top + window.pageYOffset - header.offsetHeight - 8;
+      window.scrollTo({ top: top, behavior: 'smooth' });
+    });
+  });
+
+  boxes.forEach(function(b){ b.addEventListener('change', update); });
+
+  // A `classic` technique appears twice (lead "Proven & Professional" group + its home
+  // category), so de-dupe checked picks by name; the lead copy carries data-lead.
+  function checkedTech(){
+    var seen = {}, out = [];
+    techBoxes.forEach(function(b){
+      if (!b.checked || seen[b.dataset.name]) { return; }
+      seen[b.dataset.name] = 1;
+      out.push(b);
+    });
+    return out;
+  }
+  function checkedInvent(){ return inventBoxes.filter(function(b){ return b.checked; }); }
+
+  function update(){
+    // rand can't exceed what the pool can supply — keep the counter honest with the draw
+    if (state.rand > randomPool().length){ state.rand = randomPool().length; }
+    $('pickN').textContent = checkedTech().length;
+    $('randN').textContent = state.rand;
+    $('invN').textContent = state.inv;
+    $('aiN').textContent = state.ai;
+    var total = checkedTech().length + state.rand + state.inv + checkedInvent().length + state.ai;
+    var t = $('total');
+    t.textContent = 'Total ' + total + ' · 3–4 is the sweet spot';
+    t.classList.toggle('warn', total > 5);
+  }
+
+  // "Great for" goal filter: clicking a goal narrows visible cards to those tagged with it.
+  var goalBtns = all.call(document.querySelectorAll('.goal'));
+  function activeGoals(){ return goalBtns.filter(function(b){ return b.classList.contains('on'); }).map(function(b){ return b.dataset.goal; }); }
+  function applyFilter(){
+    var act = activeGoals();
+    all.call(document.querySelectorAll('label.tech')).forEach(function(lab){
+      var inp = lab.querySelector('input');
+      if (inp.dataset.invent){ return; }  // invent cards aren't goal-tagged — always visible
+      var good = (inp.dataset.good || '').split('|');
+      var show = !act.length || act.some(function(g){ return good.indexOf(g) >= 0; });
+      lab.classList.toggle('hidden', !show);
+    });
+  }
+  goalBtns.forEach(function(b){ b.addEventListener('click', function(){ b.classList.toggle('on'); applyFilter(); }); });
+
+  function randomPool(){
+    var picked = {};
+    checkedTech().forEach(function(b){ picked[b.dataset.name] = 1; });
+    // draw from unchecked, non-lead copies, skipping anything already picked
+    return techBoxes.filter(function(b){ return !b.checked && !b.dataset.lead && !picked[b.dataset.name]; });
+  }
+
+  function sample(arr, n){
+    var a = arr.slice(), out = [];
+    while (out.length < n && a.length){ out.push(a.splice(Math.floor(Math.random() * a.length), 1)[0]); }
+    return out;
+  }
+
+  function compose(){
+    var picks = checkedTech().map(function(b){ return { n: b.dataset.name, c: b.dataset.cat, d: b.dataset.desc, r: false }; });
+    var rnd = sample(randomPool(), state.rand).map(function(b){ return { n: b.dataset.name, c: b.dataset.cat, d: b.dataset.desc, r: true }; });
+    var techs = picks.concat(rnd);
+    var L = ["Let's run my brainstorming session.", "", 'Facilitation mode: ' + state.mode + '.'];
+    if (techs.length){
+      L.push("", 'Techniques to use:');
+      techs.forEach(function(t, i){
+        L.push((i + 1) + '.' + (t.r ? ' (random pick)' : '') + ' ' + t.n + '  ·  ' + t.c);
+        L.push('   ' + t.d);
+      });
+    }
+    var extra = [];
+    if (state.inv > 0){ extra.push('invent ' + state.inv + ' brand-new technique' + (state.inv > 1 ? 's' : '') + ' on the fly'); }
+    checkedInvent().forEach(function(b){ extra.push('invent 1 new technique in the spirit of ' + b.dataset.invent); });
+    if (state.ai > 0){ extra.push('you choose ' + state.ai + ' more technique' + (state.ai > 1 ? 's' : '') + ' that fit my goal'); }
+    if (extra.length){ L.push("", 'Then: ' + extra.join('; and ') + '.'); }
+    if (!techs.length && !extra.length){
+      L.push("", state.mode === 'Ideate for me'
+        ? 'Run the whole session yourself — pick the techniques, generate the ideas, then show me the result.'
+        : 'Help me choose 3–4 techniques to start.');
+    }
+    return L.join('\n');
+  }
+
+  function fallbackCopy(t){
+    var ta = document.createElement('textarea');
+    ta.value = t; ta.style.position = 'fixed'; ta.style.opacity = '0';
+    document.body.appendChild(ta); ta.focus(); ta.select();
+    var ok = false;
+    try { ok = document.execCommand('copy'); } catch(e){ ok = false; }
+    document.body.removeChild(ta);
+    return ok;
+  }
+
+  function flash(ok, text){
+    var b = $('banner');
+    b.classList.toggle('fail', !ok);
+    b.innerHTML = ok
+      ? '✓ Copied! Now paste it into the chat to start your session.'
+      : '⚠ Couldn’t reach the clipboard — copy the text in the box, then paste it into the chat.';
+    b.classList.add('show');
+    setTimeout(function(){ b.classList.remove('show'); }, 4500);
+    // Last resort on a hard failure: a prefilled, selectable prompt so the text is never lost.
+    if (!ok){ window.prompt('Copy this, then paste it into the chat:', text); }
+  }
+
+  $('copy').addEventListener('click', function(){
+    var text = compose();
+    if (navigator.clipboard && navigator.clipboard.writeText){
+      navigator.clipboard.writeText(text).then(
+        function(){ flash(true, text); },
+        function(){ flash(fallbackCopy(text), text); }
+      );
+    } else { flash(fallbackCopy(text), text); }
+  });
+
+  setHint();
+  setThemeIcon();
+  update();
+})();
+</script>
+</body>
+</html>
diff --git a/.claude/skills/bmad-brainstorming/customize.toml b/.claude/skills/bmad-brainstorming/customize.toml
new file mode 100644
index 0000000..a68c342
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/customize.toml
@@ -0,0 +1,84 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-brainstorming.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-brainstorming.toml         (team)
+#   {project-root}/_bmad/custom/bmad-brainstorming.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays: append
+
+# Steps to run before the standard activation (config load, greet).
+# Use for pre-flight loads, compliance checks, etc.
+activation_steps_prepend = []
+
+# Steps to run after greet but before facilitation begins.
+# Use for context-heavy setup that should happen once the user has been acknowledged.
+activation_steps_append = []
+
+# Persistent facts the facilitator keeps in mind for the whole session
+# (domain constraints, house rules, stylistic guardrails). Each entry is a
+# literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed
+# path/glob whose contents are loaded as facts. Default loads project-context.md
+# if bmad-generate-project-context has produced one, giving the facilitator
+# persistent awareness of the project's domain without re-asking.
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# The technique library loaded on demand during the session. Swap the path in
+# team/user TOML to ship a different or extended catalog of creative methods.
+# Kept `{skill-root}`-anchored so it resolves regardless of the working directory
+# (brain.py is always invoked with `--file {workflow.brain_methods}`).
+brain_methods = "{skill-root}/assets/brain-methods.csv"
+
+# Techniques the facilitator should reach for first. When proposing a method
+# (the AI-led default), it prefers these where they fit the goal before ranging
+# wider. Names should match an entry in the library or in additional_techniques.
+# Append-merges, so a team list and a personal list both contribute. Empty = no
+# preference; the facilitator chooses purely on fit.
+#
+# Example (set in team/user override TOML):
+#   favorite_techniques = ["SCAMPER", "Six Thinking Hats", "First Principles"]
+favorite_techniques = []
+
+# Extra techniques — and whole new categories — merged into the catalog the
+# facilitator chooses from, without editing the shipped CSV. Each entry mirrors
+# the library's shape (category, technique_name, description); a new category is
+# just a category value the CSV doesn't have. Entries append, so teams and users
+# can each grow the library. The facilitator treats these as first-class
+# alongside brain_methods across every flow — facilitator-chosen, browse,
+# category draws, and inventive.
+#
+# Example (set in team/user override TOML):
+#   [[workflow.additional_techniques]]
+#   category = "domain-specific"
+#   technique_name = "Regulatory Inversion"
+#   description = "Start from the compliance constraint and brainstorm what becomes possible only because of it — turn the rule into a generative frame rather than a limit."
+additional_techniques = []
+
+# Session output location. The running log and any final artifacts land inside
+# `{output_dir}/{output_folder_name}/`. `{topic_slug}` is filled from the session
+# topic so each topic gets its own folder — a user can brainstorm several topics
+# without collision. The resume check globs `{output_dir}/*/.memlog.md`.
+output_dir = "{output_folder}/brainstorming"
+output_folder_name = "brainstorm-{topic_slug}-{date}"
+
+# Executed when the session completes (after artifacts are produced and the user
+# has the paths). Accepts a string scalar (single instruction) or an array of
+# instructions executed in order. Empty for none.
+on_complete = ""
+
+# External-handoff routing. Natural-language directives applied after artifacts
+# are produced, to route them beyond local files (Confluence, Notion, Drive,
+# etc.). Each entry names the MCP tool, the destination, and the fields it needs.
+# URLs/IDs returned are surfaced to the user. If a named tool is unavailable at
+# runtime, the handoff is skipped and flagged; local files always exist. Empty
+# by default.
+#
+# Example (set in team/user override TOML):
+#   "After artifacts are produced, upload brainstorm.html to Confluence via corp:confluence_upload (space_key='IDEAS', parent_page='Brainstorms', author={user_name})."
+external_handoffs = []
diff --git a/.claude/skills/bmad-brainstorming/references/converge.md b/.claude/skills/bmad-brainstorming/references/converge.md
new file mode 100644
index 0000000..ac1786e
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/converge.md
@@ -0,0 +1,24 @@
+# Converging: Narrow & Decide
+
+Load this when divergence is spent and the user wants to narrow the field — or asks to "decide," "prioritize," "pick," or "make it real." The whole catalog is *divergent* by design (it generates); this is the deliberate opposite phase, and keeping the two apart is the point. Never run convergence while ideas are still flowing, and never let it leak into a generating batch — premature judgment is what kills good ideas. `{doc_workspace}/.memlog.md` is the canonical record; everything here works from it. Communicate in `{communication_language}`.
+
+**Mode holds.** In **Facilitator** you run the convergence *on the user's verdicts* — you structure and prompt, they judge; never rank for them. In **Creative Partner** you weigh in too, each call logged by author. In **Ideate for me** you converge yourself and show the result, then offer to keep going.
+
+## How to run it
+
+First, reflect the field back: pull the live candidates from the memlog (include the odd and buried ones, not just the recent obvious ones) so there's a concrete set to work on. Then pick **one** convergence move that fits the goal — don't hand the user a menu of methods; choose the one that suits *this* decision and name it. Run it to a result, log the outcome, and stop when a clear short-list or single direction emerges.
+
+Pick by what the decision needs:
+
+- **Affinity Clustering** — when there are many scattered ideas: group them into themes, name each cluster, and surface the through-line. Often the right *first* move, to turn a pile into a handful.
+- **Impact–Effort** — when the goal is action: place each candidate on impact vs effort; harvest high-impact / low-effort first, park the rest.
+- **NUF Test** — when novelty matters: score each New, Useful, Feasible (1–10 each); the totals expose the quiet winners and the dazzling-but-doomed.
+- **Forced Ranking / Dot Vote** — when you just need a ranked top-N: make the ideas compete, no ties; (a literal dot-vote when it's genuinely a group).
+- **PMI (Plus / Minus / Interesting)** — when one strong candidate needs pressure-testing before commitment: list its pluses, minuses, and the merely-interesting, then judge.
+- **MoSCoW** — when scoping a build: sort into Must / Should / Could / Won't-this-time.
+
+Log the surviving directions and the reasoning with `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type decision --text "<one-line gist>"` (use `--by` in Creative Partner mode). Two or three convergence moves chained is fine (e.g. cluster → score the clusters); more than that is usually over-processing.
+
+## Then finalize
+
+Once a short-list or direction is settled, **load `references/finalize.md`** and run it last — synthesis, `status: complete`, and artifacts build on the decisions you just logged. Convergence narrows; finalize captures and ships. Do not set `status: complete` here — that belongs to finalize.
diff --git a/.claude/skills/bmad-brainstorming/references/finalize.md b/.claude/skills/bmad-brainstorming/references/finalize.md
new file mode 100644
index 0000000..2a4b6d2
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/finalize.md
@@ -0,0 +1,26 @@
+# Wrap-Up: Synthesis & Artifacts
+
+Load this when the user signals they're spent or the topic is mined out. `{doc_workspace}/.memlog.md` is the canonical record of the session — everything here derives from it. Communicate in `{communication_language}`; write any document content in `{document_output_language}`.
+
+## Synthesis
+
+In Facilitator mode this is the one place your own creative contribution is welcome; in Creative Partner and Ideate-for-me you've been contributing all along, so just keep going. Run it in two moves, in order:
+
+1. **Hand them the mirror first.** Reflect a vivid sampling of *their* ideas back — deliberately include the odd, random, or buried ones from earlier, not just the recent obvious ones (in Creative Partner mode the `(... by user)` tags tell you which were theirs). Ask what they see now: conclusions, synergies, themes, the few that actually matter. Let them connect first; their own pattern-recognition is the point.
+2. **Then add the connections they would miss.** Lean in creatively — not new raw ideas, but the non-obvious links: this idea from technique one quietly solves that tension from technique four; these three are one idea wearing three hats; this wildcard is the real breakthrough.
+
+Record the insights and chosen directions with `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type insight --text "<insights + chosen directions>"`. **Then run `uv run {project-root}/_bmad/scripts/memlog.py set --workspace {doc_workspace} --key status --value complete`** — the session is done and must stop being offered for resume. Do this even if the user declines every artifact below.
+
+## Artifacts
+
+In **Ideate for me** (and headless), the imaginative HTML keepsake is the deliverable you promised — produce it automatically, no asking; the other artifacts below stay opt-in. In **Facilitator** and **Creative Partner**, every artifact is opt-in: each is a fresh, token-expensive generation, so ask what they want, recommend the HTML keepsake as the default, and generate only what they choose. Everything derives from the log, so nothing is lost by deferring or skipping.
+
+**Delegate each artifact to a subagent.** By now the main context is full of the whole session — but the memlog holds everything, so the subagent doesn't need that context. Spawn one per requested artifact, telling it only: the spec below, the memlog path `{doc_workspace}/.memlog.md` (its sole source — read it in full), the output path, `{document_output_language}`, and "return ONLY the written file path." This keeps the heavy generation out of the main thread and proves the memlog is genuinely the canonical source. (Subagents can't spawn subagents — run these from here.)
+
+- **Imaginative HTML keepsake (recommended default).** A single self-contained `brainstorm.html` in `{doc_workspace}` — a genuine creative artifact, not a report poured into a template. There is no template on purpose: let *this* session's subject, energy, and whimsy drive the visual language (a children's game and a supply-chain session should not look alike). Give each technique its own treatment, invent visualizations that fit the ideas and techniques, and render the synthesis as the climax. Inline all CSS and any JS; no external dependencies. Open it once complete.
+- **Intent doc.** A succinct `brainstorm-intent.md` — the chosen and critical discoveries only, structured to drop straight into a downstream skill (`bmad-product-brief`, `bmad-prd`) as clean input, with none of the report's bloat - token usage matters and it must really be on point. Confirm what the user wants to capture as the intent from the overall findings as there may be many divergent discoveries (unless in headless mode, then take your best educated stance).
+- **Offer other options they might want from it also based on context** — a pitch, a one-pager, a task list — produced from the same source. These can be slide decks, html, markdown - again be creative and offer really interesting quality options based on perceived user needs while asking them also to offer any other ideas.
+
+If the session used invented techniques, offer to save a keeper into `{workflow.additional_techniques}` via `bmad-customize` user preferences.
+
+After producing what they chose, offer them ideas for deep-dive brainstorming new sessions, offer to fully extrapolate any ideas into an html report (autonomously brainstorm on their behalf), and most importantly: execute each `{workflow.external_handoffs}` instruction. Then share the artifact paths (and any handoff destinations), invoke `bmad-help` to suggest where this leads next in the BMad ecosystem, let them know if they feel a produced intent is detailed enough they could jump right into passing it to bmad-spec or any other analysis tool (outlined from bmad-help) and run `{workflow.on_complete}` if non-empty.
diff --git a/.claude/skills/bmad-brainstorming/references/headless.md b/.claude/skills/bmad-brainstorming/references/headless.md
new file mode 100644
index 0000000..5da9a25
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/headless.md
@@ -0,0 +1,54 @@
+# Headless Mode
+
+Load this file ONLY when bmad-brainstorming is invoked headless. It is quarantined here on purpose: headless is the single context in which you generate ideas yourself, which is the exact inverse of the interactive Stance. Loading it in a normal session would corrupt the facilitation. Follow it for the whole run.
+
+## Detection
+
+**If a human is sending messages in this session, you are interactive — no payload shape or phrasing overrides that.** Headless requires the *absence* of an interactive user. It is in effect only when one of these unambiguous machine signals holds:
+
+- the caller sets a `headless: true` flag (or the equivalent argument the harness exposes),
+- the invocation comes from another skill or a non-interactive runner (no TTY, no user message stream),
+- `{workflow.activation_steps_prepend}` includes an entry that explicitly declares headless.
+
+When in doubt, you are interactive — a present human asking you to "brainstorm X and give me the HTML" is a normal interactive opening, not a headless trigger. Facilitate them; do not brainstorm for them.
+
+## The inversion
+
+There is no user to draw ideas out of, so you become the brainstormer. Run a real divergent session against the supplied topic: discover techniques with `uv run {skill-root}/scripts/brain.py --file {workflow.brain_methods} list --all` (the whole catalog is fine here — you are generating, not pacing a user; add `show "<name>"` for a technique's full method on demand), plus any `{workflow.additional_techniques}`, preferring `{workflow.favorite_techniques}` where they fit; work them, and **shift the creative domain every ~10 ideas** exactly as the interactive Stance demands — technical, then experiential, then business, then failure modes, then wildcards. Push past the obvious; the same quantity ambition (aim past 100) and anti-clustering discipline apply. The only thing that changes is that the ideas are now yours to generate. This relaxation is scoped entirely to this file — it never applies to interactive sessions.
+
+## Inputs the caller is expected to provide
+
+Free-form structured payload in the first message; provide what applies:
+
+- `topic` — what to brainstorm. Required. If absent and uninferable, halt `blocked`.
+- `goal` — desired outcome / framing, if any.
+- `techniques` — specific methods to use; otherwise you choose fitting ones from the library.
+- `context` — file paths or text to ground the session (problem statement, prior notes, brief).
+- `doc_workspace` — a specific run folder; otherwise bind the default `{workflow.output_dir}/{workflow.output_folder_name}/`.
+- `artifacts` — which outputs to produce: `html`, `intent`, or both. Default: both.
+
+## Run
+
+1. Bind `{doc_workspace}` and create the memlog with `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<topic>" [--field goal="<goal>"]`. It remains the canonical source every artifact derives from.
+2. Run the divergent session per **The inversion**, capturing each idea with `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type idea --text "<idea>"` as it lands, and marking each technique switch with `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type technique --text "started <name>"`.
+3. Synthesize: surface the conclusions, connections, and the few directions that matter; record them with `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type insight --text "<insights>"`, then run `uv run {project-root}/_bmad/scripts/memlog.py set --workspace {doc_workspace} --key status --value complete`.
+4. Produce the requested artifacts from the log — `brainstorm.html` (the imaginative, self-contained, no-template report) and/or the succinct `brainstorm-intent.md` — the same artifacts `references/finalize.md` describes, delegating each to a subagent that reads the log as its sole source. (Headless produces the `artifacts` payload directly; it does not ask, unlike the interactive opt-in.)
+5. Execute each entry in `{workflow.external_handoffs}` (capture returned URLs/IDs into the JSON `external_handoffs` array; skip and flag unavailable tools — local files always exist). Then run `{workflow.on_complete}` if non-empty.
+
+Do not ask questions; do not greet. Record any assumption you made (a topic you had to infer, a goal you invented to frame the session) in `assumptions[]`.
+
+## Return
+
+End with a JSON status block. Use `complete` when the artifacts stand on their own, `partial` when produced but key inputs were inferred (e.g. topic was thin), `blocked` when no artifact was produced (e.g. no topic). Omit keys for artifacts not produced.
+
+```json
+{
+  "status": "complete",
+  "intent": "brainstorm",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "html": "{doc_workspace}/brainstorm.html",
+  "intent_doc": "{doc_workspace}/brainstorm-intent.md",
+  "assumptions": [],
+  "external_handoffs": []
+}
+```
diff --git a/.claude/skills/bmad-brainstorming/references/in-chat-techniques.md b/.claude/skills/bmad-brainstorming/references/in-chat-techniques.md
new file mode 100644
index 0000000..4e0e02a
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/in-chat-techniques.md
@@ -0,0 +1,18 @@
+# Choosing Techniques In Chat
+
+Loaded only when the user won't use the composer page (no browser, headless, or they declined). Here you pick the batch in conversation. **3–4 is the sweet spot.** Present the four ways below — this is the one allowed menu — and wait for their pick.
+
+- **Facilitator Chosen (default)** — from the goal, your `{workflow.favorite_techniques}`, and the `categories` map, name a batch of 3–4. Confirm exact names with a targeted `list --category` on only the categories you're drawing from; never enumerate the library to choose.
+- **Browse** — send them to the composer page after all (`## Run a Session` in `SKILL.md`); they tick techniques and paste the result back, which carries each one's full name/category/description.
+- **Category** — the user names 1–n categories; `random --category` draws the batch from them. No listing needed.
+- **Inventive Flow** — invent at least 3 techniques, announce the order before the first, touch no script. Log each one's name + description so you can offer to save a keeper to `{workflow.additional_techniques}` (via `bmad-customize`) at wrap-up.
+
+The library is large — never pull it whole into context. The only way in is the helper, always passing `--file {workflow.brain_methods}`. Subcommands of `uv run {skill-root}/scripts/brain.py --file {workflow.brain_methods}`:
+
+- `categories` — names + counts; the cheap survey map.
+- `list --category X [--category Y]` — the index (name + gist) for those categories. Bare `list` is refused by the script.
+- `random --category X [...] -n 4` — draw a batch blind, listing nothing.
+- `show "<name>"` — one technique's full method; call only the moment it is about to run.
+- `html --out <path>` — write the composer page to a file (the Browse option above).
+
+Treat `{workflow.additional_techniques}` as first-class entries (including new categories), preferring `{workflow.favorite_techniques}` where they fit. To include the additional techniques in any command, pass `--extra <json>` (a JSON list of `{category, technique_name, description}` objects). The `list` gist usually suffices to propose and run a technique; reach for `show` for deeper mechanics.
diff --git a/.claude/skills/bmad-brainstorming/references/mode-autonomous.md b/.claude/skills/bmad-brainstorming/references/mode-autonomous.md
new file mode 100644
index 0000000..1013895
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/mode-autonomous.md
@@ -0,0 +1,10 @@
+# Mode: Ideate For Me
+
+The user handed you the topic and wants to see what you come up with on your own, then look at the result. You become the brainstormer — this is the one interactive mode where the ideas are yours to generate.
+
+- **Run a real divergent session yourself.** If the user supplied techniques (e.g. a composed prompt pasted from the selector page), honor those first; otherwise pick and run techniques on your own (use `brain.py` as in `## Choosing Techniques`, but *you* choose — no menu for the user). Capture each idea to the memlog with `--type idea --by coach`, marking each technique switch with a `technique` entry, shifting the creative domain every ~10 ideas, aiming past 100. Push past the obvious.
+- **Don't pepper the user with questions** — this is your run. One quick confirm of topic and goal up front is plenty.
+- **When it's mined out, synthesize and produce the keepsake.** Go to `## Wrap-Up` (`references/finalize.md`): record the insights, mark the memlog complete, and **auto-generate the imaginative HTML keepsake — don't ask first; the keepsake is the result you promised to show them.** Offer the other artifacts (intent doc, etc.) after.
+- **Then, because a human is here, offer to keep going together.** They may want to push an idea further or react to what you found — if so, switch into **Facilitator** or **Creative Partner** (load that frame), **record the switch in the memlog** so a resume restores the new stance — `uv run {project-root}/_bmad/scripts/memlog.py set --workspace {doc_workspace} --key mode --value <facilitator|partner>` — and continue from the same memlog.
+
+This is the interactive sibling of headless mode (`references/headless.md`): the same self-generation, but a person is present to receive the output and may continue. headless is the no-human, returns-JSON runner; this one greets, presents, and hands off.
diff --git a/.claude/skills/bmad-brainstorming/references/mode-facilitator.md b/.claude/skills/bmad-brainstorming/references/mode-facilitator.md
new file mode 100644
index 0000000..1bee220
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/mode-facilitator.md
@@ -0,0 +1,11 @@
+# Mode: Facilitator
+
+You are a forcing function for the user's creativity, never a source of ideas. The best version of this session ends with the user surprised by what *they* came up with — every idea in the memlog is theirs.
+
+- **You do not supply ideas.** Your moves are questions, provocations, constraints, and reflections that make *the user* generate, while you steer within the chosen technique. When the well looks dry, don't fill it — change the technique, shift the angle, or push harder.
+- **The one exception:** if the user *directly asks* for an idea, give exactly one as a spark, then hand the pen back. Reaching for that repeatedly is the signal to change technique, not to keep feeding ideas.
+- This holds for the whole generative session; it relaxes only during synthesis at wrap-up (`references/finalize.md`).
+
+Every idea you log is the user's, so no attribution is needed — log with `--type idea` (no `--by`).
+
+Go to `## Choosing Techniques`.
diff --git a/.claude/skills/bmad-brainstorming/references/mode-partner.md b/.claude/skills/bmad-brainstorming/references/mode-partner.md
new file mode 100644
index 0000000..8477400
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/mode-partner.md
@@ -0,0 +1,16 @@
+# Mode: Creative Partner
+
+You are still the facilitator — their creativity is the point, and they do the **majority** of the generating. But here you also play: you ride alongside and throw in your own ideas as sparks and yes-and fuel, so the two of you build a chain neither would alone. The energy is collaborative, not extractive — you feed off each other.
+
+**Set it up first.** Before you start, tell the user how this mode works and that they stay in control: they can **reject any idea you offer, ask you to help more or less, and tell you how to brainstorm** — a technique to try, a tone, a direction to chase. You're a partner they can steer, not a script.
+
+Hold the balance:
+
+- **Their fire, your kindling.** After you offer an idea, hand the pen back with a question. Never run a string of your own while they go quiet.
+- **"Yes, and" is the default move.** Take what they just said, build it one rung higher, then dare them to top you. Make them *want* to outdo you.
+- **Offer real alternatives**, not leading questions — a genuine idea they can mutate or reject, an opening, never a conclusion.
+- **Watch the ratio.** If you've contributed more than they have over the last few exchanges, you've slipped toward doing it *for* them — pull back to questions and constraints.
+
+**Attribution is mandatory here.** Every idea entry records who it came from: `--by user` for theirs, `--by coach` for yours (e.g. `append --type idea --by coach --text "..."`). This keeps the record honest and lets the wrap-up hand *them* the mirror of what *they* generated.
+
+Go to `## Choosing Techniques`.
diff --git a/.claude/skills/bmad-brainstorming/references/resume.md b/.claude/skills/bmad-brainstorming/references/resume.md
new file mode 100644
index 0000000..48ff453
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/references/resume.md
@@ -0,0 +1,5 @@
+# Resuming a Session
+
+Read the chosen `{doc_workspace}/.memlog.md` **in full** — the one time you read the memlog. Frontmatter restores topic, goal, status, and **mode**: reload that mode's frame (`mode-facilitator.md` / `mode-partner.md` / `mode-autonomous.md`) and hold it again. The body restores everything generated — entries in order, `technique` entries marking which lens was active, `by` tags marking authorship.
+
+Reconstruct the picture, then reflect back where things stand (topic, what's already mined, which threads felt live) to re-establish shared state before continuing. Then continue per the mode's frame (appending to the same memlog) — or, if they're ready to land it, go to Wrap-Up (`references/finalize.md`).
diff --git a/.claude/skills/bmad-brainstorming/scripts/brain.py b/.claude/skills/bmad-brainstorming/scripts/brain.py
new file mode 100644
index 0000000..1028cf6
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/scripts/brain.py
@@ -0,0 +1,770 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""Serve the brainstorming technique library without loading it all into context.
+
+The library is a CSV (category, technique_name, description, detail). `description`
+is a short gist — enough to propose and run most techniques. `detail` is optional:
+a path (relative to the CSV's directory) to a fuller instruction file for a technique
+complex enough to warrant one. Only `show` resolves detail files, and only for the
+technique asked for — so the heavy material never enters context until it is run.
+
+Commands:
+  categories                  list category names + counts (the cheap entry point)
+  list --category C [...]      the index (name + gist) for those categories
+  list --all                  the whole index at once — deliberate; large, avoid interactively
+  show NAME [NAME ...]         full gist for each, inlining its detail file if it has one
+  random [--category C] [-n N]  pick N at random (optionally within categories)
+  html --out PATH             write the offline 'browse all' selection page to a file
+
+`list` refuses to run with neither --category nor --all, and `html` writes to a file
+rather than stdout: dumping the full catalog into context is a footgun, so reaching the
+whole library at once must always be an explicit, deliberate choice.
+
+`--extra PATH` merges a JSON overlay of additional techniques (customize.toml's
+`additional_techniques`) into every command. An extra whose technique_name matches
+a shipped row (case-insensitive) REPLACES it — retune a shipped technique; others
+append, so custom techniques and whole new categories are first-class everywhere —
+including the browse page and category draws. (Same overlay semantics as
+bmad-advanced-elicitation's pick_methods.py.)
+
+Default output is lean text for an LLM to read; pass --json for structured output.
+"""
+import argparse
+import csv
+import hashlib
+import html
+import json
+import random
+import sys
+from pathlib import Path
+
+DEFAULT_FILE = Path(__file__).resolve().parent.parent / "assets" / "brain-methods.csv"
+FIELDS = ("category", "technique_name", "description", "detail", "provenance", "good_for", "audience")
+# Optional columns beyond the original four — absent in older CSVs and in --extra
+# overlays, so always read through .get/setdefault. `provenance` (classic|signature|
+# playful) drives the "Proven & Professional" lead group; `good_for` (a |-separated
+# list of goal tags) drives the browse page's goal filter; `audience` (solo|group|either)
+# is advisory.
+OPTIONAL_FIELDS = ("detail", "provenance", "good_for", "audience")
+
+
+def load(file: Path) -> list[dict]:
+    # utf-8-sig: tolerate BOM-prefixed catalogs (Excel "CSV UTF-8", Notepad)
+    with open(file, newline="", encoding="utf-8-sig") as f:
+        rows = list(csv.DictReader(f))
+    for r in rows:
+        for k in FIELDS:
+            r.setdefault(k, "")
+            r[k] = (r.get(k) or "").strip()
+    return rows
+
+
+def load_extra(file: Path) -> list[dict]:
+    """Merge-in techniques from a JSON overlay — a list of
+    {category, technique_name, description[, detail]} objects. This is how
+    customize.toml's `additional_techniques` become first-class across *every*
+    subcommand (categories/list/random/show/html), so the browse page and
+    category draws include them too, not just the in-chat flows."""
+    data = json.loads(file.read_text(encoding="utf-8-sig"))
+    if not isinstance(data, list):
+        raise ValueError("--extra must be a JSON array of objects")
+    rows = []
+    for item in data:
+        if not isinstance(item, dict):
+            raise ValueError(f"each --extra entry must be a JSON object, got: {item!r}")
+        rows.append({
+            "category": str(item.get("category", "")).strip(),
+            "technique_name": str(item.get("technique_name", "")).strip(),
+            "description": str(item.get("description", "")).strip(),
+            "detail": str(item.get("detail") or "").strip(),
+            "provenance": str(item.get("provenance") or "").strip(),
+            "good_for": str(item.get("good_for") or "").strip(),
+            "audience": str(item.get("audience") or "").strip(),
+        })
+    return rows
+
+
+def merge_extra(rows: list[dict], extras: list[dict]) -> list[dict]:
+    """Extras replace a catalog row with the same technique_name (case-insensitive),
+    otherwise append — the same overlay semantics as pick_methods.py, so
+    customize.toml additional_* entries behave identically across sibling skills."""
+    merged = list(rows)
+    index = {r["technique_name"].lower(): i for i, r in enumerate(merged)}
+    for e in extras:
+        key = e["technique_name"].lower()
+        if key in index:
+            merged[index[key]] = e
+        else:
+            index[key] = len(merged)
+            merged.append(e)
+    return merged
+
+
+def categories(rows: list[dict]) -> list[tuple[str, int]]:
+    counts: dict[str, int] = {}
+    for r in rows:
+        counts[r["category"]] = counts.get(r["category"], 0) + 1
+    return sorted(counts.items())
+
+
+def filter_cats(rows: list[dict], cats: list[str] | None) -> list[dict]:
+    if not cats:
+        return rows
+    wanted = {c.lower() for c in cats}
+    return [r for r in rows if r["category"].lower() in wanted]
+
+
+def find(rows: list[dict], names: list[str]) -> tuple[list[dict], list[str]]:
+    by_name = {r["technique_name"].lower(): r for r in rows}
+    found, missing = [], []
+    for n in names:
+        r = by_name.get(n.strip().lower())
+        (found if r else missing).append(r if r else n)
+    return found, missing
+
+
+def resolve_detail(row: dict, csv_dir: Path) -> str | None:
+    """Return the contents of a row's detail file, or None if there is no detail
+    (or the file is missing — a missing file is reported to stderr, not fatal)."""
+    if not row.get("detail"):
+        return None
+    path = (csv_dir / row["detail"]).resolve()
+    if not path.is_file():
+        print(f"# detail file not found for {row['technique_name']}: {row['detail']}", file=sys.stderr)
+        return None
+    return path.read_text(encoding="utf-8").strip()
+
+
+def fmt_categories(cats: list[tuple[str, int]], as_json: bool) -> str:
+    if as_json:
+        return json.dumps([{"category": c, "count": n} for c, n in cats])
+    return "\n".join(f"{c}\t{n}" for c, n in cats)
+
+
+def fmt_list(rows: list[dict], as_json: bool) -> str:
+    if as_json:
+        return json.dumps([{k: r[k] for k in ("category", "technique_name", "description")} for r in rows])
+    return "\n".join(f"{r['category']}\t{r['technique_name']}\t{r['description']}" for r in rows)
+
+
+def fmt_show(rows: list[dict], csv_dir: Path, as_json: bool) -> str:
+    if as_json:
+        out = []
+        for r in rows:
+            d = resolve_detail(r, csv_dir)
+            entry = {k: r[k] for k in ("category", "technique_name", "description")}
+            if d:
+                entry["detail"] = d
+            out.append(entry)
+        return json.dumps(out)
+    blocks = []
+    for r in rows:
+        block = f"## {r['technique_name']}  [{r['category']}]\n{r['description']}"
+        d = resolve_detail(r, csv_dir)
+        if d:
+            block += f"\n\n{d}"
+        blocks.append(block)
+    return "\n\n".join(blocks)
+
+
+def pretty(cat: str) -> str:
+    """Turn a category slug (e.g. 'speculative_future') into a display name."""
+    return cat.replace("_", " ").replace("-", " ").title()
+
+
+# --- card visuals: a crafted duotone icon + hue per category, plus a per-technique icon ---
+# The hues and SVG glyphs are *data*, not logic: they live in the icon sidecar
+# (assets/brain-icons.json) so the catalog's visuals can be edited without touching code.
+# It maps category slug -> {hue, glyph} and technique name -> svg (inner markup, drawn in
+# `currentColor` which the CSS sets to the category hue; the shared CHIP frame is added by
+# the renderer). Anything missing falls back here — an unknown category gets a hash-derived
+# hue + generic glyph, an unknown/not-yet-iconed technique a neutral mark — so custom
+# catalogs always render.
+
+ICON_FILE = DEFAULT_FILE.parent / "brain-icons.json"
+
+CHIP = '<rect x="1.5" y="1.5" width="41" height="41" rx="12" fill="currentColor" fill-opacity="0.12"/>'
+
+_FALLBACK_GLYPH = (
+    '<circle cx="22" cy="22" r="11" fill="currentColor" fill-opacity="0.16"/>'
+    '<circle cx="22" cy="22" r="11" stroke="currentColor" stroke-width="1.6" fill="none"/>'
+    '<circle cx="22" cy="22" r="3.4" fill="currentColor"/>'
+)
+_FALLBACK_TECH = (
+    '<rect x="15" y="15" width="14" height="14" rx="2.5" transform="rotate(45 22 22)" '
+    'fill="none" stroke="currentColor" stroke-width="2"/><circle cx="22" cy="22" r="2.4" fill="currentColor"/>'
+)
+
+
+def _load_icons(file: Path = ICON_FILE) -> tuple[dict, dict]:
+    """Read the icon sidecar: (category slug -> {hue, glyph}, technique name -> svg).
+    A missing or malformed file is non-fatal — everything then uses the fallbacks below."""
+    try:
+        data = json.loads(file.read_text(encoding="utf-8"))
+    except (OSError, ValueError):
+        return {}, {}
+    return (data.get("categories") or {}), (data.get("techniques") or {})
+
+
+_CATEGORY_STYLES, _TECH_ICONS = _load_icons()
+
+
+def _hsl_hex(deg: int, s: float, lt: float) -> str:
+    import colorsys
+
+    r, g, b = colorsys.hls_to_rgb((deg % 360) / 360, lt, s)
+    return "#%02x%02x%02x" % (round(r * 255), round(g * 255), round(b * 255))
+
+
+def category_style(cat: str) -> tuple[str, str]:
+    """(hue, glyph markup) for a category — from the sidecar for the shipped set, derived for extras."""
+    style = _CATEGORY_STYLES.get(cat)
+    if style and style.get("hue"):
+        return style["hue"], style.get("glyph") or _FALLBACK_GLYPH
+    deg = int(hashlib.md5(cat.encode("utf-8")).hexdigest(), 16) % 360
+    return _hsl_hex(deg, 0.58, 0.52), _FALLBACK_GLYPH
+
+
+def tech_icon(name: str) -> str:
+    """The hand-picked line-icon for a specific technique (neutral mark if unknown)."""
+    return _TECH_ICONS.get(name, _FALLBACK_TECH)
+
+
+SELECTOR_TEMPLATE = r"""<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>BMad Method Brainstorming Selection</title>
+<script>
+/* set the theme before first paint so there's no light-mode flash */
+(function(){ try {
+  var t = localStorage.getItem('bmad-theme');
+  if (!t) { t = (window.matchMedia && window.matchMedia('(prefers-color-scheme: dark)').matches) ? 'dark' : 'light'; }
+  document.documentElement.setAttribute('data-theme', t);
+} catch(e){} })();
+</script>
+<style>
+  :root {
+    --bg:#f6f7fb; --surface:#fff; --ink:#1c1e2b; --muted:#6b7080;
+    --accent:#5b4bdc; --accent-ink:#5b4bdc; --warn:#c0561f;
+    --line:#e6e8f0; --control:#eef0f7; --control2:#f1f2f8; --raised:#fff;
+    --cnt:#b9bdce; --foot:#aeb2c4; --shadow:rgba(20,20,50,.06);
+  }
+  :root[data-theme="dark"] {
+    --bg:#0f1117; --surface:#171a23; --ink:#e7e9f2; --muted:#9aa0b4;
+    --accent:#6d5cf0; --accent-ink:#a99bff; --warn:#e08a4a;
+    --line:#2a2f3e; --control:#222634; --control2:#1d212d; --raised:#2c3242;
+    --cnt:#5a6076; --foot:#5a6076; --shadow:rgba(0,0,0,.45);
+  }
+  /* lift the category hue toward white on dark surfaces so deep hues stay legible */
+  :root[data-theme="dark"] section > h2 { color:color-mix(in srgb, var(--c) 62%, #fff); }
+  :root[data-theme="dark"] .tech .ico { color:color-mix(in srgb, var(--c) 68%, #fff); }
+  :root[data-theme="dark"] label.tech:has(input:checked) { border-color:color-mix(in srgb, var(--c) 60%, #fff); }
+  .titlerow { display:flex; align-items:flex-start; justify-content:space-between; gap:12px; }
+  .themebtn { flex:none; width:36px; height:36px; border-radius:9px; background:var(--control); color:var(--ink); font-size:17px; line-height:1; display:inline-flex; align-items:center; justify-content:center; }
+  .themebtn:hover { background:var(--raised); }
+  * { box-sizing:border-box; }
+  body { margin:0; font:16px/1.5 -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif; background:var(--bg); color:var(--ink); }
+  header { position:sticky; top:0; z-index:5; background:var(--surface); padding:20px 0 12px; border-bottom:1px solid var(--line); box-shadow:0 2px 12px var(--shadow); }
+  .hwrap { max-width:1120px; margin:0 auto; padding:0 24px; }  /* align header content with the card column on wide screens */
+  h1 { margin:0 0 4px; font-size:24px; letter-spacing:-.02em; }
+  .sub { margin:0 0 12px; color:var(--muted); font-size:14px; max-width:74ch; }
+  button { font:inherit; border:0; border-radius:8px; cursor:pointer; }
+  .composer { display:flex; flex-direction:column; gap:9px; margin:6px 0 12px; }
+  .grp { display:flex; gap:8px; align-items:center; flex-wrap:wrap; }
+  .glabel { font-size:11px; text-transform:uppercase; letter-spacing:.07em; color:var(--muted); min-width:74px; }
+  .modes { display:inline-flex; background:var(--control); border-radius:9px; padding:3px; gap:2px; }
+  .mode { padding:7px 13px; font-size:14px; font-weight:600; color:var(--muted); background:transparent; }
+  .mode.on { background:var(--raised); color:var(--accent-ink); box-shadow:0 1px 3px var(--shadow); }
+  .modehint { flex:1 1 240px; min-width:0; font-size:13px; color:var(--muted); font-style:italic; }
+  .pill { font-size:13px; color:var(--muted); background:var(--control); padding:6px 12px; border-radius:20px; }
+  .pill b { color:var(--accent-ink); }
+  .step { display:inline-flex; align-items:center; gap:7px; font-size:13px; color:var(--ink); background:var(--control2); padding:4px 6px 4px 12px; border-radius:20px; }
+  .step b { min-width:12px; text-align:center; font-size:14px; color:var(--ink); }
+  .step button { width:24px; height:24px; border-radius:50%; background:var(--raised); color:var(--muted); font-size:17px; line-height:22px; text-align:center; box-shadow:0 1px 2px var(--shadow); }
+  .step button:hover { color:var(--accent-ink); }
+  .total { font-size:12px; color:var(--muted); }
+  .total.warn { color:var(--warn); font-weight:600; }
+  .bar { display:flex; gap:10px 14px; align-items:center; flex-wrap:wrap; }
+  #copy { margin-left:auto; padding:9px 22px; background:var(--accent); color:#fff; font-size:14px; font-weight:700; }
+  #copy:hover { filter:brightness(1.07); }
+  .chips { flex:1 1 320px; min-width:0; display:flex; gap:7px; flex-wrap:wrap; align-items:center; }
+  .chip { font-size:12px; padding:4px 11px; border-radius:16px; border:0; color:#fff; background:var(--cc); font-weight:600; cursor:pointer; }
+  .chip:hover { filter:brightness(1.08); }
+  .banner { max-height:0; overflow:hidden; transition:max-height .25s ease, padding .22s ease, margin .22s ease; background:linear-gradient(90deg,var(--accent),#8275f2); color:#fff; border-radius:10px; font-weight:700; text-align:center; padding:0 14px; }
+  .banner.show { max-height:64px; padding:13px 14px; margin-top:10px; }
+  .banner.fail { background:linear-gradient(90deg,var(--warn),#e0894a); }
+  main { padding:18px 24px 60px; max-width:1120px; margin:0 auto; }
+  section { margin:0 0 26px; }
+  section > h2 { font-size:13px; text-transform:uppercase; letter-spacing:.08em; color:var(--c); margin:0 0 10px; border-bottom:1px solid color-mix(in srgb, var(--c) 24%, var(--line)); padding-bottom:6px; }
+  section > h2 .cnt { color:color-mix(in srgb, var(--c) 45%, var(--cnt)); margin-left:6px; }
+  .grid { display:grid; grid-template-columns:repeat(auto-fill,minmax(360px,1fr)); gap:10px; }
+  label.tech { display:flex; gap:12px; align-items:flex-start; background:color-mix(in srgb, var(--c) 5%, var(--surface)); border:1px solid color-mix(in srgb, var(--c) 18%, var(--line)); border-radius:10px; padding:11px 13px; cursor:pointer; transition:border-color .12s, box-shadow .12s, background .12s; }
+  label.tech:hover { border-color:color-mix(in srgb, var(--c) 45%, var(--surface)); }
+  label.tech input { margin-top:2px; width:17px; height:17px; accent-color:var(--c); flex:none; }
+  label.tech:has(input:checked) { border-color:var(--c); background:color-mix(in srgb, var(--c) 12%, var(--surface)); box-shadow:0 0 0 2px color-mix(in srgb, var(--c) 30%, transparent); }
+  .tech .ic2 { display:flex; gap:5px; flex:none; }
+  .tech .ico { width:40px; height:40px; flex:none; color:var(--c); }
+  .tech .n { font-weight:600; display:block; }
+  .tech .d { color:var(--muted); font-size:13.5px; display:block; margin-top:2px; }
+  .tech .gf { color:var(--accent-ink); font-size:11px; display:block; margin-top:5px; opacity:.85; }
+  .grouphdr { margin:30px 0 12px; font-size:12px; text-transform:uppercase; letter-spacing:.14em; font-weight:700; color:var(--c); opacity:.92; border-bottom:1px solid color-mix(in srgb, var(--c) 22%, var(--line)); padding-bottom:7px; }
+  main > .grouphdr:first-child { margin-top:2px; }
+  :root[data-theme="dark"] .grouphdr { color:color-mix(in srgb, var(--c) 62%, #fff); }
+  .goals { display:flex; gap:7px; flex-wrap:wrap; }
+  .goal { font-size:12px; padding:5px 12px; border-radius:16px; background:var(--control); color:var(--muted); font-weight:600; }
+  .goal:hover { color:var(--ink); }
+  .goal.on { background:var(--accent); color:#fff; }
+  label.tech.invent { border-style:dashed; background:transparent; }
+  label.tech.invent:hover { border-color:var(--c); }
+  label.tech.invent .n { color:var(--c); }
+  label.tech.hidden { display:none; }
+  footer { text-align:center; color:var(--foot); font-size:12px; padding:24px; }
+</style>
+</head>
+<body>
+<header>
+  <div class="hwrap">
+  <div class="titlerow">
+    <h1>BMad Method Brainstorming Selection</h1>
+    <button id="theme" class="themebtn" type="button" aria-label="Toggle dark mode" title="Toggle dark mode"></button>
+  </div>
+  <p class="sub">Compose your session, hit <strong>Copy prompt</strong>, and paste it back into the chat to begin. {{TOTAL}}</p>
+
+  <div class="composer">
+    <div class="grp">
+      <span class="glabel">Facilitation</span>
+      <div class="modes" id="modes">
+        <button type="button" class="mode on" data-mode="Facilitator">Facilitator</button>
+        <button type="button" class="mode" data-mode="Creative Partner">Creative Partner</button>
+        <button type="button" class="mode" data-mode="Ideate for me">Ideate for me</button>
+      </div>
+      <span class="modehint" id="modehint"></span>
+    </div>
+    <div class="grp">
+      <span class="glabel">Techniques</span>
+      <span class="pill">Picked <b id="pickN">0</b></span>
+      <span class="step">Random <button type="button" data-step="rand" data-d="-1">&minus;</button><b id="randN">0</b><button type="button" data-step="rand" data-d="1">+</button></span>
+      <span class="step">Invent <button type="button" data-step="inv" data-d="-1">&minus;</button><b id="invN">0</b><button type="button" data-step="inv" data-d="1">+</button></span>
+      <span class="step">AI picks <button type="button" data-step="ai" data-d="-1">&minus;</button><b id="aiN">0</b><button type="button" data-step="ai" data-d="1">+</button></span>
+      <span class="total" id="total">Total 0 &middot; 3&ndash;4 is the sweet spot</span>
+      <button id="copy" type="button">Copy prompt</button>
+    </div>
+  </div>
+
+  {{GOALBAR}}
+  <div class="bar">
+    <span class="glabel">Jump to</span>
+    <div class="chips" id="chips">{{CHIPS}}</div>
+  </div>
+
+  <div class="banner" id="banner">&#10003; Copied! Now paste it into the chat to start your session.</div>
+  </div>
+</header>
+<main>
+{{BODY}}
+</main>
+<footer>BMad Method &middot; Brainstorming</footer>
+<script>
+(function(){
+  var $ = function(id){ return document.getElementById(id); };
+  var all = Array.prototype.slice;
+  var boxes = all.call(document.querySelectorAll('input[type=checkbox]'));
+  var techBoxes = boxes.filter(function(b){ return b.dataset.name; });      // real technique cards
+  var inventBoxes = boxes.filter(function(b){ return b.dataset.invent; });  // per-category "invent in the spirit of" cards
+  var header = document.querySelector('header');
+  var sections = all.call(document.querySelectorAll('section'));
+  var state = { mode: 'Facilitator', rand: 0, inv: 0, ai: 0 };
+  var MODE_HINTS = {
+    'Facilitator': 'A forcing function for your ideas — I prompt and push, but never supply them.',
+    'Creative Partner': 'We riff together — I facilitate and add ideas too, each logged as yours or mine.',
+    'Ideate for me': 'I run the whole session myself, then show you the result and offer to keep going.'
+  };
+  function setHint(){ $('modehint').textContent = MODE_HINTS[state.mode] || ''; }
+
+  var themeBtn = $('theme');
+  function setThemeIcon(){ themeBtn.textContent = document.documentElement.getAttribute('data-theme') === 'dark' ? '☀' : '☾'; }
+  themeBtn.addEventListener('click', function(){
+    var next = document.documentElement.getAttribute('data-theme') === 'dark' ? 'light' : 'dark';
+    document.documentElement.setAttribute('data-theme', next);
+    try { localStorage.setItem('bmad-theme', next); } catch(e){}
+    setThemeIcon();
+  });
+
+  all.call(document.querySelectorAll('.mode')).forEach(function(b){
+    b.addEventListener('click', function(){
+      all.call(document.querySelectorAll('.mode')).forEach(function(m){ m.classList.remove('on'); });
+      b.classList.add('on');
+      state.mode = b.dataset.mode;
+      setHint();
+    });
+  });
+
+  all.call(document.querySelectorAll('[data-step]')).forEach(function(btn){
+    btn.addEventListener('click', function(){
+      var k = btn.dataset.step, d = parseInt(btn.dataset.d, 10);
+      state[k] = Math.max(0, state[k] + d);
+      update();
+    });
+  });
+
+  // Category chips are jump-nav: click one to smooth-scroll its section into view,
+  // offsetting by the sticky header's height so the heading isn't hidden beneath it.
+  all.call(document.querySelectorAll('.chip')).forEach(function(chip){
+    chip.addEventListener('click', function(){
+      var sec = null;
+      for (var i = 0; i < sections.length; i++){ if (sections[i].dataset.cat === chip.dataset.cat){ sec = sections[i]; break; } }
+      if (!sec){ return; }
+      var top = sec.getBoundingClientRect().top + window.pageYOffset - header.offsetHeight - 8;
+      window.scrollTo({ top: top, behavior: 'smooth' });
+    });
+  });
+
+  boxes.forEach(function(b){ b.addEventListener('change', update); });
+
+  // A `classic` technique appears twice (lead "Proven & Professional" group + its home
+  // category), so de-dupe checked picks by name; the lead copy carries data-lead.
+  function checkedTech(){
+    var seen = {}, out = [];
+    techBoxes.forEach(function(b){
+      if (!b.checked || seen[b.dataset.name]) { return; }
+      seen[b.dataset.name] = 1;
+      out.push(b);
+    });
+    return out;
+  }
+  function checkedInvent(){ return inventBoxes.filter(function(b){ return b.checked; }); }
+
+  function update(){
+    // rand can't exceed what the pool can supply — keep the counter honest with the draw
+    if (state.rand > randomPool().length){ state.rand = randomPool().length; }
+    $('pickN').textContent = checkedTech().length;
+    $('randN').textContent = state.rand;
+    $('invN').textContent = state.inv;
+    $('aiN').textContent = state.ai;
+    var total = checkedTech().length + state.rand + state.inv + checkedInvent().length + state.ai;
+    var t = $('total');
+    t.textContent = 'Total ' + total + ' · 3–4 is the sweet spot';
+    t.classList.toggle('warn', total > 5);
+  }
+
+  // "Great for" goal filter: clicking a goal narrows visible cards to those tagged with it.
+  var goalBtns = all.call(document.querySelectorAll('.goal'));
+  function activeGoals(){ return goalBtns.filter(function(b){ return b.classList.contains('on'); }).map(function(b){ return b.dataset.goal; }); }
+  function applyFilter(){
+    var act = activeGoals();
+    all.call(document.querySelectorAll('label.tech')).forEach(function(lab){
+      var inp = lab.querySelector('input');
+      if (inp.dataset.invent){ return; }  // invent cards aren't goal-tagged — always visible
+      var good = (inp.dataset.good || '').split('|');
+      var show = !act.length || act.some(function(g){ return good.indexOf(g) >= 0; });
+      lab.classList.toggle('hidden', !show);
+    });
+  }
+  goalBtns.forEach(function(b){ b.addEventListener('click', function(){ b.classList.toggle('on'); applyFilter(); }); });
+
+  function randomPool(){
+    var picked = {};
+    checkedTech().forEach(function(b){ picked[b.dataset.name] = 1; });
+    // draw from unchecked, non-lead copies, skipping anything already picked
+    return techBoxes.filter(function(b){ return !b.checked && !b.dataset.lead && !picked[b.dataset.name]; });
+  }
+
+  function sample(arr, n){
+    var a = arr.slice(), out = [];
+    while (out.length < n && a.length){ out.push(a.splice(Math.floor(Math.random() * a.length), 1)[0]); }
+    return out;
+  }
+
+  function compose(){
+    var picks = checkedTech().map(function(b){ return { n: b.dataset.name, c: b.dataset.cat, d: b.dataset.desc, r: false }; });
+    var rnd = sample(randomPool(), state.rand).map(function(b){ return { n: b.dataset.name, c: b.dataset.cat, d: b.dataset.desc, r: true }; });
+    var techs = picks.concat(rnd);
+    var L = ["Let's run my brainstorming session.", "", 'Facilitation mode: ' + state.mode + '.'];
+    if (techs.length){
+      L.push("", 'Techniques to use:');
+      techs.forEach(function(t, i){
+        L.push((i + 1) + '.' + (t.r ? ' (random pick)' : '') + ' ' + t.n + '  ·  ' + t.c);
+        L.push('   ' + t.d);
+      });
+    }
+    var extra = [];
+    if (state.inv > 0){ extra.push('invent ' + state.inv + ' brand-new technique' + (state.inv > 1 ? 's' : '') + ' on the fly'); }
+    checkedInvent().forEach(function(b){ extra.push('invent 1 new technique in the spirit of ' + b.dataset.invent); });
+    if (state.ai > 0){ extra.push('you choose ' + state.ai + ' more technique' + (state.ai > 1 ? 's' : '') + ' that fit my goal'); }
+    if (extra.length){ L.push("", 'Then: ' + extra.join('; and ') + '.'); }
+    if (!techs.length && !extra.length){
+      L.push("", state.mode === 'Ideate for me'
+        ? 'Run the whole session yourself — pick the techniques, generate the ideas, then show me the result.'
+        : 'Help me choose 3–4 techniques to start.');
+    }
+    return L.join('\n');
+  }
+
+  function fallbackCopy(t){
+    var ta = document.createElement('textarea');
+    ta.value = t; ta.style.position = 'fixed'; ta.style.opacity = '0';
+    document.body.appendChild(ta); ta.focus(); ta.select();
+    var ok = false;
+    try { ok = document.execCommand('copy'); } catch(e){ ok = false; }
+    document.body.removeChild(ta);
+    return ok;
+  }
+
+  function flash(ok, text){
+    var b = $('banner');
+    b.classList.toggle('fail', !ok);
+    b.innerHTML = ok
+      ? '✓ Copied! Now paste it into the chat to start your session.'
+      : '⚠ Couldn’t reach the clipboard — copy the text in the box, then paste it into the chat.';
+    b.classList.add('show');
+    setTimeout(function(){ b.classList.remove('show'); }, 4500);
+    // Last resort on a hard failure: a prefilled, selectable prompt so the text is never lost.
+    if (!ok){ window.prompt('Copy this, then paste it into the chat:', text); }
+  }
+
+  $('copy').addEventListener('click', function(){
+    var text = compose();
+    if (navigator.clipboard && navigator.clipboard.writeText){
+      navigator.clipboard.writeText(text).then(
+        function(){ flash(true, text); },
+        function(){ flash(fallbackCopy(text), text); }
+      );
+    } else { flash(fallbackCopy(text), text); }
+  });
+
+  setHint();
+  setThemeIcon();
+  update();
+})();
+</script>
+</body>
+</html>
+"""
+
+
+# --- browse-page layout: a "Proven & Professional" lead group, then super-groups ----------
+CLASSIC_GROUP = "Proven & Professional"
+LEAD_HUE = "#3d4f73"  # a dignified slate for the professional lead group
+
+# Super-group order for the shipped categories. Categories not listed (e.g. user-added
+# via --extra) render last under "More", alphabetically — so custom catalogs always show.
+CATEGORY_GROUPS = (
+    ("Structured & Analytical", ("structured", "deep")),
+    ("Creative & Generative", ("creative", "biomimetic", "cultural", "speculative_future", "quantum")),
+    ("Wild & Playful", ("wild", "absurdist", "theatrical", "constraint")),
+    ("Introspective & Personal", ("introspective_delight", "collaborative")),
+)
+
+# Human labels for the `good_for` goal tags; this dict's order is the filter-bar order.
+GOAL_LABELS = {
+    "feature": "Build a feature",
+    "novel": "Novel concept",
+    "strategy": "Strategy",
+    "planning": "Planning",
+    "diagnosis": "Diagnose",
+    "personal": "Personal / life",
+    "unstuck": "Get unstuck",
+}
+
+
+def _good_for_label(good: str) -> str:
+    parts = [GOAL_LABELS.get(g, g) for g in good.split("|") if g]
+    return ("Great for: " + " · ".join(parts)) if parts else ""
+
+
+def _svg(inner: str) -> str:
+    return f'<svg class="ico" viewBox="0 0 44 44" xmlns="http://www.w3.org/2000/svg">{CHIP}{inner}</svg>'
+
+
+def _card(r: dict, lead: bool = False) -> str:
+    """One technique card. `lead=True` cards live in the cross-cutting professional group;
+    they carry their own category hue (inline --c) and data-lead so selection can de-dupe."""
+    name = html.escape(r["technique_name"])
+    desc = html.escape(r["description"])
+    hue, glyph = category_style(r["category"])
+    disp_cat = html.escape(pretty(r["category"]))
+    good = html.escape(r.get("good_for", ""))
+    prov = html.escape(r.get("provenance", ""))
+    style = f' style="--c:{hue}"' if lead else ""
+    lead_attr = ' data-lead="1"' if lead else ""
+    gf = _good_for_label(r.get("good_for", ""))
+    gf_html = f'<span class="gf">{html.escape(gf)}</span>' if gf else ""
+    return (
+        f'<label class="tech"{style}><input type="checkbox" '
+        f'data-name="{name}" data-cat="{disp_cat}" data-desc="{desc}" data-good="{good}" data-prov="{prov}"{lead_attr}>'
+        f'<span class="ic2">{_svg(glyph)}{_svg(tech_icon(r["technique_name"]))}</span>'
+        f'<span><span class="n">{name}</span><span class="d">{desc}</span>{gf_html}</span></label>'
+    )
+
+
+def _invent_card(disp_cat: str, glyph: str) -> str:
+    """A dashed 'invent on the fly, in this category's spirit' card appended to each section."""
+    return (
+        f'<label class="tech invent"><input type="checkbox" data-invent="{disp_cat}">'
+        f'<span class="ic2">{_svg(glyph)}</span>'
+        f'<span><span class="n">✨ Invent a {disp_cat} technique</span>'
+        f'<span class="d">Make up a brand-new technique on the fly, in the spirit of {disp_cat}</span></span></label>'
+    )
+
+
+def html_doc(rows: list[dict]) -> str:
+    """Render the self-contained 'browse all techniques' selection page from the catalog.
+
+    Deterministic ordering so the shipped asset can be snapshot-tested against the CSV:
+    a cross-cutting "Proven & Professional" lead group (every `classic`-tagged row), then
+    the categories in fixed super-group order, then any unlisted/custom categories under
+    "More" alphabetically. Techniques render in file order within a category. A `classic`
+    row appears both in the lead group and its home category; the page de-dupes on select.
+    """
+    groups: dict[str, list[dict]] = {}
+    for r in rows:
+        groups.setdefault(r["category"], []).append(r)
+
+    body: list[str] = []
+    chips: list[str] = []
+
+    def add_section(cat: str) -> None:
+        hue, glyph = category_style(cat)
+        disp = html.escape(pretty(cat))
+        cards = [_card(r) for r in groups[cat]]
+        cards.append(_invent_card(disp, glyph))
+        chips.append(f'<button type="button" class="chip" data-cat="{disp}" style="--cc:{hue}">{disp}</button>')
+        body.append(
+            f'<section data-cat="{disp}" style="--c:{hue}"><h2>{disp}<span class="cnt">{len(groups[cat])}</span></h2>'
+            f'<div class="grid">{"".join(cards)}</div></section>'
+        )
+
+    # 1) lead group — every classic-tagged technique, cross-category (no invent card here)
+    classics = [r for r in rows if r.get("provenance", "").lower() == "classic"]
+    if classics:
+        disp = html.escape(CLASSIC_GROUP)
+        lead_cards = "".join(_card(r, lead=True) for r in classics)
+        chips.append(f'<button type="button" class="chip" data-cat="{disp}" style="--cc:{LEAD_HUE}">{disp}</button>')
+        body.append(
+            f'<section data-cat="{disp}" style="--c:{LEAD_HUE}"><h2>{disp}<span class="cnt">{len(classics)}</span></h2>'
+            f'<div class="grid">{lead_cards}</div></section>'
+        )
+
+    # 2) shipped categories, in super-group order
+    placed = set()
+    for group_title, cats in CATEGORY_GROUPS:
+        present = [c for c in cats if c in groups]
+        if not present:
+            continue
+        hue, _ = category_style(present[0])
+        body.append(f'<h2 class="grouphdr" style="--c:{hue}">{html.escape(group_title)}</h2>')
+        for c in present:
+            add_section(c)
+            placed.add(c)
+
+    # 3) leftover (custom / --extra) categories, alphabetically
+    leftover = sorted(c for c in groups if c not in placed)
+    if leftover:
+        body.append('<h2 class="grouphdr" style="--c:#8a8f9e">More</h2>')
+        for c in leftover:
+            add_section(c)
+
+    # goal-affinity filter bar — only if the catalog actually carries good_for tags
+    present_goals: set[str] = set()
+    for r in rows:
+        for g in (r.get("good_for", "") or "").split("|"):
+            if g:
+                present_goals.add(g)
+    goalbar = ""
+    if present_goals:
+        ordered = [g for g in GOAL_LABELS if g in present_goals] + sorted(present_goals - set(GOAL_LABELS))
+        gchips = "".join(
+            f'<button type="button" class="goal" data-goal="{html.escape(g)}">{html.escape(GOAL_LABELS.get(g, g))}</button>'
+            for g in ordered
+        )
+        goalbar = f'<div class="bar"><span class="glabel">Great for</span><div class="goals" id="goals">{gchips}</div></div>'
+
+    total = html.escape(f"{len(rows)} techniques across {len(groups)} categories.")
+    return (
+        SELECTOR_TEMPLATE.replace("{{BODY}}", "\n".join(body))
+        .replace("{{CHIPS}}", "".join(chips))
+        .replace("{{GOALBAR}}", goalbar)
+        .replace("{{TOTAL}}", total)
+    )
+
+
+def main(argv: list[str] | None = None) -> int:
+    p = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
+    p.add_argument("--file", type=Path, default=DEFAULT_FILE, help="technique CSV (default: sibling assets/brain-methods.csv)")
+    p.add_argument("--extra", type=Path, help="JSON overlay of additional techniques (customize.toml additional_techniques), merged into every command")
+    p.add_argument("--json", action="store_true", help="emit structured JSON instead of lean text")
+    sub = p.add_subparsers(dest="cmd", required=True)
+    sub.add_parser("categories", help="list category names + counts")
+    pl = sub.add_parser("list", help="the index: category/name/gist (needs --category or --all)")
+    pl.add_argument("--category", action="append", help="filter to a category (repeatable)")
+    pl.add_argument("--all", action="store_true", help="dump the entire catalog (deliberate; large)")
+    ps = sub.add_parser("show", help="full gist + detail file for named techniques")
+    ps.add_argument("names", nargs="+")
+    pr = sub.add_parser("random", help="pick techniques at random")
+    pr.add_argument("--category", action="append", help="restrict to a category (repeatable)")
+    pr.add_argument("-n", type=int, default=1, help="how many (default 1)")
+    ph = sub.add_parser("html", help="write the offline 'browse all' selection page")
+    ph.add_argument("--out", help="file to write the page to (required; never prints the catalog)")
+    args = p.parse_args(argv)
+
+    if not args.file.is_file():
+        print(f"error: technique file not found: {args.file}", file=sys.stderr)
+        return 2
+    rows = load(args.file)
+    if args.extra:
+        if not args.extra.is_file():
+            print(f"error: --extra file not found: {args.extra}", file=sys.stderr)
+            return 2
+        try:
+            rows = merge_extra(rows, load_extra(args.extra))
+        except (OSError, ValueError) as e:
+            print(f"error: could not read --extra: {e}", file=sys.stderr)
+            return 2
+    csv_dir = args.file.resolve().parent
+
+    if args.cmd == "categories":
+        print(fmt_categories(categories(rows), args.json))
+    elif args.cmd == "list":
+        if not args.category and not args.all:
+            print(
+                "error: `list` needs --category (one or more) — or --all to dump the whole "
+                "catalog on purpose. Use `categories` for the cheap map, or `random` to draw blind.",
+                file=sys.stderr,
+            )
+            return 2
+        print(fmt_list(filter_cats(rows, args.category), args.json))
+    elif args.cmd == "show":
+        found, missing = find(rows, args.names)
+        for m in missing:
+            print(f"# not found: {m}", file=sys.stderr)
+        if not found:
+            return 1
+        print(fmt_show(found, csv_dir, args.json))
+    elif args.cmd == "random":
+        pool = filter_cats(rows, args.category)
+        if not pool:
+            print("# no techniques match", file=sys.stderr)
+            return 1
+        n = max(0, min(args.n, len(pool)))  # clamp: never crash on a negative or oversized -n
+        print(fmt_list(random.sample(pool, n), args.json))
+    elif args.cmd == "html":
+        if not args.out:
+            print(
+                "error: `html` needs --out PATH — it writes the selection page to a file and "
+                "never prints the catalog to stdout (which would defeat the point).",
+                file=sys.stderr,
+            )
+            return 2
+        out = Path(args.out)
+        out.parent.mkdir(parents=True, exist_ok=True)
+        out.write_text(html_doc(rows), encoding="utf-8")
+        print(f"wrote {out} ({len(rows)} techniques, {len(categories(rows))} categories)")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/.claude/skills/bmad-brainstorming/scripts/tests/test_brain.py b/.claude/skills/bmad-brainstorming/scripts/tests/test_brain.py
new file mode 100644
index 0000000..329a6a5
--- /dev/null
+++ b/.claude/skills/bmad-brainstorming/scripts/tests/test_brain.py
@@ -0,0 +1,239 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0"]
+# ///
+"""Tests for brain.py. Run: uv run -m pytest scripts/tests/test_brain.py"""
+import json
+import sys
+from pathlib import Path
+
+import pytest
+
+sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
+import brain  # noqa: E402
+
+CSV = """category,technique_name,description,detail
+collaborative,Yes And Building,Build on every idea with "yes and" to keep momentum,
+wild,Quantum Superposition,Hold contradictory ideas as simultaneously true,techniques/quantum.md
+structured,SCAMPER Method,Run the idea through seven transformation lenses,
+wild,Anti-Solution,Brainstorm how to make the problem worse then invert,
+"""
+
+DETAIL = "# Quantum Superposition\nFull multi-step instructions for the complex technique."
+
+
+@pytest.fixture
+def lib(tmp_path):
+    csv_path = tmp_path / "brain-methods.csv"
+    csv_path.write_text(CSV, encoding="utf-8")
+    (tmp_path / "techniques").mkdir()
+    (tmp_path / "techniques" / "quantum.md").write_text(DETAIL, encoding="utf-8")
+    return csv_path
+
+
+def test_load_normalizes_detail(lib):
+    rows = brain.load(lib)
+    assert len(rows) == 4
+    assert rows[0]["detail"] == ""
+    assert rows[1]["detail"] == "techniques/quantum.md"
+
+
+def test_categories_counts_sorted(lib):
+    assert brain.categories(brain.load(lib)) == [("collaborative", 1), ("structured", 1), ("wild", 2)]
+
+
+def test_filter_is_case_insensitive(lib):
+    rows = brain.filter_cats(brain.load(lib), ["WILD"])
+    assert {r["technique_name"] for r in rows} == {"Quantum Superposition", "Anti-Solution"}
+
+
+def test_filter_none_returns_all(lib):
+    assert len(brain.filter_cats(brain.load(lib), None)) == 4
+
+
+def test_find_hits_and_misses(lib):
+    found, missing = brain.find(brain.load(lib), ["scamper method", "Nope"])
+    assert [r["technique_name"] for r in found] == ["SCAMPER Method"]
+    assert missing == ["Nope"]
+
+
+def test_resolve_detail_present(lib):
+    row = next(r for r in brain.load(lib) if r["detail"])
+    assert "multi-step instructions" in brain.resolve_detail(row, lib.parent)
+
+
+def test_resolve_detail_absent_is_none(lib):
+    row = next(r for r in brain.load(lib) if not r["detail"])
+    assert brain.resolve_detail(row, lib.parent) is None
+
+
+def test_resolve_detail_missing_file_warns_not_fatal(lib, capsys):
+    rows = brain.load(lib)
+    rows[1]["detail"] = "techniques/gone.md"
+    assert brain.resolve_detail(rows[1], lib.parent) is None
+    assert "not found" in capsys.readouterr().err
+
+
+def test_show_inlines_detail(lib, capsys):
+    assert brain.main(["--file", str(lib), "show", "Quantum Superposition"]) == 0
+    out = capsys.readouterr().out
+    assert "multi-step instructions" in out and "[wild]" in out
+
+
+def test_show_simple_has_no_detail(lib, capsys):
+    brain.main(["--file", str(lib), "show", "SCAMPER Method"])
+    out = capsys.readouterr().out
+    assert "transformation lenses" in out
+
+
+def test_show_all_missing_returns_1(lib):
+    assert brain.main(["--file", str(lib), "show", "Ghost"]) == 1
+
+
+def test_list_filtered_text(lib, capsys):
+    brain.main(["--file", str(lib), "list", "--category", "structured"])
+    out = capsys.readouterr().out.strip().splitlines()
+    assert len(out) == 1 and out[0].startswith("structured\tSCAMPER Method\t")
+
+
+def test_list_bare_is_refused(lib, capsys):
+    # the footgun: bare `list` must NOT dump the catalog into context
+    assert brain.main(["--file", str(lib), "list"]) == 2
+    captured = capsys.readouterr()
+    assert captured.out == ""  # nothing leaked to stdout
+    assert "--category" in captured.err and "--all" in captured.err
+
+
+def test_list_all_dumps_everything(lib, capsys):
+    assert brain.main(["--file", str(lib), "list", "--all"]) == 0
+    out = capsys.readouterr().out.strip().splitlines()
+    assert len(out) == 4  # the deliberate full-catalog escape hatch
+
+
+def test_json_output(lib, capsys):
+    import json
+    brain.main(["--file", str(lib), "--json", "categories"])
+    data = json.loads(capsys.readouterr().out)
+    assert {"category": "wild", "count": 2} in data
+
+
+def test_random_respects_n_and_category(lib, capsys):
+    brain.main(["--file", str(lib), "random", "--category", "wild", "-n", "5"])
+    lines = capsys.readouterr().out.strip().splitlines()
+    assert len(lines) == 2  # only 2 wild exist, n capped
+    assert all(line.startswith("wild\t") for line in lines)
+
+
+def test_random_negative_n_does_not_crash(lib, capsys):
+    # a negative -n is clamped to 0, not passed to random.sample (which would raise)
+    assert brain.main(["--file", str(lib), "random", "-n", "-1"]) == 0
+    assert capsys.readouterr().out.strip() == ""
+
+
+def test_missing_file_returns_2(tmp_path):
+    assert brain.main(["--file", str(tmp_path / "nope.csv"), "categories"]) == 2
+
+
+# --- html selection page ------------------------------------------------
+
+def test_html_requires_out(lib, capsys):
+    # never dump the catalog to stdout — writing to a file is the whole point
+    assert brain.main(["--file", str(lib), "html"]) == 2
+    assert "--out" in capsys.readouterr().err
+
+
+def test_html_writes_selection_page(lib, tmp_path):
+    out = tmp_path / "sel.html"
+    assert brain.main(["--file", str(lib), "html", "--out", str(out)]) == 0
+    doc = out.read_text(encoding="utf-8")
+    assert doc.startswith("<!DOCTYPE html>")
+    assert "BMad Method Brainstorming Selection" in doc
+    for r in brain.load(lib):
+        assert r["technique_name"] in doc  # every technique is selectable
+    assert "&quot;yes and&quot;" in doc  # quotes in a description are escaped, not raw
+
+
+def test_html_creates_missing_parent(lib, tmp_path):
+    out = tmp_path / "nested" / "deep" / "sel.html"
+    assert brain.main(["--file", str(lib), "html", "--out", str(out)]) == 0
+    assert out.is_file()
+
+
+# --- --extra overlay (customize.toml additional_techniques) -------------
+
+EXTRA = (
+    '[{"category": "domain-specific", "technique_name": "Regulatory Inversion", '
+    '"description": "Start from the compliance constraint and brainstorm what it unlocks."}, '
+    '{"category": "wild", "technique_name": "Extra Wild One", "description": "An added wild method."}]'
+)
+
+
+@pytest.fixture
+def extra(tmp_path):
+    p = tmp_path / "extra.json"
+    p.write_text(EXTRA, encoding="utf-8")
+    return p
+
+
+def test_extra_merges_into_categories(lib, extra, capsys):
+    brain.main(["--file", str(lib), "--extra", str(extra), "categories"])
+    out = capsys.readouterr().out
+    assert "domain-specific\t1" in out  # a brand-new category appears
+    assert "wild\t3" in out  # the extra wild one is counted alongside the shipped two
+
+
+def test_extra_appears_in_list_and_random(lib, extra, capsys):
+    brain.main(["--file", str(lib), "--extra", str(extra), "list", "--category", "domain-specific"])
+    assert "Regulatory Inversion" in capsys.readouterr().out
+
+
+def test_extra_replaces_shipped_row_by_name(lib, extra, tmp_path, capsys):
+    shipped = brain.load(Path(lib))[0]
+    overlay = tmp_path / "replace.json"
+    overlay.write_text(
+        json.dumps([{"category": shipped["category"], "technique_name": shipped["technique_name"], "description": "RETUNED"}]),
+        encoding="utf-8",
+    )
+    brain.main(["--file", str(lib), "--extra", str(overlay), "list", "--all"])
+    out = capsys.readouterr().out
+    assert "RETUNED" in out
+    assert out.count(shipped["technique_name"]) == 1  # replaced, not duplicated
+
+
+def test_extra_malformed_exits_cleanly(lib, tmp_path, capsys):
+    bad = tmp_path / "bad.json"
+    for content in ('{not json', '{"a": 1}', '["not-an-object"]'):
+        bad.write_text(content, encoding="utf-8")
+        assert brain.main(["--file", str(lib), "--extra", str(bad), "categories"]) == 2
+        assert "could not read --extra" in capsys.readouterr().err
+
+
+def test_extra_is_first_class_in_html(lib, extra, tmp_path):
+    out = tmp_path / "sel.html"
+    assert brain.main(["--file", str(lib), "--extra", str(extra), "html", "--out", str(out)]) == 0
+    doc = out.read_text(encoding="utf-8")
+    # custom technique is selectable and its new category renders without crashing (fallback glyph/hue)
+    assert "Regulatory Inversion" in doc
+    assert "Domain Specific" in doc
+
+
+def test_extra_missing_file_returns_2(lib, tmp_path):
+    assert brain.main(["--file", str(lib), "--extra", str(tmp_path / "nope.json"), "categories"]) == 2
+
+
+def test_unknown_category_style_uses_fallback_glyph():
+    hue, glyph = brain.category_style("totally-made-up-category")
+    assert hue.startswith("#") and len(hue) == 7  # valid derived hex
+    assert glyph == brain._FALLBACK_GLYPH
+
+
+def test_shipped_selector_is_in_sync_with_catalog():
+    # foolproofing: if someone edits brain-methods.csv they must regenerate the page.
+    # Regenerate with: uv run brain.py html --out assets/brain-selector.html
+    asset = brain.DEFAULT_FILE.parent / "brain-selector.html"
+    assert asset.is_file(), "missing assets/brain-selector.html — generate it"
+    expected = brain.html_doc(brain.load(brain.DEFAULT_FILE))
+    assert asset.read_text(encoding="utf-8") == expected, (
+        "assets/brain-selector.html is stale; regenerate: "
+        "uv run brain.py html --out assets/brain-selector.html"
+    )
diff --git a/.claude/skills/bmad-build-auto/SKILL.md b/.claude/skills/bmad-build-auto/SKILL.md
new file mode 100644
index 0000000..193d367
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/SKILL.md
@@ -0,0 +1,13 @@
+---
+name: bmad-build-auto
+description: 'One iteration of an unattended development loop. Use when invoked by name.'
+---
+
+Run the following command exactly once without changing the current working directory. Replace `{project-root}` with the absolute path to the project root and `{skill-root}` with the absolute path to this skill's directory:
+
+```bash
+uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"
+```
+
+- On success, read and follow the one absolute `workflow.md` instruction printed to stdout.
+- On failure (including `uv` being unavailable), report the command output and HALT. Do not run any workflow source directly.
diff --git a/.claude/skills/bmad-build-auto/compile-epic-context.md b/.claude/skills/bmad-build-auto/compile-epic-context.md
new file mode 100644
index 0000000..d920761
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/compile-epic-context.md
@@ -0,0 +1,62 @@
+# Compile Epic Context
+
+**Task**
+Given an epic number, the epics file, the planning artifacts directory, and a desired output path, compile a clean, focused, developer-ready context file (`epic-<N>-context.md`).
+
+**Steps**
+
+1. Read the epics file and extract the target epic's title, goal, and list of stories.
+2. Scan the planning artifacts directory for the standard files (PRD, architecture, UX/design, product brief).
+3. Pull only the information relevant to this epic.
+4. Write the compiled context to the exact output path using the format below.
+
+## Exact Output Format
+
+Use these headings:
+
+```markdown
+# Epic {N} Context: {Epic Title}
+
+<!-- Generated from planning artifacts. Regenerate with compile-epic-context if planning docs change. -->
+
+## Goal
+
+{One clear paragraph: what this epic achieves and why it matters.}
+
+## Stories
+
+- Story X.Y: Brief title only
+- ...
+
+## Requirements & Constraints
+
+{Relevant functional/non-functional requirements and success criteria for this epic (describe by purpose, not source).}
+
+## Technical Decisions
+
+{Key architecture decisions, constraints, patterns, data models, and conventions relevant to this epic.}
+
+## UX & Interaction Patterns
+
+{Relevant UX flows, interaction patterns, and design constraints (omit section entirely if nothing relevant).}
+
+## Cross-Story Dependencies
+
+{Dependencies between stories in this epic or with other epics/systems (omit if none).}
+```
+
+## Rules
+
+- **Scope aggressively.** Include only what a developer working on any story in this epic actually needs. When in doubt, leave it out — the developer can always read the full planning doc.
+- **Describe by purpose, not by source.** Write "API responses must include pagination metadata" not "Per PRD section 3.2.1, pagination is required." Planning doc internals will change; the constraint won't.
+- **No full copies.** Never quote source documents, section numbers, or paste large blocks verbatim. Always distill.
+- **No story-level details.** The story list is for orientation only. Individual story specs handle the details.
+- **Nothing derivable from the codebase.** Don't document what a developer can learn by reading the code.
+- **Be concise and actionable.** Target 800–1500 tokens total. This file loads into bmad-build-auto's context alongside other material.
+- **Never hallucinate content.** If source material doesn't say something, don't invent it.
+- **Omit empty sections entirely**, except Goal and Stories, which are always required.
+
+## Error handling
+
+- **If the epics file is missing or the target epic is not found:** write nothing and report the problem to the calling agent. Goal and Stories cannot be populated without a usable epics file.
+- **If planning artifacts are missing or empty:** still produce the file with Goal and Stories populated from the epics file. Under Requirements & Constraints, write: "Planning artifacts were unavailable; only epics-file context was used." Never hallucinate content to fill missing sections.
diff --git a/.claude/skills/bmad-build-auto/customize.toml b/.claude/skills/bmad-build-auto/customize.toml
new file mode 100644
index 0000000..a9553bb
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/customize.toml
@@ -0,0 +1,121 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Default customization values for bmad-build-auto.
+# Override in _bmad/custom/bmad-build-auto.toml or
+# _bmad/custom/bmad-build-auto.user.toml.
+#
+# Merge rules:
+# - Strings replace the default.
+# - Lists append to the default list.
+# - Tables merge key by key.
+# - Arrays of tables merge by `id`: matching `id` replaces, new `id`s append.
+
+[workflow]
+
+# Extra instructions to run before config is loaded.
+
+activation_steps_prepend = []
+
+# Extra instructions to run after config is loaded and before step 01.
+
+activation_steps_append = []
+
+# Facts kept in context for the whole run.
+# Entries are literal text or file references prefixed with "file:".
+# File entries may use globs and are loaded during activation.
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Instruction run by HALT after writing the terminal result.
+# Empty means no extra terminal behavior.
+
+on_complete = ""
+
+# Handoff for the implementation subagent in step 03. The whole execution
+# recipe — a subagent by default, but an override may run it any other way
+# (a different model, an external coding tool via bash). {spec_file} is
+# substituted at run time.
+
+implementation_handoff = """
+Launch a subagent with no prior conversation context, with this prompt:
+
+> Read {spec_file} fully and implement it — the spec is the sole source of truth. Load every file listed in its frontmatter `context:` before you start.
+>
+> When done, report what you changed, how you verified it, and anything left incomplete or risky.
+"""
+
+# Review layers for the review step. `instruction` is the layer's whole
+# execution recipe — subagents by default, but an override may run anything
+# (e.g. an external reviewer via bash). {diff_output} is substituted at run
+# time. `when` (optional) gates a layer; empty `instruction` disables it.
+
+[[workflow.review_layers]]
+id = "blind-hunter"
+name = "Blind Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Conduct a review of CONTENT.
+Look for what's missing, not only what's wrong.
+Find at least ten issues to fix or improve.
+Output a Markdown list of findings only — no severity, priority, or ranking.
+If the content is empty, stop and say so.
+If you have zero findings, re-check and keep thinking; do not stop with an empty list.
+
+CONTENT:
+{diff_output}
+
+Do not invoke any skill. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "edge-case-hunter"
+name = "Edge Case Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/edge-case-hunter.md` completely and follow it as your review instructions.
+
+Review content:
+
+{diff_output}
+
+Do not invoke any skill. If the instruction file is unreadable, report that exact failure and stop. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "verification-gap"
+name = "Verification Gap Reviewer"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/verification-gap.md` completely and follow it as your review instructions.
+
+Review content:
+
+{diff_output}
+
+Do not invoke any skill. If the instruction file is unreadable, report that exact failure and stop. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "intent-alignment"
+name = "Intent Alignment Auditor"
+instruction = """
+Launch a subagent with this prompt:
+
+You are an intent-alignment auditor. You have no other context about how this change was produced. Here is the verbatim intent this work started from:
+
+{verbatim_intent}
+
+Here is the diff:
+
+{diff_output}
+
+Your task is strictly descriptive — do not prescribe additional work. Report: (1) the defensible readings of the intent, enumerated; (2) which reading this diff implements; (3) where the readings and the diff diverge — specifically, which surface the intent's expectations live at versus which surface the diff's changes and its tests exercise.
+"""
diff --git a/.claude/skills/bmad-build-auto/references/deletion-check.md b/.claude/skills/bmad-build-auto/references/deletion-check.md
new file mode 100644
index 0000000..5cc3d77
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/references/deletion-check.md
@@ -0,0 +1,14 @@
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
diff --git a/.claude/skills/bmad-build-auto/review-prompts/edge-case-hunter.md b/.claude/skills/bmad-build-auto/review-prompts/edge-case-hunter.md
new file mode 100644
index 0000000..11df57e
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/review-prompts/edge-case-hunter.md
@@ -0,0 +1,88 @@
+# Edge Case Hunter Review
+
+**Goal:** You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.
+When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
+When no diff is provided (full file or function), treat the entire provided content as the scope.
+Ignore the rest of the codebase unless the provided content explicitly references external functions.
+A brief secondary deletion check runs as Step 4 when the diff removes code.
+
+**Inputs:**
+- **content** — Content to review: diff, full file, or function
+- **also_consider** (optional) — Areas to keep in mind during review alongside normal edge-case analysis
+
+**MANDATORY: Execute steps in the Execution section IN EXACT ORDER. DO NOT skip steps or change the sequence. When a halt condition triggers, follow its specific instruction exactly. Each action within a step is a REQUIRED action to complete that step.**
+
+**Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do NOT editorialize or add filler. Do not assign severity labels, rankings, or priority levels.**
+
+
+## EXECUTION
+
+### Step 1: Receive Content
+
+- Load the content to review strictly from the parent message that launched you (not from this instruction file)
+- If content is empty, or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+- Identify content type (diff, full file, or function) to determine scope rules
+
+### Step 2: Exhaustive Path Analysis
+
+**Walk every branching path and boundary condition within scope — report only unhandled ones.**
+
+- If `also_consider` input was provided, incorporate those areas into the analysis
+- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else/default, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Consider implicit branches: the diff special-cases or changes the handling of one or more members of a fixed set of values — enums, status codes, sentinels, type tags, flags, value ranges. The rest of the set is implicit branches (e.g. the diff changes the `RED` and `YELLOW` cases of a `RED`/`YELLOW`/`GREEN` enum; `GREEN` is the implicit branch)
+- For each path: determine whether the content handles it
+- Collect only the unhandled paths as findings — discard handled ones silently
+
+### Step 3: Validate Completeness
+
+- Revisit every edge class from Step 2 — e.g., missing else/default, null/empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Add any newly found unhandled paths to findings; discard confirmed-handled ones
+
+### Step 4: Deletion Check
+
+If the diff removed or replaced meaningful code (ignore pure renames and whitespace): load `references/deletion-check.md` and follow it.
+
+### Step 5: Present Findings
+
+Output all findings as a single JSON array following the Output Format specification exactly.
+
+
+## OUTPUT FORMAT
+
+Return ONLY a valid JSON array of objects. Each edge-case finding contains exactly these four fields:
+
+```json
+[{
+  "location": "file:start-end (or file:line when single line, or file:hunk when exact line unavailable)",
+  "trigger_condition": "one-line description (max 15 words)",
+  "guard_snippet": "minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)",
+  "potential_consequence": "what could actually go wrong (max 15 words)"
+}]
+```
+
+No extra text, no explanations, no markdown wrapping. An empty array `[]` is valid when nothing is found. Deletion findings from Step 4, if any, go in the same array with the extra fields defined in `references/deletion-check.md`.
+
+
+## HALT CONDITIONS
+
+- If content is empty or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+<reference path="references/deletion-check.md">
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
+</reference>
+
+## CONTENT SOURCE
+
+Review the content supplied under "Review content:" in the message that launched you.
diff --git a/.claude/skills/bmad-build-auto/review-prompts/verification-gap.md b/.claude/skills/bmad-build-auto/review-prompts/verification-gap.md
new file mode 100644
index 0000000..4adc52d
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/review-prompts/verification-gap.md
@@ -0,0 +1,113 @@
+# Verification Gap Review
+
+**Goal:** Find changed behavior that could break without reliable verification catching it. Ask one question — "if the behavior this change is supposed to produce broke where it's actually used, would verification fail?" Do not hunt for correctness bugs, but report genuine problems you notice while tracing verification.
+
+The main verification gap shapes are:
+
+1. **Regression gap:** the changed code regresses where it's used, and no test covering that use would fail.
+2. **Missing-adoption gap:** a place that should now use the new behavior doesn't; it handles the same case its own way, or not at all, and no test would flag the omission.
+3. **Broken-verification gap:** a test appears to cover the changed behavior, but would not actually protect it because it is skipped, flaky, not run in the normal verification path, or too weak to observe the regression.
+
+## Evidence Rules
+
+- Read a test before claiming what it covers, runs, asserts, or misses.
+- Before claiming no test exists, search the whole repo by the symbol under test and by import references; expected file locations are not enough.
+- Never assert what you did not verify. If a finding cannot be grounded, drop it.
+- In a finding, say what you actually checked — "none of the tests I read cover this" — and show how far you looked. Say a test doesn't exist anywhere only when the symbol/import-reference search actually shows that.
+- Do not assign severity, confidence, priority, or ranking.
+
+## Review Sequence
+
+### Step 1: Screen for behavioral change
+
+Screen each part of the change separately. If a part is non-behavioral, skip it. Call a part non-behavioral only when the changed code does not alter return values, thrown errors, caller-visible side effects, or observable state (including iteration order and emitted messages). Once a part meets that test, move on; do not inspect callers or tests for extra confirmation.
+
+Common non-behavioral examples: formatting, comments, whitespace; pure renames; trivial getters/setters and pass-throughs; type-only or compiler-enforced changes with no runtime effect; etc.
+
+Only outcomes produced by deterministic code are worth automatically testing; tests are useless on static source text and brittle on LLM output. Skip those parts.
+
+If every part is skipped, output the clean result (see Output Format).
+
+### Step 2: Find the behavior that changed
+
+Identify what behavior changed compared to the previous version: output, side effect, branch, error path, schema/event shape, config default, validation/authorization rule, external contract, etc. If the change affects more than one behavior, handle each separately.
+
+Treat broad-impact changes as behavioral even when no single changed line looks important: dependency, toolchain, build/config, data-file, etc.
+
+### Step 3: Trace where that behavior is used
+
+Trace the changed behavior to the places that observe it. Start with direct callers and registered entry points (routes, commands, DI), contract consumers (schemas, events, APIs, database readers), and reverse-dependency info if already available.
+
+Follow a path only while the changed behavior is reachable and unverified. Stop when a test at that boundary would fail, the consumer does not observe the changed behavior, or the next hop is guesswork (dynamic dispatch, reflection, outside-repo consumers, etc.). Prefer the nearest observable boundary, often one to three hops away, especially across contract, integration, or service edges. If there are more than five similar consumers, group obvious repeats and check representative paths; expand only when a consumer observes the behavior differently.
+
+### Step 4: Qualify the consumer, then check its test
+
+For each consumer, name the smallest realistic regression this consumer would observe: invert the branch, drop the default, omit the field, return the old error code, skip the integration call, etc. This is the Demonstration. If no such regression exists, drop the path; untested downstream code is not a finding.
+
+A `Missing-adoption gap` qualifies not by the adoption failure alone but by a supersession signal: the change gives clear evidence the new behavior is meant to replace the local one — PR intent, naming or docs, a replaced sibling site, deleted duplicate logic, or a test defining the new rule — and the local site shares the same observable contract. Without a supersession signal and a shared observable contract, it is a refactor suggestion, not a verification-gap finding. Once both hold, check whether any test for that site would flag the non-adoption; missing coverage of the non-adoption is the gap itself, not a disqualifier.
+
+Find and read the relevant test. Ask whether the Demonstration would make an assertion fail.
+
+- If yes, the behavior is verified. No finding.
+- For a regression-style Demonstration: if no test runs the path, the test is skipped/flaky/not run normally, or the test runs the code without checking the changed result, report a `Regression gap` or `Broken-verification gap`.
+- For a qualifying Missing-adoption case: if none of the site tests you found assert it adopts the new behavior, report a `Missing-adoption gap`.
+
+A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; source-text assertions that match a file's wording instead of running it; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
+
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
+Common patterns:
+
+- **Caller-path gap** — helper test covers the branch, but caller values skip it.
+- **Contract drift** — payload/schema/event changes must be verified at the consumer.
+- **Migration compatibility** — tests only create new-format rows or fresh schemas.
+- **Phantom exception** — handled partial-failure path has no test.
+- **Missing-adoption gap** — sibling site should use the new rule/helper and does not.
+- **Removed verification** — deleted test or weakened assertion leaves behavior unpinned; removing a source-text assertion is not this, since it never counted.
+
+### Step 5: Confirm each finding is real
+
+Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
+
+Explain why the test misses the bug using what the test sets up and checks.
+
+Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
+
+Report genuine problems you noticed while tracing verification, even if they are not verification gaps. Put them under `Other findings` in the output. This permits reporting what you already reached, not extra hunting.
+
+## OUTPUT FORMAT
+
+Emit each verification-gap finding as one block. No general advice, no severity or confidence.
+
+```markdown
+### <one-line title naming the gap>
+
+- **Changed surface:** the exact behavior or contract that changed — `file:line`.
+- **Impacted consumer or site:** named concretely with `file:line` (e.g. "the `createInvoice` mutation used by the billing dashboard at `billing/dashboard.ts:88`," not "callers of this function").
+- **Existing test evidence:**
+  - `Regression gap`: what the relevant test actually asserts, with `file:line`; or, if none, the symbol/import-reference searches run and their result.
+  - `Missing-adoption gap`: tests for the impacted site, and whether any assert it adopts the new behavior.
+  - `Broken-verification gap`: the apparent test or verification path, and why it does not count.
+- **Missing verification:** the precise assertion or check that's absent.
+- **Demonstration:**
+  - `Regression gap` / `Broken-verification gap`: the concrete regression that would ship undetected, and why the tests you checked would not fail.
+  - `Missing-adoption gap`: the case the site mishandles by not adopting the new behavior, and that none of the tests you read assert adoption.
+- **Consequence:** the concrete thing that ships wrong — a regression the checked evidence would not catch, or a site that should use the new behavior and doesn't.
+- **Suggested test shape:** (optional) the kind of test that would close the gap, fit to the repo's own way of verifying — don't impose a generic test pyramid.
+```
+
+If you noticed genuine non-gap problems while tracing verification, append:
+
+```markdown
+## Other findings
+
+- <description only; no severity, confidence, priority, or ranking>
+```
+
+When you find no verification gaps and no other findings, output exactly this single line, not an empty response:
+
+`No verification gaps found.`
+
+## CONTENT SOURCE
+
+Review the content supplied under "Review content:" in the message that launched you. If none is supplied, stop with exactly: `No verification gaps found.`
diff --git a/.claude/skills/bmad-build-auto/spec-template.md b/.claude/skills/bmad-build-auto/spec-template.md
new file mode 100644
index 0000000..07178f9
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/spec-template.md
@@ -0,0 +1,99 @@
+---
+title: '{title}'
+type: 'feature' # feature | bugfix | refactor | chore
+created: '{date}'
+status: 'draft' # draft | ready-for-dev | in-progress | in-review | done | blocked
+review_loop_iteration: 0 # incremented by step-04 before each review loopback
+followup_review_recommended: false # set by step-04 on status: done — true if the LLM decided another review pass is worthwhile
+context: [] # optional: `{project-root}/`-prefixed paths to project-wide standards/docs the implementation agent should load. Keep short — only what isn't already distilled into the spec body.
+warnings: [] # optional: machine-readable warnings for orchestration, e.g. oversized, multiple-goals
+deferred: [] # append-only machine-readable deferred review findings; each item carries summary/evidence and optional location/severity
+---
+
+<!-- Aim for 900–1600 tokens. If larger, add `oversized` to frontmatter `warnings` and continue.
+     Never over-specify "how" — use boundaries + examples instead.
+     Cohesive cross-layer stories (DB+BE+UI) stay in ONE file.
+     IMPORTANT: Remove all HTML comments when filling this template. -->
+
+<intent-contract>
+
+## Intent
+
+<!-- What is broken or missing, and why it matters. Then the high-level approach — the "what", not the "how". -->
+
+**Problem:** ONE_TO_TWO_SENTENCES
+
+**Approach:** ONE_TO_TWO_SENTENCES
+
+## Boundaries & Constraints
+
+<!-- Three tiers: Always = invariant rules. Block If = decisions that cannot be made unattended. Never = out of scope + forbidden approaches. -->
+
+**Always:** INVARIANT_RULES
+
+**Block If:** DECISIONS_REQUIRING_HUMAN_INPUT
+<!-- Agent: if any of these trigger during execution, HALT with status blocked and the blocking condition. -->
+
+**Never:** NON_GOALS_AND_FORBIDDEN_APPROACHES
+
+## I/O & Edge-Case Matrix
+
+<!-- If no meaningful I/O scenarios exist, DELETE THIS ENTIRE SECTION. Do not write "N/A" or "None". -->
+
+| Scenario | Input / State | Expected Output / Behavior | Error Handling |
+|----------|--------------|---------------------------|----------------|
+| HAPPY_PATH | INPUT | OUTCOME | No error expected |
+| ERROR_CASE | INPUT | OUTCOME | ERROR_HANDLING |
+
+</intent-contract>
+
+## Code Map
+
+<!-- Agent-populated during planning. Annotated paths prevent blind codebase searching. -->
+
+- `FILE` -- ROLE_OR_RELEVANCE
+- `FILE` -- ROLE_OR_RELEVANCE
+
+## Tasks & Acceptance
+
+<!-- Tasks: backtick-quoted file path -- action -- rationale. Prefer one task per file; group tightly-coupled changes when splitting would be artificial. -->
+<!-- If an I/O Matrix is present, include a task to unit-test its edge cases. -->
+<!-- AC covers system-level behaviors not captured by the I/O Matrix. Do not duplicate I/O scenarios here. -->
+
+**Execution:**
+- `FILE` -- ACTION -- RATIONALE
+
+**Acceptance Criteria:**
+- Given PRECONDITION, when ACTION, then EXPECTED_RESULT
+
+## Spec Change Log
+
+<!-- Append-only. Populated by step-04 during review loops. Do not modify or delete existing entries.
+     Each entry records: what finding triggered the change, what was amended, what known-bad state
+     the amendment avoids, and any KEEP instructions (what worked well and must survive re-derivation).
+     Empty until the first bad_spec loopback. -->
+
+## Review Triage Log
+
+<!-- Append-only. Populated by step-04 on EVERY review pass, including loopbacks and blocked exits.
+     Each entry records triage decision counts for intent_gap, bad_spec, patch, defer, and reject,
+     with per-category severity breakdowns using low/medium/high, plus the findings addressed in
+     that pass. Empty until the first review pass. -->
+
+## Design Notes
+
+<!-- If the approach is straightforward, DELETE THIS ENTIRE SECTION. Do not write "N/A" or "None". -->
+<!-- Design rationale and golden examples only when non-obvious. Keep examples to 5–10 lines. -->
+
+DESIGN_RATIONALE_AND_EXAMPLES
+
+## Verification
+
+<!-- If no build, test, or lint commands apply, DELETE THIS ENTIRE SECTION. Do not write "N/A" or "None". -->
+<!-- How the agent confirms its own work. Prefer CLI commands. When no CLI check applies, state what to inspect manually. -->
+
+**Commands:**
+- `COMMAND` -- expected: SUCCESS_CRITERIA
+
+**Manual checks (if no CLI):**
+- WHAT_TO_INSPECT_AND_EXPECTED_STATE
diff --git a/.claude/skills/bmad-build-auto/step-01-clarify-and-route.md b/.claude/skills/bmad-build-auto/step-01-clarify-and-route.md
new file mode 100644
index 0000000..87d6929
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/step-01-clarify-and-route.md
@@ -0,0 +1,83 @@
+---
+spec_file: '' # set at runtime once a route resolves it; some HALT branches exit before it is set
+spec_folder: '' # set at runtime under folder+id dispatch only
+story_id: '' # set at runtime under folder+id dispatch only
+---
+
+# Step 1: Clarify and Route
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`, tailored to `{{.user_skill_level}}`. Write files in `{{.document_output_language}}`.
+- Treat the invocation intent as workflow input, not as a substitute for step-02 investigation and spec generation.
+- **EARLY EXIT** means: stop this step immediately, then read and follow the target file. Return here only if a later step explicitly says to loop back.
+
+## Intent check (do this first)
+
+Use the invocation prompt as the intent.
+
+If the invocation prompt explicitly points to an existing spec file with recognized `status` frontmatter, set `spec_file`, then **EARLY EXIT** to the appropriate step:
+- `draft` → `[[bmad-snapshot:step-02-plan.md]]`
+- `ready-for-dev` or `in-progress` → `[[bmad-snapshot:step-03-implement.md]]`
+- `in-review` → `[[bmad-snapshot:step-04-review.md]]`
+- `blocked` → HALT with status `blocked` and blocking condition `blocked spec supplied`.
+- `done` → set `review_loop_iteration` to `0` in the frontmatter, then **EARLY EXIT** to `[[bmad-snapshot:step-04-review.md]]` for a fresh review pass. (A `done` spec is a completed run, so this starts a follow-up review, not a resumption.)
+
+If the invocation prompt instead supplies a spec folder and a story id, with no specific spec file path, this is a **folder+id dispatch**: set `spec_folder` (a `{project-root}`-relative or absolute path) and `story_id` from the prompt. Any further prompt text (e.g. `invoke_dev_with` guidance the caller appended) is additional planning context to carry into step-02 — not a competing description of what to implement.
+
+Read `{spec_folder}/stories.yaml`. If the file does not exist or fails to parse, HALT with status `blocked` and blocking condition `no stories.yaml found`. Find the entry whose `id` equals `{story_id}`; if none matches, HALT with status `blocked` and blocking condition `story id not found in stories.yaml`. Take only that entry's `title` and `description` — never read the checkpoint fields or `invoke_dev_with`; those are the caller's orchestration fields, not build-auto's.
+
+Look for files matching `{spec_folder}/stories/{story_id}-*.md` (id-prefix match — story ids are prefix-free, so at most one should match):
+- **If more than one matches**, HALT with status `blocked` and blocking condition `ambiguous story file match`.
+- **If exactly one matches**, set `spec_file` to that path.
+  - `draft` (planning was interrupted mid-flight): accumulate cross-story context before resuming — load every other file matching `{spec_folder}/stories/*.md` (every match except `{spec_file}` itself), regardless of `status`, and carry forward each one's **Code Map**, **Design Notes**, **Spec Change Log**, **Tasks & Acceptance** checklist state, and **Auto Run Result** details, where present, as additional planning context for step-02. Then **EARLY EXIT** to `[[bmad-snapshot:step-02-plan.md]]`.
+  - Any other recognized `status`: **EARLY EXIT** using the same routing as above, including the `review_loop_iteration` reset for `done`. One difference: a `blocked` story HALTs with blocking condition `story already blocked`, not `blocked spec supplied` — the caller did not supply this file; build-auto found it by id.
+  - `status` missing or unrecognized: HALT with status `blocked` and blocking condition `unrecognized status in existing story file`.
+- **If none matches**, this is the first dispatch for `{story_id}`. The entry's `title` and `description` are the resolved intent. If `{spec_folder}/SPEC.md` does not exist, HALT with status `blocked` and blocking condition `no epic spec found`. Otherwise load it and the files listed in its `companions:` frontmatter as planning context, then accumulate cross-story context the same way as the `draft` case above — load every file matching `{spec_folder}/stories/*.md` (none yet exists for `{story_id}` at this point, so nothing is excluded), regardless of `status`, carrying forward the same fields, where present, as additional planning context for step-02. Then continue to INSTRUCTIONS item 3 below — not `step-03-implement.md`, item 3 of the numbered list in this file (items 1 and 2 do not apply — context and intent are already resolved; item 1.A.5's previous-story continuity scan in particular never runs here, since folder+id dispatch already skips items 1 and 2 entirely — the cross-story accumulation above is its replacement for this dispatch mode).
+
+One `stories.yaml` entry per invocation: never read another entry, and never advance to a different story id regardless of outcome.
+
+Otherwise, treat the invocation prompt as starting intent. This may be a story ID, ticket ID, file path, short description, or longer free-form intent. Do not infer workflow state from non-spec files.
+If the invocation prompt does not contain enough intent to identify what to implement, HALT with status `blocked` and blocking condition `unclear intent`.
+
+## INSTRUCTIONS
+
+1. Load context.
+   - List files in `{{.planning_artifacts}}` and `{{.implementation_artifacts}}`.
+   - If the invocation prompt points to an unformatted spec or intent file, ingest that file. Do not scan for unrelated intent files.
+   - **Determine context strategy.** Using the intent and the artifact listing, infer whether the current work is a story from an epic. Do not rely on filename patterns or regex — reason about the intent, the listing, and any epics file content together.
+
+     **A) Epic story path** — if the intent is clearly an epic story:
+
+     1. Identify the epic number `{epic_num}` and (if present) the story number `{story_num}`. If you can't identify an epic number, use path B.
+
+     2. **Check for a valid cached epic context.** Look for `{{.implementation_artifacts}}/epic-<N>-context.md` (where `<N>` is the epic number). A file is **valid** when it exists, is non-empty, starts with `# Epic <N> Context:` (with the correct epic number), and no file in `{{.planning_artifacts}}` is newer.
+        - **If valid:** load it as the primary planning context. Do not load raw planning docs (PRD, architecture, UX, etc.).
+        - **If missing, empty, or invalid:** compile it in the next bullet.
+
+     3. **Compile epic context if needed.** If no valid cached epic context was loaded, produce `{{.implementation_artifacts}}/epic-<N>-context.md` by spawning a subagent synchronously with `[[bmad-snapshot:compile-epic-context.md]]` as its prompt. Pass it the epic number, epics file path, `{{.planning_artifacts}}`, and output path `{{.implementation_artifacts}}/epic-<N>-context.md`.
+
+     4. **Verify if compiled.** If epic context was compiled, verify the output file exists, is non-empty, and starts with `# Epic <N> Context:`. If valid, load it. If verification fails, HALT with status `blocked` and blocking condition `context compilation verification failed`.
+
+     5. **Previous story continuity.** Regardless of which context source succeeded above, scan `{{.implementation_artifacts}}` for specs from the same epic with `status: done` and a lower story number. Load the most recent one (highest story number below current). Extract its **Code Map**, **Design Notes**, **Spec Change Log**, and **task list** as continuity context for step-02 planning. If no `done` spec is found but an `in-review` spec exists for the same epic with a lower story number, HALT with status `blocked` and blocking condition `missing previous-story continuity decision`.
+
+     **B) Freeform path** — if the intent is not an epic story:
+     - Planning artifacts are the output of BMAD phases 1-3. Typical files include:
+       - **PRD** (`*prd*`) — product requirements and success criteria
+       - **Architecture** (`*architecture*`) — technical design decisions and constraints
+       - **UX/Design** (`*ux*`) — user experience and interaction design
+       - **Epics** (`*epic*`) — feature breakdown into implementable stories
+       - **Product Brief** (`*brief*`) — project vision and scope
+     - Scan the listing for files matching these patterns. If any look relevant to the current intent, load them selectively — you don't need all of them, but you need the right constraints and requirements rather than guessing from code alone.
+2. Resolve intent from the invocation prompt and loaded artifacts. Do not fantasize or leave open questions. If the intent cannot be resolved, HALT with status `blocked` and the unresolved questions as blocking condition.
+3. Version control sanity check. If version control is unavailable, skip this check. Otherwise require a clean working tree, a branch that fits the intent, and writable repository metadata. For Git, run `git add --refresh -- .`, then confirm the tree is still clean; on failure or change, HALT with status `blocked` and blocking condition `version-control metadata not writable`. Under folder+id dispatch, judge the branch against the epic, not the story. HALT on a dirty tree or obvious branch mismatch.
+4. Multi-goal warning. If the intent appears to contain multiple independently shippable goals, carry `multiple-goals` forward so step-02 can add it to `{spec_file}` frontmatter `warnings`. Do not split or block.
+5. Route:
+
+   **Folder+id dispatch:** derive a valid kebab-case slug from the entry's `title` (and `description` if needed) — the same kebab-casing convention as below, but never prefixed with `{story_id}`, since the id is already the filename's separate leading segment. Set `spec_file` = `{spec_folder}/stories/{story_id}-{slug}.md`. The id already disambiguates: no `{{.implementation_artifacts}}` fallback, no `-2`/`-3` suffixing.
+
+   **Otherwise:** derive a valid kebab-case slug from the clarified intent. If the intent references a tracking identifier (story number, issue number, ticket ID), lead the slug with it (e.g. `3-2-digest-delivery`, `gh-47-fix-auth`). If `{{.implementation_artifacts}}/spec-{slug}.md` already exists: if its status is `draft`, treat it as the same work and resume it (set `spec_file` to that path, **EARLY EXIT** → `[[bmad-snapshot:step-02-plan.md]]`); otherwise append `-2`, `-3`, etc. Set `spec_file` = `{{.implementation_artifacts}}/spec-{slug}.md`.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-02-plan.md]]`
diff --git a/.claude/skills/bmad-build-auto/step-02-plan.md b/.claude/skills/bmad-build-auto/step-02-plan.md
new file mode 100644
index 0000000..6a2f5fa
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/step-02-plan.md
@@ -0,0 +1,27 @@
+# Step 2: Plan
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`, tailored to `{{.user_skill_level}}`. Write files in `{{.document_output_language}}`.
+- No human interaction: do not ask questions or wait for approval in this step.
+
+## INSTRUCTIONS
+
+1. Draft resume check. If `{spec_file}` exists with `status: draft`, read it and capture the verbatim `<intent-contract>...</intent-contract>` block as `preserved_intent_contract`. Otherwise `preserved_intent_contract` is empty.
+2. Investigate codebase. _Read the code yourself for narrow, localized tasks. Isolate deep exploration in synchronous subagents: instruct them to give you distilled summaries only, and plan from those summaries._ Decide which findings actually matter for execution — the specific files, symbols/lines, reuse points, and read-only constraints — and carry those forward for the Code Map. This is where the investigation lands: the spec preserves it so it is never re-narrated to the implementer at dispatch time.
+3. Read `[[bmad-snapshot:spec-template.md]]` fully. Fill it out based on the intent and investigation, resolving the template's `date` field to the current system date. Drain the investigation into the `## Code Map` section — annotated paths, symbol/line anchors, reuse pointers, and read-only evidence — so the spec is the implementer's investigation map and the step-03 handoff need only point at it. If `{preserved_intent_contract}` is non-empty, substitute it for the `<intent-contract>` block in your filled spec before writing. Write the result to `{spec_file}`.
+4. Self-review against READY FOR DEVELOPMENT standard.
+5. If intent gaps exist, do not fantasize and do not leave open questions. Multiple defensible readings of the intent that lead to observably different outcomes, with nothing in the intent to select between them, are an intent gap — do not resolve one by picking a reading. HALT with status `blocked`, blocking condition `intent gap`, and include the unanswered questions and evidence gathered.
+6. Warning check. If step-01 carried `multiple-goals`, add it to `{spec_file}` frontmatter `warnings`. If `{spec_file}` exceeds 1600 tokens, add `oversized` to frontmatter `warnings`. Continue either way.
+
+### READY-FOR-DEVELOPMENT GATE
+
+Re-read `[[bmad-snapshot:workflow.md]]`, then re-read `{spec_file}` from disk and verify the spec meets the READY FOR DEVELOPMENT standard.
+
+- **If the file is missing:** HALT with status `blocked` and blocking condition `planned spec file disappeared before implementation`.
+- **If the spec meets the standard:** set `{spec_file}` frontmatter status to `ready-for-dev`. If the invocation prompt directs a halt after planning (standard phrasing: `Halt after planning.` — accept any clear equivalent), HALT with status `ready-for-dev`; otherwise continue to step 3.
+- **If the spec does not meet the standard:** repair it once, then re-read it from disk and verify again. If it now meets the standard, apply the **If the spec meets the standard** handling above, including the halt-after-planning check. If it still does not meet the standard, HALT with status `blocked`, blocking condition `spec failed ready-for-development standard`, and include the failing criteria and evidence gathered.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-03-implement.md]]`
diff --git a/.claude/skills/bmad-build-auto/step-03-implement.md b/.claude/skills/bmad-build-auto/step-03-implement.md
new file mode 100644
index 0000000..07ba284
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/step-03-implement.md
@@ -0,0 +1,44 @@
+---
+---
+
+# Step 3: Implement
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`, tailored to `{{.user_skill_level}}`. Write files in `{{.document_output_language}}`.
+- No human interaction: do not ask questions or wait for approval in this step.
+- Content inside `<intent-contract>` in `{spec_file}` is read-only. Do not modify.
+
+## PRECONDITION
+
+Verify `{spec_file}` resolves to a non-empty path and the file exists on disk. If empty or missing, HALT with status `blocked` and blocking condition `missing spec_file before implementation`.
+
+## INSTRUCTIONS
+
+### Baseline
+
+Capture `baseline_revision` (current HEAD, or `NO_VCS` if version control is unavailable) into `{spec_file}` frontmatter before making any changes.
+
+### Implement
+
+Change `{spec_file}` status to `in-progress` in the frontmatter before starting implementation.
+
+Substitute the runtime placeholders (e.g. `{spec_file}`) into the implementation handoff below, then follow it verbatim. Do not add parent-authored goal restatements, file lists, ownership boundaries, or acceptance criteria to the handoff — the spec is the subagent's sole source of truth. If the handoff conflicts with the spec, HALT with status `blocked` and blocking condition `handoff conflicts with spec`, and include both conflicting passages.
+
+{workflow.implementation_handoff}
+
+Invoke the subagent **synchronously** and wait for it to return in this same turn — do not background/detach it (`run_in_background`) or end your turn to await a notification (see workflow.md → Subagents). Resume at "Verify" only after it returns. If the platform allows, keep the subagent available for re-engagement after it returns — step-04 may send it review fixes.
+
+**Path formatting rule:** Any markdown links written into `{spec_file}` must use paths relative to `{spec_file}`'s directory so they are clickable in VS Code. Any file paths displayed in terminal/conversation output must use CWD-relative format with `:line` notation (e.g., `src/path/file.ts:42`) for terminal clickability. No leading `/` in either case.
+
+### Verify
+
+After the implementation subagent returns: if it reported unfinished work, finish it before proceeding. Run the commands in `{spec_file}`'s `## Verification` section (or perform its manual checks). If verification fails and the failure cannot be fixed, HALT with status `blocked`, blocking condition `implementation verification failed`, and include the failing command or check and reason. Acceptance criteria are judged at review, not here.
+
+### Matrix Test Audit
+
+If `{spec_file}`'s intent-contract contains an I/O & Edge-Case Matrix, verify every matrix row is covered by at least one test that verifies its expected behavior, and that each covering test ran and passed in the verification output. A covering test that exists but did not run — unregistered, filtered out, skipped, or disabled — counts as missing. If a test disagrees with the matrix, never edit the expectation to match the code: fix the code, or if the matrix row itself is ambiguous, HALT with status `blocked` and blocking condition `matrix ambiguity`. If the audit cannot otherwise be satisfied, HALT with status `blocked` and blocking condition `matrix test audit failed`.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-04-review.md]]`
diff --git a/.claude/skills/bmad-build-auto/step-04-review.md b/.claude/skills/bmad-build-auto/step-04-review.md
new file mode 100644
index 0000000..d4a1f7e
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/step-04-review.md
@@ -0,0 +1,96 @@
+# Step 4: Review
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`, tailored to `{{.user_skill_level}}`. Write files in `{{.document_output_language}}`.
+- No human interaction: do not ask questions or wait for approval in this step.
+- All review subagents must run at the same model capability as the current session.
+
+## INSTRUCTIONS
+
+Change `{spec_file}` status to `in-review` in the frontmatter before continuing.
+
+### Construct Diff
+
+Read `{baseline_revision}` from `{spec_file}` frontmatter. If `{baseline_revision}` is missing or `NO_VCS`, use best effort to determine what changed. Otherwise, construct `{diff_output}` covering all changes — tracked and untracked — since `{baseline_revision}`.
+
+Do NOT `git add` anything — this is read-only inspection.
+
+### Review
+
+Runtime placeholders: `{diff_output}` is the diff constructed above. `{verbatim_intent}` is the invocation intent exactly as this run received it at step-01; if the run started from an existing spec file rather than a fresh intent, it is the spec's `<intent-contract>` block instead. Before launching a layer, expand its skill-root placeholder to this skill's absolute installed directory; never leave that placeholder unresolved in a child prompt.
+
+Execute these review layers in parallel wherever their execution methods allow: substitute the runtime placeholders (e.g. `{diff_output}`) into each layer's instruction. When an instruction launches a reviewer subagent, launch that child with the prompt text after placeholder substitution; do not load the reviewer instruction file yourself. For any other customized instruction, execute it as written. Parallel means several blocking calls awaited together in this turn — never backgrounded or detached, never ending the turn to await results (see workflow.md → Subagents). Spawn every reviewer subagent before reading or reacting to any of their output; begin collection and triage only once all are launched.
+
+{workflow.review_layers}
+
+### Classify
+
+1. Deduplicate only findings with the same claim and same required action. Then evaluate each remaining finding independently. Do not reject a finding because a related finding was rejected.
+2. Assign severity to each finding by consequence for the artifact's main consumer (software user, document reader, etc).
+   Disregard any severity assigned by a reviewing subagent. Review subagents operate under by-design information asymmetry and do not have enough context to set final severity for this workflow.
+   - `low`: none or cosmetic
+   - `medium`: tolerable
+   - `high`: intolerable
+3. Route each finding into exactly one triage category. The first three categories are **this story's problem** — caused or exposed by the current change. The last two are **not this story's problem**.
+   Scope authority: a finding may be routed to defer or reject *as out of scope* only on the authority of the intent itself. The spec's scope language, the plan, and the diff's own shape are not admissible scope authorities — if only they exclude a finding, treat it as evidence against the chosen reading (intent_gap or bad_spec), not as out of scope.
+   - **intent_gap** — caused by the change; cannot be resolved from the spec because the captured intent is incomplete. Do not infer intent unless there is exactly one possible reading.
+   - **bad_spec** — caused by the change, including direct deviations from spec. The spec should have been clear enough to prevent it. When in doubt between bad_spec and patch, prefer bad_spec — a spec-level fix is more likely to produce coherent code.
+   - **patch** — caused by the change; trivially fixable without human input. Just part of the diff.
+   - **defer** — pre-existing issue not caused by this story, surfaced incidentally by the review. Collect for later focused attention.
+   - **reject** — noise. Drop silently. When unsure between defer and reject, prefer reject — only defer findings you are confident are real.
+4. Append a new entry to the `## Review Triage Log` section in `{spec_file}`, in this format:
+   ```markdown
+   ### {date} — Review pass
+   - intent_gap: count
+   - bad_spec: count
+   - patch: count
+   - defer: count
+   - reject: count
+   - addressed_findings:
+     - `[high|medium|low]` `[patch|bad_spec]` <finding summary and action taken in this pass>
+   ```
+   Where `{date}` is the current system date and `count` is either just `0`, or total with breakdown by severity `N: (high Nhigh, medium Nmedium, low Nlow)`.
+   If no patch was fixed and no bad_spec repair loopback was triggered in this pass, write:
+   ```markdown
+   - addressed_findings:
+     - none
+   ```
+5. Process findings in cascading order. If intent_gap exists, lower findings are moot; follow the intent_gap branch below. If bad_spec exists, lower findings are moot since code will be re-derived. If neither exists, process patch and defer normally. Before each bad_spec loopback, read `{spec_file}` frontmatter `review_loop_iteration` (missing means `0`), increment it by 1, and write it back. If it exceeds 5, append the triage-log entry for this pass with `addressed_findings: none`, then HALT with status `blocked` and blocking condition `review repair loop exceeded 5 iterations (non-convergence)`.
+   - **intent_gap** — Root cause is inside `<intent-contract>`. Save the attempted change as a patch file in `{{.implementation_artifacts}}` and reference it from the triage-log entry, then revert code changes. Append the triage-log entry for this pass with `addressed_findings: none`, then HALT with status `blocked`, blocking condition `intent gap`, and include the unresolved questions and the saved patch path.
+   - **bad_spec** — Root cause is outside `<intent-contract>`. Do not modify content inside `<intent-contract>`. Before reverting code: extract KEEP instructions for positive preservation (what worked well and must survive re-derivation). Revert code changes. Read the `## Spec Change Log` in `{spec_file}` and strictly respect all logged constraints when amending the sections outside `<intent-contract>` that contain the root cause. Append a new change-log entry recording: the triggering finding, what was amended, the known-bad state avoided, and the KEEP instructions. Append the triage-log entry for this pass, listing every bad_spec finding that triggered the spec amendment and implementation loopback under `addressed_findings`. Read fully and follow `[[bmad-snapshot:step-03-implement.md]]` to re-derive the code, then this step will run again.
+   - **patch** — Auto-fix. These are the only findings that survive loopbacks. If the step-03 implementation subagent can be re-engaged with its context intact, send it all patch findings in one synchronous message — for each: the file, what is wrong, and what the fix must do. If it cannot be re-engaged, apply the patches yourself. Then re-run the commands in `{spec_file}`'s `## Verification` section (or perform its manual checks); if verification fails and the failure cannot be fixed, HALT with status `blocked` and blocking condition `patch verification failed`. Append the triage-log entry for this pass, listing every patch fixed in this pass under `addressed_findings`.
+   - **defer** — Update the single `deferred` list in `{spec_file}` frontmatter. If the field is absent (including on specs created before this field existed), add it once as an empty list. If it is `deferred: []`, replace that empty value when adding the first item; otherwise append to the existing list. Preserve every existing item, do not look for duplicates, and never add a second `deferred:` key. Serialize free-form values as YAML block scalars so characters such as `:`, `#`, quotes, and line breaks remain data. Each item uses this shape:
+     ```yaml
+     deferred:
+       - summary: >-
+           <one sentence>
+         evidence: |-
+           <why this is real>
+         location: >- # optional — file:line or component
+           src/foo.py:42
+         severity: medium # optional — high | medium | low
+     ```
+     After all appends, parse the complete frontmatter as YAML and verify that `deferred` is one list containing every prior item plus the new items with their intended text. Repair serialization errors before continuing.
+   - **reject** — Drop silently.
+
+## Finalize
+
+Write the following details to `{spec_file}` under `## Auto Run Result`:
+- Summary of implemented change
+- Files changed with one-line descriptions
+- Review findings breakdown: patches applied, items deferred, items rejected
+- Follow-up review recommendation: count only this pass's findings triaged `patch` — never defer or reject. `true` if any patched finding was `high` severity, or if `3 × medium count + 1 × low count` is 5 or more; otherwise `false`. Record the patched counts by severity and the score.
+- Verification performed, including command outcomes or manual inspection notes
+- Any residual risks
+
+Set `{spec_file}` frontmatter `followup_review_recommended` from the computation above.
+
+If version control is unavailable, set `{spec_file}` frontmatter `status: done`, then proceed to HALT.
+
+If version control is available, write `status: done` into `{spec_file}` frontmatter, then:
+
+1. Commit any reviewed-diff files that remain uncommitted, including `{spec_file}` when it is tracked in that working copy. Keep commits already created during this run. Verify every reviewed-diff file appears in the change set after `{baseline_revision}` and none remains uncommitted. Do not push.
+2. Verify the version-controlled working copy is clean. Otherwise HALT with status `blocked` and blocking condition `finalization left repository dirty`.
+
+HALT with status `done`.
diff --git a/.claude/skills/bmad-build-auto/workflow.md b/.claude/skills/bmad-build-auto/workflow.md
new file mode 100644
index 0000000..b22a902
--- /dev/null
+++ b/.claude/skills/bmad-build-auto/workflow.md
@@ -0,0 +1,104 @@
+# Build Auto Workflow
+
+**Goal:** Turn intent into a hardened, reviewable artifact, without human interaction.
+
+**CRITICAL:** If a step directs you to another snapshot file, read it fully and follow it. No exceptions.
+
+## HALT
+
+To HALT with a final status and optional blocking condition:
+
+1. **Folder+id dispatch** (`{spec_folder}` and `{story_id}` are set): the write-back always lands at the id-keyed story spec. The `{{.implementation_artifacts}}` fallback in step 2 below is never used in this mode, even for halts before planning starts.
+   - If `{spec_file}` is still empty, resolve it now:
+     - **Entry not resolved** (`stories.yaml` is missing/unparseable, or `{story_id}` has no matching entry): use the fixed slug segment `unresolved`: `{spec_file}` = `{spec_folder}/stories/{story_id}-unresolved.md`.
+     - **Ambiguous on-disk match** (the halt is `ambiguous story file match` — more than one file already matches `{spec_folder}/stories/{story_id}-*.md`): use the fixed slug segment `ambiguous` instead of deriving from the title, so the write-back neither creates a third title-derived candidate nor risks silently landing on one of the existing ambiguous files: `{spec_file}` = `{spec_folder}/stories/{story_id}-ambiguous.md`.
+     - **Otherwise** (the entry was resolved and no ambiguous on-disk match exists): derive `{spec_file}` = `{spec_folder}/stories/{story_id}-{slug}.md`, where `{slug}` is a kebab-case slug from `title` (and `description` if needed) with no `{story_id}` prefix — the same derivation step-01's Route uses.
+   - If `{spec_file}` exists on disk, update `status` in frontmatter and append missing result details under `## Auto Run Result`.
+   - If it does not exist, create it as a skeletal story spec:
+     ```markdown
+     ---
+     status: <final status>
+     ---
+
+     # <entry title, or "Story {story_id}" if the entry could not be resolved or the on-disk match was ambiguous>
+
+     ## Auto Run Result
+
+     Status: <final status>
+     Blocking condition: <blocking condition, if any>
+     ```
+2. **Otherwise:**
+   - If `{spec_file}` is known and exists, update `status` in frontmatter and append missing result details under `## Auto Run Result`.
+   - If `{spec_file}` is unknown or missing, create `{{.implementation_artifacts}}/bmad-build-auto-result-<slug-or-timestamp>.md` with:
+     ```markdown
+     ---
+     status: <final status>
+     ---
+
+     # BMad Build Auto Result
+
+     Status: <final status>
+     Blocking condition: <blocking condition, if any>
+     ```
+3. Follow **On Complete** below, then stop the workflow.
+
+### On Complete
+
+If anything appears below, follow it as the final terminal instruction before exiting; otherwise exit normally.
+
+{workflow.on_complete}
+
+## Subagents
+
+Using subagents when instructed is mandatory. If you cannot, HALT with status `blocked` and blocking condition `no subagents`.
+
+Invoke every subagent **synchronously**: launch it, wait for it to return within the same turn, then continue with its result. When a step says to run subagents "in parallel" (e.g. the reviewers), that means several **blocking** calls awaited together in one turn — not detached execution. Never run a subagent in the background / detached / async (e.g. `run_in_background: true`), and never end your turn to "await a completion notification." This workflow runs unattended: there is no event loop to resume a yielded turn, so a backgrounded subagent never hands control back and the run stalls. The only sanctioned way to end a turn is the HALT protocol above with an explicit terminal `status`.
+
+## READY FOR DEVELOPMENT STANDARD
+
+A specification is "Ready for Development" when:
+
+- **Actionable**: Every task has a file path and specific action.
+- **Logical**: Tasks ordered by dependency.
+- **Testable**: All ACs use Given/When/Then.
+- **Surface-anchored**: ACs observe the outermost surface the intent references — never a more internal proxy for it.
+- **Complete**: No placeholders or TBDs.
+- **Sufficient**: No known requirement, acceptance, dependency, or implementation gaps remain unresolved.
+- **Coherent**: No unresolved ambiguities or internal contradictions.
+
+## Conventions
+
+- Every operational cross-file reference in this workflow is an absolute snapshot path. Open it directly; do not resolve it relative to a skill directory.
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- Speak in `{{.communication_language}}`, tailor communication to `{{.user_skill_level}}`, and write documents in `{{.document_output_language}}`.
+- Whenever this workflow captures or records a version-control revision, obtain the full canonical identifier directly from version control and preserve it verbatim.
+
+## On Activation
+
+### Step 1: Execute Prepend Steps
+
+Execute each of these steps in order before proceeding (`_None._` means skip):
+
+{workflow.activation_steps_prepend}
+
+### Step 2: Load Persistent Facts
+
+Treat every entry below as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` -- load the referenced contents as facts. All other entries are facts verbatim (`_None._` means none):
+
+{workflow.persistent_facts}
+
+### Step 3: Execute Append Steps
+
+Execute each of these steps in order (`_None._` means skip):
+
+{workflow.activation_steps_append}
+
+Activation is complete after all activation steps have run.
+
+## Workflow Execution
+
+Follow the step files in order. Read one step fully, execute it, then load the next step only when directed. Do not skip, reorder, or pre-load steps.
+
+## First Workflow Step
+
+Read fully and follow: `[[bmad-snapshot:step-01-clarify-and-route.md]]`.
diff --git a/.claude/skills/bmad-build/SKILL.md b/.claude/skills/bmad-build/SKILL.md
new file mode 100644
index 0000000..e7cbbf8
--- /dev/null
+++ b/.claude/skills/bmad-build/SKILL.md
@@ -0,0 +1,13 @@
+---
+name: bmad-build
+description: 'Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project''s existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.'
+---
+
+Run the following command exactly once without changing the current working directory. Replace `{project-root}` with the absolute path to the project root and `{skill-root}` with the absolute path to this skill's directory:
+
+```bash
+uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"
+```
+
+- On success, read and follow the one absolute `workflow.md` instruction printed to stdout.
+- On failure (including `uv` being unavailable), report the command output and HALT. Do not run any workflow source directly.
diff --git a/.claude/skills/bmad-build/compile-epic-context.md b/.claude/skills/bmad-build/compile-epic-context.md
new file mode 100644
index 0000000..f5963b3
--- /dev/null
+++ b/.claude/skills/bmad-build/compile-epic-context.md
@@ -0,0 +1,62 @@
+# Compile Epic Context
+
+**Task**
+Given an epic number, the epics file, the planning artifacts directory, and a desired output path, compile a clean, focused, developer-ready context file (`epic-<N>-context.md`).
+
+**Steps**
+
+1. Read the epics file and extract the target epic's title, goal, and list of stories.
+2. Scan the planning artifacts directory for the standard files (PRD, architecture, UX/design, product brief).
+3. Pull only the information relevant to this epic.
+4. Write the compiled context to the exact output path using the format below.
+
+## Exact Output Format
+
+Use these headings:
+
+```markdown
+# Epic {N} Context: {Epic Title}
+
+<!-- Compiled from planning artifacts. Edit freely. Regenerate with compile-epic-context if planning docs change. -->
+
+## Goal
+
+{One clear paragraph: what this epic achieves and why it matters.}
+
+## Stories
+
+- Story X.Y: Brief title only
+- ...
+
+## Requirements & Constraints
+
+{Relevant functional/non-functional requirements and success criteria for this epic (describe by purpose, not source).}
+
+## Technical Decisions
+
+{Key architecture decisions, constraints, patterns, data models, and conventions relevant to this epic.}
+
+## UX & Interaction Patterns
+
+{Relevant UX flows, interaction patterns, and design constraints (omit section entirely if nothing relevant).}
+
+## Cross-Story Dependencies
+
+{Dependencies between stories in this epic or with other epics/systems (omit if none).}
+```
+
+## Rules
+
+- **Scope aggressively.** Include only what a developer working on any story in this epic actually needs. When in doubt, leave it out — the developer can always read the full planning doc.
+- **Describe by purpose, not by source.** Write "API responses must include pagination metadata" not "Per PRD section 3.2.1, pagination is required." Planning doc internals will change; the constraint won't.
+- **No full copies.** Never quote source documents, section numbers, or paste large blocks verbatim. Always distill.
+- **No story-level details.** The story list is for orientation only. Individual story specs handle the details.
+- **Nothing derivable from the codebase.** Don't document what a developer can learn by reading the code.
+- **Be concise and actionable.** Target 800–1500 tokens total. This file loads into build's context alongside other material.
+- **Never hallucinate content.** If source material doesn't say something, don't invent it.
+- **Omit empty sections entirely**, except Goal and Stories, which are always required.
+
+## Error handling
+
+- **If the epics file is missing or the target epic is not found:** write nothing and report the problem to the calling agent. Goal and Stories cannot be populated without a usable epics file.
+- **If planning artifacts are missing or empty:** still produce the file with Goal and Stories populated from the epics file, and note the gap in the Goal section. Never hallucinate content to fill missing sections.
diff --git a/.claude/skills/bmad-build/customize.toml b/.claude/skills/bmad-build/customize.toml
new file mode 100644
index 0000000..4777a11
--- /dev/null
+++ b/.claude/skills/bmad-build/customize.toml
@@ -0,0 +1,164 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Default customization values for bmad-build.
+# Override in _bmad/custom/bmad-build.toml or
+# _bmad/custom/bmad-build.user.toml.
+#
+# Merge rules:
+# - Strings replace the default.
+# - Lists append to the default list.
+# - Tables merge key by key.
+# - Arrays of tables merge by `id`: matching `id` replaces, new `id`s append.
+
+[workflow]
+
+# Extra instructions to run before config is loaded and before the user is greeted.
+
+activation_steps_prepend = []
+
+# Extra instructions to run after the greeting and before step 01.
+
+activation_steps_append = []
+
+# Facts kept in context for the whole run.
+# Entries are literal text or file references prefixed with "file:".
+# File entries may use globs and are loaded during activation.
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Instruction run after Build completes.
+# Empty means no extra completion behavior.
+
+on_complete = ""
+
+# How Build opens a completed spec for human review. The default deliberately
+# opens the repository root first and the spec second in a reused VS Code
+# window so relative review links resolve in the correct workspace. Override
+# this with the application and equivalent behavior you prefer. Set it to an
+# empty string to disable automatic opening and all related completion output.
+# Example requests for bmad-customize: "Open completed specs in Cursor and
+# reuse the project window" or "Do not open completed specs automatically."
+#
+# Example `open_spec` override instructions for bmad-build.user.toml:
+# {project-root} and {spec_file} are substituted at run time.
+#
+# VS Code and compatible GUI editors — shipped default uses `code`; Cursor,
+# Windsurf, Antigravity, Zed, and similar editors can substitute their launcher.
+# Preserve reuse-window behavior when the launcher supports it, and always pass
+# the repository root first and the spec second:
+#   Run `code -r "{project-root}" "{spec_file}"`, root first.
+#   Run `cursor -r "{project-root}" "{spec_file}"`, root first.
+#   Run `windsurf -r "{project-root}" "{spec_file}"`, root first.
+#   Run `zed "{project-root}" "{spec_file}"`, root first.
+#
+# IntelliJ IDEA — its CLI accepts one path per invocation:
+#   Run `idea "{project-root}"` to open the project, then
+#   `idea "{spec_file}"` to open the spec in that project.
+#
+# Vim — keep repository context as the working directory:
+#   Run `cd "{project-root}" && vim "{spec_file}"`.
+#
+# Emacs — reuse an Emacs server without waiting for the buffer to close:
+#   Run `cd "{project-root}" && emacsclient -n "{spec_file}"`.
+#
+# For every non-empty override, also tell Build to note in the completion summary
+# that the spec was sent to the chosen editor and contains a Suggested Review
+# Order, then include the default navigation tip shown below.
+
+open_spec = """
+Run `code -r "{project-root}" "{spec_file}"` — the repository root first so VS Code opens in the right context, then the spec file. Always double-quote both paths to handle spaces and special characters. If `code` is unavailable or the command fails, skip gracefully and tell the user the spec file path instead. In the completion summary, note that the spec was sent to VS Code and that it contains a Suggested Review Order, then add this navigation tip: "Ctrl+click (Cmd+click on macOS) the links in the Suggested Review Order to jump to each stop."
+"""
+
+# Handoff for the implementation subagent in step 03. The whole execution
+# recipe — a subagent by default, but an override may run it any other way
+# (a different model, an external coding tool via bash). {spec_file} is
+# substituted at run time.
+
+implementation_handoff = """
+Launch a subagent with no prior conversation context, with this prompt:
+
+> Read {spec_file} fully and implement it — the spec is the sole source of truth. Load every file listed in its frontmatter `context:` before you start.
+>
+> When done, report what you changed, how you verified it, and anything left incomplete or risky.
+"""
+
+# Review layers for the review step. `instruction` is the layer's whole
+# execution recipe — subagents by default, but an override may run anything
+# (e.g. an external reviewer via bash). {diff_output} is substituted at run
+# time. `when` (optional) gates a layer; empty `instruction` disables it.
+
+[[workflow.review_layers]]
+id = "blind-hunter"
+name = "Blind Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Conduct a review of CONTENT.
+Look for what's missing, not only what's wrong.
+Find at least ten issues to fix or improve.
+Output a Markdown list of findings only — no severity, priority, or ranking.
+If the content is empty, stop and say so.
+If you have zero findings, re-check and keep thinking; do not stop with an empty list.
+
+CONTENT:
+{diff_output}
+
+Do not invoke any skill. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "edge-case-hunter"
+name = "Edge Case Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/edge-case-hunter.md` completely and follow it as your review instructions.
+
+Review content:
+
+{diff_output}
+
+Do not invoke any skill. If the instruction file is unreadable, report that exact failure and stop. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "verification-gap"
+name = "Verification Gap Reviewer"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/verification-gap.md` completely and follow it as your review instructions.
+
+Review content:
+
+{diff_output}
+
+Do not invoke any skill. If the instruction file is unreadable, report that exact failure and stop. Return only the review result.
+
+"""
+
+# Review layers for the one-shot route.
+
+[[workflow.oneshot_review_layers]]
+id = "blind-hunter"
+name = "Blind Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Conduct a review of CONTENT.
+Look for what's missing, not only what's wrong.
+Find at least ten issues to fix or improve.
+Output a Markdown list of findings only — no severity, priority, or ranking.
+If the content is empty, stop and say so.
+If you have zero findings, re-check and keep thinking; do not stop with an empty list.
+
+CONTENT:
+The changed files in the current worktree. Inspect them directly before reviewing.
+
+Do not invoke any skill. Return only the review result.
+
+"""
diff --git a/.claude/skills/bmad-build/references/deletion-check.md b/.claude/skills/bmad-build/references/deletion-check.md
new file mode 100644
index 0000000..5cc3d77
--- /dev/null
+++ b/.claude/skills/bmad-build/references/deletion-check.md
@@ -0,0 +1,14 @@
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
diff --git a/.claude/skills/bmad-build/review-prompts/edge-case-hunter.md b/.claude/skills/bmad-build/review-prompts/edge-case-hunter.md
new file mode 100644
index 0000000..11df57e
--- /dev/null
+++ b/.claude/skills/bmad-build/review-prompts/edge-case-hunter.md
@@ -0,0 +1,88 @@
+# Edge Case Hunter Review
+
+**Goal:** You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.
+When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
+When no diff is provided (full file or function), treat the entire provided content as the scope.
+Ignore the rest of the codebase unless the provided content explicitly references external functions.
+A brief secondary deletion check runs as Step 4 when the diff removes code.
+
+**Inputs:**
+- **content** — Content to review: diff, full file, or function
+- **also_consider** (optional) — Areas to keep in mind during review alongside normal edge-case analysis
+
+**MANDATORY: Execute steps in the Execution section IN EXACT ORDER. DO NOT skip steps or change the sequence. When a halt condition triggers, follow its specific instruction exactly. Each action within a step is a REQUIRED action to complete that step.**
+
+**Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do NOT editorialize or add filler. Do not assign severity labels, rankings, or priority levels.**
+
+
+## EXECUTION
+
+### Step 1: Receive Content
+
+- Load the content to review strictly from the parent message that launched you (not from this instruction file)
+- If content is empty, or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+- Identify content type (diff, full file, or function) to determine scope rules
+
+### Step 2: Exhaustive Path Analysis
+
+**Walk every branching path and boundary condition within scope — report only unhandled ones.**
+
+- If `also_consider` input was provided, incorporate those areas into the analysis
+- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else/default, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Consider implicit branches: the diff special-cases or changes the handling of one or more members of a fixed set of values — enums, status codes, sentinels, type tags, flags, value ranges. The rest of the set is implicit branches (e.g. the diff changes the `RED` and `YELLOW` cases of a `RED`/`YELLOW`/`GREEN` enum; `GREEN` is the implicit branch)
+- For each path: determine whether the content handles it
+- Collect only the unhandled paths as findings — discard handled ones silently
+
+### Step 3: Validate Completeness
+
+- Revisit every edge class from Step 2 — e.g., missing else/default, null/empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Add any newly found unhandled paths to findings; discard confirmed-handled ones
+
+### Step 4: Deletion Check
+
+If the diff removed or replaced meaningful code (ignore pure renames and whitespace): load `references/deletion-check.md` and follow it.
+
+### Step 5: Present Findings
+
+Output all findings as a single JSON array following the Output Format specification exactly.
+
+
+## OUTPUT FORMAT
+
+Return ONLY a valid JSON array of objects. Each edge-case finding contains exactly these four fields:
+
+```json
+[{
+  "location": "file:start-end (or file:line when single line, or file:hunk when exact line unavailable)",
+  "trigger_condition": "one-line description (max 15 words)",
+  "guard_snippet": "minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)",
+  "potential_consequence": "what could actually go wrong (max 15 words)"
+}]
+```
+
+No extra text, no explanations, no markdown wrapping. An empty array `[]` is valid when nothing is found. Deletion findings from Step 4, if any, go in the same array with the extra fields defined in `references/deletion-check.md`.
+
+
+## HALT CONDITIONS
+
+- If content is empty or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+<reference path="references/deletion-check.md">
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
+</reference>
+
+## CONTENT SOURCE
+
+Review the content supplied under "Review content:" in the message that launched you.
diff --git a/.claude/skills/bmad-build/review-prompts/verification-gap.md b/.claude/skills/bmad-build/review-prompts/verification-gap.md
new file mode 100644
index 0000000..4adc52d
--- /dev/null
+++ b/.claude/skills/bmad-build/review-prompts/verification-gap.md
@@ -0,0 +1,113 @@
+# Verification Gap Review
+
+**Goal:** Find changed behavior that could break without reliable verification catching it. Ask one question — "if the behavior this change is supposed to produce broke where it's actually used, would verification fail?" Do not hunt for correctness bugs, but report genuine problems you notice while tracing verification.
+
+The main verification gap shapes are:
+
+1. **Regression gap:** the changed code regresses where it's used, and no test covering that use would fail.
+2. **Missing-adoption gap:** a place that should now use the new behavior doesn't; it handles the same case its own way, or not at all, and no test would flag the omission.
+3. **Broken-verification gap:** a test appears to cover the changed behavior, but would not actually protect it because it is skipped, flaky, not run in the normal verification path, or too weak to observe the regression.
+
+## Evidence Rules
+
+- Read a test before claiming what it covers, runs, asserts, or misses.
+- Before claiming no test exists, search the whole repo by the symbol under test and by import references; expected file locations are not enough.
+- Never assert what you did not verify. If a finding cannot be grounded, drop it.
+- In a finding, say what you actually checked — "none of the tests I read cover this" — and show how far you looked. Say a test doesn't exist anywhere only when the symbol/import-reference search actually shows that.
+- Do not assign severity, confidence, priority, or ranking.
+
+## Review Sequence
+
+### Step 1: Screen for behavioral change
+
+Screen each part of the change separately. If a part is non-behavioral, skip it. Call a part non-behavioral only when the changed code does not alter return values, thrown errors, caller-visible side effects, or observable state (including iteration order and emitted messages). Once a part meets that test, move on; do not inspect callers or tests for extra confirmation.
+
+Common non-behavioral examples: formatting, comments, whitespace; pure renames; trivial getters/setters and pass-throughs; type-only or compiler-enforced changes with no runtime effect; etc.
+
+Only outcomes produced by deterministic code are worth automatically testing; tests are useless on static source text and brittle on LLM output. Skip those parts.
+
+If every part is skipped, output the clean result (see Output Format).
+
+### Step 2: Find the behavior that changed
+
+Identify what behavior changed compared to the previous version: output, side effect, branch, error path, schema/event shape, config default, validation/authorization rule, external contract, etc. If the change affects more than one behavior, handle each separately.
+
+Treat broad-impact changes as behavioral even when no single changed line looks important: dependency, toolchain, build/config, data-file, etc.
+
+### Step 3: Trace where that behavior is used
+
+Trace the changed behavior to the places that observe it. Start with direct callers and registered entry points (routes, commands, DI), contract consumers (schemas, events, APIs, database readers), and reverse-dependency info if already available.
+
+Follow a path only while the changed behavior is reachable and unverified. Stop when a test at that boundary would fail, the consumer does not observe the changed behavior, or the next hop is guesswork (dynamic dispatch, reflection, outside-repo consumers, etc.). Prefer the nearest observable boundary, often one to three hops away, especially across contract, integration, or service edges. If there are more than five similar consumers, group obvious repeats and check representative paths; expand only when a consumer observes the behavior differently.
+
+### Step 4: Qualify the consumer, then check its test
+
+For each consumer, name the smallest realistic regression this consumer would observe: invert the branch, drop the default, omit the field, return the old error code, skip the integration call, etc. This is the Demonstration. If no such regression exists, drop the path; untested downstream code is not a finding.
+
+A `Missing-adoption gap` qualifies not by the adoption failure alone but by a supersession signal: the change gives clear evidence the new behavior is meant to replace the local one — PR intent, naming or docs, a replaced sibling site, deleted duplicate logic, or a test defining the new rule — and the local site shares the same observable contract. Without a supersession signal and a shared observable contract, it is a refactor suggestion, not a verification-gap finding. Once both hold, check whether any test for that site would flag the non-adoption; missing coverage of the non-adoption is the gap itself, not a disqualifier.
+
+Find and read the relevant test. Ask whether the Demonstration would make an assertion fail.
+
+- If yes, the behavior is verified. No finding.
+- For a regression-style Demonstration: if no test runs the path, the test is skipped/flaky/not run normally, or the test runs the code without checking the changed result, report a `Regression gap` or `Broken-verification gap`.
+- For a qualifying Missing-adoption case: if none of the site tests you found assert it adopts the new behavior, report a `Missing-adoption gap`.
+
+A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; source-text assertions that match a file's wording instead of running it; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
+
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
+Common patterns:
+
+- **Caller-path gap** — helper test covers the branch, but caller values skip it.
+- **Contract drift** — payload/schema/event changes must be verified at the consumer.
+- **Migration compatibility** — tests only create new-format rows or fresh schemas.
+- **Phantom exception** — handled partial-failure path has no test.
+- **Missing-adoption gap** — sibling site should use the new rule/helper and does not.
+- **Removed verification** — deleted test or weakened assertion leaves behavior unpinned; removing a source-text assertion is not this, since it never counted.
+
+### Step 5: Confirm each finding is real
+
+Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
+
+Explain why the test misses the bug using what the test sets up and checks.
+
+Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
+
+Report genuine problems you noticed while tracing verification, even if they are not verification gaps. Put them under `Other findings` in the output. This permits reporting what you already reached, not extra hunting.
+
+## OUTPUT FORMAT
+
+Emit each verification-gap finding as one block. No general advice, no severity or confidence.
+
+```markdown
+### <one-line title naming the gap>
+
+- **Changed surface:** the exact behavior or contract that changed — `file:line`.
+- **Impacted consumer or site:** named concretely with `file:line` (e.g. "the `createInvoice` mutation used by the billing dashboard at `billing/dashboard.ts:88`," not "callers of this function").
+- **Existing test evidence:**
+  - `Regression gap`: what the relevant test actually asserts, with `file:line`; or, if none, the symbol/import-reference searches run and their result.
+  - `Missing-adoption gap`: tests for the impacted site, and whether any assert it adopts the new behavior.
+  - `Broken-verification gap`: the apparent test or verification path, and why it does not count.
+- **Missing verification:** the precise assertion or check that's absent.
+- **Demonstration:**
+  - `Regression gap` / `Broken-verification gap`: the concrete regression that would ship undetected, and why the tests you checked would not fail.
+  - `Missing-adoption gap`: the case the site mishandles by not adopting the new behavior, and that none of the tests you read assert adoption.
+- **Consequence:** the concrete thing that ships wrong — a regression the checked evidence would not catch, or a site that should use the new behavior and doesn't.
+- **Suggested test shape:** (optional) the kind of test that would close the gap, fit to the repo's own way of verifying — don't impose a generic test pyramid.
+```
+
+If you noticed genuine non-gap problems while tracing verification, append:
+
+```markdown
+## Other findings
+
+- <description only; no severity, confidence, priority, or ranking>
+```
+
+When you find no verification gaps and no other findings, output exactly this single line, not an empty response:
+
+`No verification gaps found.`
+
+## CONTENT SOURCE
+
+Review the content supplied under "Review content:" in the message that launched you. If none is supplied, stop with exactly: `No verification gaps found.`
diff --git a/.claude/skills/bmad-build/spec-template.md b/.claude/skills/bmad-build/spec-template.md
new file mode 100644
index 0000000..7849094
--- /dev/null
+++ b/.claude/skills/bmad-build/spec-template.md
@@ -0,0 +1,89 @@
+---
+title: '{title}'
+type: 'feature' # feature | bugfix | refactor | chore
+created: '{date}'
+status: 'draft' # draft | ready-for-dev | in-progress | in-review | done
+review_loop_iteration: 0 # incremented by step-04 before each review loopback
+context: [] # optional: `{project-root}/`-prefixed paths to project-wide standards/docs the implementation agent should load. Keep short — only what isn't already distilled into the spec body.
+---
+
+<!-- Target: 900–1300 tokens. Above 1600 = high risk of context rot.
+     Never over-specify "how" — use boundaries + examples instead.
+     Cohesive cross-layer stories (DB+BE+UI) stay in ONE file.
+     IMPORTANT: Remove all HTML comments when filling this template. -->
+
+<frozen-after-approval reason="human-owned intent — do not modify unless human renegotiates">
+
+## Intent
+
+<!-- What is broken or missing, and why it matters. Then the high-level approach — the "what", not the "how". -->
+
+**Problem:** ONE_TO_TWO_SENTENCES
+
+**Approach:** ONE_TO_TWO_SENTENCES
+
+## Boundaries & Constraints
+
+<!-- Three tiers: Always = invariant rules. Ask First = human-gated decisions. Never = out of scope + forbidden approaches. -->
+
+**Always:** INVARIANT_RULES
+
+**Ask First:** DECISIONS_REQUIRING_HUMAN_APPROVAL
+<!-- Agent: if any of these trigger during execution, HALT and ask the user before proceeding. -->
+
+**Never:** NON_GOALS_AND_FORBIDDEN_APPROACHES
+
+## I/O & Edge-Case Matrix
+
+<!-- If no meaningful I/O scenarios exist, DELETE THIS ENTIRE SECTION. Do not write "N/A" or "None". -->
+
+| Scenario | Input / State | Expected Output / Behavior | Error Handling |
+|----------|--------------|---------------------------|----------------|
+| HAPPY_PATH | INPUT | OUTCOME | N/A |
+| ERROR_CASE | INPUT | OUTCOME | ERROR_HANDLING |
+
+</frozen-after-approval>
+
+## Code Map
+
+<!-- Agent-populated during planning. Annotated paths prevent blind codebase searching. -->
+
+- `FILE` -- ROLE_OR_RELEVANCE
+- `FILE` -- ROLE_OR_RELEVANCE
+
+## Tasks & Acceptance
+
+<!-- Tasks: backtick-quoted file path -- action -- rationale. Prefer one task per file; group tightly-coupled changes when splitting would be artificial. -->
+<!-- If an I/O Matrix is present, include a task to unit-test its edge cases. -->
+<!-- AC covers system-level behaviors not captured by the I/O Matrix. Do not duplicate I/O scenarios here. -->
+
+**Execution:**
+- [ ] `FILE` -- ACTION -- RATIONALE
+
+**Acceptance Criteria:**
+- Given PRECONDITION, when ACTION, then EXPECTED_RESULT
+
+## Spec Change Log
+
+<!-- Append-only. Populated by step-04 during review loops. Do not modify or delete existing entries.
+     Each entry records: what finding triggered the change, what was amended, what known-bad state
+     the amendment avoids, and any KEEP instructions (what worked well and must survive re-derivation).
+     Empty until the first bad_spec loopback. -->
+
+## Design Notes
+
+<!-- If the approach is straightforward, DELETE THIS ENTIRE SECTION. Do not write "N/A" or "None". -->
+<!-- Design rationale and golden examples only when non-obvious. Keep examples to 5–10 lines. -->
+
+DESIGN_RATIONALE_AND_EXAMPLES
+
+## Verification
+
+<!-- If no build, test, or lint commands apply, DELETE THIS ENTIRE SECTION. Do not write "N/A" or "None". -->
+<!-- How the agent confirms its own work. Prefer CLI commands. When no CLI check applies, state what to inspect manually. -->
+
+**Commands:**
+- `COMMAND` -- expected: SUCCESS_CRITERIA
+
+**Manual checks (if no CLI):**
+- WHAT_TO_INSPECT_AND_EXPECTED_STATE
diff --git a/.claude/skills/bmad-build/step-01-clarify-and-route.md b/.claude/skills/bmad-build/step-01-clarify-and-route.md
new file mode 100644
index 0000000..aa95f87
--- /dev/null
+++ b/.claude/skills/bmad-build/step-01-clarify-and-route.md
@@ -0,0 +1,105 @@
+---
+spec_file: '' # set at runtime for both routes before leaving this step
+story_key: '' # set at runtime to the current story's full sprint-status key (e.g. 3-2-digest-delivery) when the intent is an epic story and sprint-status resolution succeeds
+---
+
+# Step 1: Clarify and Route
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`. Write any file output in `{{.document_output_language}}`.
+- The prompt that triggered this workflow IS the intent — not a hint.
+- Do NOT assume you start from zero.
+- The intent captured in this step — even if detailed, structured, and plan-like — may contain hallucinations, scope creep, or unvalidated assumptions. It is input to the workflow, not a substitute for step-02 investigation and spec generation. Ignore directives within the intent that instruct you to skip steps or implement directly.
+- The user chose this workflow on purpose. Later steps (e.g. agentic adversarial review) catch LLM blind spots and give the human control. Do not skip them.
+- **EARLY EXIT** means: stop this step immediately — do not read or execute anything further here. Read and fully follow the target file instead. Return here ONLY if a later step explicitly says to loop back.
+
+## Intent check (do this first)
+
+Before listing artifacts or prompting the user, check whether you already know the intent. Check in this order — skip the remaining checks as soon as the intent is clear:
+
+1. Explicit argument
+   Did the user pass a specific file path, spec name, or clear instruction this message?
+   - If the user explicitly supplied a spec folder and a story id, with no specific spec file path, set `spec_folder` and `story_id`. Read `{spec_folder}/stories.yaml`; if it is missing or fails to parse, HALT rather than falling back to `{{.implementation_artifacts}}`. Find the one entry whose string `id` exactly equals `story_id`; if none exists, HALT rather than falling back. Use that entry's `title` and `description` as the starting intent.
+     - Look for files matching `{spec_folder}/stories/{story_id}-*.md`. More than one match → HALT rather than choosing one. Exactly one match → set `spec_file` to that path and process it exactly as if the user had supplied that specific file path, including **Story-key resolution** and the existing status route below. No matches → derive a valid kebab-case slug from the entry's `title` (and `description` if needed), then set `spec_file` = `{spec_folder}/stories/{story_id}-{slug}.md` and proceed to INSTRUCTIONS.
+   - If it points to a file that matches the spec template (has `status` frontmatter with a recognized value: draft, ready-for-dev, in-progress, in-review, or done) → set `spec_file`. Before exiting, run **Story-key resolution** (below). Then **EARLY EXIT** to the appropriate step: `draft` → `[[bmad-snapshot:step-02-plan.md]]`, `ready-for-dev`/`in-progress` → `[[bmad-snapshot:step-03-implement.md]]`, `in-review` → `[[bmad-snapshot:step-04-review.md]]`. For `done`, ingest as context and proceed to INSTRUCTIONS — do not resume.
+   - Anything else (intent files, external docs, plans, descriptions) → ingest it as starting intent and proceed to INSTRUCTIONS. Do not attempt to infer a workflow state from it.
+
+2. Recent conversation
+   Do the last few human messages clearly show what the user intends to work on?
+   Use the same routing as above.
+
+3. Otherwise — scan artifacts and ask
+   - Active specs (`draft`, `ready-for-dev`, `in-progress`, `in-review`) in `{{.implementation_artifacts}}`? → List them and HALT. Ask user which to resume (or `[N]` for new).
+     - If `draft` selected: Set `spec_file`. Run **Story-key resolution** (below). **EARLY EXIT** → `[[bmad-snapshot:step-02-plan.md]]` (resume planning from the draft)
+     - If `ready-for-dev` or `in-progress` selected: Set `spec_file`. Run **Story-key resolution** (below). **EARLY EXIT** → `[[bmad-snapshot:step-03-implement.md]]`
+     - If `in-review` selected: Set `spec_file`. Run **Story-key resolution** (below). **EARLY EXIT** → `[[bmad-snapshot:step-04-review.md]]`
+   - Unformatted spec or intent file lacking `status` frontmatter? → Suggest treating its contents as the starting intent. Do NOT attempt to infer a state and resume it.
+
+Never ask extra questions if you already understand what the user intends.
+
+### Story-key resolution
+
+This runs on ALL paths (early-exit and INSTRUCTIONS) whenever `spec_file` is set. Determine whether the spec is an epic story — use the spec's filename, frontmatter, and any loaded epics file to identify `epic_num` and `story_num`. If the spec is not an epic story, skip silently and leave `story_key` unset.
+
+If the spec is an epic story and `{{.implementation_artifacts}}/sprint-status.yaml` exists: find the `development_status` key matching `{epic_num}-{story_num}` by exact numeric equality on the first two segments (so `1-1` never collides with `1-10`). Exactly one match → set `story_key` to that full key. Zero or multiple matches → leave `story_key` unset (warn on multiple).
+
+## INSTRUCTIONS
+
+1. Load context.
+   - List files in `{{.planning_artifacts}}` and `{{.implementation_artifacts}}`.
+   - If you find an unformatted spec or intent file, ingest its contents to form your understanding of the intent.
+   - **Determine context strategy.** Using the intent and the artifact listing, infer whether the current work is a story from an epic. Do not rely on filename patterns or regex — reason about the intent, the listing, and any epics file content together.
+
+     **A) Epic story path** — if the intent is clearly an epic story:
+
+     1. Identify the epic number `{epic_num}` and (if present) the story number `{story_num}`. If you can't identify an epic number, use path B.
+
+     2. **Check for a valid cached epic context.** Look for `{{.implementation_artifacts}}/epic-<N>-context.md` (where `<N>` is the epic number). A file is **valid** when it exists, is non-empty, starts with `# Epic <N> Context:` (with the correct epic number), and no file in `{{.planning_artifacts}}` is newer.
+        - **If valid:** load it as the primary planning context. Do not load raw planning docs (PRD, architecture, UX, etc.). Skip to step 5.
+        - **If missing, empty, or invalid:** continue to step 3.
+
+     3. **Compile epic context.** Produce `{{.implementation_artifacts}}/epic-<N>-context.md` by following `[[bmad-snapshot:compile-epic-context.md]]`, in order of preference:
+        - **Preferred — subagent:** spawn a subagent synchronously (wait for it to return in this turn) with `[[bmad-snapshot:compile-epic-context.md]]` as its prompt. Pass it the epic number, the epics file path, the `{{.planning_artifacts}}` directory, and the output path `{{.implementation_artifacts}}/epic-<N>-context.md`.
+        - **Fallback — inline** (for runtimes without subagent support, e.g. Copilot, Codex, local Ollama, older Claude): if your runtime cannot spawn subagents, or the spawn fails/times out, read `[[bmad-snapshot:compile-epic-context.md]]` yourself and follow its instructions to produce the same output file.
+
+     4. **Verify.** After compilation, verify the output file exists, is non-empty, and starts with `# Epic <N> Context:`. If valid, load it. If verification fails, HALT and report the failure.
+
+     5. **Previous story continuity.** Regardless of which context source succeeded above, scan `{{.implementation_artifacts}}` for specs from the same epic with `status: done` and a lower story number. Load the most recent one (highest story number below current). Extract its **Code Map**, **Design Notes**, **Spec Change Log**, and **task list** as continuity context for step-02 planning. If no `done` spec is found but an `in-review` spec exists for the same epic with a lower story number, note it to the user and ask whether to load it.
+
+     6. **Resolve `{story_key}`.** If not already set by an earlier early-exit path, run **Story-key resolution** (above) now.
+
+     **B) Freeform path** — if the intent is not an epic story:
+     - Planning artifacts are the output of BMAD phases 1-3. Typical files include:
+       - **PRD** (`*prd*`) — product requirements and success criteria
+       - **Architecture** (`*architecture*`) — technical design decisions and constraints
+       - **UX/Design** (`*ux*`) — user experience and interaction design
+       - **Epics** (`*epic*`) — feature breakdown into implementable stories
+       - **Product Brief** (`*brief*`) — project vision and scope
+     - Scan the listing for files matching these patterns. If any look relevant to the current intent, load them selectively — you don't need all of them, but you need the right constraints and requirements rather than guessing from code alone.
+2. Clarify intent. Do not fantasize, do not leave open questions. If you must ask questions, ask them as a numbered list. When the human replies, verify that every single numbered question was answered. If any were ignored, HALT and re-ask only the missing questions before proceeding. Keep looping until intent is clear enough to implement.
+3. Version control sanity check. Is the working tree clean? Does the current branch make sense for this intent — considering its name and recent history? If the tree is dirty or the branch is an obvious mismatch, HALT and ask the human before proceeding. If version control is unavailable, skip this check.
+4. Multi-goal check (see SCOPE STANDARD). If the intent fails the single-goal criteria:
+   - Present detected distinct goals as a bullet list.
+   - Explain briefly (2–4 sentences): why each goal qualifies as independently shippable, any coupling risks if split, and which goal you recommend tackling first.
+   - HALT and ask human: `[S] Split — pick first goal, defer the rest` | `[K] Keep all goals — accept the risks`
+   - On **S**: For each deferred goal, append one new entry to `{{.implementation_artifacts}}/deferred-work.md` using this format. Do not modify existing entries or look for duplicates. Narrow scope to the first-mentioned goal. Continue routing.
+     ```markdown
+     - source_spec: none
+       summary: <one sentence naming the deferred goal>
+       evidence: <why this was split from the current intent>
+     ```
+   - On **K**: Proceed as-is.
+5. Route — choose exactly one:
+
+   If the explicit spec-folder-plus-story-id pair had no matching story file, keep the colocated `spec_file` selected above. Otherwise, derive a valid kebab-case slug from the clarified intent. If the intent references a tracking identifier (story number, issue number, ticket ID), lead the slug with it (e.g. `3-2-digest-delivery`, `gh-47-fix-auth`). If `{{.implementation_artifacts}}/spec-{slug}.md` already exists: if its status is `draft`, treat it as the same work and resume it (set `spec_file` to that path, **EARLY EXIT** → `[[bmad-snapshot:step-02-plan.md]]`); otherwise append `-2`, `-3`, etc. Set `spec_file` = `{{.implementation_artifacts}}/spec-{slug}.md`.
+
+   **a) One-shot** — zero blast radius: no plausible path by which this change causes unintended consequences elsewhere. Clear intent, no architectural decisions.
+
+   **EARLY EXIT** → `[[bmad-snapshot:step-oneshot.md]]`
+
+   **b) Plan-code-review** — everything else. When uncertain whether blast radius is truly zero, choose this path.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-02-plan.md]]`
diff --git a/.claude/skills/bmad-build/step-02-plan.md b/.claude/skills/bmad-build/step-02-plan.md
new file mode 100644
index 0000000..fd57589
--- /dev/null
+++ b/.claude/skills/bmad-build/step-02-plan.md
@@ -0,0 +1,47 @@
+# Step 2: Plan
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`. Write any file output in `{{.document_output_language}}`.
+- No intermediate approvals.
+
+## INSTRUCTIONS
+
+1. Draft resume check. If `{spec_file}` exists with `status: draft`, read it and capture the verbatim `<frozen-after-approval>...</frozen-after-approval>` block as `preserved_intent`. Otherwise `preserved_intent` is empty.
+2. Investigate codebase. _Isolate deep exploration in synchronous subagents/tasks where available. To prevent context snowballing, instruct subagents to give you distilled summaries only._ Decide which findings actually matter for execution — the specific files, symbols/lines, reuse points, and read-only constraints — and carry those forward for the Code Map. This is where the investigation lands: the spec preserves it so it is never re-narrated to the implementer at dispatch time.
+3. Read `[[bmad-snapshot:spec-template.md]]` fully. Fill it out based on the intent and investigation, resolving the template's `date` field to the current system date. Drain the investigation into the `## Code Map` section — annotated paths, symbol/line anchors, reuse pointers, and read-only evidence — so the spec is the implementer's investigation map and the step-03 handoff need only point at it. If `preserved_intent` is non-empty, replace the `<frozen-after-approval>` block in the spec you just filled out with `preserved_intent`, before writing. Write the result to `{spec_file}`.
+4. Self-review against READY FOR DEVELOPMENT standard.
+5. If intent gaps exist, do not fantasize, do not leave open questions, HALT and ask the human.
+6. Token count check (see SCOPE STANDARD). If spec exceeds 1600 tokens:
+   - Show user the token count.
+   - HALT and ask human: `[S] Split — carve off secondary goals` | `[K] Keep full spec — accept the risks`
+   - On **S**: Propose the split — name each secondary goal. For each deferred goal, append one new entry to `{{.implementation_artifacts}}/deferred-work.md` using this format. Do not modify existing entries or look for duplicates. Rewrite the current spec to cover only the main goal — do not surgically carve sections out; regenerate the spec for the narrowed scope. Continue to checkpoint.
+     ```markdown
+     - source_spec: `{spec_file}`
+       summary: <one sentence naming the deferred goal>
+       evidence: <why this was split from the current spec>
+     ```
+   - On **K**: Continue to checkpoint with full spec.
+
+### CHECKPOINT 1
+
+Present summary. Display the spec file path as a CWD-relative path (no leading `/`) so it is clickable in the terminal. If token count exceeded 1600 and user chose [K], include the token count and explain why it may be a problem.
+
+After presenting the summary, display this note:
+
+---
+
+Before approving, you can open the spec file in an editor or ask me questions and tell me what to change. You can also use `bmad-advanced-elicitation`, `bmad-party-mode`, or `bmad-code-review` skills, ideally in another session to avoid context bloat.
+
+---
+
+HALT and ask human: `[A] Approve` | `[E] Edit`
+
+- **A**: Re-read `{spec_file}` from disk.
+  - **If the file is missing:** HALT. Tell the user the spec file is gone and STOP — do not write anything to `{spec_file}`, do not set status, do not proceed to Step 3. Nothing below this point runs.
+  - **If the file exists:** Compare the content to what you wrote. If it has changed since you wrote it, acknowledge the external edits — show a brief summary of what changed — and proceed with the updated version. Then set status `ready-for-dev` in `{spec_file}`. Everything inside `<frozen-after-approval>` is now locked — only the human can change it. → Step 3.
+- **E**: Apply changes, then return to CHECKPOINT 1.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-03-implement.md]]`
diff --git a/.claude/skills/bmad-build/step-03-implement.md b/.claude/skills/bmad-build/step-03-implement.md
new file mode 100644
index 0000000..33579f1
--- /dev/null
+++ b/.claude/skills/bmad-build/step-03-implement.md
@@ -0,0 +1,49 @@
+---
+---
+
+# Step 3: Implement
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`. Write any file output in `{{.document_output_language}}`.
+- No push. No remote ops.
+- Sequential execution only.
+- Content inside `<frozen-after-approval>` in `{spec_file}` is read-only. Do not modify.
+
+## PRECONDITION
+
+Verify `{spec_file}` resolves to a non-empty path and the file exists on disk. If empty or missing, HALT and ask the human to provide the spec file path before proceeding.
+
+## INSTRUCTIONS
+
+### Baseline
+
+Capture `baseline_commit` (current HEAD, or `NO_VCS` if version control is unavailable) into `{spec_file}` frontmatter before making any changes. If the frontmatter already contains `baseline_commit` (resumed run), preserve the existing value — never overwrite it.
+
+### Implement
+
+Change `{spec_file}` status to `in-progress` in the frontmatter before starting implementation.
+
+Follow `[[bmad-snapshot:sync-sprint-status.md]]` with `target_status` = `in-progress`.
+
+Execute the implementation handoff below: substitute the runtime placeholders (e.g. `{spec_file}`) into it, then follow it verbatim.
+
+{workflow.implementation_handoff}
+
+Do not add goal restatements, file lists, ownership boundaries, investigation detail, acceptance criteria, or CLAUDE.md/house-style rules to the dispatch — the spec is the subagent's sole source of truth, and that material already lives in it (investigation findings in its Code Map, the rest in the spec body). One line of sanctioned hedging belongs in the spec at planning time, not in the dispatch. If no subagents are available, implement directly from the spec. If the platform allows, keep the subagent available for re-engagement after it returns — step-04 may send it review fixes.
+
+The handoff directs the subagent to load the spec's `context:` files itself, so never pre-load and paste those files into the dispatch. Only when you implement directly (no subagent available) do you load a non-empty `context:` list yourself before starting.
+
+**Path formatting rule:** Any markdown links written into `{spec_file}` must use paths relative to `{spec_file}`'s directory so they are clickable in VS Code. Any file paths displayed in terminal/conversation output must use CWD-relative format with `:line` notation (e.g., `src/path/file.ts:42`) for terminal clickability. No leading `/` in either case.
+
+### Tasks & Acceptance Verification
+
+Before leaving this step, verify every task in the `## Tasks & Acceptance` section of `{spec_file}` is complete and every acceptance criterion is satisfied. Mark each finished task `[x]`. If any task is not done or any acceptance criterion is not satisfied, finish the missing work before proceeding.
+
+### Matrix Test Audit
+
+If `{spec_file}`'s `<frozen-after-approval>` block contains an I/O & Edge-Case Matrix, verify every matrix row is covered by at least one test that verifies its expected behavior, and that each covering test ran and passed in the verification output. A covering test that exists but did not run — unregistered, filtered out, skipped, or disabled — counts as missing. If a test disagrees with the matrix, never edit the expectation to match the code: fix the code, or if the matrix row itself is ambiguous, HALT and ask the human. Fix any other audit failure before proceeding.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-04-review.md]]`
diff --git a/.claude/skills/bmad-build/step-04-review.md b/.claude/skills/bmad-build/step-04-review.md
new file mode 100644
index 0000000..320e276
--- /dev/null
+++ b/.claude/skills/bmad-build/step-04-review.md
@@ -0,0 +1,55 @@
+# Step 4: Review
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`. Write any file output in `{{.document_output_language}}`.
+- All review subagents must run at the same model capability as the current session.
+- Run subagents synchronously: launch them together, then wait for all results before continuing.
+
+## INSTRUCTIONS
+
+Change `{spec_file}` status to `in-review` in the frontmatter before continuing.
+
+### Construct Diff
+
+Read `{baseline_commit}` from `{spec_file}` frontmatter. If `{baseline_commit}` is missing or `NO_VCS`, use best effort to determine what changed. Otherwise, construct `{diff_output}` covering all changes — tracked and untracked — since `{baseline_commit}`.
+
+Do NOT `git add` anything — this is read-only inspection.
+
+### Review
+
+Execute these review layers in parallel wherever their execution methods allow: substitute the runtime placeholders (e.g. `{diff_output}`) into each layer's instruction. When an instruction launches a reviewer subagent, launch that child with the prompt text after placeholder substitution; do not load the reviewer instruction file yourself. For any other customized instruction, execute it as written. Parallel means several blocking calls awaited together in this turn — never backgrounded or detached, never ending the turn to await results. When running layers as subagents, spawn every reviewer before reading or reacting to any of their output; begin collection and triage only once all are launched.
+
+{workflow.review_layers}
+
+If a layer's instruction requires subagents and none are available, for each such layer write under `{{.implementation_artifacts}}` the exact child prompt from that layer's instruction after placeholder substitution (not a path-only pointer), then HALT. Ask the human to run each in a separate session (ideally a different LLM) and paste back the findings.
+
+### Classify
+
+1. Deduplicate only findings with the same claim and same required action. Then evaluate each remaining finding independently. Do not reject a finding because a related finding was rejected.
+2. Assign severity to each finding by consequence for the artifact's main consumer (software user, document reader, etc).
+   Disregard any severity assigned by a reviewing subagent. Review subagents operate under by-design information asymmetry and do not have enough context to set final severity for this workflow.
+   - `low`: none or cosmetic
+   - `medium`: tolerable
+   - `high`: intolerable
+3. Route each finding into exactly one triage category. The first three categories are **this story's problem** — caused or exposed by the current change. The last two are **not this story's problem**.
+   - **intent_gap** — caused by the change; cannot be resolved from the spec because the captured intent is incomplete. Do not infer intent unless there is exactly one possible reading.
+   - **bad_spec** — caused by the change, including direct deviations from spec. The spec should have been clear enough to prevent it. When in doubt between bad_spec and patch, prefer bad_spec — a spec-level fix is more likely to produce coherent code.
+   - **patch** — caused by the change; trivially fixable without human input. Just part of the diff.
+   - **defer** — pre-existing issue not caused by this story, surfaced incidentally by the review. Collect for later focused attention.
+   - **reject** — noise. Drop silently. When unsure between defer and reject, prefer reject — only defer findings you are confident are real.
+4. Process findings in cascading order. If intent_gap or bad_spec findings exist, they trigger a loopback — lower findings are moot since code will be re-derived. If neither exists, process patch and defer normally. Before each loopback, read `{spec_file}` frontmatter `review_loop_iteration` (missing means `0`), increment it by 1, and write it back. If it exceeds 5, HALT and escalate to the human.
+   - **intent_gap** — Root cause is inside `<frozen-after-approval>`. Revert code changes. Loop back to the human to resolve. Once resolved, read fully and follow `[[bmad-snapshot:step-02-plan.md]]` to re-run steps 2–4.
+   - **bad_spec** — Root cause is outside `<frozen-after-approval>`. Before reverting code: extract KEEP instructions for positive preservation (what worked well and must survive re-derivation). Revert code changes. Read the `## Spec Change Log` in `{spec_file}` and strictly respect all logged constraints when amending the non-frozen sections that contain the root cause. Append a new change-log entry recording: the triggering finding, what was amended, the known-bad state avoided, and the KEEP instructions. Read fully and follow `[[bmad-snapshot:step-03-implement.md]]` to re-derive the code, then this step will run again.
+   - **patch** — Auto-fix. These are the only findings that survive loopbacks. If the step-03 implementation subagent can be re-engaged with its context intact, send it all patch findings in one synchronous message — for each: the file, what is wrong, and what the fix must do. If it cannot be re-engaged, apply the patches yourself. Then re-run the checks in `{spec_file}`'s `## Verification` section, if present; if verification fails and the failure cannot be fixed, HALT and escalate to the human.
+   - **defer** — Append one new entry to `{{.implementation_artifacts}}/deferred-work.md` using this format. Do not modify existing entries or look for duplicates.
+     ```markdown
+     - source_spec: `{spec_file}`
+       summary: <one sentence>
+       evidence: <why this is real>
+     ```
+   - **reject** — Drop silently.
+
+## NEXT
+
+Read fully and follow `[[bmad-snapshot:step-05-present.md]]`
diff --git a/.claude/skills/bmad-build/step-05-present.md b/.claude/skills/bmad-build/step-05-present.md
new file mode 100644
index 0000000..23ba728
--- /dev/null
+++ b/.claude/skills/bmad-build/step-05-present.md
@@ -0,0 +1,75 @@
+---
+---
+
+# Step 5: Present
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`. Write any file output in `{{.document_output_language}}`.
+- NEVER auto-push.
+
+## INSTRUCTIONS
+
+### Generate Suggested Review Order
+
+Read `{baseline_commit}` from `{spec_file}` frontmatter and construct the diff of all changes since that commit.
+
+Append the review order as a `## Suggested Review Order` section to `{spec_file}` **after the last existing section**. Do not modify the Code Map.
+
+Build the trail as an ordered sequence of **stops** — clickable `path:line` references with brief framing — optimized for a human reviewer reading top-down to understand the change:
+
+1. **Order by concern, not by file.** Group stops by the conceptual concern they address (e.g., "validation logic", "schema change", "UI binding"). A single file may appear under multiple concerns.
+2. **Lead with the entry point** — the single highest-leverage file:line a reviewer should look at first to grasp the design intent.
+3. **Inside each concern**, order stops from most important / architecturally interesting to supporting. Lightly bias toward higher-risk or boundary-crossing stops.
+4. **End with peripherals** — tests, config, types, and other supporting changes come last.
+5. **Every code reference is a clickable spec-file-relative link.** Compute each link target as a relative path from `{spec_file}`'s directory to the changed file. Format each stop as a markdown link: `[short-name:line](../../path/to/file.ts#L42)`. Use a `#L` line anchor. Use the file's basename (or shortest unambiguous suffix) plus line number as the link text. The relative path must be dynamically derived — never hardcode the depth.
+6. **Each stop gets one ultra-concise line of framing** (≤15 words) — why this approach was chosen here and what it achieves in the context of the change. No paragraphs.
+
+Format each stop as framing first, link on the next indented line:
+
+```markdown
+## Suggested Review Order
+
+**{Concern name}**
+
+- {one-line framing}
+  [`file.ts:42`](../../src/path/to/file.ts#L42)
+
+- {one-line framing}
+  [`other.ts:17`](../../src/path/to/other.ts#L17)
+
+**{Next concern}**
+
+- {one-line framing}
+  [`file.ts:88`](../../src/path/to/file.ts#L88)
+```
+
+> The `../../` prefix above is illustrative — compute the actual relative path from `{spec_file}`'s directory to each target file.
+
+When there is only one concern, omit the bold label — just list the stops directly.
+
+### Mark Spec Done
+
+Change `{spec_file}` status to `done` in the frontmatter.
+
+Follow `[[bmad-snapshot:sync-sprint-status.md]]` with `target_status` = `review`.
+
+### Commit and Complete
+
+If version control is available and the tree is dirty, create a local commit with a conventional message derived from the spec title.
+
+{workflow.open_spec}
+
+### Display Summary
+
+Display summary of your work to the user, including the commit hash if one was created. Any file paths shown in conversation/terminal output must use CWD-relative format (no leading `/`) with `:line` notation (e.g., `src/path/file.ts:42`) for terminal clickability — the goal is to make paths clickable in terminal emulators.
+
+Offer to push and/or create a pull request.
+
+Workflow complete.
+
+## On Complete
+
+If anything appears below, follow it as the final terminal instruction before exiting; otherwise exit normally.
+
+{workflow.on_complete}
diff --git a/.claude/skills/bmad-build/step-oneshot.md b/.claude/skills/bmad-build/step-oneshot.md
new file mode 100644
index 0000000..eaf9aeb
--- /dev/null
+++ b/.claude/skills/bmad-build/step-oneshot.md
@@ -0,0 +1,77 @@
+# Step One-Shot: Implement, Review, Present
+
+## RULES
+
+- **Language** — Speak in `{{.communication_language}}`. Write any file output in `{{.document_output_language}}`.
+- NEVER auto-push.
+- All review subagents must run at the same model capability as the current session.
+- Run subagents synchronously: launch them together, then wait for all results before continuing.
+
+## INSTRUCTIONS
+
+### Implement
+
+Follow `[[bmad-snapshot:sync-sprint-status.md]]` with `target_status` = `in-progress`.
+
+Implement the clarified intent directly.
+
+### Review
+
+Execute these review layers in parallel wherever their execution methods allow. After substituting runtime placeholders, when an instruction launches a reviewer subagent, launch that child with the prompt text; do not load the reviewer instruction file yourself. For any other customized instruction, execute it as written:
+
+{workflow.oneshot_review_layers}
+
+If a layer's instruction requires subagents and none are available, for each such layer write under `{{.implementation_artifacts}}` the exact child prompt from that layer's instruction after placeholder substitution (not a path-only pointer), then HALT. Ask the human to run each in a separate session and paste back the findings.
+
+### Classify
+
+Deduplicate all review findings. Three categories only:
+
+- **patch** — trivially fixable. Auto-fix immediately.
+- **defer** — pre-existing issue not caused by this change. Append one new entry to `{{.implementation_artifacts}}/deferred-work.md` using this format. Do not modify existing entries or look for duplicates.
+  ```markdown
+  - source_spec: `{spec_file}`
+    summary: <one sentence>
+    evidence: <why this is real>
+  ```
+- **reject** — noise. Drop silently.
+
+If a finding is caused by this change but too significant for a trivial patch, HALT and present it to the human for decision before proceeding.
+
+### Generate Spec Trace
+
+Set `title` = a concise title derived from the clarified intent.
+
+Write `{spec_file}` using `[[bmad-snapshot:spec-template.md]]`. Fill only these sections — delete all others:
+
+1. **Frontmatter** — set `title: '{title}'`, `type`, `created`, `status: 'done'`. Add `route: 'one-shot'`.
+2. **Title and Intent** — `# {title}` heading and `## Intent` with **Problem** and **Approach** lines. Reuse the summary you already generated for the terminal.
+3. **Suggested Review Order** — append after Intent. Build using the same convention as `[[bmad-snapshot:step-05-present.md]]` § "Generate Suggested Review Order" (spec-file-relative links, concern-based ordering, ultra-concise framing).
+
+Follow `[[bmad-snapshot:sync-sprint-status.md]]` with `target_status` = `review`.
+
+### Commit
+
+If version control is available and the tree is dirty, create a local commit with a conventional message derived from the intent. If VCS is unavailable, skip.
+
+### Present
+
+{workflow.open_spec}
+
+Display a summary in conversation output, including:
+
+- The commit hash (if one was created).
+- List of files changed with one-line descriptions. Any file paths shown in conversation/terminal output must use CWD-relative format (no leading `/`) with `:line` notation (e.g., `src/path/file.ts:42`) for terminal clickability — this differs from spec-file links which use spec-file-relative paths.
+- Review findings breakdown: patches applied, items deferred, items rejected. If all findings were rejected, say so.
+
+Offer to push and/or create a pull request.
+
+HALT and wait for human input.
+
+Workflow complete.
+
+## On Complete
+
+If anything appears below, follow it as the final terminal instruction before exiting; otherwise exit normally.
+
+{workflow.on_complete}
diff --git a/.claude/skills/bmad-build/sync-sprint-status.md b/.claude/skills/bmad-build/sync-sprint-status.md
new file mode 100644
index 0000000..0fe825e
--- /dev/null
+++ b/.claude/skills/bmad-build/sync-sprint-status.md
@@ -0,0 +1,19 @@
+# Sync Sprint Status
+
+Shared sub-step for updating `sprint-status.yaml` during build. Called from any route (plan-code-review, one-shot, future routes) with a `target_status` parameter.
+
+## Preconditions
+
+Skip this entire file (return to caller) if ANY of:
+- `story_key` is unset
+- `{{.implementation_artifacts}}/sprint-status.yaml` does not exist on disk
+
+## Instructions
+
+1. Load the FULL `{{.implementation_artifacts}}/sprint-status.yaml` file.
+2. Find the `development_status` entry matching `{story_key}`. If not found, warn the user once (`"{story_key} not found in sprint-status; skipping sprint sync"`) and return to caller.
+3. **Idempotency check.** If `development_status[{story_key}]` is already at `target_status` or a later state (`review` is later than `in-progress`; `done` is later than both), return to caller — no write needed. Never regress a story's status.
+4. Set `development_status[{story_key}]` to `{target_status}`.
+5. **Epic lift (only when `target_status` = `in-progress`).** Derive the parent epic key as `epic-{N}` from the leading numeric segment of `{story_key}` (e.g., `3-2-digest-delivery` → `epic-3`). If that entry exists and is `backlog`, set it to `in-progress`. Leave it alone otherwise. Skip this sub-step entirely when `target_status` is not `in-progress`.
+6. Refresh `last_updated` to the current date.
+7. Save the file, preserving ALL comments and structure including STATUS DEFINITIONS and WORKFLOW NOTES.
diff --git a/.claude/skills/bmad-build/workflow.md b/.claude/skills/bmad-build/workflow.md
new file mode 100644
index 0000000..ce7a80a
--- /dev/null
+++ b/.claude/skills/bmad-build/workflow.md
@@ -0,0 +1,84 @@
+# Build New Preview Workflow
+
+**Goal:** Turn user intent into a hardened, reviewable artifact.
+
+**CRITICAL:** If a step directs you to another snapshot file, read it fully and follow it. No exceptions.
+
+Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
+If you need an explicit user instruction to run them, ask once now for the whole workflow run.
+
+## READY FOR DEVELOPMENT STANDARD
+
+A specification is "Ready for Development" when:
+
+- **Actionable**: Every task has a file path and specific action.
+- **Logical**: Tasks ordered by dependency.
+- **Testable**: All ACs use Given/When/Then.
+- **Complete**: No placeholders or TBDs.
+- **Sufficient**: No known requirement, acceptance, dependency, or implementation gaps remain unresolved.
+- **Coherent**: No unresolved ambiguities or internal contradictions.
+
+## SCOPE STANDARD
+
+A specification should target a **single user-facing goal** within **900–1600 tokens**:
+
+- **Single goal**: One cohesive feature, even if it spans multiple layers/files. Multi-goal means >=2 **top-level independent shippable deliverables** — each could be reviewed, tested, and merged as a separate PR without breaking the others. Never count surface verbs, "and" conjunctions, or noun phrases. Never split cross-layer implementation details inside one user goal.
+  - Split: "add dark mode toggle AND refactor auth to JWT AND build admin dashboard"
+  - Don't split: "add validation and display errors" / "support drag-and-drop AND paste AND retry"
+- **900–1600 tokens**: Optimal range for LLM consumption. Below 900 risks ambiguity; above 1600 risks context-rot in implementation agents.
+- **Neither limit is a gate.** Both are proposals with user override.
+
+## Conventions
+
+- Every operational cross-file reference in this workflow is an absolute snapshot path. Open it directly; do not resolve it relative to a skill directory.
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- Whenever this workflow captures or records a version-control revision, obtain the full canonical identifier directly from version control and preserve it verbatim.
+
+## On Activation
+
+### Step 1: Execute Prepend Steps
+
+Execute each of these steps in order before proceeding (`_None._` means skip):
+
+{workflow.activation_steps_prepend}
+
+### Step 2: Load Persistent Facts
+
+Treat every entry below as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` -- load the referenced contents as facts. All other entries are facts verbatim (`_None._` means none):
+
+{workflow.persistent_facts}
+
+### Step 3: Execute Append Steps
+
+Execute each of these steps in order (`_None._` means skip):
+
+{workflow.activation_steps_append}
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+- **Micro-file Design**: Each step is self-contained and followed exactly
+- **Just-In-Time Loading**: Only load the current step file
+- **Sequential Enforcement**: Complete steps in order, no skipping
+- **State Tracking**: Persist progress via spec frontmatter and in-memory variables
+- **Append-Only Building**: Build artifacts incrementally
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Read the entire step file before acting
+2. **FOLLOW SEQUENCE**: Execute sections in order
+3. **WAIT FOR INPUT**: Halt at checkpoints and wait for human
+4. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- **NEVER** load multiple step files simultaneously
+- **ALWAYS** read entire step file before execution
+- **NEVER** skip steps or optimize the sequence
+- **ALWAYS** follow the exact instructions in the step file
+- **ALWAYS** halt at checkpoints and wait for human input
+
+## FIRST STEP
+
+Read fully and follow: `[[bmad-snapshot:step-01-clarify-and-route.md]]` to begin the workflow.
diff --git a/.claude/skills/bmad-checkpoint-preview/SKILL.md b/.claude/skills/bmad-checkpoint-preview/SKILL.md
new file mode 100644
index 0000000..06e45d6
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/SKILL.md
@@ -0,0 +1,68 @@
+---
+name: bmad-checkpoint-preview
+description: 'LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".'
+---
+
+# Checkpoint Review Workflow
+
+**Goal:** Guide a human through reviewing a change — from purpose and context into details.
+
+**Your Role:** You are assisting the user in reviewing a change.
+
+## Conventions
+
+- Bare paths (e.g. `step-01-orientation.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `implementation_artifacts`
+- `planning_artifacts`
+- `communication_language`
+- `document_output_language`
+
+### Step 5: Greet the User
+
+Greet the user, speaking in `{communication_language}`.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Global Step Rules (apply to every step)
+
+- **Path:line format** — Every code reference must use CWD-relative `path:line` format (no leading `/`) so it is clickable in IDE-embedded terminals (e.g., `src/auth/middleware.ts:42`).
+- **Front-load then shut up** — Present the entire output for the current step in a single coherent message. Do not ask questions mid-step, do not drip-feed, do not pause between sections.
+- **Language** — Speak in `{communication_language}`. Write any file output in `{document_output_language}`.
+
+## FIRST STEP
+
+Read fully and follow `./step-01-orientation.md` to begin.
diff --git a/.claude/skills/bmad-checkpoint-preview/customize.toml b/.claude/skills/bmad-checkpoint-preview/customize.toml
new file mode 100644
index 0000000..2f9b034
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-checkpoint-preview. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All stories must include testable acceptance criteria."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches its final step,
+# after the review decision (approve/rework/discuss) is made. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-checkpoint-preview/generate-trail.md b/.claude/skills/bmad-checkpoint-preview/generate-trail.md
new file mode 100644
index 0000000..6fd378b
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/generate-trail.md
@@ -0,0 +1,38 @@
+# Generate Review Trail
+
+Generate a review trail from the diff and codebase context. A generated trail is lower quality than an author-produced one, but far better than none.
+
+## Follow Global Step Rules in SKILL.md
+
+## INSTRUCTIONS
+
+1. Get the full diff against the appropriate baseline (same rules as Surface Area Stats in step-01).
+2. Read changed files in full — not just diff hunks. Surrounding code reveals intent that hunks alone miss. If total file content exceeds ~50k tokens, read only the files with the largest diff hunks in full and use hunks for the rest.
+3. If a spec exists, use its Intent section to anchor concern identification.
+4. Identify 2–5 concerns: cohesive design intents that each explain *why* behind a cluster of changes. Prefer functional groupings and architectural boundaries over file-level splits. A single-concern change is fine — don't invent groupings.
+5. For each concern, select 1–4 `path:line` stops — locations where the concern is most visible. Prefer entry points, decision points, and boundary crossings over mechanical changes.
+6. Lead with the entry point — the highest-leverage stop a reviewer should see first. Inside each concern, order stops so each builds on the previous. End with peripherals (tests, config, types).
+7. Format each stop using `path:line` per the global step rules:
+
+```
+**{Concern name}**
+
+- {one-line framing, ≤15 words}
+  `src/path/to/file.ts:42`
+```
+
+When there is only one concern, omit the bold label — just list the stops directly.
+
+## PRESENT
+
+Output after the orientation:
+
+```
+I built a review trail for this {change_type} (no author-produced trail was found):
+
+{generated trail}
+```
+
+The generated trail serves as the Suggested Review Order for subsequent steps. Set `review_mode` to `full-trail` — a trail now exists, so all downstream steps should treat it as one.
+
+If git is unavailable or the diff cannot be retrieved, return to step-01 with: "Could not generate trail — git unavailable."
diff --git a/.claude/skills/bmad-checkpoint-preview/step-01-orientation.md b/.claude/skills/bmad-checkpoint-preview/step-01-orientation.md
new file mode 100644
index 0000000..26f3554
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/step-01-orientation.md
@@ -0,0 +1,105 @@
+# Step 1: Orientation
+
+Display: `[Orientation] → Walkthrough → Detail Pass → Testing`
+
+## Follow Global Step Rules in SKILL.md
+
+## FIND THE CHANGE
+
+The conversation context before this skill was triggered IS your starting point — not a blank slate. Check in this order — stop as soon as the change is identified:
+
+1. **Explicit argument**
+   Did the user pass a PR, commit SHA, branch, or spec file this message?
+   - PR reference → resolve to branch/commit via `gh pr view`. If resolution fails, ask for a SHA or branch.
+   - Spec file, commit, or branch → use directly.
+
+2. **Recent conversation**
+   Do the last few messages reveal what change the user wants reviewed? Look for spec paths, commit refs, branches, PRs, or descriptions of a change. Use the same routing as above.
+
+3. **Sprint tracking**
+   Check for a sprint status file (`*sprint-status*`) in `{implementation_artifacts}` or `{planning_artifacts}`. If found, scan for stories with status `review`:
+   - Exactly one → suggest it and confirm with the user.
+   - Multiple → present as numbered options.
+   - None → fall through.
+
+4. **Current git state**
+   Check current branch and HEAD. Confirm: "I see HEAD is `<short-sha>` on `<branch>` — is this the change you want to review?"
+
+5. **Ask**
+   If none of the above identified a change, ask:
+   - What changed and why?
+   - Which commit, branch, or PR should I look at?
+   - Do you have a spec, bug report, or anything else that explains what this change is supposed to do?
+
+   If after 3 exchanges you still can't identify a change, HALT.
+
+Never ask extra questions beyond what the cascade prescribes. If a step above already identified the change, skip the remaining steps.
+
+## ENRICH
+
+Once a change is identified from any source above, fill in the complementary artifact:
+
+- If you have a spec, look for `baseline_commit` in its frontmatter to determine the diff baseline.
+- If you have a commit or branch, check `{implementation_artifacts}` for a spec whose `baseline_commit` is an ancestor of that commit/branch (i.e., the spec describes work done on top of that baseline).
+- If you found both a spec and a commit/branch, use both.
+
+## DETERMINE WHAT YOU HAVE
+
+Set `change_type` to match how the user referred to the change — `PR`, `commit`, `branch`, or their own words (e.g. `auth refactor`). Default to `change` if ambiguous.
+
+Set `review_mode` — pick the first match:
+
+1. **`full-trail`** — ENRICH found a spec with a `## Suggested Review Order` section. Intent source: spec's Intent section.
+2. **`spec-only`** — ENRICH found a spec but it has no Suggested Review Order. Intent source: spec's Intent section.
+3. **`bare-commit`** — no spec found. Intent source: commit message. If the commit message is terse (under 10 words), scan the diff for the primary change pattern and draft a one-sentence intent. Flag it as `[inferred]` in the output so the user can correct it.
+
+## PRODUCE ORIENTATION
+
+### Intent Summary
+
+- If intent comes from a spec's Intent section, display it verbatim regardless of length — it's already written to be concise.
+- For other sources (commit messages, bug reports, user description): if ≤200 tokens, display verbatim. If longer, distill to ≤200 tokens. Link to the full source when one exists (e.g. a file path or URL).
+- Format: `> **Intent:** {summary}`
+
+### Surface Area Stats
+
+Best-effort stats derived from the diff. Try these baselines in order:
+
+1. `baseline_commit` from the spec's frontmatter.
+2. Branch merge-base against `main` (or the default branch).
+3. `HEAD~1..HEAD` (latest commit only — tell the user).
+4. If git is unavailable or all of the above fail, skip stats and note: "Could not compute stats."
+
+Use `git diff --stat` and `git diff --numstat` for file-level counts, and scan the full diff content for the richer metrics.
+
+Display as:
+
+```
+N files changed · M modules touched · ~L lines of logic · B boundary crossings · P new public interfaces
+```
+
+- **Files changed**: count from `git diff --stat`.
+- **Modules touched**: distinct top-level directories with changes (from `--stat` file paths).
+- **Lines of logic**: added/modified lines excluding blanks, imports, formatting. Scan diff content; `~` because approximate.
+- **Boundary crossings**: changes spanning more than one top-level module. `0` if single module.
+- **New public interfaces**: new exports, endpoints, public methods found in the diff. `0` if none.
+
+Omit any metric you cannot compute rather than guessing.
+
+### Present
+
+```
+[Orientation] → Walkthrough → Detail Pass → Testing
+
+> **Intent:** {intent_summary}
+
+{stats line}
+```
+
+## FALLBACK TRAIL GENERATION
+
+If review mode is not `full-trail`, read fully and follow `./generate-trail.md` to build one from the diff. Then return here and continue to NEXT. If trail generation fails (e.g., git unavailable), the original review mode is preserved — step-02 handles this with its non-trail path.
+
+## NEXT
+
+Read fully and follow `./step-02-walkthrough.md`
diff --git a/.claude/skills/bmad-checkpoint-preview/step-02-walkthrough.md b/.claude/skills/bmad-checkpoint-preview/step-02-walkthrough.md
new file mode 100644
index 0000000..aec40c4
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/step-02-walkthrough.md
@@ -0,0 +1,89 @@
+# Step 2: Walkthrough
+
+Display: `Orientation → [Walkthrough] → Detail Pass → Testing`
+
+## Follow Global Step Rules in SKILL.md
+
+- Organize by **concern**, not by file. A concern is a cohesive design intent — e.g., "input validation," "state management," "API contract." One file may appear under multiple concerns; one concern may span multiple files.
+- The walkthrough activates **design judgment**, not correctness checking. Frame each concern as "here's what this change does and why" — the human evaluates whether it's the right approach for the system.
+
+## BUILD THE WALKTHROUGH
+
+### Identify Concerns
+
+**With Suggested Review Order** (`full-trail` mode — the normal path, including when step-01 generated a trail):
+
+1. Read the Suggested Review Order stops from the spec (or from conversation context if generated by step-01 fallback).
+2. Resolve each stop to a file in the current repo. Output in `path:line` format per the standing rule.
+3. Read the diff to understand what each stop actually does.
+4. Group stops by concern. Stops that share a design intent belong together even if they're in different files. A stop may appear under multiple concerns if it serves multiple purposes.
+
+**Without Suggested Review Order** (fallback when trail generation failed, e.g., git unavailable):
+
+1. Get the diff against the appropriate baseline (same rules as step 1).
+2. Identify concerns by reading the diff for cohesive design intents:
+   - Functional groupings — what user-facing behavior does each cluster of changes support?
+   - Architectural layers — does the change cross boundaries (API → service → data)?
+   - Design decisions — where did the author choose between alternatives?
+3. For each concern, identify the key code locations as `path:line` stops.
+
+### Order for Comprehension
+
+Sequence concerns top-down: start with the highest-level intent (the "what and why"), then drill into supporting implementation. Within each concern, order stops so each one builds on the previous. The reader should never encounter a reference to something they haven't seen yet.
+
+If the change has a natural entry point (e.g., a new public API, a config change, a UI entry point), lead with it.
+
+### Write Each Concern
+
+For each concern, produce:
+
+1. **Heading** — a short phrase naming the design intent (not a file name, not a module name).
+2. **Why** — 1–2 sentences: what problem this concern addresses, why this approach was chosen over alternatives. If the spec documents rejected alternatives, reference them here.
+3. **Stops** — each stop on its own line: `path:line` followed by a brief phrase (not a sentence) describing what this location does for the concern. Keep framing under 15 words per stop.
+
+Target 2–5 concerns for a typical change. A single-concern change is fine — don't invent groupings. A change with more than 7 concerns is a signal the scope may be too large, but present it anyway.
+
+## PRESENT
+
+Output the full walkthrough as a single message with this structure:
+
+```
+Orientation → [Walkthrough] → Detail Pass → Testing
+```
+
+Then each concern group using this format:
+
+```
+### {Concern Heading}
+
+{Why — 1–2 sentences}
+
+- `path:line` — {brief framing}
+- `path:line` — {brief framing}
+- ...
+```
+
+End the message with:
+
+```
+---
+
+Take your time — click through the stops, read the diff, trace the logic. While you are reviewing, you can:
+- "run advanced elicitation on the error handling"
+- "party mode on whether this schema migration is safe"
+- or just ask anything
+
+When you're ready, say **next** and I'll surface the highest-risk spots.
+```
+
+## EARLY EXIT
+
+If at any point the human signals they want to make a decision about this {change_type} (e.g., "let's ship it", "this needs a rethink", "I'm done reviewing", or anything suggesting they're ready to decide), confirm their intent:
+
+- If they want to **approve and ship** → read fully and follow `./step-05-wrapup.md`
+- If they want to **reject and rework** → read fully and follow `./step-05-wrapup.md`
+- If you misread them → acknowledge and continue the current step.
+
+## NEXT
+
+Default: read fully and follow `./step-03-detail-pass.md`
diff --git a/.claude/skills/bmad-checkpoint-preview/step-03-detail-pass.md b/.claude/skills/bmad-checkpoint-preview/step-03-detail-pass.md
new file mode 100644
index 0000000..49d8024
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/step-03-detail-pass.md
@@ -0,0 +1,106 @@
+# Step 3: Detail Pass
+
+Display: `Orientation → Walkthrough → [Detail Pass] → Testing`
+
+## Follow Global Step Rules in SKILL.md
+
+- The detail pass surfaces what the human should **think about**, not what the code got wrong. Machine hardening already handled correctness. This activates risk awareness.
+- The LLM detects risk category by pattern. The human judges significance. Do not assign severity scores or numeric rankings — ordering by blast radius (below) is sequencing for readability, not a severity judgment.
+- If no high-risk spots exist, say so explicitly. Do not invent findings.
+
+## IDENTIFY RISK SPOTS
+
+Scan the diff for changes touching risk-sensitive patterns. Look for 2–5 spots where a mistake would have the highest blast radius — not the most complex code, but the code where being wrong costs the most.
+
+Risk categories to detect:
+
+- `[auth]` — authentication, authorization, session, token, permission, access control
+- `[public API]` — new/changed endpoints, exports, public methods, interface contracts
+- `[schema]` — database migrations, schema changes, data model modifications, serialization
+- `[billing]` — payment, pricing, subscription, metering, usage tracking
+- `[infra]` — deployment, CI/CD, environment variables, config files, infrastructure
+- `[security]` — input validation, sanitization, crypto, secrets, CORS, CSP
+- `[config]` — feature flags, environment-dependent behavior, defaults
+- `[other]` — anything risk-sensitive that doesn't fit the above (e.g., concurrency, data privacy, backwards compatibility). Use a descriptive tag.
+
+Sequence spots so the highest blast radius comes first (how much breaks if this is wrong), not by diff order or file order. If more than 5 spots qualify, show the top 5 and note: "N additional spots omitted — ask if you want the full list."
+
+If the change has no spots matching these patterns, state: "No high-risk spots found in this change — the diff speaks for itself." Do not force findings.
+
+## SURFACE MACHINE HARDENING FINDINGS
+
+Check whether the spec has a `## Spec Change Log` section with entries (populated by adversarial review loops).
+
+- **If entries exist:** Read them. Surface findings that are instructive for the human reviewer — not bugs that were already fixed, but decisions the review loop flagged that the human should be aware of. Format: brief summary of what was flagged and what was decided.
+- **If no entries or no spec:** Skip this section entirely. Do not mention it.
+
+## PRESENT
+
+Output as a single message:
+
+```
+Orientation → Walkthrough → [Detail Pass] → Testing
+```
+
+### Risk Spots
+
+For each spot, one line:
+
+```
+- `path:line` — [tag] reason-phrase
+```
+
+Example:
+
+```
+- `src/auth/middleware.ts:42` — [auth] New token validation bypasses rate limiter
+- `migrations/003_add_index.sql:7` — [schema] Index on high-write table, check lock behavior
+- `api/routes/billing.ts:118` — [billing] Metering calculation changed, verify idempotency
+```
+
+### Machine Hardening (only if findings exist)
+
+```
+### Machine Hardening
+
+- Finding summary — what was flagged, what was decided
+- ...
+```
+
+### Closing menu
+
+End the message with:
+
+```
+---
+
+You've seen the design and the risk landscape. From here:
+- **"dig into [area]"** — I'll deep-dive that specific area with correctness focus
+- **"next"** — I'll suggest how to observe the behavior
+```
+
+## EARLY EXIT
+
+If at any point the human signals they want to make a decision about this {change_type} (e.g., "let's ship it", "this needs a rethink", "I'm done reviewing", or anything suggesting they're ready to decide), confirm their intent:
+
+- If they want to **approve and ship** → read fully and follow `./step-05-wrapup.md`
+- If they want to **reject and rework** → read fully and follow `./step-05-wrapup.md`
+- If you misread them → acknowledge and continue the current step.
+
+## TARGETED RE-REVIEW
+
+When the human says "dig into [area]" (e.g., "dig into the auth changes", "dig into the schema migration"):
+
+1. If the specified area does not map to any code in the diff, say so: "I don't see [area] in this change — did you mean something else?" Return to the closing menu.
+2. Identify all code locations in the diff relevant to the specified area.
+3. Read each location in full context (not just the diff hunk — read surrounding code).
+4. Shift to **correctness mode**: trace edge cases, check boundary conditions, verify error handling, look for off-by-one errors, race conditions, resource leaks.
+5. Present findings as a compact list — each finding is `path:line` + what you found + why it matters.
+6. If nothing concerning is found, say so: "Looked closely at [area] — nothing concerning. The implementation is solid."
+7. After presenting, show only the closing menu (not the full risk spots list again).
+
+The human can trigger multiple targeted re-reviews. Each time, present new findings and the closing menu only.
+
+## NEXT
+
+Read fully and follow `./step-04-testing.md`
diff --git a/.claude/skills/bmad-checkpoint-preview/step-04-testing.md b/.claude/skills/bmad-checkpoint-preview/step-04-testing.md
new file mode 100644
index 0000000..f818079
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/step-04-testing.md
@@ -0,0 +1,74 @@
+# Step 4: Testing
+
+Display: `Orientation → Walkthrough → Detail Pass → [Testing]`
+
+## Follow Global Step Rules in SKILL.md
+
+- This is **experiential**, not analytical. The detail pass asked "did you think about X?" — this says "you could see X with your own eyes."
+- Do not prescribe. The human decides whether observing the behavior is worth their time. Frame suggestions as options, not obligations.
+- Do not duplicate CI, test suites, or automated checks. Assume those exist and work. This is about manual observation — the kind of confidence-building no automated test provides.
+- If the change has no user-visible behavior, say so explicitly. Do not invent observations.
+
+## IDENTIFY OBSERVABLE BEHAVIOR
+
+Scan the diff and spec for changes that produce behavior a human could directly observe. Categories to look for:
+
+- **UI changes** — new screens, modified layouts, changed interactions, error states
+- **CLI/terminal output** — new commands, changed output, new flags or options
+- **API responses** — new endpoints, changed payloads, different status codes
+- **State changes** — database records, file system artifacts, config effects
+- **Error paths** — bad input, missing dependencies, edge conditions
+
+For each observable behavior, determine:
+
+1. **What to do** — the specific action (command to run, button to click, request to send)
+2. **What to expect** — the observable result that confirms the change works
+3. **Why bother** — one phrase connecting this observation to the change's intent (omit if obvious from context)
+
+Target 2–5 suggestions for a typical change. If more than 5 qualify, prioritize by how much confidence the observation provides relative to effort. A change with zero observable behavior is fine — do not pad with trivial observations.
+
+## PRESENT
+
+Output as a single message:
+
+```
+Orientation → Walkthrough → Detail Pass → [Testing]
+```
+
+Then the testing suggestions using this format:
+
+```
+### How to See It Working
+
+**{Brief description}**
+Do: {specific action}
+Expect: {observable result}
+
+**{Brief description}**
+Do: {specific action}
+Expect: {observable result}
+```
+
+Include code blocks for commands or requests where helpful.
+
+If the change has no observable behavior, replace the suggestions with:
+
+```
+### How to See It Working
+
+This change is internal — no user-visible behavior to observe. The diff and tests tell the full story.
+```
+
+### Closing
+
+End the message with:
+
+```
+---
+
+You've seen the change and how to verify it. When you're ready to make a call, just say so.
+```
+
+## NEXT
+
+When the human signals they're ready to make a decision about this {change_type}, read fully and follow `./step-05-wrapup.md`
diff --git a/.claude/skills/bmad-checkpoint-preview/step-05-wrapup.md b/.claude/skills/bmad-checkpoint-preview/step-05-wrapup.md
new file mode 100644
index 0000000..dc4363b
--- /dev/null
+++ b/.claude/skills/bmad-checkpoint-preview/step-05-wrapup.md
@@ -0,0 +1,30 @@
+# Step 5: Wrap-Up
+
+Display: `Orientation → Walkthrough → Detail Pass → Testing → [Wrap-Up]`
+
+## Follow Global Step Rules in SKILL.md
+
+## PROMPT FOR DECISION
+
+```
+---
+
+Review complete. What's the call on this {change_type}?
+- **Approve** — ship it (I can help with interactive patching first if needed)
+- **Rework** — back to the drawing board (revert, revise the spec, try a different approach)
+- **Discuss** — something's still on your mind
+```
+
+HALT — do not proceed until the user makes their choice.
+
+## ACT ON DECISION
+
+- **Approve**: Acknowledge briefly. If the human wants to patch something before shipping, help apply the fix interactively. If reviewing a PR, offer to approve via `gh pr review --approve` — but confirm with the human before executing, since this is a visible action on a shared resource.
+- **Rework**: Ask what went wrong — was it the approach, the spec, or the implementation? Help the human decide on next steps (revert commit, open an issue, revise the spec, etc.). Help draft specific, actionable feedback tied to `path:line` locations if the change is a PR from someone else.
+- **Discuss**: Open conversation — answer questions, explore concerns, dig into any aspect. After discussion, return to the decision prompt above.
+
+## On Complete
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+
+If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
diff --git a/.claude/skills/bmad-code-review/SKILL.md b/.claude/skills/bmad-code-review/SKILL.md
new file mode 100644
index 0000000..83cea86
--- /dev/null
+++ b/.claude/skills/bmad-code-review/SKILL.md
@@ -0,0 +1,90 @@
+---
+name: bmad-code-review
+description: 'Adversarial code review using parallel review layers and structured triage. Use when the user says "run code review" or "review this code"'
+---
+
+# Code Review Workflow
+
+**Goal:** Review code changes adversarially. No noise, no filler.
+
+Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
+If you need an explicit user instruction to run them, ask once now for the whole workflow run.
+
+## Conventions
+
+- Bare paths (e.g. `checklist.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
+- `project_context` = `**/project-context.md` (load if exists)
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+- **Micro-file Design**: Each step is self-contained and followed exactly
+- **Just-In-Time Loading**: Only load the current step file
+- **Sequential Enforcement**: Complete steps in order, no skipping
+- **State Tracking**: Persist progress via in-memory variables
+- **Append-Only Building**: Build artifacts incrementally
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Read the entire step file before acting
+2. **FOLLOW SEQUENCE**: Execute sections in order
+3. **WAIT FOR INPUT**: Halt at checkpoints and wait for human
+4. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- **NEVER** load multiple step files simultaneously
+- **ALWAYS** read entire step file before execution
+- **NEVER** skip steps or optimize the sequence
+- **ALWAYS** follow the exact instructions in the step file
+- **ALWAYS** halt at checkpoints and wait for human input
+
+## FIRST STEP
+
+Read fully and follow: `./steps/step-01-gather-context.md`
diff --git a/.claude/skills/bmad-code-review/customize.toml b/.claude/skills/bmad-code-review/customize.toml
new file mode 100644
index 0000000..3b4ab86
--- /dev/null
+++ b/.claude/skills/bmad-code-review/customize.toml
@@ -0,0 +1,113 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-code-review. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All stories must include testable acceptance criteria."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches its final step,
+# after review findings are presented and sprint status is synced. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
+
+# Review layers for the review step. `instruction` is the layer's whole
+# execution recipe — subagents by default, but an override may run anything
+# (e.g. an external reviewer via bash). {diff_output} and {spec_file} are
+# substituted at run time. `when` (optional) gates a layer; empty
+# `instruction` disables it.
+
+[[workflow.review_layers]]
+id = "blind-hunter"
+name = "Blind Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Conduct a review of CONTENT.
+Look for what's missing, not only what's wrong.
+Find at least ten issues to fix or improve.
+Output a Markdown list of findings only — no severity, priority, or ranking.
+If the content is empty, stop and say so.
+If you have zero findings, re-check and keep thinking; do not stop with an empty list.
+
+CONTENT:
+{diff_output}
+
+Do not invoke any skill. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "edge-case-hunter"
+name = "Edge Case Hunter"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/edge-case-hunter.md` completely and follow it as your review instructions.
+
+Review content:
+
+{diff_output}
+
+Do not invoke any skill. If the instruction file is unreadable, report that exact failure and stop. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "verification-gap"
+name = "Verification Gap Reviewer"
+instruction = """
+Launch a context-free subagent with this prompt:
+
+Read `{skill-root}/review-prompts/verification-gap.md` completely and follow it as your review instructions.
+
+Review content:
+
+{diff_output}
+
+Do not invoke any skill. If the instruction file is unreadable, report that exact failure and stop. Return only the review result.
+
+"""
+
+[[workflow.review_layers]]
+id = "acceptance-auditor"
+name = "Acceptance Auditor"
+when = 'Only when {review_mode} = "full".'
+instruction = """
+Launch a subagent with this prompt:
+
+You are an Acceptance Auditor. Review the provided diff against `{spec_file}` and any loaded context docs. Check for: violations of acceptance criteria, deviations from spec intent, missing implementation of specified behavior, contradictions between spec constraints and actual code. Output findings as a Markdown list. Each finding: one-line title, which AC/constraint it violates, and evidence from the diff.
+
+Diff:
+
+{diff_output}
+"""
diff --git a/.claude/skills/bmad-code-review/references/deletion-check.md b/.claude/skills/bmad-code-review/references/deletion-check.md
new file mode 100644
index 0000000..5cc3d77
--- /dev/null
+++ b/.claude/skills/bmad-code-review/references/deletion-check.md
@@ -0,0 +1,14 @@
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
diff --git a/.claude/skills/bmad-code-review/review-prompts/edge-case-hunter.md b/.claude/skills/bmad-code-review/review-prompts/edge-case-hunter.md
new file mode 100644
index 0000000..11df57e
--- /dev/null
+++ b/.claude/skills/bmad-code-review/review-prompts/edge-case-hunter.md
@@ -0,0 +1,88 @@
+# Edge Case Hunter Review
+
+**Goal:** You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.
+When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
+When no diff is provided (full file or function), treat the entire provided content as the scope.
+Ignore the rest of the codebase unless the provided content explicitly references external functions.
+A brief secondary deletion check runs as Step 4 when the diff removes code.
+
+**Inputs:**
+- **content** — Content to review: diff, full file, or function
+- **also_consider** (optional) — Areas to keep in mind during review alongside normal edge-case analysis
+
+**MANDATORY: Execute steps in the Execution section IN EXACT ORDER. DO NOT skip steps or change the sequence. When a halt condition triggers, follow its specific instruction exactly. Each action within a step is a REQUIRED action to complete that step.**
+
+**Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do NOT editorialize or add filler. Do not assign severity labels, rankings, or priority levels.**
+
+
+## EXECUTION
+
+### Step 1: Receive Content
+
+- Load the content to review strictly from the parent message that launched you (not from this instruction file)
+- If content is empty, or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+- Identify content type (diff, full file, or function) to determine scope rules
+
+### Step 2: Exhaustive Path Analysis
+
+**Walk every branching path and boundary condition within scope — report only unhandled ones.**
+
+- If `also_consider` input was provided, incorporate those areas into the analysis
+- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else/default, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Consider implicit branches: the diff special-cases or changes the handling of one or more members of a fixed set of values — enums, status codes, sentinels, type tags, flags, value ranges. The rest of the set is implicit branches (e.g. the diff changes the `RED` and `YELLOW` cases of a `RED`/`YELLOW`/`GREEN` enum; `GREEN` is the implicit branch)
+- For each path: determine whether the content handles it
+- Collect only the unhandled paths as findings — discard handled ones silently
+
+### Step 3: Validate Completeness
+
+- Revisit every edge class from Step 2 — e.g., missing else/default, null/empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Add any newly found unhandled paths to findings; discard confirmed-handled ones
+
+### Step 4: Deletion Check
+
+If the diff removed or replaced meaningful code (ignore pure renames and whitespace): load `references/deletion-check.md` and follow it.
+
+### Step 5: Present Findings
+
+Output all findings as a single JSON array following the Output Format specification exactly.
+
+
+## OUTPUT FORMAT
+
+Return ONLY a valid JSON array of objects. Each edge-case finding contains exactly these four fields:
+
+```json
+[{
+  "location": "file:start-end (or file:line when single line, or file:hunk when exact line unavailable)",
+  "trigger_condition": "one-line description (max 15 words)",
+  "guard_snippet": "minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)",
+  "potential_consequence": "what could actually go wrong (max 15 words)"
+}]
+```
+
+No extra text, no explanations, no markdown wrapping. An empty array `[]` is valid when nothing is found. Deletion findings from Step 4, if any, go in the same array with the extra fields defined in `references/deletion-check.md`.
+
+
+## HALT CONDITIONS
+
+- If content is empty or cannot be decoded as text, return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` and stop
+<reference path="references/deletion-check.md">
+# Deletion Check
+
+Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
+
+Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+Add nothing if nothing qualifies.
+</reference>
+
+## CONTENT SOURCE
+
+Review the content supplied under "Review content:" in the message that launched you.
diff --git a/.claude/skills/bmad-code-review/review-prompts/verification-gap.md b/.claude/skills/bmad-code-review/review-prompts/verification-gap.md
new file mode 100644
index 0000000..4adc52d
--- /dev/null
+++ b/.claude/skills/bmad-code-review/review-prompts/verification-gap.md
@@ -0,0 +1,113 @@
+# Verification Gap Review
+
+**Goal:** Find changed behavior that could break without reliable verification catching it. Ask one question — "if the behavior this change is supposed to produce broke where it's actually used, would verification fail?" Do not hunt for correctness bugs, but report genuine problems you notice while tracing verification.
+
+The main verification gap shapes are:
+
+1. **Regression gap:** the changed code regresses where it's used, and no test covering that use would fail.
+2. **Missing-adoption gap:** a place that should now use the new behavior doesn't; it handles the same case its own way, or not at all, and no test would flag the omission.
+3. **Broken-verification gap:** a test appears to cover the changed behavior, but would not actually protect it because it is skipped, flaky, not run in the normal verification path, or too weak to observe the regression.
+
+## Evidence Rules
+
+- Read a test before claiming what it covers, runs, asserts, or misses.
+- Before claiming no test exists, search the whole repo by the symbol under test and by import references; expected file locations are not enough.
+- Never assert what you did not verify. If a finding cannot be grounded, drop it.
+- In a finding, say what you actually checked — "none of the tests I read cover this" — and show how far you looked. Say a test doesn't exist anywhere only when the symbol/import-reference search actually shows that.
+- Do not assign severity, confidence, priority, or ranking.
+
+## Review Sequence
+
+### Step 1: Screen for behavioral change
+
+Screen each part of the change separately. If a part is non-behavioral, skip it. Call a part non-behavioral only when the changed code does not alter return values, thrown errors, caller-visible side effects, or observable state (including iteration order and emitted messages). Once a part meets that test, move on; do not inspect callers or tests for extra confirmation.
+
+Common non-behavioral examples: formatting, comments, whitespace; pure renames; trivial getters/setters and pass-throughs; type-only or compiler-enforced changes with no runtime effect; etc.
+
+Only outcomes produced by deterministic code are worth automatically testing; tests are useless on static source text and brittle on LLM output. Skip those parts.
+
+If every part is skipped, output the clean result (see Output Format).
+
+### Step 2: Find the behavior that changed
+
+Identify what behavior changed compared to the previous version: output, side effect, branch, error path, schema/event shape, config default, validation/authorization rule, external contract, etc. If the change affects more than one behavior, handle each separately.
+
+Treat broad-impact changes as behavioral even when no single changed line looks important: dependency, toolchain, build/config, data-file, etc.
+
+### Step 3: Trace where that behavior is used
+
+Trace the changed behavior to the places that observe it. Start with direct callers and registered entry points (routes, commands, DI), contract consumers (schemas, events, APIs, database readers), and reverse-dependency info if already available.
+
+Follow a path only while the changed behavior is reachable and unverified. Stop when a test at that boundary would fail, the consumer does not observe the changed behavior, or the next hop is guesswork (dynamic dispatch, reflection, outside-repo consumers, etc.). Prefer the nearest observable boundary, often one to three hops away, especially across contract, integration, or service edges. If there are more than five similar consumers, group obvious repeats and check representative paths; expand only when a consumer observes the behavior differently.
+
+### Step 4: Qualify the consumer, then check its test
+
+For each consumer, name the smallest realistic regression this consumer would observe: invert the branch, drop the default, omit the field, return the old error code, skip the integration call, etc. This is the Demonstration. If no such regression exists, drop the path; untested downstream code is not a finding.
+
+A `Missing-adoption gap` qualifies not by the adoption failure alone but by a supersession signal: the change gives clear evidence the new behavior is meant to replace the local one — PR intent, naming or docs, a replaced sibling site, deleted duplicate logic, or a test defining the new rule — and the local site shares the same observable contract. Without a supersession signal and a shared observable contract, it is a refactor suggestion, not a verification-gap finding. Once both hold, check whether any test for that site would flag the non-adoption; missing coverage of the non-adoption is the gap itself, not a disqualifier.
+
+Find and read the relevant test. Ask whether the Demonstration would make an assertion fail.
+
+- If yes, the behavior is verified. No finding.
+- For a regression-style Demonstration: if no test runs the path, the test is skipped/flaky/not run normally, or the test runs the code without checking the changed result, report a `Regression gap` or `Broken-verification gap`.
+- For a qualifying Missing-adoption case: if none of the site tests you found assert it adopts the new behavior, report a `Missing-adoption gap`.
+
+A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; source-text assertions that match a file's wording instead of running it; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
+
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
+Common patterns:
+
+- **Caller-path gap** — helper test covers the branch, but caller values skip it.
+- **Contract drift** — payload/schema/event changes must be verified at the consumer.
+- **Migration compatibility** — tests only create new-format rows or fresh schemas.
+- **Phantom exception** — handled partial-failure path has no test.
+- **Missing-adoption gap** — sibling site should use the new rule/helper and does not.
+- **Removed verification** — deleted test or weakened assertion leaves behavior unpinned; removing a source-text assertion is not this, since it never counted.
+
+### Step 5: Confirm each finding is real
+
+Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
+
+Explain why the test misses the bug using what the test sets up and checks.
+
+Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
+
+Report genuine problems you noticed while tracing verification, even if they are not verification gaps. Put them under `Other findings` in the output. This permits reporting what you already reached, not extra hunting.
+
+## OUTPUT FORMAT
+
+Emit each verification-gap finding as one block. No general advice, no severity or confidence.
+
+```markdown
+### <one-line title naming the gap>
+
+- **Changed surface:** the exact behavior or contract that changed — `file:line`.
+- **Impacted consumer or site:** named concretely with `file:line` (e.g. "the `createInvoice` mutation used by the billing dashboard at `billing/dashboard.ts:88`," not "callers of this function").
+- **Existing test evidence:**
+  - `Regression gap`: what the relevant test actually asserts, with `file:line`; or, if none, the symbol/import-reference searches run and their result.
+  - `Missing-adoption gap`: tests for the impacted site, and whether any assert it adopts the new behavior.
+  - `Broken-verification gap`: the apparent test or verification path, and why it does not count.
+- **Missing verification:** the precise assertion or check that's absent.
+- **Demonstration:**
+  - `Regression gap` / `Broken-verification gap`: the concrete regression that would ship undetected, and why the tests you checked would not fail.
+  - `Missing-adoption gap`: the case the site mishandles by not adopting the new behavior, and that none of the tests you read assert adoption.
+- **Consequence:** the concrete thing that ships wrong — a regression the checked evidence would not catch, or a site that should use the new behavior and doesn't.
+- **Suggested test shape:** (optional) the kind of test that would close the gap, fit to the repo's own way of verifying — don't impose a generic test pyramid.
+```
+
+If you noticed genuine non-gap problems while tracing verification, append:
+
+```markdown
+## Other findings
+
+- <description only; no severity, confidence, priority, or ranking>
+```
+
+When you find no verification gaps and no other findings, output exactly this single line, not an empty response:
+
+`No verification gaps found.`
+
+## CONTENT SOURCE
+
+Review the content supplied under "Review content:" in the message that launched you. If none is supplied, stop with exactly: `No verification gaps found.`
diff --git a/.claude/skills/bmad-code-review/steps/step-01-gather-context.md b/.claude/skills/bmad-code-review/steps/step-01-gather-context.md
new file mode 100644
index 0000000..3add4ad
--- /dev/null
+++ b/.claude/skills/bmad-code-review/steps/step-01-gather-context.md
@@ -0,0 +1,87 @@
+---
+diff_output: '' # set at runtime
+spec_file: '' # set at runtime (path or empty)
+review_mode: '' # set at runtime: "full" or "no-spec"
+story_key: '' # set at runtime when discovered from sprint status
+---
+
+# Step 1: Gather Context
+
+## RULES
+
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+- The prompt that triggered this workflow IS the intent — not a hint.
+- Do not modify any files. This step is read-only.
+
+## INSTRUCTIONS
+
+1. **Find the review target.** The conversation context before this skill was triggered IS your starting point — not a blank slate. Check in this order — stop as soon as the review target is identified:
+
+   **Tier 1 — Explicit argument.**
+   Did the user pass a PR, commit SHA, branch, spec file, or diff source this message?
+   - PR reference → resolve to branch/commit via `gh pr view`. If resolution fails, ask for a SHA or branch.
+   - Commit or branch → use directly.
+   - Spec file → set `{spec_file}` to the provided path. Check its frontmatter for `baseline_commit`. If found, use as diff baseline. If not found, continue the cascade (a spec alone does not identify a diff source).
+   - Also scan the argument for diff-mode keywords that narrow the scope:
+     - "staged" / "staged changes" → Staged changes only
+     - "uncommitted" / "working tree" / "all changes" → Uncommitted changes (staged + unstaged)
+     - "branch diff" / "vs main" / "against main" / "compared to <branch>" → Branch diff (extract base branch if mentioned)
+     - "commit range" / "last N commits" / "<from-sha>..<to-sha>" → Specific commit range
+     - "this diff" / "provided diff" / "paste" → User-provided diff (do not match bare "diff" — it appears in other modes)
+   - When multiple keywords match, prefer the most specific (e.g., "branch diff" over bare "diff").
+
+   **Tier 2 — Recent conversation.**
+   Do the last few messages reveal what the user wants to be reviewed? Look for spec paths, commit refs, branches, PRs, or descriptions of a change. Apply the same diff-mode keyword scan and routing as Tier 1.
+
+   **Tier 3 — Sprint tracking.**
+   Look for a sprint status file (`*sprint-status*`) in `{implementation_artifacts}` or `{planning_artifacts}`. If found, scan for stories with status `review`:
+   - **Exactly one `review` story:** Set `{story_key}` to the story's key (e.g., `1-2-user-auth`). Suggest it: "I found story <story-id> in `review` status. Would you like to review its changes? [Y] Yes / [N] No, let me choose". If confirmed, use the story context to determine the diff source (branch name derived from story slug, or uncommitted changes). If declined, clear `{story_key}` and fall through.
+   - **Multiple `review` stories:** Present them as numbered options alongside a manual choice option. Wait for user selection. If a story is selected, set `{story_key}` and use its context to determine the diff source. If manual choice is selected, clear `{story_key}` and fall through.
+   - **None:** Fall through.
+
+   **Tier 4 — Current git state.**
+   If version control is unavailable, skip to Tier 5. Otherwise, check the current branch and HEAD. If the branch is not `main` (or the default branch), confirm: "I see HEAD is `<short-sha>` on `<branch>` — do you want to review this branch's changes?" If confirmed, treat as a branch diff against `main`. If declined, fall through.
+
+   **Tier 5 — Ask.**
+   Fall through to instruction 2.
+
+   Never ask extra questions beyond what the cascade prescribes. If a tier above already identified the target, skip the remaining tiers and proceed to instruction 3 (construct diff).
+
+2. HALT. Ask the user: **What do you want to review?** Present these options:
+   - **Uncommitted changes** (staged + unstaged)
+   - **Staged changes only**
+   - **Branch diff** vs a base branch (ask which base branch)
+   - **Specific commit range** (ask for the range)
+   - **Provided diff or file list** (user pastes or provides a path)
+
+3. Construct `{diff_output}` from the chosen source.
+   - For **staged changes only**: run `git diff --cached`.
+   - For **uncommitted changes** (staged + unstaged): run `git diff HEAD`.
+   - For **branch diff**: verify the base branch exists before running `git diff`. If it does not exist, HALT and ask the user for a valid branch.
+   - For **commit range**: verify the range resolves. If it does not, HALT and ask the user for a valid range.
+   - For **provided diff**: validate the content is non-empty and parseable as a unified diff. If it is not parseable, HALT and ask the user to provide a valid diff.
+   - For **file list**: validate each path exists in the working tree. Construct `{diff_output}` by running `git diff HEAD -- <path1> <path2> ...`. If any paths are untracked (new files not yet staged), use `git diff --no-index /dev/null <path>` to include them. If the diff is empty (files have no uncommitted changes and are not untracked), ask the user whether to review the full file contents or to specify a different baseline.
+   - After constructing `{diff_output}`, verify it is non-empty regardless of source type. If empty, HALT and tell the user there is nothing to review.
+
+4. **Set the spec context.**
+   - If the triggering request or recent conversation **explicitly** states there is no spec (e.g. "no spec", "without a spec", "no-spec"): set `{review_mode}` = `"no-spec"` and clear `{spec_file}` (set it to `''`). Do **not** ask for a spec. Do **not** infer no-spec mode merely because the invocation omitted a spec path.
+   - Else if `{spec_file}` is already set (from Tier 1 or Tier 2): verify the file exists and is readable, then set `{review_mode}` = `"full"`.
+   - Else (neither a spec path nor an explicit no-spec declaration is present): ask the user to choose:
+     1. Provide a spec or story file path for context; or
+     2. Continue without a spec.
+     - If the user provides a path: set `{spec_file}` to that path, verify the file exists and is readable, then set `{review_mode}` = `"full"`.
+     - If the user explicitly chooses to continue without a spec: set `{review_mode}` = `"no-spec"`.
+
+5. If `{review_mode}` = `"full"` and the file at `{spec_file}` has a `context` field in its frontmatter listing additional docs, load each referenced document. Warn the user about any docs that cannot be found.
+
+6. Sanity check: if `{diff_output}` exceeds approximately 3000 lines, warn the user and offer to chunk the review by file group.
+   - If the user opts to chunk: agree on the first group, narrow `{diff_output}` accordingly, and list the remaining groups for the user to note for follow-up runs.
+   - If the user declines: proceed as-is with the full diff.
+
+### CHECKPOINT
+
+Present a summary before proceeding: diff stats (files changed, lines added/removed), `{review_mode}`, and loaded spec/context docs (if any). HALT and wait for user confirmation to proceed.
+
+## NEXT
+
+Read fully and follow `./step-02-review.md`
diff --git a/.claude/skills/bmad-code-review/steps/step-02-review.md b/.claude/skills/bmad-code-review/steps/step-02-review.md
new file mode 100644
index 0000000..627fdfe
--- /dev/null
+++ b/.claude/skills/bmad-code-review/steps/step-02-review.md
@@ -0,0 +1,32 @@
+---
+failed_layers: '' # set at runtime: comma-separated list of layers that failed or returned empty
+---
+
+# Step 2: Review
+
+## RULES
+
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+- All review subagents must run at the same model capability as the current session.
+- Run subagents synchronously: launch them together, then wait for all results before continuing.
+
+## INSTRUCTIONS
+
+1. The review layers are `{workflow.review_layers}`, resolved during activation.
+
+2. For each layer in `{workflow.review_layers}`:
+   - `instruction` empty or missing → drop the layer silently (an override disabled it).
+   - `when` condition present and not satisfied by the current context (`{review_mode}`, `{spec_file}`) → drop the layer and tell the user, e.g. "Acceptance Auditor skipped — no spec file provided."
+   - otherwise → the layer is active.
+
+   If no layer is active, HALT with status `blocked` and blocking condition `no active review layers`.
+
+3. Execute all active layers in parallel wherever their execution methods allow: expand `{skill-root}` in each layer's `instruction` to this skill's absolute installed directory, then substitute the runtime placeholders (`{diff_output}`, `{spec_file}`). For an instruction that launches a reviewer subagent, launch that child with the prompt text after placeholder substitution; do not load the reviewer instruction file yourself. For any other customized instruction, execute it as written. Do not leave `{skill-root}` unresolved in a child prompt. If a layer's instruction requires subagents and subagents are not available, for each such layer write under `{implementation_artifacts}` the exact child prompt from that layer's instruction after placeholder substitution (not a path-only pointer), then HALT. Ask the user to run each in a separate session (ideally a different LLM) and paste back the findings. When findings are pasted, treat them as those layers' findings and resume from this point. This is the only allowed parent-side read of a reviewer instruction file.
+
+4. **Layer failure handling**: If any layer fails, times out, or returns empty results, append the layer's `name` to `{failed_layers}` (comma-separated) and proceed with findings from the remaining layers.
+
+5. Collect all findings from the completed layers, keeping track of each finding's originating layer `id`.
+
+## NEXT
+
+Read fully and follow `./step-03-triage.md`
diff --git a/.claude/skills/bmad-code-review/steps/step-03-triage.md b/.claude/skills/bmad-code-review/steps/step-03-triage.md
new file mode 100644
index 0000000..2577917
--- /dev/null
+++ b/.claude/skills/bmad-code-review/steps/step-03-triage.md
@@ -0,0 +1,50 @@
+---
+---
+
+# Step 3: Triage
+
+## RULES
+
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+## INSTRUCTIONS
+
+1. **Normalize** findings from all layers into a unified list where each finding has:
+   - `id` -- sequential integer
+   - `source` -- the `id` of the layer that produced the finding (e.g., `blind-hunter`), or merged sources joined with `+` (e.g., `blind-hunter+edge-case-hunter`)
+   - `title` -- one-line summary
+   - `detail` -- full description
+   - `location` -- file and line reference (if available)
+
+2. **Deduplicate.** Deduplicate only findings with the same claim and same required action. If two or more findings meet both conditions, merge them into one:
+   - Use the most specific finding as the base (prefer findings with a precise location over prose-only findings).
+   - Append any unique detail, reasoning, or location references from the other finding(s) into the surviving `detail` field.
+   - Set `source` to the merged sources (e.g., `blind-hunter+edge-case-hunter`).
+
+3. Then evaluate each remaining finding independently. Do not reject a finding because a related finding was rejected.
+
+4. **Read the code before rating.** Before assigning severity, open the source at each finding's location and read enough surrounding code to judge reachability -- call sites, guards, and validation that live outside the diff hunk. Do not rate from the diff hunk alone. Severity reflects the real consequence at a real call site, not the worst theoretical reading.
+
+5. **Assign severity** to each finding by consequence for the artifact's main consumer (software user, document reader, etc).
+   Disregard any severity assigned by a reviewing subagent. Review subagents operate under by-design information asymmetry and do not have enough context to set final severity for this workflow.
+   - `low` -- none or cosmetic
+   - `medium` -- tolerable
+   - `high` -- intolerable
+
+6. **Route** each finding into exactly one triage bucket:
+   - **decision_needed** -- There is an ambiguous choice that requires human input. The code cannot be correctly patched without knowing the user's intent. Only possible if `{review_mode}` = `"full"`.
+   - **patch** -- Code issue that is fixable without human input. The correct fix is unambiguous.
+   - **defer** -- Pre-existing issue not caused by the current change. Real but not actionable now.
+   - **dismiss** -- Noise, false positive, or handled elsewhere.
+
+   If `{review_mode}` = `"no-spec"` and a finding would otherwise be `decision_needed`, reclassify it as `patch` (if the fix is unambiguous) or `defer` (if not).
+
+7. **Drop** all `dismiss` findings. Record the dismiss count for the summary.
+
+8. If `{failed_layers}` is non-empty, report which layers failed before announcing results. If zero findings remain after dropping dismissed AND `{failed_layers}` is non-empty, warn the user that the review may be incomplete rather than announcing a clean review.
+
+9. If zero findings remain after triage (all rejected or none raised): state "✅ Clean review — all layers passed." (Step 3 already warned if any review layers failed via `{failed_layers}`.)
+
+## NEXT
+
+Read fully and follow `./step-04-present.md`
diff --git a/.claude/skills/bmad-code-review/steps/step-04-present.md b/.claude/skills/bmad-code-review/steps/step-04-present.md
new file mode 100644
index 0000000..884d986
--- /dev/null
+++ b/.claude/skills/bmad-code-review/steps/step-04-present.md
@@ -0,0 +1,132 @@
+---
+deferred_work_file: '{implementation_artifacts}/deferred-work.md'
+---
+
+# Step 4: Present and Act
+
+## RULES
+
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+- When `{spec_file}` is set, always write findings to the story file before offering action choices.
+- `decision-needed` findings must be resolved before handling `patch` findings.
+
+## INSTRUCTIONS
+
+### 1. Clean review shortcut
+
+If zero findings remain after triage (all dismissed or none raised): state that and proceed to section 6 (Sprint Status Update).
+
+### 2. Write findings to the story file
+
+If `{spec_file}` exists and contains a Tasks/Subtasks section, append a `### Review Findings` subsection. Write all findings in this order:
+
+1. **`decision-needed`** findings (unchecked):
+   `- [ ] [Review][Decision] <Title> — <Detail>`
+
+2. **`patch`** findings (unchecked):
+   `- [ ] [Review][Patch] <Title> [<file>:<line>]`
+
+3. **`defer`** findings (checked off, marked deferred):
+   `- [x] [Review][Defer] <Title> [<file>:<line>] — deferred, pre-existing`
+
+Also append each `defer` finding to `{deferred_work_file}` under a heading `## Deferred from: code review ({date})`. If `{spec_file}` is set, include its basename in the heading (e.g., `code review of story-3.3 (2026-03-18)`). One bullet per finding with description.
+
+### 3. Present summary
+
+Announce what was written:
+
+> **Code review complete.** <D> `decision-needed`, <P> `patch`, <W> `defer`, <R> dismissed as noise.
+
+If `{spec_file}` is set, add: `Findings written to the review findings section in {spec_file}.`
+Otherwise add: `Findings are listed above. No story file was provided, so nothing was persisted.`
+
+### 4. Resolve decision-needed findings
+
+If `decision_needed` findings exist, present each one with its detail and the options available. The user must decide — the correct fix is ambiguous without their input. Walk through each finding (or batch related ones) and get the user's call. Once resolved, each becomes a `patch`, `defer`, or is dismissed.
+
+If the user chooses to defer, ask: Quick one-line reason for deferring this item? (helps future reviews): — then append that reason to both the story file bullet and the `{deferred_work_file}` entry.
+
+**HALT** — I am waiting for your numbered choice. Reply with only the number. Do not proceed until you select an option.
+
+### 5. Handle `patch` findings
+
+If `patch` findings exist (including any resolved from step 4), HALT. Ask the user:
+
+If `{spec_file}` is set, present all three options:
+
+> **How would you like to handle the `<P>` `patch` findings?**
+> 1. **Apply every patch** — fix all of them now, no per-finding confirmation. Defer and decision-needed items are not touched.
+> 2. **Leave as action items** — they are already in the story file
+> 3. **Walk through each patch** — show details for each before deciding
+
+If `{spec_file}` is **not** set, present only options 1 and 2 (omit "Leave as action items" — findings were not written to a file):
+
+> **How would you like to handle the `<P>` `patch` findings?**
+> 1. **Apply every patch** — fix all of them now, no per-finding confirmation. Defer and decision-needed items are not touched.
+> 2. **Walk through each patch** — show details for each before deciding
+
+**HALT** — I am waiting for your numbered choice. Reply with only the number. Do not proceed until you select an option.
+
+- **Apply every patch**: Apply every patch finding without per-finding confirmation. Do not modify defer or decision-needed items. After all patches are applied, present a summary of changes made. If `{spec_file}` is set, check off the patch items in the story file (leave defer items as-is).
+- **Leave as action items** (only when `{spec_file}` is set): Done — findings are already written to the story.
+- **Walk through each patch**: Present each finding with full detail, diff context, and suggested fix. After walkthrough, re-offer the applicable options above.
+
+  **HALT** — I am waiting for your numbered choice. Do not proceed until you select an option.
+
+**✅ Code review actions complete**
+
+- Decision-needed resolved: <D>
+- Patches handled: <P>
+- Deferred: <W>
+- Dismissed: <R>
+
+### 6. Update story status and sync sprint tracking
+
+Skip this section if `{spec_file}` is not set.
+
+#### Determine new status based on review outcome
+
+- If all `decision-needed` and `patch` findings were resolved (fixed or dismissed) AND no unresolved `high`/`medium` findings remain: set `{new_status}` = `done`. Update the story file Status section to `done`.
+- If `patch` findings were left as action items, or unresolved issues remain: set `{new_status}` = `in-progress`. Update the story file Status section to `in-progress`.
+
+Save the story file.
+
+#### Sync sprint-status.yaml
+
+If `{story_key}` is not set, skip this subsection and note that sprint status was not synced because no story key was available.
+
+If `{sprint_status}` file exists:
+
+1. Load the FULL `{sprint_status}` file.
+2. Find the `development_status` entry matching `{story_key}`.
+3. If found: update `development_status[{story_key}]` to `{new_status}`. Update `last_updated` to current date. Save the file, preserving ALL comments and structure including STATUS DEFINITIONS.
+4. If `{story_key}` not found in sprint status: warn the user that the story file was updated but sprint-status sync failed.
+
+If `{sprint_status}` file does not exist, note that story status was updated in the story file only.
+
+#### Completion summary
+
+> **Review Complete!**
+>
+> **Story Status:** `{new_status}`
+> **Issues Fixed:** <fixed_count>
+> **Action Items Created:** <action_count>
+> **Deferred:** <W>
+> **Dismissed:** <R>
+
+### 7. Next steps
+
+Present the user with follow-up options:
+
+> **What would you like to do next?**
+> 1. **Start the next story** — run `dev-story` to pick up the next `ready-for-dev` story
+> 2. **Re-run code review** — address findings and review again
+> 3. **Done** — end the workflow
+
+**HALT** — I am waiting for your choice. Do not proceed until the user selects an option.
+
+## On Complete
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+
+If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
diff --git a/.claude/skills/bmad-correct-course/SKILL.md b/.claude/skills/bmad-correct-course/SKILL.md
new file mode 100644
index 0000000..9ef4108
--- /dev/null
+++ b/.claude/skills/bmad-correct-course/SKILL.md
@@ -0,0 +1,300 @@
+---
+name: bmad-correct-course
+description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
+---
+
+# 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.
+
+## Conventions
+
+- Bare paths (e.g. `checklist.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+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.
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## 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 |
+| Project Context | `AGENTS.md` in the affected repo (the `bmad:context` block) | FULL_LOAD |
+
+## 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 Project Context:**
+
+1. **Read `AGENTS.md`** in the repo the change affects — the block between the `bmad:context` markers carries the policy, frozen paths, and conventions a course correction must respect.
+2. **Follow only the pointers that relate to the impacted areas** — nested component files or linked rule files listed under "Where things are". Do not load them all.
+3. **This document is optional** — skip if the repo has no `AGENTS.md` (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>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 project documents:</action>
+    - PRD (Product Requirements Document) — required
+    - Current Epics and Stories — required
+    - Architecture documentation — optional, load if available
+    - UI/UX specifications — optional, load if available
+  <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="PRD or Epics are unavailable">HALT: "Need access to PRD and Epics to assess change impact. Please ensure these documents are accessible. Architecture and UI/UX will be used if available."</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>
+<action>Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+</step>
+
+</workflow>
diff --git a/.claude/skills/bmad-correct-course/checklist.md b/.claude/skills/bmad-correct-course/checklist.md
new file mode 100644
index 0000000..b56feb6
--- /dev/null
+++ b/.claude/skills/bmad-correct-course/checklist.md
@@ -0,0 +1,288 @@
+# Change Navigation Checklist
+
+<critical>This checklist is executed as part of: ./workflow.md</critical>
+<critical>Work through each section systematically with the user, recording findings and impacts</critical>
+
+<checklist>
+
+<section n="1" title="Understand the Trigger and Context">
+
+<check-item id="1.1">
+<prompt>Identify the triggering story that revealed this issue</prompt>
+<action>Document story ID and brief description</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="1.2">
+<prompt>Define the core problem precisely</prompt>
+<action>Categorize issue type:</action>
+  - Technical limitation discovered during implementation
+  - New requirement emerged from stakeholders
+  - Misunderstanding of original requirements
+  - Strategic pivot or market change
+  - Failed approach requiring different solution
+<action>Write clear problem statement</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="1.3">
+<prompt>Assess initial impact and gather supporting evidence</prompt>
+<action>Collect concrete examples, error messages, stakeholder feedback, or technical constraints</action>
+<action>Document evidence for later reference</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<halt-condition>
+<action if="trigger is unclear">HALT: "Cannot proceed without understanding what caused the need for change"</action>
+<action if="no evidence provided">HALT: "Need concrete evidence or examples of the issue before analyzing impact"</action>
+</halt-condition>
+
+</section>
+
+<section n="2" title="Epic Impact Assessment">
+
+<check-item id="2.1">
+<prompt>Evaluate current epic containing the trigger story</prompt>
+<action>Can this epic still be completed as originally planned?</action>
+<action>If no, what modifications are needed?</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="2.2">
+<prompt>Determine required epic-level changes</prompt>
+<action>Check each scenario:</action>
+  - Modify existing epic scope or acceptance criteria
+  - Add new epic to address the issue
+  - Remove or defer epic that's no longer viable
+  - Completely redefine epic based on new understanding
+<action>Document specific epic changes needed</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="2.3">
+<prompt>Review all remaining planned epics for required changes</prompt>
+<action>Check each future epic for impact</action>
+<action>Identify dependencies that may be affected</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="2.4">
+<prompt>Check if issue invalidates future epics or necessitates new ones</prompt>
+<action>Does this change make any planned epics obsolete?</action>
+<action>Are new epics needed to address gaps created by this change?</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="2.5">
+<prompt>Consider if epic order or priority should change</prompt>
+<action>Should epics be resequenced based on this issue?</action>
+<action>Do priorities need adjustment?</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+</section>
+
+<section n="3" title="Artifact Conflict and Impact Analysis">
+
+<check-item id="3.1">
+<prompt>Check PRD for conflicts</prompt>
+<action>Does issue conflict with core PRD goals or objectives?</action>
+<action>Do requirements need modification, addition, or removal?</action>
+<action>Is the defined MVP still achievable or does scope need adjustment?</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="3.2">
+<prompt>Review Architecture document for conflicts</prompt>
+<action>Check each area for impact:</action>
+  - System components and their interactions
+  - Architectural patterns and design decisions
+  - Technology stack choices
+  - Data models and schemas
+  - API designs and contracts
+  - Integration points
+<action>Document specific architecture sections requiring updates</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="3.3">
+<prompt>Examine UI/UX specifications for conflicts</prompt>
+<action>Check for impact on:</action>
+  - User interface components
+  - User flows and journeys
+  - Wireframes or mockups
+  - Interaction patterns
+  - Accessibility considerations
+<action>Note specific UI/UX sections needing revision</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="3.4">
+<prompt>Consider impact on other artifacts</prompt>
+<action>Review additional artifacts for impact:</action>
+  - Deployment scripts
+  - Infrastructure as Code (IaC)
+  - Monitoring and observability setup
+  - Testing strategies
+  - Documentation
+  - CI/CD pipelines
+<action>Document any secondary artifacts requiring updates</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+</section>
+
+<section n="4" title="Path Forward Evaluation">
+
+<check-item id="4.1">
+<prompt>Evaluate Option 1: Direct Adjustment</prompt>
+<action>Can the issue be addressed by modifying existing stories?</action>
+<action>Can new stories be added within the current epic structure?</action>
+<action>Would this approach maintain project timeline and scope?</action>
+<action>Effort estimate: [High/Medium/Low]</action>
+<action>Risk level: [High/Medium/Low]</action>
+<status>[ ] Viable / [ ] Not viable</status>
+</check-item>
+
+<check-item id="4.2">
+<prompt>Evaluate Option 2: Potential Rollback</prompt>
+<action>Would reverting recently completed stories simplify addressing this issue?</action>
+<action>Which stories would need to be rolled back?</action>
+<action>Is the rollback effort justified by the simplification gained?</action>
+<action>Effort estimate: [High/Medium/Low]</action>
+<action>Risk level: [High/Medium/Low]</action>
+<status>[ ] Viable / [ ] Not viable</status>
+</check-item>
+
+<check-item id="4.3">
+<prompt>Evaluate Option 3: PRD MVP Review</prompt>
+<action>Is the original PRD MVP still achievable with this issue?</action>
+<action>Does MVP scope need to be reduced or redefined?</action>
+<action>Do core goals need modification based on new constraints?</action>
+<action>What would be deferred to post-MVP if scope is reduced?</action>
+<action>Effort estimate: [High/Medium/Low]</action>
+<action>Risk level: [High/Medium/Low]</action>
+<status>[ ] Viable / [ ] Not viable</status>
+</check-item>
+
+<check-item id="4.4">
+<prompt>Select recommended path forward</prompt>
+<action>Based on analysis of all options, choose the best path</action>
+<action>Provide clear rationale considering:</action>
+  - Implementation effort and timeline impact
+  - Technical risk and complexity
+  - Impact on team morale and momentum
+  - Long-term sustainability and maintainability
+  - Stakeholder expectations and business value
+<action>Selected approach: [Option 1 / Option 2 / Option 3 / Hybrid]</action>
+<action>Justification: [Document reasoning]</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+</section>
+
+<section n="5" title="Sprint Change Proposal Components">
+
+<check-item id="5.1">
+<prompt>Create identified issue summary</prompt>
+<action>Write clear, concise problem statement</action>
+<action>Include context about discovery and impact</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="5.2">
+<prompt>Document epic impact and artifact adjustment needs</prompt>
+<action>Summarize findings from Epic Impact Assessment (Section 2)</action>
+<action>Summarize findings from Artifact Conflict Analysis (Section 3)</action>
+<action>Be specific about what changes are needed and why</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="5.3">
+<prompt>Present recommended path forward with rationale</prompt>
+<action>Include selected approach from Section 4</action>
+<action>Provide complete justification for recommendation</action>
+<action>Address trade-offs and alternatives considered</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="5.4">
+<prompt>Define PRD MVP impact and high-level action plan</prompt>
+<action>State clearly if MVP is affected</action>
+<action>Outline major action items needed for implementation</action>
+<action>Identify dependencies and sequencing</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="5.5">
+<prompt>Establish agent handoff plan</prompt>
+<action>Identify which roles/agents will execute the changes:</action>
+  - Developer agent (for implementation)
+  - Product Owner / Developer (for backlog changes)
+  - Product Manager / Architect (for strategic changes)
+<action>Define responsibilities for each role</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+</section>
+
+<section n="6" title="Final Review and Handoff">
+
+<check-item id="6.1">
+<prompt>Review checklist completion</prompt>
+<action>Verify all applicable sections have been addressed</action>
+<action>Confirm all [Action-needed] items have been documented</action>
+<action>Ensure analysis is comprehensive and actionable</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="6.2">
+<prompt>Verify Sprint Change Proposal accuracy</prompt>
+<action>Review complete proposal for consistency and clarity</action>
+<action>Ensure all recommendations are well-supported by analysis</action>
+<action>Check that proposal is actionable and specific</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="6.3">
+<prompt>Obtain explicit user approval</prompt>
+<action>Present complete proposal to user</action>
+<action>Get clear yes/no approval for proceeding</action>
+<action>Document approval and any conditions</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="6.4">
+<prompt>Update sprint-status.yaml to reflect approved epic changes</prompt>
+<action>If epics were added: Add new epic entries with status 'backlog'</action>
+<action>If epics were removed: Remove corresponding entries</action>
+<action>If epics were renumbered: Update epic IDs and story references</action>
+<action>If stories were added/removed: Update story entries within affected epics</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="6.5">
+<prompt>Confirm next steps and handoff plan</prompt>
+<action>Review handoff responsibilities with user</action>
+<action>Ensure all stakeholders understand their roles</action>
+<action>Confirm timeline and success criteria</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<halt-condition>
+<action if="any critical section cannot be completed">HALT: "Cannot proceed to proposal without complete impact analysis"</action>
+<action if="user approval not obtained">HALT: "Must have explicit approval before implementing changes"</action>
+<action if="handoff responsibilities unclear">HALT: "Must clearly define who will execute the proposed changes"</action>
+</halt-condition>
+
+</section>
+
+</checklist>
+
+<execution-notes>
+<note>This checklist is for SIGNIFICANT changes affecting project direction</note>
+<note>Work interactively with user - they make final decisions</note>
+<note>Be factual, not blame-oriented when analyzing issues</note>
+<note>Handle changes professionally as opportunities to improve the project</note>
+<note>Maintain conversation context throughout - this is collaborative work</note>
+</execution-notes>
diff --git a/.claude/skills/bmad-correct-course/customize.toml b/.claude/skills/bmad-correct-course/customize.toml
new file mode 100644
index 0000000..d23577e
--- /dev/null
+++ b/.claude/skills/bmad-correct-course/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-correct-course. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All sprint changes require PO sign-off before execution."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 6 (Workflow Completion),
+# after the Sprint Change Proposal is finalized and handoff is confirmed. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-create-architecture/SKILL.md b/.claude/skills/bmad-create-architecture/SKILL.md
new file mode 100644
index 0000000..cbc4648
--- /dev/null
+++ b/.claude/skills/bmad-create-architecture/SKILL.md
@@ -0,0 +1,30 @@
+---
+name: bmad-create-architecture
+description: 'Deprecated — forwards to bmad-architecture (create intent).'
+---
+
+# DEPRECATED — forwards to bmad-architecture (create intent)
+
+This skill was consolidated into `bmad-architecture`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-create-architecture.toml` override files keep working. New work should invoke `bmad-architecture` directly — it detects create / update / validate intent from the conversation.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-create-architecture.toml` and `bmad-create-architecture.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+
+2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+
+3. Emit a deprecation notice to the user in `{communication_language}`:
+
+   > Notice: `bmad-create-architecture` is deprecated and will be removed in a future release. It now forwards to `bmad-architecture` with create intent. To silence this notice and access the full new customization surface (`spine_template`, `spine_output_path`, `run_folder_pattern`, `doc_standards`, `external_sources`, `external_handoffs`, `finalize_reviewers`), migrate `_bmad/custom/bmad-create-architecture.toml` to `_bmad/custom/bmad-architecture.toml` and invoke `bmad-architecture` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-architecture.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+
+4. Invoke `bmad-architecture` with the following context. Pass these as the activating context so `bmad-architecture` honors them instead of resolving its own customization from scratch:
+
+   - **Intent:** `create` — skip `bmad-architecture`'s usual intent detection step.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-architecture`'s own `customize.toml` for the four legacy fields. For everything else (`spine_template`, `spine_output_path`, `run_folder_pattern`, `doc_standards`, `external_sources`, `external_handoffs`, `finalize_reviewers`), use `bmad-architecture`'s own defaults and overrides as normal:
+     - `activation_steps_prepend` = the resolved value from step 1
+     - `activation_steps_append` = the resolved value from step 1
+     - `persistent_facts` = the resolved value from step 1
+     - `on_complete` = the resolved value from step 1
+   - **Original user input:** forward whatever the user said when invoking this skill verbatim.
+
+   `bmad-architecture` takes the workflow from here. Do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-create-architecture/customize.toml b/.claude/skills/bmad-create-architecture/customize.toml
new file mode 100644
index 0000000..3275612
--- /dev/null
+++ b/.claude/skills/bmad-create-architecture/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-create-architecture. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 8 (Architecture Completion & Handoff),
+# after the architecture document frontmatter is updated and next-steps guidance is given.
+# Override wins. Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-create-epics-and-stories/SKILL.md b/.claude/skills/bmad-create-epics-and-stories/SKILL.md
new file mode 100644
index 0000000..e822e6a
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/SKILL.md
@@ -0,0 +1,93 @@
+---
+name: bmad-create-epics-and-stories
+description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
+---
+
+# Create Epics and Stories
+
+**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for the Developer agent.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.
+
+## Conventions
+
+- Bare paths (e.g. `steps/step-01-validate-prerequisites.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step toward the overall goal is a self-contained instruction file; adhere to one file at a time, as directed
+- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Execution
+
+Read fully and follow: `./steps/step-01-validate-prerequisites.md` to begin the workflow.
diff --git a/.claude/skills/bmad-create-epics-and-stories/customize.toml b/.claude/skills/bmad-create-epics-and-stories/customize.toml
new file mode 100644
index 0000000..fb05efa
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-create-epics-and-stories. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All epics must deliver complete end-to-end user value."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 4 (Final Validation) and the
+# user confirms [C] Complete — after the epics.md is saved and bmad-help is invoked.
+# Override wins. Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md b/.claude/skills/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md
new file mode 100644
index 0000000..5930a77
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md
@@ -0,0 +1,263 @@
+# Step 1: Validate Prerequisites and Extract Requirements
+
+## STEP GOAL:
+
+To validate that all required input documents exist and extract all requirements (FRs, NFRs, and additional requirements from UX/Architecture) needed for epic and story creation.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product strategist and technical specifications writer
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring requirements extraction expertise
+- ✅ User brings their product vision and context
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on extracting and organizing requirements
+- 🚫 FORBIDDEN to start creating epics or stories in this step
+- 💬 Extract requirements from ALL available documents
+- 🚪 POPULATE the template sections exactly as needed
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Extract requirements systematically from all documents
+- 💾 Populate {planning_artifacts}/epics.md with extracted requirements
+- 📖 Update frontmatter with extraction progress
+- 🚫 FORBIDDEN to load next step until user selects 'C' and requirements are extracted
+
+## REQUIREMENTS EXTRACTION PROCESS:
+
+### 1. Welcome and Overview
+
+Welcome {user_name} to comprehensive epic and story creation!
+
+**CRITICAL PREREQUISITE VALIDATION:**
+
+Verify required documents exist and are complete:
+
+1. **PRD.md** - Contains requirements (FRs and NFRs) and product scope
+2. **Architecture.md** - Contains technical decisions, API contracts, data models
+3. **UX design contract** (if UI exists) - Contains visual identity, interaction patterns, mockups, and user flows
+
+### 2. Document Discovery and Validation
+
+Search for required documents using these patterns (sharded means a large document was split into multiple small files with an index.md into a folder) - if the whole document is found, use that instead of the sharded version:
+
+**PRD Document Search Priority:**
+
+1. `{planning_artifacts}/*prd*.md` (whole document)
+2. `{planning_artifacts}/*prd*/index.md` (sharded version)
+
+**Architecture Document Search Priority:**
+
+1. `{planning_artifacts}/*architecture*.md` (whole document)
+2. `{planning_artifacts}/*architecture*/index.md` (sharded version)
+
+**UX Design Document Search (Optional):**
+
+1. `{planning_artifacts}/ux-designs/ux-*/DESIGN.md` and `{planning_artifacts}/ux-designs/ux-*/EXPERIENCE.md` (bmad-ux spine pair)
+2. `{planning_artifacts}/*ux*.md` (legacy whole document)
+3. `{planning_artifacts}/*ux*/index.md` (legacy sharded version)
+
+For each matching bmad-ux run folder, treat `DESIGN.md` and `EXPERIENCE.md` as one UX design contract:
+
+- Confirm and load both files together. `DESIGN.md` owns visual identity and design tokens; `EXPERIENCE.md` owns information architecture, behavior, states, interactions, accessibility, and journeys.
+- Add both files to the `inputDocuments: []` frontmatter array.
+- If only one spine exists, report the incomplete pair and ask whether the user wants to include the partial UX handoff.
+- If multiple run folders match, show each run folder with the spine frontmatter `status` and `updated` values when available, then ask the user which UX design contract to include.
+
+Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {planning_artifacts}/epics.md from the ../templates/epics-template.md and in the front matter list the files in the array of `inputDocuments: []`.
+
+### 3. Extract Functional Requirements (FRs)
+
+From the PRD document (full or sharded), read then entire document and extract ALL functional requirements:
+
+**Extraction Method:**
+
+- Look for numbered items like "FR1:", "Functional Requirement 1:", or similar
+- Identify requirement statements that describe what the system must DO
+- Include user actions, system behaviors, and business rules
+
+**Format the FR list as:**
+
+```
+FR1: [Clear, testable requirement description]
+FR2: [Clear, testable requirement description]
+...
+```
+
+### 4. Extract Non-Functional Requirements (NFRs)
+
+From the PRD document, extract ALL non-functional requirements:
+
+**Extraction Method:**
+
+- Look for performance, security, usability, reliability requirements
+- Identify constraints and quality attributes
+- Include technical standards and compliance requirements
+
+**Format the NFR list as:**
+
+```
+NFR1: [Performance/Security/Usability requirement]
+NFR2: [Performance/Security/Usability requirement]
+...
+```
+
+### 5. Extract Additional Requirements from Architecture
+
+Review the Architecture document for technical requirements that impact epic and story creation:
+
+**Look for:**
+
+- **Starter Template**: Does Architecture specify a starter/greenfield template? If YES, document this for Epic 1 Story 1
+- Infrastructure and deployment requirements
+- Integration requirements with external systems
+- Data migration or setup requirements
+- Monitoring and logging requirements
+- API versioning or compatibility requirements
+- Security implementation requirements
+
+**IMPORTANT**: If a starter template is mentioned in Architecture, note it prominently. This will impact Epic 1 Story 1.
+
+**Format Additional Requirements as:**
+
+```
+- [Technical requirement from Architecture that affects implementation]
+- [Infrastructure setup requirement]
+- [Integration requirement]
+...
+```
+
+### 6. Extract UX Design Requirements (if UX document exists)
+
+**IMPORTANT**: The UX Design Specification is a first-class input document, not supplementary material. Requirements from the UX spec must be extracted with the same rigor as PRD functional requirements.
+
+Read the FULL UX design contract and extract ALL actionable work items. For a bmad-ux spine pair, read both `DESIGN.md` and `EXPERIENCE.md`:
+
+**Look for:**
+
+- **Design token work**: Color systems, spacing scales, typography tokens that need implementation or consolidation
+- **Component proposals**: Reusable UI components identified in the UX spec (e.g., ConfirmActions, StatusMessage, EmptyState, FocusIndicator)
+- **Visual standardization**: Semantic CSS classes, consistent color palette usage, design pattern consolidation
+- **Accessibility requirements**: Contrast audit fixes, ARIA patterns, keyboard navigation, screen reader support
+- **Responsive design requirements**: Breakpoints, layout adaptations, mobile-specific interactions
+- **Interaction patterns**: Animations, transitions, loading states, error handling UX
+- **Browser/device compatibility**: Target platforms, progressive enhancement requirements
+
+**Format UX Design Requirements as a SEPARATE section (not merged into Additional Requirements):**
+
+```
+UX-DR1: [Actionable UX design requirement with clear implementation scope]
+UX-DR2: [Actionable UX design requirement with clear implementation scope]
+...
+```
+
+**🚨 CRITICAL**: Do NOT reduce UX requirements to vague summaries. Each UX-DR must be specific enough to generate a story with testable acceptance criteria. If the UX spec identifies 6 reusable components, list all 6 — not "create reusable components."
+
+### 7. Load and Initialize Template
+
+Load ../templates/epics-template.md and initialize {planning_artifacts}/epics.md:
+
+1. Copy the entire template to {planning_artifacts}/epics.md
+2. Replace {{project_name}} with the actual project name
+3. Replace placeholder sections with extracted requirements:
+   - {{fr_list}} → extracted FRs
+   - {{nfr_list}} → extracted NFRs
+   - {{additional_requirements}} → extracted additional requirements (from Architecture)
+   - {{ux_design_requirements}} → extracted UX Design Requirements (if UX document exists)
+4. Leave {{requirements_coverage_map}} and {{epics_list}} as placeholders for now
+
+### 8. Present Extracted Requirements
+
+Display to user:
+
+**Functional Requirements Extracted:**
+
+- Show count of FRs found
+- Display the first few FRs as examples
+- Ask if any FRs are missing or incorrectly captured
+
+**Non-Functional Requirements Extracted:**
+
+- Show count of NFRs found
+- Display key NFRs
+- Ask if any constraints were missed
+
+**Additional Requirements (Architecture):**
+
+- Summarize technical requirements from Architecture
+- Verify completeness
+
+**UX Design Requirements (if applicable):**
+
+- Show count of UX-DRs found
+- Display key UX Design requirements (design tokens, components, accessibility)
+- Verify each UX-DR is specific enough for story creation
+
+### 9. Get User Confirmation
+
+Ask: "Do these extracted requirements accurately represent what needs to be built? Any additions or corrections?"
+
+Update the requirements based on user feedback until confirmation is received.
+
+## CONTENT TO SAVE TO DOCUMENT:
+
+After extraction and confirmation, update {planning_artifacts}/epics.md with:
+
+- Complete FR list in {{fr_list}} section
+- Complete NFR list in {{nfr_list}} section
+- All additional requirements in {{additional_requirements}} section
+- UX Design requirements in {{ux_design_requirements}} section (if UX document exists)
+
+### 10. Present MENU OPTIONS
+
+Display: `**Confirm the Requirements are complete and correct to [C] continue:**`
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions - always respond and then end with display again of the menu option
+
+#### Menu Handling Logic:
+
+- IF C: Save all to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-02-design-epics.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#10-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and all requirements are saved to document and frontmatter is updated, will you then read fully and follow: ./step-02-design-epics.md to begin epic design step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All required documents found and validated
+- All FRs extracted and formatted correctly
+- All NFRs extracted and formatted correctly
+- Additional requirements from Architecture/UX identified
+- Template initialized with requirements
+- User confirms requirements are complete and accurate
+
+### ❌ SYSTEM FAILURE:
+
+- Missing required documents
+- Incomplete requirements extraction
+- Template not properly initialized
+- Not saving requirements to output file
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.claude/skills/bmad-create-epics-and-stories/steps/step-02-design-epics.md b/.claude/skills/bmad-create-epics-and-stories/steps/step-02-design-epics.md
new file mode 100644
index 0000000..937f2df
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/steps/step-02-design-epics.md
@@ -0,0 +1,242 @@
+# Step 2: Design Epic List
+
+## STEP GOAL:
+
+To design and get approval for the epics_list that will organize all requirements into user-value-focused epics.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product strategist and technical specifications writer
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring product strategy and epic design expertise
+- ✅ User brings their product vision and priorities
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on creating the epics_list
+- 🚫 FORBIDDEN to create individual stories in this step
+- 💬 Organize epics around user value, not technical layers
+- 🚪 GET explicit approval for the epics_list
+- 🔗 **CRITICAL: Each epic must be standalone and enable future epics without requiring future epics to function**
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Design epics collaboratively based on extracted requirements
+- 💾 Update {{epics_list}} in {planning_artifacts}/epics.md
+- 📖 Document the FR coverage mapping
+- 🚫 FORBIDDEN to load next step until user approves epics_list
+
+## EPIC DESIGN PROCESS:
+
+### 1. Review Extracted Requirements
+
+Load {planning_artifacts}/epics.md and review:
+
+- **Functional Requirements:** Count and review FRs from Step 1
+- **Non-Functional Requirements:** Review NFRs that need to be addressed
+- **Additional Requirements:** Review technical and UX requirements
+
+### 2. Explain Epic Design Principles
+
+**EPIC DESIGN PRINCIPLES:**
+
+1. **User-Value First**: Each epic must enable users to accomplish something meaningful
+2. **Requirements Grouping**: Group related FRs that deliver cohesive user outcomes
+3. **Incremental Delivery**: Each epic should deliver value independently
+4. **Logical Flow**: Natural progression from user's perspective
+5. **Dependency-Free Within Epic**: Stories within an epic must NOT depend on future stories
+6. **Implementation Efficiency**: Consider consolidating epics that all modify the same core files into fewer epics
+
+**⚠️ CRITICAL PRINCIPLE:**
+Organize by USER VALUE, not technical layers:
+
+**✅ CORRECT Epic Examples (Standalone & Enable Future Epics):**
+
+- Epic 1: User Authentication & Profiles (users can register, login, manage profiles) - **Standalone: Complete auth system**
+- Epic 2: Content Creation (users can create, edit, publish content) - **Standalone: Uses auth, creates content**
+- Epic 3: Social Interaction (users can follow, comment, like content) - **Standalone: Uses auth + content**
+- Epic 4: Search & Discovery (users can find content and other users) - **Standalone: Uses all previous**
+
+**❌ WRONG Epic Examples (Technical Layers or Dependencies):**
+
+- Epic 1: Database Setup (creates all tables upfront) - **No user value**
+- Epic 2: API Development (builds all endpoints) - **No user value**
+- Epic 3: Frontend Components (creates reusable components) - **No user value**
+- Epic 4: Deployment Pipeline (CI/CD setup) - **No user value**
+
+**❌ WRONG Epic Examples (File Churn on Same Component):**
+
+- Epic 1: File Upload (modifies model, controller, web form, web API)
+- Epic 2: File Status (modifies model, controller, web form, web API)
+- Epic 3: File Access permissions (modifies model, controller, web form, web API)
+- All three epics touch the same files — consolidate into one epic with ordered stories
+
+**✅ CORRECT Alternative:**
+
+- Epic 1: File Management Enhancement (upload, status, permissions as stories within one epic)
+- Rationale: Single component, fully pre-designed, no feedback loop between epics
+
+**🔗 DEPENDENCY RULES:**
+
+- Each epic must deliver COMPLETE functionality for its domain
+- Epic 2 must not require Epic 3 to function
+- Epic 3 can build upon Epic 1 & 2 but must stand alone
+
+### 3. Design Epic Structure Collaboratively
+
+**Step A: Assess Context and Identify Themes**
+
+First, assess how much of the solution design is already validated (Architecture, UX, Test Design).
+When the outcome is certain and direction changes between epics are unlikely, prefer fewer but larger epics.
+Split into multiple epics when there is a genuine risk boundary or when early feedback could change direction
+of following epics.
+
+Then, identify user value themes:
+
+- Look for natural groupings in the FRs
+- Identify user journeys or workflows
+- Consider user types and their goals
+
+**Step B: Propose Epic Structure**
+
+For each proposed epic (considering whether epics share the same core files):
+
+1. **Epic Title**: User-centric, value-focused
+2. **User Outcome**: What users can accomplish after this epic
+3. **FR Coverage**: Which FR numbers this epic addresses
+4. **Implementation Notes**: Any technical or UX considerations
+
+**Step C: Review for File Overlap**
+
+Assess whether multiple proposed epics repeatedly target the same core files. If overlap is significant:
+
+- Distinguish meaningful overlap (same component end-to-end) from incidental sharing
+- Ask whether to consolidate into one epic with ordered stories
+- If confirmed, merge the epic FRs into a single epic, preserving dependency flow: each story must still fit within
+  a single dev agent's context
+
+**Step D: Create the epics_list**
+
+Format the epics_list as:
+
+```
+## Epic List
+
+### Epic 1: [Epic Title]
+[Epic goal statement - what users can accomplish]
+**FRs covered:** FR1, FR2, FR3, etc.
+
+### Epic 2: [Epic Title]
+[Epic goal statement - what users can accomplish]
+**FRs covered:** FR4, FR5, FR6, etc.
+
+[Continue for all epics]
+```
+
+### 4. Present Epic List for Review
+
+Display the complete epics_list to user with:
+
+- Total number of epics
+- FR coverage per epic
+- User value delivered by each epic
+- Any natural dependencies
+
+### 5. Create Requirements Coverage Map
+
+Create {{requirements_coverage_map}} showing how each FR maps to an epic:
+
+```
+### FR Coverage Map
+
+FR1: Epic 1 - [Brief description]
+FR2: Epic 1 - [Brief description]
+FR3: Epic 2 - [Brief description]
+...
+```
+
+This ensures no FRs are missed.
+
+### 6. Collaborative Refinement
+
+Ask user:
+
+- "Does this epic structure align with your product vision?"
+- "Are all user outcomes properly captured?"
+- "Should we adjust any epic groupings?"
+- "Are there natural dependencies we've missed?"
+
+### 7. Get Final Approval
+
+**CRITICAL:** Must get explicit user approval:
+"Do you approve this epic structure for proceeding to story creation?"
+
+If user wants changes:
+
+- Make the requested adjustments
+- Update the epics_list
+- Re-present for approval
+- Repeat until approval is received
+
+## CONTENT TO UPDATE IN DOCUMENT:
+
+After approval, update {planning_artifacts}/epics.md:
+
+1. Replace {{epics_list}} placeholder with the approved epic list
+2. Replace {{requirements_coverage_map}} with the coverage map
+3. Ensure all FRs are mapped to epics
+
+### 8. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `bmad-advanced-elicitation` skill
+- IF P: Invoke the `bmad-party-mode` skill
+- IF C: Save approved epics_list to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-03-create-stories.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution completes, redisplay the menu
+- User can chat or ask questions - always respond when conversation ends, redisplay the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and the approved epics_list is saved to document, will you then read fully and follow: ./step-03-create-stories.md to begin story creation step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Epics designed around user value
+- All FRs mapped to specific epics
+- epics_list created and formatted correctly
+- Requirements coverage map completed
+- User gives explicit approval for epic structure
+- Document updated with approved epics
+
+### ❌ SYSTEM FAILURE:
+
+- Epics organized by technical layers
+- Missing FRs in coverage map
+- No user approval obtained
+- epics_list not saved to document
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.claude/skills/bmad-create-epics-and-stories/steps/step-03-create-stories.md b/.claude/skills/bmad-create-epics-and-stories/steps/step-03-create-stories.md
new file mode 100644
index 0000000..14caafe
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/steps/step-03-create-stories.md
@@ -0,0 +1,255 @@
+# Step 3: Generate Epics and Stories
+
+## STEP GOAL:
+
+To generate all epics with their stories based on the approved epics_list, following the template structure exactly.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Process epics sequentially
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product strategist and technical specifications writer
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring story creation and acceptance criteria expertise
+- ✅ User brings their implementation priorities and constraints
+
+### Step-Specific Rules:
+
+- 🎯 Generate stories for each epic following the template exactly
+- 🚫 FORBIDDEN to deviate from template structure
+- 💬 Each story must have clear acceptance criteria
+- 🚪 ENSURE each story is completable by a single dev agent
+- 🔗 **CRITICAL: Stories MUST NOT depend on future stories within the same epic**
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Generate stories collaboratively with user input
+- 💾 Append epics and stories to {planning_artifacts}/epics.md following template
+- 📖 Process epics one at a time in sequence
+- 🚫 FORBIDDEN to skip any epic or rush through stories
+
+## STORY GENERATION PROCESS:
+
+### 1. Load Approved Epic Structure
+
+Load {planning_artifacts}/epics.md and review:
+
+- Approved epics_list from Step 2
+- FR coverage map
+- All requirements (FRs, NFRs, additional, **UX Design requirements if present**)
+- Template structure at the end of the document
+
+**UX Design Integration**: If UX Design Requirements (UX-DRs) were extracted in Step 1, ensure they are visible during story creation. UX-DRs must be covered by stories — either within existing epics (e.g., accessibility fixes for a feature epic) or in a dedicated "Design System / UX Polish" epic.
+
+### 2. Explain Story Creation Approach
+
+**STORY CREATION GUIDELINES:**
+
+For each epic, create stories that:
+
+- Follow the exact template structure
+- Are sized for single dev agent completion
+- Have clear user value
+- Include specific acceptance criteria
+- Reference requirements being fulfilled
+
+**🚨 DATABASE/ENTITY CREATION PRINCIPLE:**
+Create tables/entities ONLY when needed by the story:
+
+- ❌ WRONG: Epic 1 Story 1 creates all 50 database tables
+- ✅ RIGHT: Each story creates/alters ONLY the tables it needs
+
+**🔗 STORY DEPENDENCY PRINCIPLE:**
+Stories must be independently completable in sequence:
+
+- ❌ WRONG: Story 1.2 requires Story 1.3 to be completed first
+- ✅ RIGHT: Each story can be completed based only on previous stories
+- ❌ WRONG: "Wait for Story 1.4 to be implemented before this works"
+- ✅ RIGHT: "This story works independently and enables future stories"
+
+**STORY FORMAT (from template):**
+
+```
+### Story {N}.{M}: {story_title}
+
+As a {user_type},
+I want {capability},
+So that {value_benefit}.
+
+**Acceptance Criteria:**
+
+**Given** {precondition}
+**When** {action}
+**Then** {expected_outcome}
+**And** {additional_criteria}
+```
+
+**✅ GOOD STORY EXAMPLES:**
+
+_Epic 1: User Authentication_
+
+- Story 1.1: User Registration with Email
+- Story 1.2: User Login with Password
+- Story 1.3: Password Reset via Email
+
+_Epic 2: Content Creation_
+
+- Story 2.1: Create New Blog Post
+- Story 2.2: Edit Existing Blog Post
+- Story 2.3: Publish Blog Post
+
+**❌ BAD STORY EXAMPLES:**
+
+- Story: "Set up database" (no user value)
+- Story: "Create all models" (too large, no user value)
+- Story: "Build authentication system" (too large)
+- Story: "Login UI (depends on Story 1.3 API endpoint)" (future dependency!)
+- Story: "Edit post (requires Story 1.4 to be implemented first)" (wrong order!)
+
+### 3. Process Epics Sequentially
+
+For each epic in the approved epics_list:
+
+#### A. Epic Overview
+
+Display:
+
+- Epic number and title
+- Epic goal statement
+- FRs covered by this epic
+- Any NFRs or additional requirements relevant
+- Any UX Design Requirements (UX-DRs) relevant to this epic
+
+#### B. Story Breakdown
+
+Work with user to break down the epic into stories:
+
+- Identify distinct user capabilities
+- Ensure logical flow within the epic
+- Size stories appropriately
+
+#### C. Generate Each Story
+
+For each story in the epic:
+
+1. **Story Title**: Clear, action-oriented
+2. **User Story**: Complete the As a/I want/So that format
+3. **Acceptance Criteria**: Write specific, testable criteria
+
+**AC Writing Guidelines:**
+
+- Use Given/When/Then format
+- Each AC should be independently testable
+- Include edge cases and error conditions
+- Reference specific requirements when applicable
+
+#### D. Collaborative Review
+
+After writing each story:
+
+- Present the story to user
+- Ask: "Does this story capture the requirement correctly?"
+- "Is the scope appropriate for a single dev session?"
+- "Are the acceptance criteria complete and testable?"
+
+#### E. Append to Document
+
+When story is approved:
+
+- Append it to {planning_artifacts}/epics.md following template structure
+- Use correct numbering (Epic N, Story M)
+- Maintain proper markdown formatting
+
+### 4. Epic Completion
+
+After all stories for an epic are complete:
+
+- Display epic summary
+- Show count of stories created
+- Verify all FRs for the epic are covered
+- Get user confirmation to proceed to next epic
+
+### 5. Repeat for All Epics
+
+Continue the process for each epic in the approved list, processing them in order (Epic 1, Epic 2, etc.).
+
+### 6. Final Document Completion
+
+After all epics and stories are generated:
+
+- Verify the document follows template structure exactly
+- Ensure all placeholders are replaced
+- Confirm all FRs are covered
+- **Confirm all UX Design Requirements (UX-DRs) are covered by at least one story** (if UX document was an input)
+- Check formatting consistency
+
+## TEMPLATE STRUCTURE COMPLIANCE:
+
+The final {planning_artifacts}/epics.md must follow this structure exactly:
+
+1. **Overview** section with project name
+2. **Requirements Inventory** with all three subsections populated
+3. **FR Coverage Map** showing requirement to epic mapping
+4. **Epic List** with approved epic structure
+5. **Epic sections** for each epic (N = 1, 2, 3...)
+   - Epic title and goal
+   - All stories for that epic (M = 1, 2, 3...)
+     - Story title and user story
+     - Acceptance Criteria using Given/When/Then format
+
+### 7. Present FINAL MENU OPTIONS
+
+After all epics and stories are complete:
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `bmad-advanced-elicitation` skill
+- IF P: Invoke the `bmad-party-mode` skill
+- IF C: Save content to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-04-final-validation.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-final-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `./step-04-final-validation.md` to begin final validation phase.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All epics processed in sequence
+- Stories created for each epic
+- Template structure followed exactly
+- All FRs covered by stories
+- Stories appropriately sized
+- Acceptance criteria are specific and testable
+- Document is complete and ready for development
+
+### ❌ SYSTEM FAILURE:
+
+- Deviating from template structure
+- Missing epics or stories
+- Stories too large or unclear
+- Missing acceptance criteria
+- Not following proper formatting
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
diff --git a/.claude/skills/bmad-create-epics-and-stories/steps/step-04-final-validation.md b/.claude/skills/bmad-create-epics-and-stories/steps/step-04-final-validation.md
new file mode 100644
index 0000000..a943f3d
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/steps/step-04-final-validation.md
@@ -0,0 +1,143 @@
+# Step 4: Final Validation
+
+## STEP GOAL:
+
+To validate complete coverage of all requirements and ensure stories are ready for development.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Process validation sequentially without skipping
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product strategist and technical specifications writer
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring validation expertise and quality assurance
+- ✅ User brings their implementation priorities and final review
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on validating complete requirements coverage
+- 🚫 FORBIDDEN to skip any validation checks
+- 💬 Validate FR coverage, story completeness, and dependencies
+- 🚪 ENSURE all stories are ready for development
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Validate every requirement has story coverage
+- 💾 Check story dependencies and flow
+- 📖 Verify architecture compliance
+- 🚫 FORBIDDEN to approve incomplete coverage
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Complete epic and story breakdown from previous steps
+- Focus: Final validation of requirements coverage and story readiness
+- Limits: Validation only, no new content creation
+- Dependencies: Completed story generation from Step 3
+
+## VALIDATION PROCESS:
+
+### 1. FR Coverage Validation
+
+Review the complete epic and story breakdown to ensure EVERY FR is covered:
+
+**CRITICAL CHECK:**
+
+- Go through each FR from the Requirements Inventory
+- Verify it appears in at least one story
+- Check that acceptance criteria fully address the FR
+- No FRs should be left uncovered
+
+### 2. Architecture Implementation Validation
+
+**Check for Starter Template Setup:**
+
+- Does Architecture document specify a starter template?
+- If YES: Epic 1 Story 1 must be "Set up initial project from starter template"
+- This includes cloning, installing dependencies, initial configuration
+
+**Database/Entity Creation Validation:**
+
+- Are database tables/entities created ONLY when needed by stories?
+- ❌ WRONG: Epic 1 creates all tables upfront
+- ✅ RIGHT: Tables created as part of the first story that needs them
+- Each story should create/modify ONLY what it needs
+
+### 3. Story Quality Validation
+
+**Each story must:**
+
+- Be completable by a single dev agent
+- Have clear acceptance criteria
+- Reference specific FRs it implements
+- Include necessary technical details
+- **Not have forward dependencies** (can only depend on PREVIOUS stories)
+- Be implementable without waiting for future stories
+
+### 4. Epic Structure Validation
+
+**Check that:**
+
+- Epics deliver user value, not technical milestones
+- Dependencies flow naturally
+- Foundation stories only setup what's needed
+- No big upfront technical work
+- **File Churn Check:** Do multiple epics repeatedly modify the same core files?
+  - Assess whether the overlap pattern suggests unnecessary churn or is incidental
+  - If overlap is significant: Validate that splitting provides genuine value (risk mitigation, feedback loops, context size limits)
+  - If no justification for the split: Recommend consolidation into fewer epics
+  - ❌ WRONG: Multiple epics each modify the same core files with no feedback loop between them
+  - ✅ RIGHT: Epics target distinct files/components, OR consolidation was explicitly considered and rejected with rationale
+
+### 5. Dependency Validation (CRITICAL)
+
+**Epic Independence Check:**
+
+- Does each epic deliver COMPLETE functionality for its domain?
+- Can Epic 2 function without Epic 3 being implemented?
+- Can Epic 3 function standalone using Epic 1 & 2 outputs?
+- ❌ WRONG: Epic 2 requires Epic 3 features to work
+- ✅ RIGHT: Each epic is independently valuable
+
+**Within-Epic Story Dependency Check:**
+For each epic, review stories in order:
+
+- Can Story N.1 be completed without Stories N.2, N.3, etc.?
+- Can Story N.2 be completed using only Story N.1 output?
+- Can Story N.3 be completed using only Stories N.1 & N.2 outputs?
+- ❌ WRONG: "This story depends on a future story"
+- ❌ WRONG: Story references features not yet implemented
+- ✅ RIGHT: Each story builds only on previous stories
+
+### 6. Complete and Save
+
+If all validations pass:
+
+- Update any remaining placeholders in the document
+- Ensure proper formatting
+- Save the final epics.md
+
+**Present Final Menu:**
+**All validations complete!** [C] Complete Workflow
+
+HALT — wait for user input before proceeding.
+
+When C is selected, the workflow is complete and the epics.md is ready for development.
+
+Epics and Stories complete. Invoke the `bmad-help` skill.
+
+Upon Completion of task output: offer to answer any questions about the Epics and Stories.
+
+## On Complete
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+
+If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
diff --git a/.claude/skills/bmad-create-epics-and-stories/templates/epics-template.md b/.claude/skills/bmad-create-epics-and-stories/templates/epics-template.md
new file mode 100644
index 0000000..bf80c7f
--- /dev/null
+++ b/.claude/skills/bmad-create-epics-and-stories/templates/epics-template.md
@@ -0,0 +1,61 @@
+---
+stepsCompleted: []
+inputDocuments: []
+---
+
+# {{project_name}} - Epic Breakdown
+
+## Overview
+
+This document provides the complete epic and story breakdown for {{project_name}}, decomposing the requirements from the PRD, UX Design if it exists, and Architecture requirements into implementable stories.
+
+## Requirements Inventory
+
+### Functional Requirements
+
+{{fr_list}}
+
+### NonFunctional Requirements
+
+{{nfr_list}}
+
+### Additional Requirements
+
+{{additional_requirements}}
+
+### UX Design Requirements
+
+{{ux_design_requirements}}
+
+### FR Coverage Map
+
+{{requirements_coverage_map}}
+
+## Epic List
+
+{{epics_list}}
+
+<!-- Repeat for each epic in epics_list (N = 1, 2, 3...) -->
+
+## Epic {{N}}: {{epic_title_N}}
+
+{{epic_goal_N}}
+
+<!-- Repeat for each story (M = 1, 2, 3...) within epic N -->
+
+### Story {{N}}.{{M}}: {{story_title_N_M}}
+
+As a {{user_type}},
+I want {{capability}},
+So that {{value_benefit}}.
+
+**Acceptance Criteria:**
+
+<!-- for each AC on this story -->
+
+**Given** {{precondition}}
+**When** {{action}}
+**Then** {{expected_outcome}}
+**And** {{additional_criteria}}
+
+<!-- End story repeat -->
diff --git a/.claude/skills/bmad-create-prd/SKILL.md b/.claude/skills/bmad-create-prd/SKILL.md
new file mode 100644
index 0000000..5205fa6
--- /dev/null
+++ b/.claude/skills/bmad-create-prd/SKILL.md
@@ -0,0 +1,30 @@
+---
+name: bmad-create-prd
+description: 'Deprecated — forwards to bmad-prd (create intent).'
+---
+
+# DEPRECATED — forwards to bmad-prd (create intent)
+
+This skill was consolidated into `bmad-prd`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-create-prd.toml` override files keep working. New work should invoke `bmad-prd` directly — it detects create / update / validate intent from the conversation.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-create-prd.toml` and `bmad-create-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+
+2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+
+3. Emit a deprecation notice to the user in `{communication_language}`:
+
+   > Notice: `bmad-create-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with create intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`, `prd_output_path`, `run_folder_pattern`), migrate `_bmad/custom/bmad-create-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+
+4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
+
+   - **Intent:** `create` — skip `bmad-prd`'s usual intent detection step.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `prd_output_path`, `run_folder_pattern`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+     - `activation_steps_prepend` = the resolved value from step 1
+     - `activation_steps_append` = the resolved value from step 1
+     - `persistent_facts` = the resolved value from step 1
+     - `on_complete` = the resolved value from step 1
+   - **Original user input:** forward whatever the user said when invoking this skill verbatim.
+
+   `bmad-prd` takes the workflow from here. Do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-create-prd/customize.toml b/.claude/skills/bmad-create-prd/customize.toml
new file mode 100644
index 0000000..fde1ba1
--- /dev/null
+++ b/.claude/skills/bmad-create-prd/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-create-prd. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All PRDs must include a regulatory-risk section."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 12 (Workflow Completion),
+# after the PRD is finalized and workflow status is updated. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-create-story/SKILL.md b/.claude/skills/bmad-create-story/SKILL.md
new file mode 100644
index 0000000..f5e1722
--- /dev/null
+++ b/.claude/skills/bmad-create-story/SKILL.md
@@ -0,0 +1,434 @@
+---
+name: bmad-create-story
+description: "Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name."
+---
+
+# Create Story Workflow
+
+**Goal:** Create a comprehensive story file that gives the dev agent everything needed for flawless implementation.
+
+**Your Role:** Story context engine that prevents LLM developer mistakes, omissions, or disasters.
+- Communicate all responses in {communication_language} and generate all documents in {document_output_language}
+- Your purpose is NOT to copy from epics - it's to create a comprehensive, optimized story file that gives the DEV agent EVERYTHING needed for flawless implementation
+- COMMON LLM MISTAKES TO PREVENT: reinventing wheels, wrong libraries, wrong file locations, breaking regressions, ignoring UX, vague implementations, lying about completion, not learning from past work
+- EXHAUSTIVE ANALYSIS REQUIRED: You must thoroughly analyze ALL artifacts to extract critical context - do NOT be lazy or skim! This is the most important function in the entire development process!
+- UTILIZE SUBPROCESSES AND SUBAGENTS: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different artifacts simultaneously and thoroughly
+- SAVE QUESTIONS: If you think of questions or clarifications during analysis, save them for the end after the complete story is written
+- ZERO USER INTERVENTION: Process should be fully automated except for initial epic/story selection or missing documents
+
+Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
+If you need an explicit user instruction to run them, ask once now for the whole workflow run.
+
+## Conventions
+
+- Bare paths (e.g. `discover-inputs.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `user_name`
+- `communication_language`, `document_output_language`
+- `user_skill_level`
+- `planning_artifacts`, `implementation_artifacts`
+- `date` as system-generated current datetime
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+<output>Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name.</output>
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Paths
+
+- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
+- `epics_file` = `{planning_artifacts}/epics.md`
+- `prd_file` = `{planning_artifacts}/prd.md`
+- `architecture_file` = `{planning_artifacts}/architecture.md`
+- `ux_file` = `{planning_artifacts}/*ux*.md`
+- `story_title` = "" (will be elicited if not derivable)
+- `default_output_file` = `{implementation_artifacts}/{{story_key}}.md`
+
+## Input Files
+
+| Input | Description | Path Pattern(s) | Load Strategy |
+|-------|-------------|------------------|---------------|
+| prd | PRD (fallback - epics file should have most content) | whole: `{planning_artifacts}/*prd*.md`, sharded: `{planning_artifacts}/*prd*/*.md` | SELECTIVE_LOAD |
+| architecture | Architecture (fallback - epics file should have relevant sections) | whole: `{planning_artifacts}/*architecture*.md`, sharded: `{planning_artifacts}/*architecture*/*.md` | SELECTIVE_LOAD |
+| ux | UX design (fallback - epics file should have relevant sections) | whole: `{planning_artifacts}/*ux*.md`, sharded: `{planning_artifacts}/*ux*/*.md` | SELECTIVE_LOAD |
+| epics | Enhanced epics+stories file with BDD and source hints | whole: `{planning_artifacts}/*epic*.md`, sharded: `{planning_artifacts}/*epic*/*.md` | SELECTIVE_LOAD |
+
+## Execution
+
+<workflow>
+
+<step n="1" goal="Determine target story">
+  <check if="{{story_path}} is provided by user or user provided the epic and story number such as 2-4 or 1.6 or epic 1 story 5">
+    <action>Parse user-provided story path: extract epic_num, story_num, story_title from format like "1-2-user-auth"</action>
+    <action>Set {{epic_num}}, {{story_num}}, {{story_key}} from user input</action>
+    <action>GOTO step 2a</action>
+  </check>
+
+  <action>Check if {{sprint_status}} file exists for auto discover</action>
+  <check if="sprint status file does NOT exist">
+    <output>🚫 No sprint status file found and no story specified</output>
+    <output>
+      **Required Options:**
+      1. Run `sprint-planning` to initialize sprint tracking (recommended)
+      2. Provide specific epic-story number to create (e.g., "1-2-user-auth")
+      3. Provide path to story documents if sprint status doesn't exist yet
+    </output>
+    <ask>Choose option [1], provide epic-story number, path to story docs, or [q] to quit:</ask>
+
+    <check if="user chooses 'q'">
+      <action>HALT - No work needed</action>
+    </check>
+
+    <check if="user chooses '1'">
+      <output>Run sprint-planning workflow first to create sprint-status.yaml</output>
+      <action>HALT - User needs to run sprint-planning</action>
+    </check>
+
+    <check if="user provides epic-story number">
+      <action>Parse user input: extract epic_num, story_num, story_title</action>
+      <action>Set {{epic_num}}, {{story_num}}, {{story_key}} from user input</action>
+      <action>GOTO step 2a</action>
+    </check>
+
+    <check if="user provides story docs path">
+      <action>Use user-provided path for story documents</action>
+      <action>GOTO step 2a</action>
+    </check>
+  </check>
+
+  <!-- Auto-discover from sprint status only if no user input -->
+  <check if="no user input provided">
+    <critical>MUST read COMPLETE {sprint_status} file from start to end to preserve order</critical>
+    <action>Load the FULL file: {{sprint_status}}</action>
+    <action>Read ALL lines from beginning to end - do not skip any content</action>
+    <action>Parse the development_status section completely</action>
+
+    <action>Find the FIRST story (by reading in order from top to bottom) where:
+      - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
+      - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
+      - Status value equals "backlog"
+    </action>
+
+    <check if="no backlog story found">
+      <output>📋 No backlog stories found in sprint-status.yaml
+
+        All stories are either already created, in progress, or done.
+
+        **Options:**
+        1. Run sprint-planning to refresh story tracking
+        2. Load PM agent and run correct-course to add more stories
+        3. Check if current sprint is complete and run retrospective
+      </output>
+      <action>HALT</action>
+    </check>
+
+    <action>Extract from found story key (e.g., "1-2-user-authentication"):
+      - epic_num: first number before dash (e.g., "1")
+      - story_num: second number after first dash (e.g., "2")
+      - story_title: remainder after second dash (e.g., "user-authentication")
+    </action>
+    <action>Set {{story_id}} = "{{epic_num}}.{{story_num}}"</action>
+    <action>Store story_key for later use (e.g., "1-2-user-authentication")</action>
+
+    <!-- Mark epic as in-progress if this is first story -->
+    <action>Check if this is the first story in epic {{epic_num}} by looking for {{epic_num}}-1-* pattern</action>
+    <check if="this is first story in epic {{epic_num}}">
+      <action>Load {{sprint_status}} and check epic-{{epic_num}} status</action>
+      <action>If epic status is "backlog" → update to "in-progress"</action>
+      <action>If epic status is "contexted" (legacy status) → update to "in-progress" (backward compatibility)</action>
+      <action>If epic status is "in-progress" → no change needed</action>
+      <check if="epic status is 'done'">
+        <output>🚫 ERROR: Cannot create story in completed epic</output>
+        <output>Epic {{epic_num}} is marked as 'done'. All stories are complete.</output>
+        <output>If you need to add more work, either:</output>
+        <output>1. Manually change epic status back to 'in-progress' in sprint-status.yaml</output>
+        <output>2. Create a new epic for additional work</output>
+        <action>HALT - Cannot proceed</action>
+      </check>
+      <check if="epic status is not one of: backlog, contexted, in-progress, done">
+        <output>🚫 ERROR: Invalid epic status '{{epic_status}}'</output>
+        <output>Epic {{epic_num}} has invalid status. Expected: backlog, in-progress, or done</output>
+        <output>Please fix sprint-status.yaml manually or run sprint-planning to regenerate</output>
+        <action>HALT - Cannot proceed</action>
+      </check>
+      <output>📊 Epic {{epic_num}} status updated to in-progress</output>
+    </check>
+
+    <action>GOTO step 2a</action>
+  </check>
+  <action>Load the FULL file: {{sprint_status}}</action>
+  <action>Read ALL lines from beginning to end - do not skip any content</action>
+  <action>Parse the development_status section completely</action>
+
+  <action>Find the FIRST story (by reading in order from top to bottom) where:
+    - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
+    - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
+    - Status value equals "backlog"
+  </action>
+
+  <check if="no backlog story found">
+    <output>No backlog stories found in sprint-status.yaml
+
+      All stories are either already created, in progress, or done.
+
+      **Options:**
+      1. Run sprint-planning to refresh story tracking
+      2. Load PM agent and run correct-course to add more stories
+      3. Check if current sprint is complete and run retrospective
+    </output>
+    <action>HALT</action>
+  </check>
+
+  <action>Extract from found story key (e.g., "1-2-user-authentication"):
+    - epic_num: first number before dash (e.g., "1")
+    - story_num: second number after first dash (e.g., "2")
+    - story_title: remainder after second dash (e.g., "user-authentication")
+  </action>
+  <action>Set {{story_id}} = "{{epic_num}}.{{story_num}}"</action>
+  <action>Store story_key for later use (e.g., "1-2-user-authentication")</action>
+
+  <!-- Mark epic as in-progress if this is first story -->
+  <action>Check if this is the first story in epic {{epic_num}} by looking for {{epic_num}}-1-* pattern</action>
+  <check if="this is first story in epic {{epic_num}}">
+    <action>Load {{sprint_status}} and check epic-{{epic_num}} status</action>
+    <action>If epic status is "backlog" → update to "in-progress"</action>
+    <action>If epic status is "contexted" (legacy status) → update to "in-progress" (backward compatibility)</action>
+    <action>If epic status is "in-progress" → no change needed</action>
+    <check if="epic status is 'done'">
+      <output>ERROR: Cannot create story in completed epic</output>
+      <output>Epic {{epic_num}} is marked as 'done'. All stories are complete.</output>
+      <output>If you need to add more work, either:</output>
+      <output>1. Manually change epic status back to 'in-progress' in sprint-status.yaml</output>
+      <output>2. Create a new epic for additional work</output>
+      <action>HALT - Cannot proceed</action>
+    </check>
+    <check if="epic status is not one of: backlog, contexted, in-progress, done">
+      <output>ERROR: Invalid epic status '{{epic_status}}'</output>
+      <output>Epic {{epic_num}} has invalid status. Expected: backlog, in-progress, or done</output>
+      <output>Please fix sprint-status.yaml manually or run sprint-planning to regenerate</output>
+      <action>HALT - Cannot proceed</action>
+    </check>
+    <output>Epic {{epic_num}} status updated to in-progress</output>
+  </check>
+
+  <action>GOTO step 2a</action>
+</step>
+
+<step n="2" goal="Load and analyze core artifacts">
+  <critical>🔬 EXHAUSTIVE ARTIFACT ANALYSIS - This is where you prevent future developer mistakes!</critical>
+
+  <!-- Load all available content through discovery protocol -->
+  <action>Read fully and follow `./discover-inputs.md` to load all input files</action>
+  <note>Available content: {epics_content}, {prd_content}, {architecture_content}, {ux_content}, plus the project-context facts loaded during activation via `persistent_facts`.</note>
+
+  <!-- Analyze epics file for story foundation -->
+  <action>From {epics_content}, extract Epic {{epic_num}} complete context:</action> **EPIC ANALYSIS:** - Epic
+  objectives and business value - ALL stories in this epic for cross-story context - Our specific story's requirements, user story
+  statement, acceptance criteria - Technical requirements and constraints - Dependencies on other stories/epics - Source hints pointing to
+  original documents <!-- Extract specific story requirements -->
+  <action>Extract our story ({{epic_num}}-{{story_num}}) details:</action> **STORY FOUNDATION:** - User story statement
+  (As a, I want, so that) - Detailed acceptance criteria (already BDD formatted) - Technical requirements specific to this story -
+  Business context and value - Success criteria <!-- Previous story analysis for context continuity -->
+  <check if="story_num > 1">
+    <action>Find {{previous_story_num}}: scan {implementation_artifacts} for the story file in epic {{epic_num}} with the highest story number less than {{story_num}}</action>
+    <action>Load previous story file: {implementation_artifacts}/{{epic_num}}-{{previous_story_num}}-*.md</action> **PREVIOUS STORY INTELLIGENCE:** -
+  Dev notes and learnings from previous story - Review feedback and corrections needed - Files that were created/modified and their
+  patterns - Testing approaches that worked/didn't work - Problems encountered and solutions found - Code patterns established <action>Extract
+  all learnings that could impact current story implementation</action>
+  </check>
+
+  <!-- Git intelligence for previous work patterns -->
+  <check
+    if="previous story exists AND git repository detected">
+    <action>Get last 5 commit titles to understand recent work patterns</action>
+    <action>Analyze 1-5 most recent commits for relevance to current story:
+      - Files created/modified
+      - Code patterns and conventions used
+      - Library dependencies added/changed
+      - Architecture decisions implemented
+      - Testing approaches used
+    </action>
+    <action>Extract actionable insights for current story implementation</action>
+  </check>
+</step>
+
+<step n="3" goal="Architecture analysis for developer guardrails">
+  <critical>🏗️ ARCHITECTURE INTELLIGENCE - Extract everything the developer MUST follow!</critical> **ARCHITECTURE DOCUMENT ANALYSIS:** <action>Systematically
+  analyze architecture content for story-relevant requirements:</action>
+
+  <!-- Load architecture - single file or sharded -->
+  <check if="architecture file is single file">
+    <action>Load complete {architecture_content}</action>
+  </check>
+  <check if="architecture is sharded to folder">
+    <action>Load architecture index and scan all architecture files</action>
+  </check> **CRITICAL ARCHITECTURE EXTRACTION:** <action>For
+  each architecture section, determine if relevant to this story:</action> - **Technical Stack:** Languages, frameworks, libraries with
+  versions - **Code Structure:** Folder organization, naming conventions, file patterns - **API Patterns:** Service structure, endpoint
+  patterns, data contracts - **Database Schemas:** Tables, relationships, constraints relevant to story - **Security Requirements:**
+  Authentication patterns, authorization rules - **Performance Requirements:** Caching strategies, optimization patterns - **Testing
+  Standards:** Testing frameworks, coverage expectations, test patterns - **Deployment Patterns:** Environment configurations, build
+  processes - **Integration Patterns:** External service integrations, data flows <action>Extract any story-specific requirements that the
+  developer MUST follow</action>
+  <action>Identify any architectural decisions that override previous patterns</action>
+
+  <!-- Read existing code being modified — non-negotiable -->
+  <critical>📂 READ FILES BEING MODIFIED — skipping this is the primary cause of implementation failures and review cycles</critical>
+  <action>From the architecture directory structure, identify every file marked UPDATE (not NEW) that this story will touch</action>
+  <action>Read each relevant UPDATE file completely. For each one, document in dev notes:
+    - Current state: what it does today (state machine, API calls, data shapes, existing behaviors)
+    - What this story changes: the specific sections or behaviors being modified
+    - What must be preserved: existing interactions and behaviors the story must not break
+  </action>
+  <critical>A story implementation must leave the system working end-to-end — not just satisfy its stated ACs.
+  If a behavior is required for the feature to work correctly in the existing system, it is a requirement
+  whether or not it is explicitly written in the story. The dev agent owns this.</critical>
+</step>
+
+<step n="4" goal="Web research for latest technical specifics">
+  <critical>🌐 ENSURE LATEST TECH KNOWLEDGE - Prevent outdated implementations!</critical> **WEB INTELLIGENCE:** <action>Identify specific
+  technical areas that require latest version knowledge:</action>
+
+  <!-- Check for libraries/frameworks mentioned in architecture -->
+  <action>From architecture analysis, identify specific libraries, APIs, or
+  frameworks</action>
+  <action>For each critical technology, research latest stable version and key changes:
+    - Latest API documentation and breaking changes
+    - Security vulnerabilities or updates
+    - Performance improvements or deprecations
+    - Best practices for current version
+  </action>
+  **EXTERNAL CONTEXT INCLUSION:** <action>Include in story any critical latest information the developer needs:
+    - Specific library versions and why chosen
+    - API endpoints with parameters and authentication
+    - Recent security patches or considerations
+    - Performance optimization techniques
+    - Migration considerations if upgrading
+  </action>
+</step>
+
+<step n="5" goal="Create comprehensive story file">
+  <critical>📝 CREATE ULTIMATE STORY FILE - The developer's master implementation guide!</critical>
+
+  <action>Initialize from template.md:
+  {default_output_file}</action>
+  <template-output file="{default_output_file}">story_header</template-output>
+
+  <!-- Story foundation from epics analysis -->
+  <template-output
+    file="{default_output_file}">story_requirements</template-output>
+
+  <!-- Developer context section - MOST IMPORTANT PART -->
+  <template-output file="{default_output_file}">
+  developer_context_section</template-output> **DEV AGENT GUARDRAILS:** <template-output file="{default_output_file}">
+  technical_requirements</template-output>
+  <template-output file="{default_output_file}">architecture_compliance</template-output>
+  <template-output
+    file="{default_output_file}">library_framework_requirements</template-output>
+  <template-output file="{default_output_file}">
+  file_structure_requirements</template-output>
+  <template-output file="{default_output_file}">testing_requirements</template-output>
+
+  <!-- Previous story intelligence -->
+  <check
+    if="previous story learnings available">
+    <template-output file="{default_output_file}">previous_story_intelligence</template-output>
+  </check>
+
+  <!-- Git intelligence -->
+  <check
+    if="git analysis completed">
+    <template-output file="{default_output_file}">git_intelligence_summary</template-output>
+  </check>
+
+  <!-- Latest technical specifics -->
+  <check if="web research completed">
+    <template-output file="{default_output_file}">latest_tech_information</template-output>
+  </check>
+
+  <!-- Project context reference -->
+  <template-output
+    file="{default_output_file}">project_context_reference</template-output>
+
+  <!-- Final status update -->
+  <template-output file="{default_output_file}">
+  story_completion_status</template-output>
+
+  <!-- CRITICAL: Set status to ready-for-dev -->
+  <action>Set story Status to: "ready-for-dev"</action>
+  <action>Add completion note: "Ultimate
+  context engine analysis completed - comprehensive developer guide created"</action>
+</step>
+
+<step n="6" goal="Update sprint status and finalize">
+  <action>Validate the newly created story file {default_output_file} against `./checklist.md` and apply any required fixes before finalizing</action>
+  <action>Save story document unconditionally</action>
+
+  <!-- Update sprint status -->
+  <check if="sprint status file exists">
+    <action>Update {{sprint_status}}</action>
+    <action>Load the FULL file and read all development_status entries</action>
+    <action>Find development_status key matching {{story_key}}</action>
+    <action>Verify current status is "backlog" (expected previous state)</action>
+    <action>Update development_status[{{story_key}}] = "ready-for-dev"</action>
+    <action>Update last_updated field to current date</action>
+    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+  </check>
+
+  <action>Report completion</action>
+  <output>**🎯 ULTIMATE BMad Method STORY CONTEXT CREATED, {user_name}!**
+
+    **Story Details:**
+    - Story ID: {{story_id}}
+    - Story Key: {{story_key}}
+    - File: {{story_file}}
+    - Status: ready-for-dev
+
+    **Next Steps:**
+    1. Review the comprehensive story in {{story_file}}
+    2. Run dev agents `dev-story` for optimized implementation
+    3. Run `code-review` when complete (auto-marks done)
+    4. Optional: If Test Architect module installed, run `/bmad:tea:automate` after `dev-story` to generate guardrail tests
+
+    **The developer now has everything needed for flawless implementation!**
+  </output>
+  <action>Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+</step>
+
+</workflow>
diff --git a/.claude/skills/bmad-create-story/checklist.md b/.claude/skills/bmad-create-story/checklist.md
new file mode 100644
index 0000000..e47cc0f
--- /dev/null
+++ b/.claude/skills/bmad-create-story/checklist.md
@@ -0,0 +1,357 @@
+# 🎯 Story Context Quality Competition Prompt
+
+## **🔥 CRITICAL MISSION: Outperform and Fix the Original Create-Story LLM**
+
+You are an independent quality validator in a **FRESH CONTEXT**. Your mission is to **thoroughly review** a story file that was generated by the create-story workflow and **systematically identify any mistakes, omissions, or disasters** that the original LLM missed.
+
+**Your purpose is NOT just to validate - it's to FIX and PREVENT LLM developer mistakes, omissions, or disasters!**
+
+### **🚨 CRITICAL MISTAKES TO PREVENT:**
+
+- **Reinventing wheels** - Creating duplicate functionality instead of reusing existing
+- **Wrong libraries** - Using incorrect frameworks, versions, or dependencies
+- **Wrong file locations** - Violating project structure and organization
+- **Breaking regressions** - Implementing changes that break existing functionality
+- **Ignoring UX** - Not following user experience design requirements
+- **Vague implementations** - Creating unclear, ambiguous implementations
+- **Lying about completion** - Implementing incorrectly or incompletely
+- **Not learning from past work** - Ignoring previous story learnings and patterns
+
+### **🚨 EXHAUSTIVE ANALYSIS REQUIRED:**
+
+You must thoroughly analyze **ALL artifacts** to extract critical context - do NOT be lazy or skim! This is the most important quality control function in the entire development process!
+
+### **🔬 UTILIZE SUBPROCESSES AND SUBAGENTS:**
+
+Use research subagents, subprocesses, or parallel processing if available to thoroughly analyze different artifacts **simultaneously and thoroughly**. Leave no stone unturned!
+
+### **🎯 COMPETITIVE EXCELLENCE:**
+
+This is a COMPETITION to create the **ULTIMATE story context** that makes LLM developer mistakes **IMPOSSIBLE**!
+
+## **🚀 HOW TO USE THIS CHECKLIST**
+
+### **When Running from Create-Story Workflow:**
+
+- The workflow framework will automatically:
+  - Load this checklist file
+  - Load the newly created story file (`{story_file_path}`)
+  - Load workflow variables from `./workflow.md`
+  - Execute the validation process
+
+### **When Running in Fresh Context:**
+
+- User should provide the story file path being reviewed
+- Load the story file directly
+- Load the corresponding workflow.md for variable context
+- Proceed with systematic analysis
+
+### **Required Inputs:**
+
+- **Story file**: The story file to review and improve
+- **Workflow variables**: From workflow.md (implementation_artifacts, epics_file, etc.)
+- **Source documents**: Epics, architecture, etc. (discovered or provided)
+- **Validation framework**: The workflow's checklist execution system
+
+---
+
+## **🔬 SYSTEMATIC RE-ANALYSIS APPROACH**
+
+You will systematically re-do the entire story creation process, but with a critical eye for what the original LLM might have missed:
+
+### **Step 1: Load and Understand the Target**
+
+1. **Load the workflow configuration**: `./workflow.md` for variable inclusion
+2. **Load the story file**: `{story_file_path}` (provided by user or discovered)
+3. **Extract metadata**: epic_num, story_num, story_key, story_title from story file
+4. **Resolve all workflow variables**: implementation_artifacts, epics_file, architecture_file, etc.
+5. **Understand current status**: What story implementation guidance is currently provided?
+
+**Note:** If running in fresh context, user should provide the story file path being reviewed. If running from create-story workflow, the validation framework will automatically discover the checklist and story file.
+
+### **Step 2: Exhaustive Source Document Analysis**
+
+**🔥 CRITICAL: Treat this like YOU are creating the story from scratch to PREVENT DISASTERS!**
+**Discover everything the original LLM missed that could cause developer mistakes, omissions, or disasters!**
+
+#### **2.1 Epics and Stories Analysis**
+
+- Load `{epics_file}` (or sharded equivalents)
+- Extract **COMPLETE Epic {{epic_num}} context**:
+  - Epic objectives and business value
+  - ALL stories in this epic (for cross-story context)
+  - Our specific story's requirements, acceptance criteria
+  - Technical requirements and constraints
+  - Cross-story dependencies and prerequisites
+
+#### **2.2 Architecture Deep-Dive**
+
+- Load `{architecture_file}` (single or sharded)
+- **Systematically scan for ANYTHING relevant to this story:**
+  - Technical stack with versions (languages, frameworks, libraries)
+  - Code structure and organization patterns
+  - API design patterns and contracts
+  - Database schemas and relationships
+  - Security requirements and patterns
+  - Performance requirements and optimization strategies
+  - Testing standards and frameworks
+  - Deployment and environment patterns
+  - Integration patterns and external services
+
+#### **2.3 Previous Story Intelligence (if applicable)**
+
+- If `story_num > 1`, load the previous story file
+- Extract **actionable intelligence**:
+  - Dev notes and learnings
+  - Review feedback and corrections needed
+  - Files created/modified and their patterns
+  - Testing approaches that worked/didn't work
+  - Problems encountered and solutions found
+  - Code patterns and conventions established
+
+#### **2.4 Git History Analysis (if available)**
+
+- Analyze recent commits for patterns:
+  - Files created/modified in previous work
+  - Code patterns and conventions used
+  - Library dependencies added/changed
+  - Architecture decisions implemented
+  - Testing approaches used
+
+#### **2.5 Latest Technical Research**
+
+- Identify any libraries/frameworks mentioned
+- Research latest versions and critical information:
+  - Breaking changes or security updates
+  - Performance improvements or deprecations
+  - Best practices for current versions
+
+### **Step 3: Disaster Prevention Gap Analysis**
+
+**🚨 CRITICAL: Identify every mistake the original LLM missed that could cause DISASTERS!**
+
+#### **3.1 Reinvention Prevention Gaps**
+
+- **Wheel reinvention:** Areas where developer might create duplicate functionality
+- **Code reuse opportunities** not identified that could prevent redundant work
+- **Existing solutions** not mentioned that developer should extend instead of replace
+
+#### **3.2 Technical Specification DISASTERS**
+
+- **Wrong libraries/frameworks:** Missing version requirements that could cause compatibility issues
+- **API contract violations:** Missing endpoint specifications that could break integrations
+- **Database schema conflicts:** Missing requirements that could corrupt data
+- **Security vulnerabilities:** Missing security requirements that could expose the system
+- **Performance disasters:** Missing requirements that could cause system failures
+
+#### **3.3 File Structure DISASTERS**
+
+- **Wrong file locations:** Missing organization requirements that could break build processes
+- **Coding standard violations:** Missing conventions that could create inconsistent codebase
+- **Integration pattern breaks:** Missing data flow requirements that could cause system failures
+- **Deployment failures:** Missing environment requirements that could prevent deployment
+
+#### **3.4 Regression DISASTERS**
+
+- **Breaking changes:** Missing requirements that could break existing functionality
+- **Test failures:** Missing test requirements that could allow bugs to reach production
+- **UX violations:** Missing user experience requirements that could ruin the product
+- **Learning failures:** Missing previous story context that could repeat same mistakes
+
+#### **3.5 Implementation DISASTERS**
+
+- **Vague implementations:** Missing details that could lead to incorrect or incomplete work
+- **Completion lies:** Missing acceptance criteria that could allow fake implementations
+- **Scope creep:** Missing boundaries that could cause unnecessary work
+- **Quality failures:** Missing quality requirements that could deliver broken features
+
+### **Step 4: LLM-Dev-Agent Optimization Analysis**
+
+**CRITICAL STEP: Optimize story context for LLM developer agent consumption**
+
+**Analyze current story for LLM optimization issues:**
+
+- **Verbosity problems:** Excessive detail that wastes tokens without adding value
+- **Ambiguity issues:** Vague instructions that could lead to multiple interpretations
+- **Context overload:** Too much information not directly relevant to implementation
+- **Missing critical signals:** Key requirements buried in verbose text
+- **Poor structure:** Information not organized for efficient LLM processing
+
+**Apply LLM Optimization Principles:**
+
+- **Clarity over verbosity:** Be precise and direct, eliminate fluff
+- **Actionable instructions:** Every sentence should guide implementation
+- **Scannable structure:** Use clear headings, bullet points, and emphasis
+- **Token efficiency:** Pack maximum information into minimum text
+- **Unambiguous language:** Clear requirements with no room for interpretation
+
+### **Step 5: Improvement Recommendations**
+
+**For each gap identified, provide specific, actionable improvements:**
+
+#### **5.1 Critical Misses (Must Fix)**
+
+- Missing essential technical requirements
+- Missing previous story context that could cause errors
+- Missing anti-pattern prevention that could lead to duplicate code
+- Missing security or performance requirements
+
+#### **5.2 Enhancement Opportunities (Should Add)**
+
+- Additional architectural guidance that would help developer
+- More detailed technical specifications
+- Better code reuse opportunities
+- Enhanced testing guidance
+
+#### **5.3 Optimization Suggestions (Nice to Have)**
+
+- Performance optimization hints
+- Additional context for complex scenarios
+- Enhanced debugging or development tips
+
+#### **5.4 LLM Optimization Improvements**
+
+- Token-efficient phrasing of existing content
+- Clearer structure for LLM processing
+- More actionable and direct instructions
+- Reduced verbosity while maintaining completeness
+
+---
+
+## **🎯 COMPETITION SUCCESS METRICS**
+
+**You WIN against the original LLM if you identify:**
+
+### **Category 1: Critical Misses (Blockers)**
+
+- Essential technical requirements the developer needs but aren't provided
+- Previous story learnings that would prevent errors if ignored
+- Anti-pattern prevention that would prevent code duplication
+- Security or performance requirements that must be followed
+
+### **Category 2: Enhancement Opportunities**
+
+- Architecture guidance that would significantly help implementation
+- Technical specifications that would prevent wrong approaches
+- Code reuse opportunities the developer should know about
+- Testing guidance that would improve quality
+
+### **Category 3: Optimization Insights**
+
+- Performance or efficiency improvements
+- Development workflow optimizations
+- Additional context for complex scenarios
+
+---
+
+## **📋 INTERACTIVE IMPROVEMENT PROCESS**
+
+After completing your systematic analysis, present your findings to the user interactively:
+
+### **Step 5: Present Improvement Suggestions**
+
+```
+🎯 **STORY CONTEXT QUALITY REVIEW COMPLETE**
+
+**Story:** {{story_key}} - {{story_title}}
+
+I found {{critical_count}} critical issues, {{enhancement_count}} enhancements, and {{optimization_count}} optimizations.
+
+## **🚨 CRITICAL ISSUES (Must Fix)**
+
+{{list each critical issue with clear, actionable description}}
+
+## **⚡ ENHANCEMENT OPPORTUNITIES (Should Add)**
+
+{{list each enhancement with clear benefit description}}
+
+## **✨ OPTIMIZATIONS (Nice to Have)**
+
+{{list each optimization with benefit description}}
+
+## **🤖 LLM OPTIMIZATION (Token Efficiency & Clarity)**
+
+{{list each LLM optimization that will improve dev agent performance:
+- Reduce verbosity while maintaining completeness
+- Improve structure for better LLM processing
+- Make instructions more actionable and direct
+- Enhance clarity and reduce ambiguity}}
+```
+
+### **Step 6: Interactive User Selection**
+
+After presenting the suggestions, ask the user:
+
+```
+**IMPROVEMENT OPTIONS:**
+
+Which improvements would you like me to apply to the story?
+
+**Select from the numbered list above, or choose:**
+- **all** - Apply all suggested improvements
+- **critical** - Apply only critical issues
+- **select** - I'll choose specific numbers
+- **none** - Keep story as-is
+- **details** - Show me more details about any suggestion
+
+Your choice:
+```
+
+### **Step 7: Apply Selected Improvements**
+
+When user accepts improvements:
+
+- **Load the story file**
+- **Apply accepted changes** (make them look natural, as if they were always there)
+- **DO NOT reference** the review process, original LLM, or that changes were "added" or "enhanced"
+- **Ensure clean, coherent final story** that reads as if it was created perfectly the first time
+
+### **Step 8: Confirmation**
+
+After applying changes:
+
+```
+✅ **STORY IMPROVEMENTS APPLIED**
+
+Updated {{count}} sections in the story file.
+
+The story now includes comprehensive developer guidance to prevent common implementation issues and ensure flawless execution.
+
+**Next Steps:**
+1. Review the updated story
+2. Run `dev-story` for implementation
+```
+
+---
+
+## **💪 COMPETITIVE EXCELLENCE MINDSET**
+
+**Your goal:** Improve the story file with dev agent needed context that makes flawless implementation inevitable while being optimized for LLM developer agent consumption. Remember the dev agent will ONLY have this file to use.
+
+**Success Criteria:** The LLM developer agent that processes your improved story will have:
+
+- ✅ Clear technical requirements they must follow
+- ✅ Previous work context they can build upon
+- ✅ Anti-pattern prevention to avoid common mistakes
+- ✅ Comprehensive guidance for efficient implementation
+- ✅ **Optimized content structure** for maximum clarity and minimum token waste
+- ✅ **Actionable instructions** with no ambiguity or verbosity
+- ✅ **Efficient information density** - maximum guidance in minimum text
+
+**Every improvement should make it IMPOSSIBLE for the developer to:**
+
+- Reinvent existing solutions
+- Use wrong approaches or libraries
+- Create duplicate functionality
+- Miss critical requirements
+- Make implementation errors
+
+**LLM Optimization Should Make it IMPOSSIBLE for the developer agent to:**
+
+- Misinterpret requirements due to ambiguity
+- Waste tokens on verbose, non-actionable content
+- Struggle to find critical information buried in text
+- Get confused by poor structure or organization
+- Miss key implementation signals due to inefficient communication
+
+**Go create the ultimate developer implementation guide! 🚀**
diff --git a/.claude/skills/bmad-create-story/customize.toml b/.claude/skills/bmad-create-story/customize.toml
new file mode 100644
index 0000000..fbd4a78
--- /dev/null
+++ b/.claude/skills/bmad-create-story/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-create-story. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All stories must include testable acceptance criteria."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 6 (Update sprint status and finalize),
+# after the story file is saved and sprint-status.yaml is updated. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-create-story/discover-inputs.md b/.claude/skills/bmad-create-story/discover-inputs.md
new file mode 100644
index 0000000..2c313db
--- /dev/null
+++ b/.claude/skills/bmad-create-story/discover-inputs.md
@@ -0,0 +1,88 @@
+# Discover Inputs Protocol
+
+**Objective:** Intelligently load project files (whole or sharded) based on the workflow's Input Files configuration.
+
+**Prerequisite:** Only execute this protocol if the workflow defines an Input Files section. If no input file patterns are configured, skip this entirely.
+
+---
+
+## Step 1: Parse Input File Patterns
+
+- Read the Input Files table from the workflow configuration.
+- For each input group (prd, architecture, epics, ux, etc.), note the **load strategy** if specified.
+
+## Step 2: Load Files Using Smart Strategies
+
+For each pattern in the Input Files table, work through the following substeps in order:
+
+### 2a: Try Sharded Documents First
+
+If a sharded pattern exists for this input, determine the load strategy (defaults to **FULL_LOAD** if not specified), then apply the matching strategy:
+
+#### FULL_LOAD Strategy
+
+Load ALL files in the sharded directory. Use this for PRD, Architecture, UX, brownfield docs, or whenever the full picture is needed.
+
+1. Use the glob pattern to find ALL `.md` files (e.g., `{planning_artifacts}/*architecture*/*.md`).
+2. Load EVERY matching file completely.
+3. Concatenate content in logical order: `index.md` first if it exists, then alphabetical.
+4. Store the combined result in a variable named `{pattern_name_content}` (e.g., `{architecture_content}`).
+
+#### SELECTIVE_LOAD Strategy
+
+Load a specific shard using a template variable. Example: used for epics with `{{epic_num}}`.
+
+1. Check for template variables in the sharded pattern (e.g., `{{epic_num}}`).
+2. If the variable is undefined, ask the user for the value OR infer it from context.
+3. Resolve the template to a specific file path.
+4. Load that specific file.
+5. Store in variable: `{pattern_name_content}`.
+
+#### INDEX_GUIDED Strategy
+
+Load index.md, analyze the structure and description of each doc in the index, then intelligently load relevant docs.
+
+**DO NOT BE LAZY** -- use best judgment to load documents that might have relevant information, even if there is only a 5% chance of relevance.
+
+1. Load `index.md` from the sharded directory.
+2. Parse the table of contents, links, and section headers.
+3. Analyze the workflow's purpose and objective.
+4. Identify which linked/referenced documents are likely relevant.
+   - *Example:* If the workflow is about authentication and the index shows "Auth Overview", "Payment Setup", "Deployment" -- load the auth docs, consider deployment docs, skip payment.
+5. Load all identified relevant documents.
+6. Store combined content in variable: `{pattern_name_content}`.
+
+**When in doubt, LOAD IT** -- context is valuable, and being thorough is better than missing critical info.
+
+---
+
+After applying the matching strategy, mark the pattern as **RESOLVED** and move to the next pattern.
+
+### 2b: Try Whole Document if No Sharded Found
+
+If no sharded matches were found OR no sharded pattern exists for this input:
+
+1. Attempt a glob match on the "whole" pattern (e.g., `{planning_artifacts}/*prd*.md`).
+2. If matches are found, load ALL matching files completely (no offset/limit).
+3. Store content in variable: `{pattern_name_content}` (e.g., `{prd_content}`).
+4. Mark pattern as **RESOLVED** and move to the next pattern.
+
+### 2c: Handle Not Found
+
+If no matches were found for either sharded or whole patterns:
+
+1. Set `{pattern_name_content}` to empty string.
+2. Note in session: "No {pattern_name} files found" -- this is not an error, just unavailable. Offer the user a chance to provide the file.
+
+## Step 3: Report Discovery Results
+
+List all loaded content variables with file counts. Example:
+
+```
+OK Loaded {prd_content} from 5 sharded files: prd/index.md, prd/requirements.md, ...
+OK Loaded {architecture_content} from 1 file: Architecture.md
+OK Loaded {epics_content} from selective load: epics/epic-3.md
+-- No ux_design files found
+```
+
+This gives the workflow transparency into what context is available.
diff --git a/.claude/skills/bmad-create-story/template.md b/.claude/skills/bmad-create-story/template.md
new file mode 100644
index 0000000..c4e129f
--- /dev/null
+++ b/.claude/skills/bmad-create-story/template.md
@@ -0,0 +1,49 @@
+# Story {{epic_num}}.{{story_num}}: {{story_title}}
+
+Status: ready-for-dev
+
+<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
+
+## Story
+
+As a {{role}},
+I want {{action}},
+so that {{benefit}}.
+
+## Acceptance Criteria
+
+1. [Add acceptance criteria from epics/PRD]
+
+## Tasks / Subtasks
+
+- [ ] Task 1 (AC: #)
+  - [ ] Subtask 1.1
+- [ ] Task 2 (AC: #)
+  - [ ] Subtask 2.1
+
+## Dev Notes
+
+- Relevant architecture patterns and constraints
+- Source tree components to touch
+- Testing standards summary
+
+### Project Structure Notes
+
+- Alignment with unified project structure (paths, modules, naming)
+- Detected conflicts or variances (with rationale)
+
+### References
+
+- Cite all technical details with source paths and sections, e.g. [Source: docs/<file>.md#Section]
+
+## Dev Agent Record
+
+### Agent Model Used
+
+{{agent_model_name_version}}
+
+### Debug Log References
+
+### Completion Notes List
+
+### File List
diff --git a/.claude/skills/bmad-customize/SKILL.md b/.claude/skills/bmad-customize/SKILL.md
new file mode 100644
index 0000000..8f7f50e
--- /dev/null
+++ b/.claude/skills/bmad-customize/SKILL.md
@@ -0,0 +1,111 @@
+---
+name: bmad-customize
+description: Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'.
+---
+
+# BMad Customize
+
+Translate the user's intent into a correctly-placed TOML override file under `{project-root}/_bmad/custom/` for a customizable agent or workflow skill. Discover, route, author, write, verify.
+
+Scope v1: per-skill `[agent]` overrides (`bmad-agent-<role>.toml` / `.user.toml`) and per-skill `[workflow]` overrides (`bmad-<workflow>.toml` / `.user.toml`). Central config (`{project-root}/_bmad/custom/config.toml`) is out of scope — point users at the [How to Customize BMad guide](https://docs.bmad-method.org/how-to/customize-bmad/).
+
+When the target's `customize.toml` doesn't expose what the user wants, say so plainly. Don't invent fields.
+
+## Preflight
+
+- No `{project-root}/_bmad/` → BMad isn't installed. Say so, stop.
+- `{project-root}/_bmad/scripts/resolve_customization.py` missing → continue, but Step 6 verify falls back to manual merge.
+- Both present → proceed.
+
+## Activation
+
+Load `_bmad/config.toml` and `_bmad/config.user.toml` from `{project-root}` for `user_name` (default `BMad`) and `communication_language` (default `English`). Greet. If the user's invocation already names a target skill AND a specific change, jump to Step 3.
+
+## Step 1: Classify intent
+
+- **Directed** — specific skill + specific change → Step 3.
+- **Exploratory** — "what can I customize?" → Step 2.
+- **Audit/iterate** — wants to review or change something already customized → Step 2, lead with skills that have existing overrides; read the existing override in Step 3 before composing.
+- **Cross-cutting** — could live on multiple surfaces → Step 3, choose agent vs workflow explicitly with the user.
+
+## Step 2: Discovery
+
+```
+uv run {skill-root}/scripts/list_customizable_skills.py --project-root {project-root}
+```
+
+Use `--extra-root <path>` (repeatable) if the user has skills installed in additional locations.
+
+Group the returned `agents` and `workflows` for the user; for each show name, description, whether `has_team_override` or `has_user_override` is true. Surface any `errors[]`. For audit/iterate intents, lead with already-overridden entries.
+
+Empty list: show `scanned_roots`, ask whether skills live elsewhere (offer `--extra-root`); otherwise stop.
+
+## Step 3: Determine the right surface
+
+Read the target's `customize.toml`. Top-level `[agent]` or `[workflow]` block defines the surface.
+
+If a team or user override already exists, read it first and summarize what's already overridden before composing.
+
+**Cross-cutting intent — walk both surfaces with the user:**
+- Every workflow a given agent runs → agent surface (e.g. `bmad-agent-pm.toml` with `persistent_facts`, `principles`).
+- One workflow only → workflow surface (e.g. `bmad-prd.toml` with `activation_steps_prepend`).
+- Several specific workflows → multiple workflow overrides in sequence, not an agent override.
+
+**Single-surface heuristic:**
+- Workflow-level: template swap, output path, step-specific behavior, or a named scalar already exposed (`*_template`, `on_complete`). Surgical, reliable.
+- Agent-level: persona, communication style, org-wide facts, menu changes, behavior that should apply to every workflow the agent dispatches.
+
+When ambiguous, present both with tradeoff, recommend one, let the user decide.
+
+Intent outside the exposed surface (step logic, ordering, anything not in `customize.toml`): say so; offer `activation_steps_prepend`/`append` or `persistent_facts` as approximations, or recommend `bmad-builder` to create a custom skill.
+
+## Step 4: Compose the override
+
+Translate plain-English into TOML against the target's `customize.toml` fields. If an existing override was read, frame the change as additive.
+
+Merge semantics:
+- **Scalars** (`icon`, `role`, `*_template`, `on_complete`) — override wins.
+- **Append arrays** (`persistent_facts`, `activation_steps_prepend`/`append`, `principles`) — team/user entries append in order.
+- **Keyed arrays of tables** (menu items with `code` or `id`) — matching keys replace, new keys append.
+
+Overrides are sparse: only the fields being changed. Never copy the whole `customize.toml`.
+
+**Template swap** (`*_template` scalar): offer to copy the default template to `{project-root}/_bmad/custom/{skill-name}-{purpose}-template.md`, point the override at the new path, offer to help edit it.
+
+## Step 5: Team or user placement
+
+Under `{project-root}/_bmad/custom/`:
+- `{skill-name}.toml` — team, committed. Policies, org conventions, compliance.
+- `{skill-name}.user.toml` — user, gitignored. Personal tone, private facts, shortcuts.
+
+Default by character (policy → team, personal → user), confirm before writing.
+
+## Step 6: Show, confirm, write, verify
+
+1. Show the full TOML. If the file exists, show a diff. Never silently overwrite.
+2. Wait for explicit yes.
+3. Write. Create `{project-root}/_bmad/custom/` if needed.
+4. Verify:
+   ```
+   uv run {project-root}/_bmad/scripts/resolve_customization.py --skill <install-path> --key <agent-or-workflow>
+   ```
+   Show the merged output, point out the changed fields.
+
+   **Resolver missing or fails:** read whichever layers exist — `<install-path>/customize.toml` (base), `{project-root}/_bmad/custom/{skill-name}.toml` (team), `{project-root}/_bmad/custom/{skill-name}.user.toml` (user) — apply base → team → user with the same merge rules (scalars override, tables deep-merge, `code`/`id`-keyed arrays merge by key, all other arrays append), describe how the changed fields resolve.
+
+   **Verify shows override didn't land** (field unchanged, merge conflict, file not picked up): re-enter Step 4 with the verify output as context. Usually wrong field name, wrong merge mode (scalar vs array), or wrong scope.
+5. Summarize what changed, where the file lives, how to iterate. Remind the user to commit team overrides.
+
+## Complete when
+
+- Override file written (or user explicitly aborted).
+- User has seen resolver output (or manual fallback merge summary).
+- User has acknowledged the summary.
+
+Otherwise the skill isn't done — finish or tell the user they're exiting incomplete.
+
+## When this skill can't help
+
+- **Central config** (`{project-root}/_bmad/custom/config.toml`) — see the [How to Customize BMad guide](https://docs.bmad-method.org/how-to/customize-bmad/).
+- **Step logic, ordering, behavior not in `customize.toml`** — open a feature request, or use `bmad-builder` to create a custom skill. Offer to help with either.
+- **Skills without a `customize.toml`** — not customizable.
diff --git a/.claude/skills/bmad-customize/scripts/list_customizable_skills.py b/.claude/skills/bmad-customize/scripts/list_customizable_skills.py
new file mode 100644
index 0000000..86fd82a
--- /dev/null
+++ b/.claude/skills/bmad-customize/scripts/list_customizable_skills.py
@@ -0,0 +1,231 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Enumerate customizable BMad skills installed alongside this one.
+
+Scans a skills directory (by default: the directory this script's own skill
+lives in, derived from __file__), finds every sibling directory containing a
+`customize.toml`, classifies each as agent and/or workflow based on its
+top-level blocks, reads the skill's SKILL.md frontmatter description for a
+one-liner, and checks whether override files already exist in
+`{project-root}/_bmad/custom/`.
+
+Skills in BMad are loaded either from a project-local location (e.g. the
+project's `.claude/skills/` or `.cursor/skills/`) or from a user-global
+location (e.g. `~/.claude/skills/`). We do not hardcode those paths — the
+running skill's own location is the source of truth for sibling discovery.
+`--extra-root` is available for the rare case where skills live in multiple
+locations on the same machine.
+
+Output: JSON to stdout. Non-empty `errors[]` in the payload is non-fatal
+by contract — the scanner surfaces malformed TOML, missing roots, and
+skills with no customization block as data for the caller to display,
+and still exits 0. Exit 2 is reserved for invocation errors (e.g.
+missing or unreadable `--project-root`) where no useful payload can be
+produced.
+"""
+
+from __future__ import annotations
+
+import argparse
+import json
+import re
+import sys
+import tomllib
+from pathlib import Path
+
+# Top-level TOML blocks that indicate a customization surface.
+SURFACE_KEYS = ("agent", "workflow")
+
+FRONTMATTER_RE = re.compile(r"^---\s*\n(.*?)\n---\s*\n", re.DOTALL)
+
+
+def default_skills_root() -> Path:
+    """Derive the skills root from this script's location.
+
+    Layout assumption: {skills_root}/bmad-customize/scripts/list_customizable_skills.py.
+    So the skills root is three parents up from this file.
+    """
+    return Path(__file__).resolve().parent.parent.parent
+
+
+def read_frontmatter_description(skill_md: Path) -> str:
+    """Extract the `description:` value from a SKILL.md YAML frontmatter block.
+
+    Returns an empty string if the file is missing, unreadable, or has no
+    description field. Intentionally permissive — this is metadata for a
+    human-facing list, not a validation target.
+    """
+    if not skill_md.is_file():
+        return ""
+    try:
+        text = skill_md.read_text(encoding="utf-8")
+    except (OSError, UnicodeDecodeError):
+        return ""
+    m = FRONTMATTER_RE.match(text)
+    if not m:
+        return ""
+    for line in m.group(1).splitlines():
+        stripped = line.strip()
+        if stripped.startswith("description:"):
+            value = stripped[len("description:") :].strip()
+            # Strip surrounding quotes if present.
+            if (value.startswith("'") and value.endswith("'")) or (
+                value.startswith('"') and value.endswith('"')
+            ):
+                value = value[1:-1]
+            return value
+    return ""
+
+
+def load_customize(toml_path: Path) -> dict | None:
+    """Return the parsed TOML, or None if unreadable."""
+    try:
+        with toml_path.open("rb") as f:
+            return tomllib.load(f)
+    except (OSError, tomllib.TOMLDecodeError):
+        return None
+
+
+def scan_skills(
+    skills_roots: list[Path],
+    project_root: Path,
+) -> dict:
+    """Scan each skills root for directories that contain a customize.toml."""
+    agents: list[dict] = []
+    workflows: list[dict] = []
+    errors: list[str] = []
+    scanned_roots: list[str] = []
+    seen_names: set[str] = set()
+    custom_dir = project_root / "_bmad" / "custom"
+
+    for root in skills_roots:
+        if not root.is_dir():
+            errors.append(f"skills root does not exist: {root}")
+            continue
+        scanned_roots.append(str(root))
+
+        for skill_dir in sorted(p for p in root.iterdir() if p.is_dir()):
+            customize_toml = skill_dir / "customize.toml"
+            if not customize_toml.is_file():
+                continue
+
+            data = load_customize(customize_toml)
+            if data is None:
+                errors.append(f"failed to parse {customize_toml}")
+                continue
+
+            skill_name = skill_dir.name
+            # If a skill with this name was already found in an earlier
+            # root, skip it — roots are scanned in the order provided, so
+            # the first occurrence wins.
+            if skill_name in seen_names:
+                continue
+            seen_names.add(skill_name)
+
+            description = read_frontmatter_description(skill_dir / "SKILL.md")
+            team_override = custom_dir / f"{skill_name}.toml"
+            user_override = custom_dir / f"{skill_name}.user.toml"
+
+            entry_base = {
+                "name": skill_name,
+                "install_path": str(skill_dir),
+                "skills_root": str(root),
+                "description": description,
+                "has_team_override": team_override.is_file(),
+                "has_user_override": user_override.is_file(),
+                "team_override_path": str(team_override),
+                "user_override_path": str(user_override),
+            }
+
+            # A skill may expose an agent surface, a workflow surface, or
+            # both. Emit one entry per surface so the caller can group cleanly.
+            surfaces_found = [k for k in SURFACE_KEYS if k in data]
+            if not surfaces_found:
+                errors.append(
+                    f"no [agent] or [workflow] block in {customize_toml}"
+                )
+                continue
+            for surface in surfaces_found:
+                entry = dict(entry_base)
+                entry["surface"] = surface
+                if surface == "agent":
+                    agents.append(entry)
+                else:
+                    workflows.append(entry)
+
+    return {
+        "project_root": str(project_root),
+        "scanned_roots": scanned_roots,
+        "custom_dir": str(custom_dir),
+        "agents": agents,
+        "workflows": workflows,
+        "errors": errors,
+    }
+
+
+def parse_args(argv: list[str]) -> argparse.Namespace:
+    parser = argparse.ArgumentParser(
+        description=(
+            "List customizable BMad skills installed alongside this one, "
+            "grouped by surface (agent vs workflow), with override status "
+            "looked up against {project-root}/_bmad/custom/."
+        )
+    )
+    parser.add_argument(
+        "--project-root",
+        required=True,
+        help="Absolute path to the project root (the folder containing _bmad/).",
+    )
+    parser.add_argument(
+        "--skills-root",
+        default=None,
+        help=(
+            "Override the primary skills directory to scan. Defaults to the "
+            "directory this script's own skill lives in."
+        ),
+    )
+    parser.add_argument(
+        "--extra-root",
+        action="append",
+        default=[],
+        metavar="PATH",
+        help=(
+            "Additional skills directory to include (repeatable). Useful "
+            "when skills live in multiple locations on the same machine "
+            "(e.g. project-local plus a user-global install)."
+        ),
+    )
+    return parser.parse_args(argv)
+
+
+def main(argv: list[str]) -> int:
+    args = parse_args(argv)
+    project_root = Path(args.project_root).expanduser().resolve()
+    if not project_root.is_dir():
+        print(
+            f"error: project-root does not exist or is not a directory: {project_root}",
+            file=sys.stderr,
+        )
+        return 2
+
+    primary = (
+        Path(args.skills_root).expanduser().resolve()
+        if args.skills_root
+        else default_skills_root()
+    )
+    extras = [Path(p).expanduser().resolve() for p in args.extra_root]
+    # Deduplicate in order of appearance.
+    roots: list[Path] = []
+    for root in [primary, *extras]:
+        if root not in roots:
+            roots.append(root)
+
+    result = scan_skills(roots, project_root)
+    print(json.dumps(result, indent=2, sort_keys=True))
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv[1:]))
diff --git a/.claude/skills/bmad-customize/scripts/tests/test_list_customizable_skills.py b/.claude/skills/bmad-customize/scripts/tests/test_list_customizable_skills.py
new file mode 100644
index 0000000..916b7c3
--- /dev/null
+++ b/.claude/skills/bmad-customize/scripts/tests/test_list_customizable_skills.py
@@ -0,0 +1,249 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Unit tests for list_customizable_skills.py.
+
+Exercises the scanner against a synthesized install tree:
+- an agent-only customize.toml
+- a workflow-only customize.toml
+- a customize.toml that exposes both surfaces
+- a skill directory with no customize.toml (ignored)
+- a pre-existing team override in _bmad/custom/
+- malformed TOML (surfaces as an error without aborting)
+- multiple skills roots (e.g. project-local + user-global mix)
+
+Run: uv run scripts/tests/test_list_customizable_skills.py
+"""
+
+from __future__ import annotations
+
+import importlib.util
+import json
+import subprocess
+import sys
+import tempfile
+import unittest
+from pathlib import Path
+
+SCRIPT = Path(__file__).resolve().parent.parent / "list_customizable_skills.py"
+
+
+def _load_module():
+    spec = importlib.util.spec_from_file_location("list_customizable_skills", SCRIPT)
+    module = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(module)  # type: ignore[union-attr]
+    return module
+
+
+MODULE = _load_module()
+
+
+def _make_skill(parent: Path, name: str, body: str, skill_md: str | None = None) -> Path:
+    skill_dir = parent / name
+    skill_dir.mkdir(parents=True, exist_ok=True)
+    (skill_dir / "customize.toml").write_text(body, encoding="utf-8")
+    if skill_md is not None:
+        (skill_dir / "SKILL.md").write_text(skill_md, encoding="utf-8")
+    return skill_dir
+
+
+class ScannerTest(unittest.TestCase):
+    def setUp(self):
+        self.tmp = tempfile.TemporaryDirectory()
+        self.root = Path(self.tmp.name)
+        self.skills = self.root / "skills"
+        self.skills.mkdir(parents=True)
+        self.custom = self.root / "_bmad" / "custom"
+        self.custom.mkdir(parents=True)
+
+    def tearDown(self):
+        self.tmp.cleanup()
+
+    def test_agent_only_skill_detected(self):
+        _make_skill(
+            self.skills,
+            "bmad-agent-pm",
+            "[agent]\nicon = \"🧠\"\n",
+            "---\nname: bmad-agent-pm\ndescription: Product manager.\n---\n",
+        )
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(len(result["agents"]), 1)
+        self.assertEqual(len(result["workflows"]), 0)
+        entry = result["agents"][0]
+        self.assertEqual(entry["name"], "bmad-agent-pm")
+        self.assertEqual(entry["surface"], "agent")
+        self.assertEqual(entry["description"], "Product manager.")
+        self.assertFalse(entry["has_team_override"])
+        self.assertFalse(entry["has_user_override"])
+
+    def test_workflow_only_skill_detected(self):
+        _make_skill(
+            self.skills,
+            "bmad-create-prd",
+            "[workflow]\npersistent_facts = []\n",
+            "---\nname: bmad-create-prd\ndescription: 'Create a PRD.'\n---\n",
+        )
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(len(result["agents"]), 0)
+        self.assertEqual(len(result["workflows"]), 1)
+        entry = result["workflows"][0]
+        self.assertEqual(entry["description"], "Create a PRD.")
+
+    def test_dual_surface_skill_emits_two_entries(self):
+        _make_skill(
+            self.skills,
+            "bmad-dual",
+            "[agent]\nicon = \"x\"\n\n[workflow]\npersistent_facts = []\n",
+            "---\nname: bmad-dual\ndescription: Dual.\n---\n",
+        )
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(len(result["agents"]), 1)
+        self.assertEqual(len(result["workflows"]), 1)
+        self.assertEqual(result["agents"][0]["name"], "bmad-dual")
+        self.assertEqual(result["workflows"][0]["name"], "bmad-dual")
+
+    def test_skill_without_customize_toml_ignored(self):
+        (self.skills / "bmad-plain").mkdir()
+        (self.skills / "bmad-plain" / "SKILL.md").write_text("# plain\n")
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(len(result["agents"]) + len(result["workflows"]), 0)
+        self.assertEqual(result["errors"], [])
+
+    def test_existing_team_override_flagged(self):
+        _make_skill(
+            self.skills,
+            "bmad-agent-pm",
+            "[agent]\nicon = \"x\"\n",
+            "---\nname: bmad-agent-pm\ndescription: PM.\n---\n",
+        )
+        (self.custom / "bmad-agent-pm.toml").write_text("[agent]\n")
+        result = MODULE.scan_skills([self.skills], self.root)
+        entry = result["agents"][0]
+        self.assertTrue(entry["has_team_override"])
+        self.assertFalse(entry["has_user_override"])
+
+    def test_missing_surface_block_reports_error(self):
+        _make_skill(self.skills, "bmad-broken", "[not_a_surface]\nfoo = 1\n")
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(len(result["agents"]) + len(result["workflows"]), 0)
+        self.assertEqual(len(result["errors"]), 1)
+        self.assertIn("no [agent] or [workflow] block", result["errors"][0])
+
+    def test_malformed_toml_reports_error_without_aborting(self):
+        skill_dir = self.skills / "bmad-bad"
+        skill_dir.mkdir()
+        (skill_dir / "customize.toml").write_text("this is not [valid toml\n")
+        # Plus a good sibling to confirm scanning continues.
+        _make_skill(
+            self.skills,
+            "bmad-good",
+            "[agent]\nicon = \"x\"\n",
+            "---\nname: bmad-good\ndescription: Good.\n---\n",
+        )
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(len(result["agents"]), 1)
+        self.assertEqual(result["agents"][0]["name"], "bmad-good")
+        self.assertTrue(any("failed to parse" in e for e in result["errors"]))
+
+    def test_description_with_double_quotes_stripped(self):
+        _make_skill(
+            self.skills,
+            "bmad-q",
+            "[agent]\nicon = \"x\"\n",
+            '---\nname: bmad-q\ndescription: "Double-quoted desc."\n---\n',
+        )
+        result = MODULE.scan_skills([self.skills], self.root)
+        self.assertEqual(result["agents"][0]["description"], "Double-quoted desc.")
+
+    def test_multiple_skills_roots_are_merged(self):
+        extra_root = self.root / "extra-skills"
+        extra_root.mkdir()
+        _make_skill(
+            self.skills,
+            "bmad-agent-pm",
+            "[agent]\nicon = \"x\"\n",
+            "---\nname: bmad-agent-pm\ndescription: PM.\n---\n",
+        )
+        _make_skill(
+            extra_root,
+            "bmad-agent-dev",
+            "[agent]\nicon = \"y\"\n",
+            "---\nname: bmad-agent-dev\ndescription: Dev.\n---\n",
+        )
+        result = MODULE.scan_skills([self.skills, extra_root], self.root)
+        names = {a["name"] for a in result["agents"]}
+        self.assertEqual(names, {"bmad-agent-pm", "bmad-agent-dev"})
+        self.assertEqual(len(result["scanned_roots"]), 2)
+
+    def test_duplicate_skill_name_across_roots_first_wins(self):
+        extra_root = self.root / "extra-skills"
+        extra_root.mkdir()
+        _make_skill(
+            self.skills,
+            "bmad-agent-pm",
+            "[agent]\nicon = \"primary\"\n",
+            "---\nname: bmad-agent-pm\ndescription: Primary.\n---\n",
+        )
+        _make_skill(
+            extra_root,
+            "bmad-agent-pm",
+            "[agent]\nicon = \"duplicate\"\n",
+            "---\nname: bmad-agent-pm\ndescription: Duplicate.\n---\n",
+        )
+        result = MODULE.scan_skills([self.skills, extra_root], self.root)
+        self.assertEqual(len(result["agents"]), 1)
+        self.assertEqual(result["agents"][0]["description"], "Primary.")
+        self.assertEqual(result["agents"][0]["skills_root"], str(self.skills))
+
+    def test_missing_skills_root_reports_error(self):
+        result = MODULE.scan_skills(
+            [self.root / "does-not-exist", self.skills],
+            self.root,
+        )
+        self.assertTrue(any("skills root does not exist" in e for e in result["errors"]))
+
+    def test_cli_emits_valid_json_and_exits_zero(self):
+        _make_skill(
+            self.skills,
+            "bmad-agent-pm",
+            "[agent]\nicon = \"x\"\n",
+            "---\nname: bmad-agent-pm\ndescription: PM.\n---\n",
+        )
+        proc = subprocess.run(
+            [
+                sys.executable,
+                str(SCRIPT),
+                "--project-root",
+                str(self.root),
+                "--skills-root",
+                str(self.skills),
+            ],
+            capture_output=True,
+            text=True,
+            check=False,
+        )
+        self.assertEqual(proc.returncode, 0, proc.stderr)
+        payload = json.loads(proc.stdout)
+        self.assertEqual(len(payload["agents"]), 1)
+
+    def test_cli_exits_two_on_missing_project_root(self):
+        proc = subprocess.run(
+            [
+                sys.executable,
+                str(SCRIPT),
+                "--project-root",
+                str(self.root / "does-not-exist"),
+                "--skills-root",
+                str(self.skills),
+            ],
+            capture_output=True,
+            text=True,
+            check=False,
+        )
+        self.assertEqual(proc.returncode, 2)
+        self.assertIn("does not exist", proc.stderr)
+
+
+if __name__ == "__main__":
+    unittest.main()
diff --git a/.claude/skills/bmad-deep-recon/SKILL.md b/.claude/skills/bmad-deep-recon/SKILL.md
new file mode 100644
index 0000000..8542dc0
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/SKILL.md
@@ -0,0 +1,82 @@
+---
+name: bmad-deep-recon
+description: 'Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here through web fan-out. Shipped type packs: market, domain, technical, competitive, user-voice, academic-lit — plus a select shape for choose-between decisions and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between".'
+---
+
+# BMad Deep Recon
+
+## Overview
+
+You are **Deep Recon** — a research director, not a search engine. Your value is framing research worth running and turning whatever comes back into a decision-grade artifact this project consumes without reprocessing. Every engagement serves a **decision** — enter a market, pick a stack, scope a product, commit to a domain — and is shaped by it from the first question to the final artifact.
+
+Three services, freely combined — each detailed in its reference: **Draft** a deep-research prompt the user runs in their own tool, **Process** a finished report into the succinct cited summary downstream skills read, or **Run** the research here through parallel web fan-out. Draft → run externally → Process is the natural loop; Run is fully capable on its own.
+
+**Epistemics — two standing rules, inherited verbatim by every subagent you spawn:**
+
+1. **Never conclude from training data alone.** What you already know proposes hypotheses, queries, and structure; conclusions require evidence retrieved or imported *this run*. A claim you cannot evidence is stated as an unverified belief or not at all.
+2. **The research firewall.** Project context — briefs, PRDs, code, memory, `{workflow.persistent_facts}` — shapes *what to ask*, never *what is true*. It is inadmissible as evidence: every claim in a research artifact traces to a digest or import file with a source. Research subagents receive only their brief — no project files, no ambient context — unless the plan explicitly grants a named document.
+
+## How you work
+
+- **Nothing exists until it is a file.** Every digest, import extraction, and report section is written to the run folder the moment it lands — the conversation is a control channel, never the store. A run that dies mid-flight resumes from disk with nothing lost.
+- **Extract, don't ingest.** Raw reports and search results never enter the parent context whole; subagents return relevance-filtered digests, and the parent reads digest files JIT.
+- **A claim is a sentence with a source.** Publisher, publication date, access date. No naked numbers.
+- **Report what is real.** Thin public data is reported as thin, absence of evidence is a finding, and freshness is part of truth — each pack sets windows per claim class; a market size from three years ago is history, not fact.
+- **Fast by default.** Rigor is bought consciously through the knobs, never accreted through extra passes. One gate, light checkpoints, no ceremony.
+- **The memlog is the process memory.** Every decision, source batch, load-bearing claim, plan change, and assumption is one append-only line, always through the script: `uv run {project-root}/_bmad/scripts/memlog.py` with `--type <decision|source|claim|assumption|question|event>`.
+- Web access is required for Run. If unavailable, say so and offer Draft/Process — never fabricate research.
+
+## Resolution rules
+
+- Bare paths and `{skill-root}` (e.g. `references/run.md`) resolve from this skill's installed directory.
+- `{project-root}` → the project working directory; `{skill-name}` → the skill directory's basename.
+- `{workflow.<name>}` → a merged `customize.toml` field; `{doc_workspace}` → the bound run folder.
+- Forward slashes only. Config variables already contain `{project-root}` in their resolved values — never double-prefix.
+
+## On Activation
+
+**Forwarded activation:** if a caller invoked you with a stated intent, research type, or pre-resolved customization fields (the legacy research shims and Mary's menu do), honor them verbatim — skip your own inference for those values and resolve only the rest.
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow` (on failure read `{skill-root}/customize.toml`, use defaults). Run `{workflow.activation_steps_prepend}`, then `{workflow.activation_steps_append}`.
+2. Resolve config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}`. From the merged JSON resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{output_folder}` (under `core`), `{planning_artifacts}` (under `modules.bmm`; absent on core-only installs → `{output_folder}`), and `{date}`; missing keys take neutral defaults, never block.
+3. Headless (no interactive user) → see `## Headless Mode`. Otherwise greet `{user_name}` in `{communication_language}` — and stay in it every turn.
+4. Detect the intent: **draft**, **process** (the user has or names a report), **run**, or lifecycle **refresh** / **deepen** on an existing run folder. When the ask is bare research with no verb ("research X for me"), open the floor first — invite the decision they're facing and anything they already have (briefs, links, a prior report) in one turn, then ask only what's missing — and put the choice up front, once: **Run** it here now, or **Draft** a prompt for a deep-research tool they subscribe to — often cheaper and a strong gatherer, with Process turning its output into the same artifact. State the trade honestly (tokens and minutes here vs. one manual round-trip there); their call, remembered for the session.
+5. If a run folder for this topic already exists under `{workflow.research_output_path}`, offer to resume or extend it (a drafted brief awaiting its report, a report awaiting refresh) rather than start a duplicate.
+
+## Research types and decision shapes
+
+The type set is whatever `{workflow.research_types}` resolves to — shipped: `market`, `domain`, `technical`, `competitive`, `user-voice`, `academic-lit` — each pointing at a pack file. You already know how to research; the pack is where this harness is opinionated — prioritized dimensions, non-obvious source craft, freshness bars and two-source classes per claim class, downstream bindings. Apply it in every mode; don't re-derive it. Overrides replace matching codes and append new ones; never claim a fixed type list — read the resolved set.
+
+Infer the type from the user's ask and each entry's `when` clause; confirm only when genuinely ambiguous. An explicit type (argument, shim, menu) wins without discussion.
+
+Orthogonal to type is the **decision shape**: **explore** (the default — understand, assess, validate) or **select** (choose between candidates). When the shape is select, load `references/selection.md` and layer its method over the type's pack — it shapes drafted prompts and processed summaries as much as native runs.
+
+## Intents
+
+Route on the detected intent and load only what it names. Every intent shares the run-folder workspace shape — `brief.md`, `imports/`, `digests/`, `research.md`, `.memlog.md` — and ends per `references/finalize.md`.
+
+| Intent | What it does | Load |
+| --- | --- | --- |
+| Draft | Compose a deep-research prompt for the user's own tool, carrying the pack's craft | `references/draft.md` |
+| Process | File a finished report, extract its claims, distill the downstream summary | `references/process.md` |
+| Run | Native research: resolve effort, hold the plan gate — the one hard stop — then run the loop | `references/run.md`, then `references/verification.md` + `references/synthesis.md` |
+| Refresh / Deepen | Update or extend an existing run folder | `references/lifecycle.md` |
+
+## Headless Mode
+
+When invoked headless, do not ask. Bare research defaults to **run**; a named report means **process**; a requested prompt means **draft** (the brief file is the deliverable). Plan-and-proceed: infer type, build from the pack, keep configured knobs plus anything in the invocation (red team and workflow orchestration only when set `"on"`), skip checkpoints, log every judgment call as an `assumption`. Halt `blocked` only when topic or target folder cannot be inferred. End with JSON:
+
+```json
+{
+  "status": "complete",
+  "intent": "run",
+  "type": "market",
+  "report": "{doc_workspace}/research.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "claims": {"verified": 12, "unverified": 3, "overturned": 0},
+  "open_questions": [],
+  "external_handoffs": []
+}
+```
+
+Omit keys for artifacts not produced; the `claims` counts come from `uv run scripts/recon_kit.py tally {doc_workspace}/.memlog.md`, never hand-counted. Draft adds `"brief"`; process adds `"imports"`; refresh replaces `claims` scope with the refresh set plus a `deltas` array. With `output_format = "auto"`, headless runs produce no briefing; add `"briefing"` when rendered.
diff --git a/.claude/skills/bmad-deep-recon/assets/research.template.md b/.claude/skills/bmad-deep-recon/assets/research.template.md
new file mode 100644
index 0000000..14fe968
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/assets/research.template.md
@@ -0,0 +1,18 @@
+---
+title: '{research_type} research: {research_topic}'
+type: '{research_type}'
+topic: '{research_topic}'
+decision: '{decision}'
+source: '{source}'
+status: draft
+preset: '{preset}'
+validation: '{validation}'
+created: '{date}'
+updated: '{date}'
+---
+
+# {research_type} research: {research_topic}
+
+**Decision this research serves:** {decision}
+
+_Sections are appended per the approved research plan; the executive summary is written last and placed here, first._
diff --git a/.claude/skills/bmad-deep-recon/customize.toml b/.claude/skills/bmad-deep-recon/customize.toml
new file mode 100644
index 0000000..434c47d
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/customize.toml
@@ -0,0 +1,212 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-deep-recon.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-deep-recon.toml         (team)
+#   {project-root}/_bmad/custom/bmad-deep-recon.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins
+#   arrays (persistent_facts, activation_steps_*, *_sources, doc_standards,
+#   external_*): append
+#   arrays of tables keyed by `code`: matching key replaces, new keys append
+
+# Steps executed on activation: prepend runs before the skill's own
+# activation flow, append runs after it. Each entry is a literal instruction.
+activation_steps_prepend = []
+activation_steps_append = []
+
+# Standing context for framing the research — decision context only, never
+# evidence: the research firewall keeps project material out of findings.
+# Entries prefixed `file:` are paths or globs whose contents load as facts;
+# all others are literal facts. Empty by default so nothing local leaks into
+# research framing unasked.
+persistent_facts = []
+
+# Where research runs live and how each run folder is named. Draft, Process,
+# and Run all use the same folder shape: brief.md (drafted prompts),
+# imports/ (originals, full fidelity), digests/ (extracted claims),
+# research.md (the canonical summary/report), .memlog.md.
+research_output_path = "{planning_artifacts}/research"
+run_folder_pattern = "{research_type}-{topic_slug}-{date}"
+
+# Seed document for a new run.
+research_template = "assets/research.template.md"
+
+# --- Effort (Run mode) ------------------------------------------------------
+# A preset bundles the three effort knobs; any knob set here individually
+# pins that knob over the preset. What the user says in the request beats
+# both.
+#
+#   preset     subagents  sources/round  depth
+#   quick      low (2)    5              1
+#   standard   normal (3) 8              2
+#   deep       high (6)   12             3
+#
+# Grounding: orchestrator-worker research systems document 3-5 parallel
+# workers as the sweet spot (more only for genuinely wide work). Depth and
+# sources are caps, not quotas — dimensions stop early on coverage or
+# novelty exhaustion. Defaults are tuned for a fast run; buy more rigor
+# consciously, per run, in the request.
+
+preset = "standard"
+
+# "" = from preset. Values: none | low | normal | high
+# (0 / 2 / 3 / 6 parallel research assistants, ceiling 10; none also =
+# no-subagent environments, run inline sequentially).
+subagents = ""
+
+# 0 = from preset. Distinct sources actually read per dimension per round.
+# Ceiling 25 — beyond that a single round exceeds what hosted deep-research
+# products spend on an entire run.
+max_sources_per_round = 0
+
+# 0 = from preset. Rounds per dimension: initial pass + lead-following
+# follow-ups. Ceiling 5.
+max_depth = 0
+
+# Verification level, applied as material lands (never an end-of-run pass).
+#   normal  spot-check load-bearing claims only — fast, the default
+#   high    cross-check the pack's two-source classes; red-team major
+#           conclusions
+#   max     cross-check every ledger claim + the red-team pass at full
+#           breadth + primary-source-priority ranking
+validation = "normal"
+
+# Red-team stance pass — fresh-context skeptics hunting disconfirming
+# evidence for major conclusions: "off" (default), "offer" (proposed at the
+# plan gate), or "on" (always; headless honors only "on"). high/max
+# validation includes it for major conclusions regardless.
+red_team = "off"
+
+# Run the acquisition fan-out through the harness's deterministic
+# orchestration when it offers one (e.g. workflows): "off", "offer"
+# (proposed at the plan gate when available), or "on". Orchestrated runs are
+# faster wall-clock but spend more tokens.
+use_workflows = "offer"
+
+# Ordered model preference for spawned research assistants — first model the
+# harness can provide wins; [] lets the harness/skill choose (lead stays on
+# the strongest model; researchers at most one capable tier down; judgment
+# work never on the smallest tier; mechanical extraction may use a fast
+# tier).
+#
+# Example: subagent_models = ["<your-mid-tier-model-id>", "<your-fast-model-id>"]
+subagent_models = []
+
+# Source policy. Preferred sources are consulted first and weighted as more
+# credible; banned sources are never cited (their claims may still be leads
+# to verify elsewhere). Entries are domains or plain-text descriptions.
+# Draft mode writes both policies into drafted prompts.
+preferred_sources = []
+banned_sources = []
+
+# What is presented and handed off — never what exists: research.md (the
+# canonical machine-readable summary/report) always lives in the workspace.
+#   "auto"  html briefing on interactive runs; md only on headless or
+#           skill-invoked runs (the caller reads the md; render later at will)
+#   "html"  always render the briefing page (references/html-briefing.md)
+#   "md"    never render html
+#   "both"  render and present both
+output_format = "auto"
+
+# Theme for the HTML briefing: empty = the shipped neutral professional
+# theme, a `file:` path to a theme/brand spec, or inline directives
+# (e.g. "Canvas #122543, accent #B66D46, sans-serif, dark-mode aware").
+html_theme = ""
+
+# Default audience shaping for the synthesis — freeform, empty = balanced
+# technical/business register. Examples: "executive one-pager first, detail
+# after", "engineering team, keep vendor marketing out".
+audience = ""
+
+# Registry of extra research surfaces — internal knowledge bases or search
+# tools you subscribe to — consulted alongside web research in Run mode; each
+# entry names the tool and when to use it. Installed search-shaped MCP tools
+# are discovered automatically at the plan gate; an entry here adds routing
+# guidance the discovery can't infer.
+#
+# Examples:
+#   external_sources = [
+#     "Tavily MCP (tavily_search/tavily_extract): preferred web search + clean page extraction",
+#     "Perplexity Sonar MCP (perplexity_ask): cited synthesized answers — chase its citations as the sources",
+#     "xAI X Search MCP: live X/Twitter posts and threads, for user-voice and sentiment dimensions",
+#     "Gartner MCP (corp:gartner_query): analyst data on enterprise software markets",
+#   ]
+external_sources = []
+
+# Polish passes applied to research.md at finalize. Entries are `skill:NAME`
+# directives, `file:` style guides, or plain-text instructions.
+doc_standards = ["skill:bmad-review lenses=structure,prose"]
+
+# Handoffs executed at finalize to route the report beyond local files. Each
+# entry names the tool and what to do; unavailable tools are skipped and
+# flagged.
+#
+# Examples:
+#   "NotebookLM (notebooklm-mcp): create a notebook from research.md plus the top sources, generate an audio overview, return the notebook URL"
+#   "Confluence (corp:confluence_upload): publish research.md to the RESEARCH space, return the page URL"
+external_handoffs = []
+
+# Executed after finalize. A string scalar is one instruction; an array is a
+# sequence. Empty = the run ends with the finalize summary.
+on_complete = ""
+
+# ---------------------------------------------------------------------------
+# Research types — subject lenses. Each type is a pack: a policy and craft
+# card (prioritized dimensions, non-obvious source craft, freshness bars,
+# two-source classes, downstream bindings) used by all three modes — it
+# shapes drafted prompts, native runs, and processed-report gap checks
+# alike. `when` guides type inference from the user's ask; an explicitly
+# requested type always wins. The decision shape (explore vs select) is
+# orthogonal — any type can end in a selection matrix.
+#
+# Keyed by `code`: an override with a matching code replaces the shipped
+# type, a new code appends. Empty `pack` disables a type.
+#
+# Example (add an org-specific type in team/user override TOML):
+#   [[workflow.research_types]]
+#   code = "regulatory"
+#   name = "Regulatory Research"
+#   when = "Compliance posture, licensing, or regulatory exposure for a product or market."
+#   pack = "file:{project-root}/_bmad/custom/packs/regulatory.md"
+# ---------------------------------------------------------------------------
+
+[[workflow.research_types]]
+code = "market"
+name = "Market Research"
+when = "Market opportunity, customers, competition, sizing, or go-to-market for a product or business decision."
+pack = "types/market.md"
+
+[[workflow.research_types]]
+code = "domain"
+name = "Domain Research"
+when = "Understanding an industry, sector, or field: structure, players, rules, vocabulary, dynamics."
+pack = "types/domain.md"
+
+[[workflow.research_types]]
+code = "technical"
+name = "Technical Research"
+when = "A technology area's landscape, patterns, integration approaches, and implementation reality."
+pack = "types/technical.md"
+
+[[workflow.research_types]]
+code = "competitive"
+name = "Competitive Research"
+when = "Teardown of specific named competitors: offers, pricing, positioning, trajectory, their customers' sentiment."
+pack = "types/competitive.md"
+
+[[workflow.research_types]]
+code = "user-voice"
+name = "User-Voice Research"
+when = "What users of a product or category actually experience and want: reviews, communities, jobs-to-be-done."
+pack = "types/user-voice.md"
+
+[[workflow.research_types]]
+code = "academic-lit"
+name = "Academic Literature"
+when = "Published research: literature review, state of the art, grounding an approach in papers."
+pack = "types/academic-lit.md"
diff --git a/.claude/skills/bmad-deep-recon/references/draft.md b/.claude/skills/bmad-deep-recon/references/draft.md
new file mode 100644
index 0000000..68d4c90
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/draft.md
@@ -0,0 +1,8 @@
+# Draft
+
+Build a deep-research prompt the user runs themselves — in conversation, fast, not a project. The pack's craft travels inside the prompt so the outside tool works to this harness's standard.
+
+1. Open the floor before any structured questions: invite the decision they're facing and anything they already have — briefs, links, a prior report, half-formed constraints — in one turn, then ask only what's still missing. Nail the **decision**, topic, and type; load the pack. Ask which tool the prompt is for (it changes phrasing: hosted deep-research agents handle wide scopes and long source lists; social-native tools like Grok earn user-voice and sentiment dimensions; if unknown, write tool-neutral).
+2. Compose the prompt from the pack: the dimensions as explicit research questions pruned to the decision, the freshness bars as recency requirements, the two-source expectation for its critical claim classes, the audience, the source policy — `{workflow.preferred_sources}` named as sources to prefer, `{workflow.banned_sources}` as sources never to cite — and a **non-negotiable citation demand**: every claim with source URL and publication date, contrary evidence reported, gaps admitted rather than padded. Structure the requested output so Process can extract it cleanly (findings per dimension, a source list).
+3. Bind `{doc_workspace}`: expand the folder name deterministically (`uv run scripts/recon_kit.py slug "<topic>" --type <type> --pattern "{workflow.run_folder_pattern}"` — same expansion every mode, so the report comes back to the same folder) under `{workflow.research_output_path}`, init the memlog with the decision context, save the prompt as `{doc_workspace}/brief.md`, and present it paste-ready in chat.
+4. Close the loop: tell the user to run it in their tool and bring the report back — "process it" from here picks up this folder, decision context intact.
diff --git a/.claude/skills/bmad-deep-recon/references/finalize.md b/.claude/skills/bmad-deep-recon/references/finalize.md
new file mode 100644
index 0000000..24a3a3b
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/finalize.md
@@ -0,0 +1,11 @@
+# Finalize
+
+Every mode ends here once `research.md` is assembled.
+
+1. `research.md` is complete per `references/synthesis.md`: decision-first summary, findings, contrary evidence where found, recommendations with downstream bindings, source appendix, staleness map. Frontmatter metadata (`type`, `topic`, `decision`, `source`, `status`, dates) is what lets every downstream consumer trust it without reprocessing.
+2. **Citation check — mechanical, then semantic.** Run `uv run scripts/recon_kit.py citations {doc_workspace}/research.md` — it diffs inline `[n]` markers against the appendix and lists dangling markers and orphaned rows exactly; fix what it reports. Then a fresh-context subagent does only the judgment half: does each cited source actually say what the text claims? It never rewrites findings — a claim whose source doesn't back it gets its confidence downgraded and the mismatch logged as an `event`.
+3. Render per `{workflow.output_format}` (see `references/html-briefing.md`): `auto` renders the briefing page on interactive runs, skips on headless/skill-invoked; `html`/`both` always; `md` never. `research.md` always exists — the briefing is its regenerable face.
+4. Polish: apply each `{workflow.doc_standards}` entry (a `skill:`, `file:`, or plain-text directive) to `research.md`.
+5. Execute each `{workflow.external_handoffs}` entry (NotebookLM, Confluence, …) — invoke the named tool, surface returned URLs; skip and flag unavailable tools.
+6. Tell the user what exists and where — report, briefing, imports, memlog — plus what the staleness map says to re-check and when, and that Refresh/Deepen handle it. Invoke `bmad-help` to suggest the next step.
+7. Run `{workflow.on_complete}` if non-empty — a string is one instruction, an array is a sequence.
diff --git a/.claude/skills/bmad-deep-recon/references/html-briefing.md b/.claude/skills/bmad-deep-recon/references/html-briefing.md
new file mode 100644
index 0000000..8d8c379
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/html-briefing.md
@@ -0,0 +1,16 @@
+# HTML Briefing
+
+Generate `research-briefing.html` in `{doc_workspace}` after `research.md` is final, when `{workflow.output_format}` calls for it: `"auto"` renders on interactive runs and skips on headless/skill-invoked runs (the md is always there to render from later), `"html"`/`"both"` always render, `"md"` never. The page is a full-fidelity presentation of the report, never a second source of truth — same claims, same numbers, same citations; nothing is lost by reading it instead of the markdown.
+
+## Requirements
+
+- **Self-contained single file**: inline CSS and JS, no external requests of any kind (no CDN, no fonts, no remote images). It must render from a `file://` open, offline, forever.
+- **Structure**: a header (topic, type, decision, date, depth, verification level) → the executive summary as the opening card → sticky table of contents → dimension sections → contrary evidence (when present) → recommendations → collapsible source appendix → staleness map.
+- **Confidence is visual**: every claim carries its badge — verified / medium / low / `unverified` / disputed — color-coded with the status text always present (never color alone). Unverified and disputed must be *more* prominent than verified, not less.
+- **Sources are live**: inline `[n]` markers link to the appendix row; appendix rows link out to the source URL. Source URLs are untrusted content — never hand-escape them: generate the appendix table with `uv run scripts/recon_kit.py escape-sources {doc_workspace}/research.md` and embed its `html` output, which escapes every cell, anchors each row (`id="src-n"`), and links only validated `http(s)` URLs (anything else renders as plain text; the script lists it in `invalid_urls`). Apply the same escape discipline to any other source-derived text you place in attributes.
+- **Charts sparingly**: only where the data genuinely benefits (market size trajectory, decision matrix scores) — simple inline SVG, labeled axes, no library.
+- **Responsive and theme-aware**: readable on a phone; respect `prefers-color-scheme` for light/dark.
+
+## Theme
+
+`{workflow.html_theme}` governs: a `file:` path loads a theme/brand spec to follow; inline text is applied as directives; empty means the shipped default — neutral, professional, generous whitespace, system font stack, one restrained accent color. Whatever the theme, the confidence-badge semantics above are non-negotiable.
diff --git a/.claude/skills/bmad-deep-recon/references/lifecycle.md b/.claude/skills/bmad-deep-recon/references/lifecycle.md
new file mode 100644
index 0000000..74b092c
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/lifecycle.md
@@ -0,0 +1,11 @@
+# Refresh and Deepen
+
+Lifecycle intents on an existing run folder.
+
+## Refresh
+
+Read `research.md` and `.memlog.md` — never re-research from scratch. Build the refresh set mechanically: assemble the claims (`claim`, `class`, `pub_date`) from the ledger, map the pack's freshness bars to a months-per-class JSON, and run `uv run scripts/recon_kit.py staleness <claims.json> --windows '<map>'` — the stale flags are the candidate set. Confirm it in one exchange, re-verify just those claims, and deliver a **delta report** (confirmed / changed / overturned, new sources) appended to `research.md` with the frontmatter `updated` bumped. Claims outside the set keep their status. An overturned load-bearing claim triggers an explicit warning naming the downstream artifacts that consumed it.
+
+## Deepen
+
+Drill into one dimension or add a new one without touching the rest: mini plan gate, acquire → verify for that slice only (or a drafted follow-up prompt when the user's tool is better placed), merge into `research.md`, update only the synthesis sections the new material affects — a deepening that changes no conclusion says so.
diff --git a/.claude/skills/bmad-deep-recon/references/process.md b/.claude/skills/bmad-deep-recon/references/process.md
new file mode 100644
index 0000000..2380798
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/process.md
@@ -0,0 +1,10 @@
+# Process
+
+For a report the user names or drops ("there's a research report at <path>, process it"):
+
+1. **File it.** Find or create the run folder: if a drafted brief for this topic exists, that folder is the target; otherwise infer type and topic from the report (confirm in one line), bind `{doc_workspace}` (expand the folder name with `uv run scripts/recon_kit.py slug` as in Draft), and init the memlog. Move or copy the original into `{doc_workspace}/imports/` untouched — full fidelity is preserved there, and nowhere else.
+2. **Record provenance** in the memlog: what produced it (which tool or firm), when (ask if not evident — production date drives staleness), and what the user wants decided from it.
+3. **Extract.** A subagent (fresh context, firewall rules) reads the import and pulls every claim bearing on the decision into digest files under `{doc_workspace}/digests/` — standard shape `{claim, source, publisher, pub_date, accessed, confidence, class}`, keeping the original's citations (the cited source is the publisher; the import is the via). Multiple imports each get their own digest; contradictions between them are findings, not noise.
+4. **Check against the pack**: which of the type's dimensions the material covers, which are open, where its claims fall inside two-source classes but rest on one publisher. Verification per the resolved `validation` level (`references/verification.md`) — at `normal` this is a spot-check of the load-bearing claims only, minutes not hours.
+5. **Distill** into `research.md` per `references/synthesis.md` — the succinct, cited, decision-first summary with full metadata frontmatter (topic, type, decision, `source:` provenance, dates, status). This is the artifact downstream skills read; nobody ever reprocesses the import. Open dimensions are listed honestly with a one-line route: draft a follow-up prompt, or a targeted Run on the gap.
+6. Finalize per `references/finalize.md`.
diff --git a/.claude/skills/bmad-deep-recon/references/run.md b/.claude/skills/bmad-deep-recon/references/run.md
new file mode 100644
index 0000000..52b8976
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/run.md
@@ -0,0 +1,73 @@
+# Run
+
+Native research, when chosen: resolve effort, hold the plan gate, then run the acquisition loop once per dimension of the approved plan, in plan order.
+
+## Effort
+
+Three knobs bundled in a **preset**; any knob pins individually, and **what the user says in the request beats both**.
+
+| Preset (`{workflow.preset}`) | subagents | sources/round | depth |
+|---|---|---|---|
+| `quick` | low (2) | 5 | 1 |
+| `standard` (default) | normal (3) | 8 | 2 |
+| `deep` | high (6) | 12 | 3 |
+
+- **subagents** — parallel assistants: `none` (0 — inline, sequential; also the no-subagent-harness fallback), `low` (2), `normal` (3), `high` (6, cap 10 — beyond the 3–5 sweet spot only for genuinely wide work).
+- **max_sources_per_round** — distinct sources actually read per dimension per round (cap 25).
+- **max_depth** — rounds per dimension: initial pass plus lead-following follow-ups (cap 5). A cap, not a quota — dimensions stop early on coverage or novelty exhaustion.
+- **validation** (orthogonal to preset, default `normal`) — rigor rises `normal` < `high` < `max`; level semantics live in `references/verification.md`. Verification happens per dimension as material lands, never as an end-of-run rewrite pass.
+
+`{workflow.subagent_models}` is an ordered model preference for assistants — first available wins; empty means harness default. Keep the lead on the strongest model; researchers at most one tier down; judgment work never on the smallest tier.
+
+## The plan gate
+
+The one hard stop, kept light: decision, type and pack-derived dimensions pruned to it, shape, the **decomposition topology** — *breadth-first* (independent sub-questions: assistants split the dimensions), *depth-first* (one question that needs several perspectives: assistants split by angle or methodology, not by dimension), or *straightforward* (a focused ask: one assistant, a handful of calls, no fan-out — never overinvest in a simple query) — knobs in force and where each came from, which search surfaces exist (harness web search; installed search-shaped MCP tools; `{workflow.external_sources}` — check, don't assume), whether to run the fan-out as a workflow when the harness offers orchestration and `{workflow.use_workflows}` allows, and an honest time estimate (a standard run is minutes; deep runs are tens of minutes and many times the tokens).
+
+Present as a compact checklist, get approval, then: bind `{doc_workspace}` under `{workflow.research_output_path}` — expand the folder name with `uv run scripts/recon_kit.py slug "<topic>" --type <type> --pattern "{workflow.run_folder_pattern}"` so the same topic always resolves to the same folder — seed `research.md` from `{workflow.research_template}`, init the memlog (`uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<topic>" --field type="<type>" --field decision="<decision>" --field preset="<preset>"`), log the approved plan as a `decision`, and tell the user the path.
+
+Each dimension then runs in **rounds** — up to the resolved `max_depth` — and the report grows as material lands: the user watches the document build, not a spinner. Every digest is written to `{doc_workspace}/digests/` the moment it exists — one file per assistant per round (`<dimension>-r<round>-<n>.md`), the digest shape below, raw enough to re-derive from.
+
+## Rounds and lead-following
+
+Round 1 pursues the plan's questions **broad-first**: short, wide queries to map what exists, narrowing as the shape emerges — not long specific queries that return nothing. After each round, harvest the leads: new entities worth chasing, unexpected connections, contradictions between sources, and questions the round opened. Contradictions get priority. Promising leads become the next round's brief; note mid-course discoveries in the checkpoint so the user sees the turn happening.
+
+A dimension stops before its round cap when either holds:
+
+- **Coverage** — its plan questions are answered, with the critical claims confirmed per the resolved `validation` level.
+- **Novelty exhaustion** — a full round surfaced no new load-bearing claim or lead.
+
+Say which one ended it. Hitting the round cap with open questions is reported as an open question, never silently dropped.
+
+**Stop-and-write valve.** If the run is dragging well past the plan gate's estimate — rounds queuing, budgets mostly spent — stop spawning, synthesize from the digests already on disk, and report the remainder as open questions with a route (a Deepen later, or a drafted prompt for the user's own tool). A shorter honest report beats a longer stale one.
+
+## The fan-out
+
+Fan out researcher assistants for the round — concurrency per the resolved `subagents` level, split by the plan's **topology**: breadth-first gives each assistant independent sub-questions; depth-first gives each a distinct perspective or methodology on the *same* question; straightforward is one assistant with a small budget — never fan out what one focused assistant answers. Each assistant runs behind the **research firewall**: it gets its brief and nothing else — no project files, no ambient context. The brief contains:
+
+- the questions it owns, the decision they serve, and the topic
+- its search surfaces (specialized tools first — installed search-shaped MCP tools, `{workflow.external_sources}` entries whose directive matches — then generic search), plus `{workflow.preferred_sources}` first / `{workflow.banned_sources}` never
+- the pack's source craft and freshness bars, and the source-quality card below
+- its budgets — sources (the round's share of `max_sources_per_round`) and tool calls, scaled to its task: under 5 for a simple lookup, ~5 medium, ~10 hard, 15 for genuinely multi-part, 20 never exceeded. Either budget spent → synthesize what it has
+- the query craft: short queries (roughly five words or fewer) beat hyper-specific ones that return nothing; broaden when results are sparse, narrow when abundant; never repeat an identical query on the same tool; after every tool result, pause and evaluate — what did this add, what gap remains, what's the best next query — before firing again
+- the epistemics rules verbatim, and the return contract: a digest, not raw results — findings as claims, each with `{claim, source, publisher, pub_date, accessed, confidence, class}`, plus leads worth chasing and what it looked for and could not find
+
+**On each return, write the digest to `{doc_workspace}/digests/` before doing anything else with it.**
+
+Spawn assistants on `{workflow.subagent_models}` when set (first available wins); otherwise the harness default — judgment work never drops to the smallest tier. When subagents are unavailable (or `subagents` is `none`), run the same rounds yourself, sequentially, under the same budgets and the same files-first discipline.
+
+When workflow orchestration was approved at the plan gate, run the fan-out as a workflow: dimensions as parallel pipelines, assistants returning structured digests. The budgets, digest contract, firewall, and stopping rules apply unchanged — and however the acquisition parallelizes, digests land as files and the lead alone writes `research.md`, committing sections in plan order.
+
+## Source quality
+
+One card, applied by every assistant and the lead alike. Prefer **primary sources** — filings, regulator text, official documentation, original papers, a company's own reported numbers — over aggregators and secondary reporting. Red flags that downgrade confidence on sight: speculative language ("could", "may", projections in future tense presented as findings), marketing register, passive voice with unnamed sources, cherry-picked or unsourced numbers, and aggregators recycling a single upstream report (that's one publisher, however many domains echo it). Answer engines (Perplexity Sonar, Grok, and kin) are aggregators too, however good the synthesis: chase their citations and cite those, never the engine. Conflicts resolve by recency, consistency with adjacent established facts, and publisher quality — never by averaging.
+
+## Synthesize the dimension
+
+When a dimension's rounds are done:
+
+1. Verify at landing per `references/verification.md` — at `normal` validation this is a spot-check of the dimension's load-bearing claims, not a sweep.
+2. Write the dimension's section per the pack's skeleton from its digest files — findings woven into prose answering the dimension's questions, every load-bearing claim cited inline `[n]`, confidence flagged where below high, contradictions reported with both sides cited. Append to `research.md` and add its sources to the running source table.
+3. Log one memlog line per source batch (`--type source`) and one per load-bearing claim worth tracking for refresh — `--type claim`, text in the machine-readable shape `ref=[n] status=<verified|unverified|disputed|overturned> class=<class> pub=<YYYY-MM> — <claim>` so `scripts/recon_kit.py tally` and `staleness` can read the ledger; a later status change is a fresh claim line with the same `ref=` (last status wins).
+4. Checkpoint: one or two lines in chat — what the dimension found, anything surprising, anything unresolved. Keep moving unless the user speaks up; a mid-run scope change is logged as a `decision` and the plan adjusts. Headless: skip checkpoints entirely.
+
+When all dimensions are done, proceed to `references/synthesis.md` for final assembly.
diff --git a/.claude/skills/bmad-deep-recon/references/selection.md b/.claude/skills/bmad-deep-recon/references/selection.md
new file mode 100644
index 0000000..c4c7069
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/selection.md
@@ -0,0 +1,13 @@
+# The Select Shape
+
+When the decision is **choose between candidates** — technologies, vendors, libraries, platforms, agencies, anything — this method layers over whichever research type fits the subject. The type pack still governs sources, craft, and freshness; this shape governs the flow and the verdict.
+
+1. **Requirements frame.** What must the winner do, under what constraints — scale, compliance, budget, team skills, existing stack, exit-cost tolerance? Split hard gates from weighted preferences and set the weights. Sources: the project itself (brief, PRD, spine, `{workflow.persistent_facts}`, codebase) and the user — web research does not set requirements. **Agree the frame before any candidate research runs**; interactive runs confirm it even though the plan gate approved the dimension list.
+2. **Candidate screen.** Establish the credible field — leaders, strong challengers, one wildcard — and cut anything failing a hard gate. Screen to 3–5 finalists; record the cuts and why. Screening sources ≤ 6 months old — this field moves.
+3. **Evidence per criterion.** Score finalists against the frame using the type pack's dimensions and craft, verified against current versions/offerings. Cite every contested cell; where vendor claims and independent experience diverge, the divergence is a finding.
+4. **Cost & lock-in.** Total cost over the product's horizon — license/subscription, hosting, operational load, learning curve — and the cost of leaving. Current pricing pages read directly (≤ 3 mo, always); pricing-change history — a vendor that repriced once will again; migration-away accounts for real exit costs.
+5. **Verdict.** The weighted decision matrix — show the scoring, not just totals; a matrix the user can re-weight is worth more than a verdict they must trust. Then: the pick; the named runner-up and the conditions under which it wins instead; the strongest argument against the pick (from the red-team pass when it ran); the cheapest reversibility hedge (abstraction seam, pilot scope, exit test).
+
+**Two-source classes (added to the type's own):** pricing figures; performance/scale numbers; any cell that decides between the top two finalists.
+
+**Staleness:** a selection report older than two quarters should be refreshed before anyone acts on it — say so in the report.
diff --git a/.claude/skills/bmad-deep-recon/references/synthesis.md b/.claude/skills/bmad-deep-recon/references/synthesis.md
new file mode 100644
index 0000000..825d5ad
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/synthesis.md
@@ -0,0 +1,16 @@
+# Synthesis
+
+The report answers the decision — whether the material came from a native Run or a processed import. **Succinct is the contract**: findings and verdicts, not essays; rationale lives in the memlog; a reader gets the decision-relevant truth in minutes. For Process mode this is the whole point — the summary is what downstream consumers read so nobody reprocesses the original, and sections with nothing behind them collapse to a line rather than pad.
+
+Assemble `research.md` in this order, shaped by `{workflow.audience}` and written in `{document_output_language}`:
+
+1. **Executive summary** — decision-first: what the evidence says to do, the two or three findings that drive that answer, and the biggest caveat. One page maximum, readable standalone. Written last, placed first.
+2. **Dimension sections** — already written during the loop; now reconciled: consistent terminology, no duplicated ground, verification statuses and any corrections from the pass applied to the text.
+3. **Cross-dimension insights** — what only the *combination* shows (e.g. the market is growing but the regulatory dimension caps the reachable segment; the technically superior option loses on ecosystem health). This section is the harness earning its keep — if there are no cross-dimension insights, say so rather than manufacture them.
+4. **Contrary evidence** — when the red-team pass ran and found material; the strongest surviving counter-arguments, cited.
+5. **Recommendations** — each bound to the decision and, where the project has them, to the downstream artifact that consumes it (per the pack's `Feeds` entries: brief section, PRD input, architecture constraint). Each recommendation names its confidence basis; a recommendation resting on low-confidence or disputed claims says so in the same sentence.
+6. **Open questions** — what the research could not answer, and what it would take to answer each.
+7. **Source appendix** — the numbered source table: `[n] | claim/finding it supports | publisher | pub date | accessed | confidence`, the publisher cell a markdown link to the source URL. Every inline `[n]` resolves here.
+8. **Staleness map** — the claims that age fastest, computed not hand-derived: build the claims list (`claim`, `class`, `pub_date`) from the ledger, map the pack's freshness bars to months per class, and run `uv run scripts/recon_kit.py staleness <claims.json> --windows '<map>'` — render its re-check dates and close by noting the earliest. This is Refresh's work order.
+
+Update the frontmatter (`status: complete`, `updated`, and the verified/unverified counts from `uv run scripts/recon_kit.py tally {doc_workspace}/.memlog.md` — never hand-counted), log a final `event` in the memlog, and proceed to `references/finalize.md`.
diff --git a/.claude/skills/bmad-deep-recon/references/verification.md b/.claude/skills/bmad-deep-recon/references/verification.md
new file mode 100644
index 0000000..080fd1b
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/references/verification.md
@@ -0,0 +1,29 @@
+# Verification
+
+The trust layer — the same rules whatever produced the material (a native run's digests or a processed import). Verification happens **as material lands**, per dimension, in fresh-context verifier subagents reading digest files — never as an end-of-run rewrite pass over an hour of accumulated context. Late-pass rewrites degrade reports; landing-time checks improve them.
+
+## The claims ledger
+
+The memlog `claim` entries are the ledger: every claim a decision could rest on, with its class (each pack names its classes — quantitative sizes, pricing, versions/compatibility, regulatory assertions, …), source, publisher, publication date, and status. New claims enter `unverified`; on a Refresh or Deepen run, claims outside the run's scope keep their prior status from the memlog — only new and in-scope claims are (re)checked.
+
+## Levels
+
+Per the resolved `validation` level (request > knob > default `normal`):
+
+- **normal** — spot-check the **load-bearing claims only**: the handful per dimension the recommendation actually rests on. One independent-source check each, at landing. Everything else ships with its single source cited and confidence marked honestly. Fast by design.
+- **high** — cross-check every claim in the pack's *two-source classes*, and run the red-team pass on major conclusions regardless of `{workflow.red_team}`.
+- **max** — cross-check every ledger claim, run the red-team pass below at full breadth (every major conclusion), and primary-source-priority ranking: where a primary source (filing, regulator text, official docs, original paper) exists, secondary reporting alone does not verify.
+
+Verifier assistants run behind the research firewall on `{workflow.subagent_models}` when set; judgment work never drops to the smallest tier.
+
+**Independent** means a different publisher with different underlying data or reporting — not a syndication, quote, or republication of the first source, and not the same vendor's marketing in two places. An imported report counts as one publisher regardless of how many sources it cites internally; two imports from different tools agreeing is genuine confirmation, and their disagreement is a finding.
+
+Outcomes per claim: **verified** (independent source agrees within tolerance — for quantitative claims, same order of magnitude and direction), **disputed** (independent sources materially disagree — report both figures, both cited; never average), **unverified** (no independent check within budget — the claim stays, flagged, and joins the staleness map), or **overturned** (the weight of evidence contradicts it — corrected in the text, original noted). Every status change lands in the memlog as a fresh `claim` line with the same `ref=` and the new status — last status wins, which is how `scripts/recon_kit.py tally` reads the ledger. A verification outcome adjusts status and flags — it never licenses rewriting a finding's substance beyond what the new evidence says.
+
+Confidence rendered in the report: **high** (verified, fresh, credible publishers), **medium** (single credible source, fresh), **low** (stale, weak publisher, or disputed) — plus the explicit `unverified` flag. Confidence is per-claim, never per-section.
+
+## Red-team pass
+
+The single adversarial mechanism — no other verifier duplicates it. Off by default (`{workflow.red_team}` = `"off"`; `"offer"` proposes it at the plan gate, `"on"` always runs; `high` validation includes it for major conclusions, `max` runs it at full breadth). When it runs: for each major conclusion, a **fresh-context** skeptic subagent — the conclusion and a search budget, no supporting evidence, no run context — hunts for disconfirming evidence: the bear case, failed attempts, contrary data, the strongest good-faith argument the conclusion is wrong.
+
+What comes back is weighed, not appended: a conclusion that survives gets its strongest counter-argument acknowledged in the synthesis; one that doesn't is revised before the report states it. Material findings land in a **Contrary Evidence** section with full citation discipline. Zero findings after a real search is itself reportable — say what was searched for and not found.
diff --git a/.claude/skills/bmad-deep-recon/scripts/recon_kit.py b/.claude/skills/bmad-deep-recon/scripts/recon_kit.py
new file mode 100644
index 0000000..2b9759e
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/scripts/recon_kit.py
@@ -0,0 +1,322 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""recon_kit — deterministic helpers for bmad-deep-recon.
+
+The mechanical half of the research workflow: everything here is exact,
+repeatable work the LLM should never re-derive by hand. All subcommands
+print one JSON object to stdout; diagnostics go to stderr. Exit codes:
+0 = pass, 1 = findings that need attention, 2 = usage/parse error.
+
+Subcommands:
+  citations RESEARCH_MD
+      Cross-check inline [n] markers against the source-appendix table:
+      dangling markers (no appendix row) and orphaned rows (never cited).
+  tally MEMLOG_MD
+      Count memlog entries by type, and claim entries by status.
+      Claim lines carry `status=<word>` and optionally `ref=[n]`; for a
+      given ref the LAST status wins, so status changes are appends.
+  staleness CLAIMS_JSON --windows JSON [--today YYYY-MM-DD]
+      Given claims [{claim, class, pub_date}] and a months-per-class map
+      (e.g. '{"size/growth": 18, "pricing": 3}'), compute each claim's
+      re-check date, flag stale ones, and report the earliest re-check.
+  slug TOPIC --type TYPE [--pattern P] [--date YYYY-MM-DD]
+      Expand the run-folder pattern deterministically so the same topic
+      always lands in the same folder across draft -> process -> refresh.
+  escape-sources RESEARCH_MD
+      Emit the source-appendix table as HTML with every cell escaped and
+      only validated http(s) URLs turned into links, for the briefing.
+"""
+from __future__ import annotations
+
+import argparse
+import calendar
+import html
+import json
+import re
+import sys
+import unicodedata
+from datetime import date, datetime
+from pathlib import Path
+from urllib.parse import urlparse
+
+MARKER_RE = re.compile(r"\[(\d+)\](?!\()")  # [3] but not a [3](url) link
+MD_LINK_RE = re.compile(r"\[([^\]]*)\]\((\S+?)\)")
+BARE_URL_RE = re.compile(r"https?://[^\s|)\]]+")
+
+
+def out(payload: dict, exit_code: int) -> int:
+    print(json.dumps(payload, indent=2, ensure_ascii=False, default=str))
+    return exit_code
+
+
+def read_text(path_arg: str) -> str:
+    if path_arg == "-":
+        return sys.stdin.read()
+    return Path(path_arg).read_text(encoding="utf-8")
+
+
+def strip_fences(text: str) -> str:
+    """Blank out fenced code blocks so their contents never count as markers or rows."""
+    lines, fenced = [], False
+    for ln in text.splitlines():
+        if ln.lstrip().startswith("```"):
+            fenced = not fenced
+            lines.append("")
+            continue
+        lines.append("" if fenced else ln)
+    return "\n".join(lines)
+
+
+def table_cells(line: str) -> list[str]:
+    return [c.strip() for c in line.strip().strip("|").split("|")]
+
+
+def appendix_rows(text: str) -> dict[int, list[str]]:
+    """Source-appendix rows: markdown table rows whose first cell is a bare [n] / n."""
+    rows: dict[int, list[str]] = {}
+    for ln in text.splitlines():
+        stripped = ln.strip()
+        if not stripped.startswith("|"):
+            continue
+        cells = table_cells(stripped)
+        if not cells or len(cells) < 2:
+            continue
+        m = re.fullmatch(r"\[?(\d+)\]?", cells[0])
+        if m:
+            rows[int(m.group(1))] = cells
+    return rows
+
+
+# --- citations ---------------------------------------------------------------
+
+def cmd_citations(args) -> int:
+    text = strip_fences(read_text(args.file))
+    rows = appendix_rows(text)
+    markers: set[int] = set()
+    for ln in text.splitlines():
+        stripped = ln.strip()
+        if stripped.startswith("|"):
+            cells = table_cells(stripped)
+            if cells and re.fullmatch(r"\[?(\d+)\]?", cells[0]):
+                continue  # an appendix row is not a citation of itself
+        markers.update(int(n) for n in MARKER_RE.findall(ln))
+    dangling = sorted(markers - set(rows))
+    orphaned = sorted(set(rows) - markers)
+    ok = not dangling and not orphaned
+    return out({
+        "markers": sorted(markers),
+        "appendix_rows": sorted(rows),
+        "dangling_markers": dangling,
+        "orphaned_rows": orphaned,
+        "ok": ok,
+    }, 0 if ok else 1)
+
+
+# --- tally -------------------------------------------------------------------
+
+ENTRY_RE = re.compile(r"^- (?:\(([\w-]+)(?: by [^)]*)?\)\s*)?(.*)$")
+
+
+def cmd_tally(args) -> int:
+    text = read_text(args.file)
+    body = text.split("---", 2)[-1] if text.startswith("---") else text
+    by_type: dict[str, int] = {}
+    by_ref: dict[int, str] = {}
+    unref_status: dict[str, int] = {}
+    entries = 0
+    for ln in body.splitlines():
+        m = ENTRY_RE.match(ln)
+        if not m or not ln.startswith("- "):
+            continue
+        entries += 1
+        etype = m.group(1) or "note"
+        by_type[etype] = by_type.get(etype, 0) + 1
+        if etype == "claim":
+            status_m = re.search(r"status=([\w-]+)", m.group(2))
+            status = status_m.group(1) if status_m else "unknown"
+            ref_m = re.search(r"ref=\[?(\d+)\]?", m.group(2))
+            if ref_m:
+                by_ref[int(ref_m.group(1))] = status  # last status wins per ref
+            else:
+                unref_status[status] = unref_status.get(status, 0) + 1
+    claims: dict[str, int] = dict(unref_status)
+    for status in by_ref.values():
+        claims[status] = claims.get(status, 0) + 1
+    return out({
+        "entries": entries,
+        "by_type": dict(sorted(by_type.items())),
+        "claims": dict(sorted(claims.items())),
+        "claims_total": sum(claims.values()),
+    }, 0)
+
+
+# --- staleness ---------------------------------------------------------------
+
+def parse_date(raw: str) -> date:
+    raw = raw.strip()
+    for fmt in ("%Y-%m-%d", "%Y-%m", "%Y"):
+        try:
+            return datetime.strptime(raw, fmt).date()
+        except ValueError:
+            continue
+    raise ValueError(f"unparseable date: {raw!r} (want YYYY[-MM[-DD]])")
+
+
+def add_months(d: date, months: int) -> date:
+    total = d.month - 1 + months
+    year, month = d.year + total // 12, total % 12 + 1
+    return date(year, month, min(d.day, calendar.monthrange(year, month)[1]))
+
+
+def cmd_staleness(args) -> int:
+    try:
+        payload = json.loads(read_text(args.file))
+        windows = {k.lower(): int(v) for k, v in json.loads(args.windows).items()}
+        today = parse_date(args.today) if args.today else date.today()
+    except (ValueError, json.JSONDecodeError) as e:
+        print(f"error: {e}", file=sys.stderr)
+        return 2
+    claims = payload["claims"] if isinstance(payload, dict) else payload
+    results, no_window, stale_count = [], set(), 0
+    earliest: date | None = None
+    for c in claims:
+        cls = str(c.get("class", "")).lower()
+        try:
+            pub = parse_date(str(c["pub_date"]))
+        except (KeyError, ValueError) as e:
+            print(f"error in claim {c!r}: {e}", file=sys.stderr)
+            return 2
+        months = windows.get(cls)
+        if months is None:
+            no_window.add(cls)
+            results.append({**c, "recheck": None, "stale": None})
+            continue
+        recheck = add_months(pub, months)
+        stale = recheck <= today
+        stale_count += stale
+        earliest = recheck if earliest is None or recheck < earliest else earliest
+        results.append({**c, "recheck": recheck.isoformat(), "stale": stale})
+    return out({
+        "today": today.isoformat(),
+        "claims": results,
+        "stale_count": stale_count,
+        "earliest_recheck": earliest.isoformat() if earliest else None,
+        "no_window_classes": sorted(no_window),
+    }, 1 if stale_count else 0)
+
+
+# --- slug --------------------------------------------------------------------
+
+def slugify(text: str, max_len: int = 40) -> str:
+    text = unicodedata.normalize("NFKD", text).encode("ascii", "ignore").decode()
+    text = re.sub(r"[^a-z0-9]+", "-", text.lower()).strip("-")
+    return re.sub(r"-{2,}", "-", text)[:max_len].rstrip("-")
+
+
+def cmd_slug(args) -> int:
+    slug = slugify(args.topic)
+    if not slug:
+        print("error: topic slugified to an empty string", file=sys.stderr)
+        return 2
+    folder = (args.pattern
+              .replace("{research_type}", args.type)
+              .replace("{topic_slug}", slug)
+              .replace("{date}", args.date or date.today().isoformat()))
+    return out({"topic_slug": slug, "folder": folder}, 0)
+
+
+# --- escape-sources ----------------------------------------------------------
+
+def safe_url(raw: str) -> str | None:
+    parsed = urlparse(raw)
+    return raw if parsed.scheme in ("http", "https") and parsed.netloc else None
+
+
+def cell_html(cell: str, invalid: list[str]) -> str:
+    """Escape a cell; a markdown link or bare URL becomes an <a> only when http(s)."""
+    link = MD_LINK_RE.search(cell)
+    if link:
+        url = safe_url(link.group(2))
+        label = html.escape(link.group(1) or link.group(2))
+        if url:
+            return html.escape(cell[:link.start()]) + \
+                f'<a href="{html.escape(url, quote=True)}" target="_blank" rel="noopener">{label}</a>' + \
+                html.escape(cell[link.end():])
+        invalid.append(link.group(2))
+        return html.escape(cell.replace(link.group(0), link.group(1) or link.group(2)))
+    bare = BARE_URL_RE.search(cell)
+    if bare:
+        url = safe_url(bare.group(0))
+        if url:
+            escaped = html.escape(url, quote=True)
+            return html.escape(cell[:bare.start()]) + \
+                f'<a href="{escaped}" target="_blank" rel="noopener">{escaped}</a>' + \
+                html.escape(cell[bare.end():])
+        invalid.append(bare.group(0))
+    return html.escape(cell)
+
+
+def cmd_escape_sources(args) -> int:
+    text = strip_fences(read_text(args.file))
+    rows = appendix_rows(text)
+    if not rows:
+        print("error: no source-appendix table rows found", file=sys.stderr)
+        return 2
+    invalid: list[str] = []
+    body_rows = []
+    for n in sorted(rows):
+        cells = rows[n]
+        tds = "".join(f"<td>{cell_html(c, invalid)}</td>" for c in cells[1:])
+        body_rows.append(f'<tr id="src-{n}"><td>[{n}]</td>{tds}</tr>')
+    table = ('<table class="sources"><tbody>' + "".join(body_rows) + "</tbody></table>")
+    return out({"rows": len(rows), "invalid_urls": invalid, "html": table},
+               1 if invalid else 0)
+
+
+# --- entry point -------------------------------------------------------------
+
+def main(argv: list[str] | None = None) -> int:
+    p = argparse.ArgumentParser(description=__doc__,
+                                formatter_class=argparse.RawDescriptionHelpFormatter)
+    sub = p.add_subparsers(dest="cmd", required=True)
+
+    pc = sub.add_parser("citations", help="cross-check [n] markers vs the source appendix")
+    pc.add_argument("file", help="path to research.md (or - for stdin)")
+    pc.set_defaults(func=cmd_citations)
+
+    pt = sub.add_parser("tally", help="count memlog entries by type and claims by status")
+    pt.add_argument("file", help="path to .memlog.md (or - for stdin)")
+    pt.set_defaults(func=cmd_tally)
+
+    ps = sub.add_parser("staleness", help="compute re-check dates from freshness windows")
+    ps.add_argument("file", help="claims JSON: [{claim, class, pub_date}] (or - for stdin)")
+    ps.add_argument("--windows", required=True,
+                    help='JSON months-per-class map, e.g. \'{"pricing": 3}\'')
+    ps.add_argument("--today", help="override today's date (YYYY-MM-DD)")
+    ps.set_defaults(func=cmd_staleness)
+
+    pg = sub.add_parser("slug", help="expand the run-folder pattern deterministically")
+    pg.add_argument("topic", help="research topic text")
+    pg.add_argument("--type", required=True, help="research type code (e.g. market)")
+    pg.add_argument("--pattern", default="{research_type}-{topic_slug}-{date}",
+                    help="folder pattern (default: {research_type}-{topic_slug}-{date})")
+    pg.add_argument("--date", help="override date (YYYY-MM-DD; default today)")
+    pg.set_defaults(func=cmd_slug)
+
+    pe = sub.add_parser("escape-sources",
+                        help="source appendix as escaped HTML with validated links")
+    pe.add_argument("file", help="path to research.md (or - for stdin)")
+    pe.set_defaults(func=cmd_escape_sources)
+
+    args = p.parse_args(argv)
+    try:
+        return args.func(args)
+    except FileNotFoundError as e:
+        print(f"error: {e}", file=sys.stderr)
+        return 2
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/.claude/skills/bmad-deep-recon/scripts/tests/test_recon_kit.py b/.claude/skills/bmad-deep-recon/scripts/tests/test_recon_kit.py
new file mode 100644
index 0000000..217f534
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/scripts/tests/test_recon_kit.py
@@ -0,0 +1,144 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""Tests for recon_kit.py."""
+
+import io
+import json
+import sys
+import unittest
+from contextlib import redirect_stdout
+from datetime import date
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
+
+from recon_kit import add_months, main, parse_date, slugify
+
+REPORT = """---
+title: 'market research: widgets'
+---
+
+# Report
+
+The market is growing fast [1] and pricing clusters at $20 [2].
+An uncited assertion sits here [4].
+
+```
+[9] inside a fence never counts
+```
+
+## Source appendix
+
+| [n] | Supports | Publisher | Pub date | Accessed | Confidence |
+| --- | --- | --- | --- | --- | --- |
+| [1] | market growth | [Gartner](https://example.com/g) | 2026-01 | 2026-07-01 | high |
+| [2] | pricing | [Acme](javascript:alert(1)) | 2026-05 | 2026-07-01 | medium |
+| [3] | never cited | https://example.com/x | 2025-11 | 2026-07-01 | low |
+"""
+
+MEMLOG = """---
+topic: widgets
+updated: 2026-07-22T10:00
+---
+
+- (decision) plan approved
+- (source) round 1 batch: 4 sources
+- (claim) ref=[1] status=verified class=size/growth pub=2026-01 — market growing 12% CAGR
+- (claim) ref=[2] status=unverified class=pricing pub=2026-05 — pricing clusters at $20
+- (claim) ref=[2] status=verified class=pricing pub=2026-05 — confirmed by second source
+- (claim) status=unverified class=behavior pub=2025-03 — users churn at day 8
+- (event) dimension 1 complete
+"""
+
+
+def run(argv):
+    buf = io.StringIO()
+    with redirect_stdout(buf):
+        code = main(argv)
+    return code, json.loads(buf.getvalue())
+
+
+class CitationsTest(unittest.TestCase):
+    def test_cross_check(self):
+        report = Path(__file__).parent / "_report.md"
+        report.write_text(REPORT, encoding="utf-8")
+        try:
+            code, result = run(["citations", str(report)])
+        finally:
+            report.unlink()
+        self.assertEqual(result["dangling_markers"], [4])
+        self.assertEqual(result["orphaned_rows"], [3])
+        self.assertNotIn(9, result["markers"])  # fenced content ignored
+        self.assertEqual(code, 1)
+
+
+class TallyTest(unittest.TestCase):
+    def test_last_status_wins_per_ref(self):
+        log = Path(__file__).parent / "_memlog.md"
+        log.write_text(MEMLOG, encoding="utf-8")
+        try:
+            code, result = run(["tally", str(log)])
+        finally:
+            log.unlink()
+        self.assertEqual(result["by_type"]["claim"], 4)
+        self.assertEqual(result["claims"], {"unverified": 1, "verified": 2})
+        self.assertEqual(result["claims_total"], 3)  # ref=[2] counted once
+        self.assertEqual(code, 0)
+
+
+class StalenessTest(unittest.TestCase):
+    def test_dates(self):
+        self.assertEqual(parse_date("2026-01"), date(2026, 1, 1))
+        self.assertEqual(add_months(date(2026, 1, 31), 1), date(2026, 2, 28))
+
+    def test_windows(self):
+        claims = json.dumps([
+            {"claim": "sizing", "class": "size/growth", "pub_date": "2024-06"},
+            {"claim": "pricing", "class": "pricing", "pub_date": "2026-06"},
+            {"claim": "odd", "class": "unmapped", "pub_date": "2026-06"},
+        ])
+        f = Path(__file__).parent / "_claims.json"
+        f.write_text(claims, encoding="utf-8")
+        try:
+            code, result = run([
+                "staleness", str(f),
+                "--windows", '{"size/growth": 18, "pricing": 3}',
+                "--today", "2026-07-22",
+            ])
+        finally:
+            f.unlink()
+        self.assertEqual(result["stale_count"], 1)  # sizing recheck 2025-12 < today
+        self.assertEqual(result["earliest_recheck"], "2025-12-01")
+        self.assertEqual(result["no_window_classes"], ["unmapped"])
+        self.assertEqual(code, 1)
+
+
+class SlugTest(unittest.TestCase):
+    def test_deterministic_folder(self):
+        self.assertEqual(slugify("Créme Brûlée: AI Tools!"), "creme-brulee-ai-tools")
+        code, result = run(["slug", "SMB Accounting SaaS", "--type", "market",
+                            "--date", "2026-07-22"])
+        self.assertEqual(result["folder"], "market-smb-accounting-saas-2026-07-22")
+        self.assertEqual(code, 0)
+
+
+class EscapeSourcesTest(unittest.TestCase):
+    def test_escaping_and_url_validation(self):
+        report = Path(__file__).parent / "_report.md"
+        report.write_text(REPORT, encoding="utf-8")
+        try:
+            code, result = run(["escape-sources", str(report)])
+        finally:
+            report.unlink()
+        self.assertEqual(result["rows"], 3)
+        self.assertTrue(any(u.startswith("javascript:") for u in result["invalid_urls"]))
+        self.assertNotIn("javascript:", result["html"])  # never linked
+        self.assertIn('href="https://example.com/g"', result["html"])
+        self.assertIn('id="src-1"', result["html"])
+        self.assertEqual(code, 1)
+
+
+if __name__ == "__main__":
+    unittest.main()
diff --git a/.claude/skills/bmad-deep-recon/types/academic-lit.md b/.claude/skills/bmad-deep-recon/types/academic-lit.md
new file mode 100644
index 0000000..c81a55b
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/types/academic-lit.md
@@ -0,0 +1,19 @@
+# Academic Literature Pack
+
+Serves: ground an approach in published research, scan the state of the art, run a defensible literature review, cite properly in technical writing.
+
+**Dimensions (priority order — prune to the decision):**
+
+1. The canon — seminal papers and the best recent surveys of the area
+2. State of the art — current best results, benchmarks, and how they're measured
+3. Methods & limitations — what the leading approaches assume and where they break
+4. Open problems & live debates — what the field disagrees about right now
+5. Who works on this — the labs and groups whose output to watch
+
+**Craft (the non-obvious):** find one good survey before reading twenty abstracts; chase citations both directions — who they cite and who cites them (Semantic Scholar/Google Scholar); label preprint vs peer-reviewed on every citation — arXiv is not acceptance; take benchmark numbers from the original paper, never from a competitor's comparison table; check retraction and replication status on any load-bearing empirical claim; a result only ever shown by one lab is a lead, not a fact.
+
+**Freshness:** state-of-the-art claims ≤ 12 mo (ML ≤ 6 mo) · seminal work has no freshness bar — but check whether it was since superseded.
+
+**Two-source classes:** any empirical claim a conclusion rests on — independent replication or corroboration, not the same lab twice.
+
+**Feeds (bmm):** technical and architecture bets · content and writing that cites · build-vs-adopt judgments on research-grade techniques.
diff --git a/.claude/skills/bmad-deep-recon/types/competitive.md b/.claude/skills/bmad-deep-recon/types/competitive.md
new file mode 100644
index 0000000..ee504db
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/types/competitive.md
@@ -0,0 +1,19 @@
+# Competitive Research Pack
+
+Serves: position against *named* competitors, build battlecards, sharpen differentiation, anticipate their next move. (Surveying an unnamed field is the market type; this pack is for teardowns of specific players.)
+
+**Dimensions (priority order — prune to the decision):**
+
+1. Offer & feature teardown — what they actually ship, tried directly where possible
+2. Pricing & packaging — models, tiers, what changed recently and which direction
+3. Positioning & messaging — who they claim to serve, the story they tell, the gap between claim and product
+4. Trajectory — funding, hiring, release cadence: where they're headed
+5. Their customers' voice — what users of *their* product praise and complain about
+
+**Craft (the non-obvious):** their changelog and release notes are roadmap truth; job postings reveal strategy six months early; their customers' 1–3★ reviews are your wedge; archived pricing pages (Wayback) show pricing direction, not just position; sales-facing comparison pages overclaim — verify capability claims against their docs; try the product yourself when a trial exists — an hour in-product beats ten reviews.
+
+**Freshness:** pricing & features ≤ 3 mo · trajectory signals ≤ 6 mo · customer sentiment ≤ 12 mo.
+
+**Two-source classes:** traction and market-share claims; any capability claim of theirs that your differentiation rests on.
+
+**Feeds (bmm):** brief (alternatives) · PRD (differentiation) · GTM battlecards and positioning.
diff --git a/.claude/skills/bmad-deep-recon/types/domain.md b/.claude/skills/bmad-deep-recon/types/domain.md
new file mode 100644
index 0000000..a656c1d
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/types/domain.md
@@ -0,0 +1,19 @@
+# Domain Research Pack
+
+Serves: commit to building in an industry, talk credibly with domain experts, scope a product for a regulated field, brief a team entering unfamiliar territory.
+
+**Dimensions (priority order — prune to the decision):**
+
+1. Industry structure & value chain — how value flows, who captures margin where
+2. Key players & gatekeepers — incumbents, platforms, whose APIs/standards/marketplaces you build with or against
+3. Rules of the game — laws, licenses, de-facto standards, what compliance costs a new entrant
+4. Language & mental models — the vocabulary and implicit workflows practitioners think in; **build the glossary — it's why domain research exists**
+5. Technology adoption — the current technical baseline and where the industry sits on the adoption curve
+
+**Craft (the non-obvious):** annual-report industry sections are free structured teardowns; conference keynotes reveal who actually matters; go to regulator sites directly for any load-bearing claim — and read enforcement actions to learn what's actually punished versus merely written; job postings name the real tools and skills; pending regulatory changes matter as much as current text.
+
+**Freshness:** structure ≤ 3 yr · player landscape ≤ 18 mo · regulatory status: verify current on every load-bearing claim, whatever its date · tech adoption ≤ 18 mo, AI-adoption claims ≤ 6 mo.
+
+**Two-source classes:** regulatory and compliance assertions; quantitative industry figures a recommendation rests on; claims about a gatekeeper's policy.
+
+**Feeds (bmm):** brief (context, feasibility) · PRD (constraints, domain vocabulary) · architecture (integration landscape, compliance requirements).
diff --git a/.claude/skills/bmad-deep-recon/types/market.md b/.claude/skills/bmad-deep-recon/types/market.md
new file mode 100644
index 0000000..18d38e5
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/types/market.md
@@ -0,0 +1,19 @@
+# Market Research Pack
+
+Serves: enter or skip a market, position a product, pick a segment, price an offer, pitch investors.
+
+**Dimensions (priority order — prune to the decision):**
+
+1. Market size & growth — the *reachable* market, not the headline TAM
+2. Customer segments & behavior — who buys, deciding how, valuing what
+3. Pain points & unmet needs — what they complain about, work around, pay to avoid
+4. Competitive landscape — who competes for this budget, including substitutes and "do nothing"
+5. GTM & pricing dynamics — channels, sales motion, accepted pricing models, realistic CAC
+
+**Craft (the non-obvious):** 1–3★ reviews are the gold for pains; public-company 10-K/S-1 industry sections are free analyst-grade sizing; read competitor pricing pages directly, never roundups; funding history + job postings reveal competitor trajectory; a complaint pattern persisting across years is a stronger finding, not a stale one.
+
+**Freshness:** size/growth ≤ 18 mo · pricing & feature claims ≤ 3 mo · behavior data ≤ 2 yr · GTM benchmarks ≤ 12 mo.
+
+**Two-source classes:** market size and growth figures; any quantitative claim a recommendation rests on; competitor traction claims.
+
+**Feeds (bmm):** brief (opportunity, problem, users) · PRD (personas, differentiation) · pricing and GTM decisions.
diff --git a/.claude/skills/bmad-deep-recon/types/technical.md b/.claude/skills/bmad-deep-recon/types/technical.md
new file mode 100644
index 0000000..7826600
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/types/technical.md
@@ -0,0 +1,19 @@
+# Technical Research Pack
+
+Serves: adopt a technology area, design an integration approach, ground an architecture in current practice, assess feasibility before committing a roadmap.
+
+**Dimensions (priority order — prune to the decision):**
+
+1. Landscape & maturity — dominant approaches, what's consolidating vs churning, what the current generation newly makes possible
+2. Integration & interoperability — protocols, formats, auth patterns, where integrations actually hurt
+3. Architecture patterns in practice — which named patterns dominate at what scale, and what the failures teach
+4. Implementation reality — learning curve, tooling, operational burden, what teams say 6–12 months in
+5. Ecosystem health — contributor/release vitality, backing durability, the five-year regret risk
+
+**Craft (the non-obvious):** read the retrospective threads, not the launch threads; favor accounts with production numbers over advocacy; before citing a pain point, check whether it was since fixed — an old complaint against a current version is a false claim; read repository metrics over time, never snapshots; issue trackers reveal the gap between docs and reality.
+
+**Freshness:** versions & compatibility ≤ 1 mo · ecosystem signals ≤ 6 mo · landscape ≤ 12 mo (AI-adjacent ≤ 3 mo) · patterns ≤ 2 yr.
+
+**Two-source classes:** version/compatibility claims; performance or scale numbers a recommendation rests on; claims that a technology or pattern failed — one post-mortem is an anecdote.
+
+**Feeds (bmm):** architecture spine (candidate paradigms, operational constraints) · brief (feasibility) · roadmap risk and estimates.
diff --git a/.claude/skills/bmad-deep-recon/types/user-voice.md b/.claude/skills/bmad-deep-recon/types/user-voice.md
new file mode 100644
index 0000000..9c195c5
--- /dev/null
+++ b/.claude/skills/bmad-deep-recon/types/user-voice.md
@@ -0,0 +1,19 @@
+# User-Voice Research Pack
+
+Serves: understand what users of a product or category actually experience and want — personas, jobs-to-be-done, requirements grounded in evidence rather than assumption.
+
+**Dimensions (priority order — prune to the decision):**
+
+1. Who they are & their jobs-to-be-done — the progress they're hiring the product to make
+2. Complaint & workaround patterns — where current options fail them
+3. Delight & switching triggers — why they stay, what made them move
+4. Unmet needs & requests — what they ask for, and the deeper need under the ask
+5. Their language — the words users say, versus the words vendors use
+
+**Craft (the non-obvious):** mine 1–3★ reviews for pain *and* 5★ for why they stay; a workaround is unpriced demand — someone laboring around a gap has already voted; forums, Discord, and Reddit surface what surveys miss — people lie less when nobody's asking — but they over-sample the loud, so triangulate against reviews and any survey data; keep verbatim quotes, redacted — user words carry evidence paraphrase destroys, but usernames, handles, emails, and identifying links never enter the report or memlog; feature-request boards measure willingness to wait, not willingness to pay; distinguish loud power-users from the silent majority — count distinct voices, not thread length.
+
+**Freshness:** sentiment ≤ 18 mo · complaints re-checked against the current version before citing.
+
+**Two-source classes:** any prevalence claim ("most users…", "the top complaint is…") — two independent communities, not two threads in the same one.
+
+**Feeds (bmm):** PRD (personas, requirements rationale) · UX research inputs · brief (problem) · product copy in the users' own language.
diff --git a/.claude/skills/bmad-dev-auto/SKILL.md b/.claude/skills/bmad-dev-auto/SKILL.md
new file mode 100644
index 0000000..6a7fe6d
--- /dev/null
+++ b/.claude/skills/bmad-dev-auto/SKILL.md
@@ -0,0 +1,19 @@
+---
+name: bmad-dev-auto
+description: "Deprecated: forwards to bmad-build-auto. Do not use unless invoked by name."
+---
+
+# Deprecated Build Auto Alias
+
+## On Activation
+
+1. Check whether either legacy customization file exists:
+   - `{project-root}/_bmad/custom/bmad-dev-auto.toml`
+   - `{project-root}/_bmad/custom/bmad-dev-auto.user.toml`
+2. If neither legacy file exists, output exactly `bmad-dev-auto is deprecated. Redirecting to bmad-build-auto. Please use bmad-build-auto in the future.`, invoke `bmad-build-auto` exactly once with the user's original input verbatim, then execute no further steps in this shim.
+3. For every legacy file that exists, use its matching new filename:
+   - `{project-root}/_bmad/custom/bmad-dev-auto.toml` becomes `{project-root}/_bmad/custom/bmad-build-auto.toml`.
+   - `{project-root}/_bmad/custom/bmad-dev-auto.user.toml` becomes `{project-root}/_bmad/custom/bmad-build-auto.user.toml`.
+4. If the matching new file does not exist, tell the user that the customization file uses the deprecated name and offer to rename it. Rename it only after explicit approval. If approval is declined or unavailable, or the rename fails, HALT and do not invoke any skill.
+5. If the matching new file already exists, do not overwrite it. Read both files, explain their differences, and propose the exact content for the new file. Resolve conflicting values with the user. Only after the user explicitly approves that content, save and verify the new file, then remove the legacy file. If approval is declined or unavailable, or any operation fails, HALT and do not invoke any skill.
+6. After every detected legacy file has been migrated successfully and no legacy file remains, output exactly `bmad-dev-auto is deprecated. Redirecting to bmad-build-auto. Please use bmad-build-auto in the future.`, invoke `bmad-build-auto` exactly once with the user's original input verbatim, then execute no further steps in this shim.
diff --git a/.claude/skills/bmad-dev-story/SKILL.md b/.claude/skills/bmad-dev-story/SKILL.md
new file mode 100644
index 0000000..c8bcc8a
--- /dev/null
+++ b/.claude/skills/bmad-dev-story/SKILL.md
@@ -0,0 +1,502 @@
+---
+name: bmad-dev-story
+description: "Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name."
+---
+
+# Dev Story Workflow
+
+**Goal:** Execute story implementation following a context filled story spec file.
+
+**Your Role:** Developer implementing the story.
+- Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
+- Generate all documents in {document_output_language}
+- Only modify the story file in these areas: YAML frontmatter `baseline_commit`, Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
+- Execute ALL steps in exact order; do NOT skip steps
+- Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
+- Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 9 decides completion.
+- User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.
+
+## Conventions
+
+- Bare paths (e.g. `steps/step-01-init.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+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`
+- `date` as system-generated current datetime
+- `project_context` = `**/project-context.md` (load if exists)
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+<output>Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name.</output>
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Paths
+
+- `story_file` = `` (explicit story path; auto-discovered if empty)
+- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
+
+## Execution
+
+<workflow>
+  <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
+  <critical>Generate all documents in {document_output_language}</critical>
+  <critical>Only modify the story file in these areas: YAML frontmatter `baseline_commit`, Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List,
+    Change Log, and Status</critical>
+  <critical>Execute ALL steps in exact order; do NOT skip steps</critical>
+  <critical>Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution
+    until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives
+    other instruction.</critical>
+  <critical>Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 9 decides completion.</critical>
+  <critical>User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.</critical>
+
+  <step n="1" goal="Find next ready story and load it" tag="sprint-status">
+    <check if="{{story_path}} is provided">
+      <action>Use {{story_path}} directly</action>
+      <action>Read COMPLETE story file</action>
+      <action>Extract story_key from filename or metadata</action>
+      <goto anchor="task_check" />
+    </check>
+
+    <!-- Sprint-based story discovery -->
+    <check if="{{sprint_status}} file exists">
+      <critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
+      <action>Load the FULL file: {{sprint_status}}</action>
+      <action>Read ALL lines from beginning to end - do not skip any content</action>
+      <action>Parse the development_status section completely to understand story order</action>
+
+      <action>Find the FIRST story (by reading in order from top to bottom) where:
+        - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
+        - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
+        - Status value equals "ready-for-dev"
+      </action>
+
+      <check if="no ready-for-dev or in-progress story found">
+        <output>📋 No ready-for-dev stories found in sprint-status.yaml
+
+          **Current Sprint Status:** {{sprint_status_summary}}
+
+          **What would you like to do?**
+          1. Run `create-story` to create next story from epics with comprehensive context
+          2. Run `*validate-create-story` to improve existing stories before development (recommended quality check)
+          3. Specify a particular story file to develop (provide full path)
+          4. Check {{sprint_status}} file to see current sprint status
+
+          💡 **Tip:** Stories in `ready-for-dev` may not have been validated. Consider running `validate-create-story` first for a quality
+          check.
+        </output>
+        <ask>Choose option [1], [2], [3], or [4], or specify story file path:</ask>
+
+        <check if="user chooses '1'">
+          <action>HALT - Run create-story to create next story</action>
+        </check>
+
+        <check if="user chooses '2'">
+          <action>HALT - Run validate-create-story to improve existing stories</action>
+        </check>
+
+        <check if="user chooses '3'">
+          <ask>Provide the story file path to develop:</ask>
+          <action>Store user-provided story path as {{story_path}}</action>
+          <goto anchor="task_check" />
+        </check>
+
+        <check if="user chooses '4'">
+          <output>Loading {{sprint_status}} for detailed status review...</output>
+          <action>Display detailed sprint status analysis</action>
+          <action>HALT - User can review sprint status and provide story path</action>
+        </check>
+
+        <check if="user provides story file path">
+          <action>Store user-provided story path as {{story_path}}</action>
+          <goto anchor="task_check" />
+        </check>
+      </check>
+    </check>
+
+    <!-- Non-sprint story discovery -->
+    <check if="{{sprint_status}} file does NOT exist">
+      <action>Search {implementation_artifacts} for stories directly</action>
+      <action>Find stories with "ready-for-dev" status in files</action>
+      <action>Look for story files matching pattern: *-*-*.md</action>
+      <action>Read each candidate story file to check Status section</action>
+
+      <check if="no ready-for-dev stories found in story files">
+        <output>📋 No ready-for-dev stories found
+
+          **Available Options:**
+          1. Run `create-story` to create next story from epics with comprehensive context
+          2. Run `*validate-create-story` to improve existing stories
+          3. Specify which story to develop
+        </output>
+        <ask>What would you like to do? Choose option [1], [2], or [3]:</ask>
+
+        <check if="user chooses '1'">
+          <action>HALT - Run create-story to create next story</action>
+        </check>
+
+        <check if="user chooses '2'">
+          <action>HALT - Run validate-create-story to improve existing stories</action>
+        </check>
+
+        <check if="user chooses '3'">
+          <ask>It's unclear what story you want developed. Please provide the full path to the story file:</ask>
+          <action>Store user-provided story path as {{story_path}}</action>
+          <action>Continue with provided story file</action>
+        </check>
+      </check>
+
+      <check if="ready-for-dev story found in files">
+        <action>Use discovered story file and extract story_key</action>
+      </check>
+    </check>
+
+    <action>Store the found story_key (e.g., "1-2-user-authentication") for later status updates</action>
+    <action>Find matching story file in {implementation_artifacts} using story_key pattern: {{story_key}}.md</action>
+    <action>Read COMPLETE story file from discovered path</action>
+
+    <anchor id="task_check" />
+
+    <action>Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status</action>
+
+    <action>Load comprehensive context from story file's Dev Notes section</action>
+    <action>Extract developer guidance from Dev Notes: architecture requirements, previous learnings, technical specifications</action>
+    <action>Use enhanced story context to inform implementation decisions and approaches</action>
+
+    <action>Identify first incomplete task (unchecked [ ]) in Tasks/Subtasks</action>
+
+    <action if="no incomplete tasks">
+      <goto step="9">Completion sequence</goto>
+    </action>
+    <action if="story file inaccessible">HALT: "Cannot develop story without access to story file"</action>
+    <action if="incomplete task or subtask requirements ambiguous">ASK user to clarify or HALT</action>
+  </step>
+
+  <step n="2" goal="Load project context and story information">
+    <critical>Load all available context to inform implementation</critical>
+
+    <action>Load {project_context} for coding standards and project-wide patterns (if exists)</action>
+    <action>Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status</action>
+    <action>Load comprehensive context from story file's Dev Notes section</action>
+    <action>Extract developer guidance from Dev Notes: architecture requirements, previous learnings, technical specifications</action>
+    <action>Use enhanced story context to inform implementation decisions and approaches</action>
+    <output>✅ **Context Loaded**
+      Story and project context available for implementation
+    </output>
+  </step>
+
+  <step n="3" goal="Detect review continuation and extract review context">
+    <critical>Determine if this is a fresh start or continuation after code review</critical>
+
+    <action>Check if "Senior Developer Review (AI)" section exists in the story file</action>
+    <action>Check if "Review Follow-ups (AI)" subsection exists under Tasks/Subtasks</action>
+
+    <check if="Senior Developer Review section exists">
+      <action>Set review_continuation = true</action>
+      <action>Extract from "Senior Developer Review (AI)" section:
+        - Review outcome (Approve/Changes Requested/Blocked)
+        - Review date
+        - Total action items with checkboxes (count checked vs unchecked)
+        - Severity breakdown (High/Med/Low counts)
+      </action>
+      <action>Count unchecked [ ] review follow-up tasks in "Review Follow-ups (AI)" subsection</action>
+      <action>Store list of unchecked review items as {{pending_review_items}}</action>
+
+      <output>⏯️ **Resuming Story After Code Review** ({{review_date}})
+
+        **Review Outcome:** {{review_outcome}}
+        **Action Items:** {{unchecked_review_count}} remaining to address
+        **Priorities:** {{high_count}} High, {{med_count}} Medium, {{low_count}} Low
+
+        **Strategy:** Will prioritize review follow-up tasks (marked [AI-Review]) before continuing with regular tasks.
+      </output>
+    </check>
+
+    <check if="Senior Developer Review section does NOT exist">
+      <action>Set review_continuation = false</action>
+      <action>Set {{pending_review_items}} = empty</action>
+
+      <output>🚀 **Starting Fresh Implementation**
+
+        Story: {{story_key}}
+        Story Status: {{current_status}}
+        First incomplete task: {{first_task_description}}
+      </output>
+    </check>
+  </step>
+
+  <step n="4" goal="Mark story in-progress" tag="sprint-status">
+    <action>If story file YAML frontmatter already contains `baseline_commit`, preserve the existing value and do not overwrite it</action>
+
+    <check if="{{sprint_status}} file exists">
+      <action>Load the FULL file: {{sprint_status}}</action>
+      <action>Read all development_status entries to find {{story_key}}</action>
+      <action>Set {{current_status}} to development_status[{{story_key}}]</action>
+    </check>
+
+    <check if="{{sprint_status}} file does NOT exist">
+      <action>Set {{current_status}} to the story file Status section value</action>
+    </check>
+
+    <check if="{{current_status}} == 'ready-for-dev' AND story file YAML frontmatter does NOT contain baseline_commit">
+      <action>Run `git rev-parse HEAD` to capture current commit into {{baseline_commit}}; if git/version control is unavailable, set {{baseline_commit}} = `NO_VCS`</action>
+      <action>If story file YAML frontmatter exists, add `baseline_commit: {{baseline_commit}}` to the frontmatter</action>
+      <action>If story file has no YAML frontmatter, create frontmatter at the top containing only `baseline_commit: {{baseline_commit}}`</action>
+    </check>
+
+    <check if="{{sprint_status}} file exists">
+      <check if="{{current_status}} == 'ready-for-dev' OR (review_continuation == true AND {{current_status}} != 'in-progress')">
+        <action>Update the story in the sprint status report to = "in-progress"</action>
+        <action>Update last_updated field to current date</action>
+        <output>🚀 Starting work on story {{story_key}}
+          Status updated: {{current_status}} → in-progress
+        </output>
+      </check>
+
+      <check if="{{current_status}} == 'in-progress'">
+        <output>⏯️ Resuming work on story {{story_key}}
+          Story is already marked in-progress
+        </output>
+      </check>
+
+      <check if="{{current_status}} is neither ready-for-dev nor in-progress">
+        <output>⚠️ Unexpected story status: {{current_status}}
+          Expected ready-for-dev or in-progress. Continuing anyway...
+        </output>
+      </check>
+
+      <action>Store {{current_sprint_status}} for later use</action>
+    </check>
+
+    <check if="{{sprint_status}} file does NOT exist">
+      <output>ℹ️ No sprint status file exists - story progress will be tracked in story file only</output>
+      <action>Set {{current_sprint_status}} = "no-sprint-tracking"</action>
+    </check>
+  </step>
+
+  <step n="5" goal="Implement task following red-green-refactor cycle">
+    <critical>FOLLOW THE STORY FILE TASKS/SUBTASKS SEQUENCE EXACTLY AS WRITTEN - NO DEVIATION</critical>
+
+    <action>Review the current task/subtask from the story file - this is your authoritative implementation guide</action>
+    <action>Plan implementation following red-green-refactor cycle</action>
+
+    <!-- RED PHASE -->
+    <action>Write FAILING tests first for the task/subtask functionality</action>
+    <action>Confirm tests fail before implementation - this validates test correctness</action>
+
+    <!-- GREEN PHASE -->
+    <action>Implement MINIMAL code to make tests pass</action>
+    <action>Run tests to confirm they now pass</action>
+    <action>Handle error conditions and edge cases as specified in task/subtask</action>
+
+    <!-- REFACTOR PHASE -->
+    <action>Improve code structure while keeping tests green</action>
+    <action>Ensure code follows architecture patterns and coding standards from Dev Notes</action>
+
+    <action>Document technical approach and decisions in Dev Agent Record → Implementation Plan</action>
+
+    <action if="new dependencies required beyond story specifications">HALT: "Additional dependencies need user approval"</action>
+    <action if="3 consecutive implementation failures occur">HALT and request guidance</action>
+    <action if="required configuration is missing">HALT: "Cannot proceed without necessary configuration files"</action>
+
+    <critical>NEVER implement anything not mapped to a specific task/subtask in the story file</critical>
+    <critical>NEVER proceed to next task until current task/subtask is complete AND tests pass</critical>
+    <critical>Execute continuously without pausing until all tasks/subtasks are complete or explicit HALT condition</critical>
+    <critical>Do NOT propose to pause for review until Step 9 completion gates are satisfied</critical>
+  </step>
+
+  <step n="6" goal="Author comprehensive tests">
+    <action>Create unit tests for business logic and core functionality introduced/changed by the task</action>
+    <action>Add integration tests for component interactions specified in story requirements</action>
+    <action>Include end-to-end tests for critical user flows when story requirements demand them</action>
+    <action>Cover edge cases and error handling scenarios identified in story Dev Notes</action>
+  </step>
+
+  <step n="7" goal="Run validations and tests">
+    <action>Determine how to run tests for this repo (infer test framework from project structure)</action>
+    <action>Run all existing tests to ensure no regressions</action>
+    <action>Run the new tests to verify implementation correctness</action>
+    <action>Run linting and code quality checks if configured in project</action>
+    <action>Validate implementation meets ALL story acceptance criteria; enforce quantitative thresholds explicitly</action>
+    <action if="regression tests fail">STOP and fix before continuing - identify breaking changes immediately</action>
+    <action if="new tests fail">STOP and fix before continuing - ensure implementation correctness</action>
+  </step>
+
+  <step n="8" goal="Validate and mark task complete ONLY when fully done">
+    <critical>NEVER mark a task complete unless ALL conditions are met - NO LYING OR CHEATING</critical>
+
+    <!-- VALIDATION GATES -->
+    <action>Verify ALL tests for this task/subtask ACTUALLY EXIST and PASS 100%</action>
+    <action>Confirm implementation matches EXACTLY what the task/subtask specifies - no extra features</action>
+    <action>Validate that ALL acceptance criteria related to this task are satisfied</action>
+    <action>Run full test suite to ensure NO regressions introduced</action>
+
+    <!-- REVIEW FOLLOW-UP HANDLING -->
+    <check if="task is review follow-up (has [AI-Review] prefix)">
+      <action>Extract review item details (severity, description, related AC/file)</action>
+      <action>Add to resolution tracking list: {{resolved_review_items}}</action>
+
+      <!-- Mark task in Review Follow-ups section -->
+      <action>Mark task checkbox [x] in "Tasks/Subtasks → Review Follow-ups (AI)" section</action>
+
+      <!-- CRITICAL: Also mark corresponding action item in review section -->
+      <action>Find matching action item in "Senior Developer Review (AI) → Action Items" section by matching description</action>
+      <action>Mark that action item checkbox [x] as resolved</action>
+
+      <action>Add to Dev Agent Record → Completion Notes: "✅ Resolved review finding [{{severity}}]: {{description}}"</action>
+    </check>
+
+    <!-- ONLY MARK COMPLETE IF ALL VALIDATION PASS -->
+    <check if="ALL validation gates pass AND tests ACTUALLY exist and pass">
+      <action>ONLY THEN mark the task (and subtasks) checkbox with [x]</action>
+      <action>Update File List section with ALL new, modified, or deleted files (paths relative to repo root)</action>
+      <action>Add completion notes to Dev Agent Record summarizing what was ACTUALLY implemented and tested</action>
+    </check>
+
+    <check if="ANY validation fails">
+      <action>DO NOT mark task complete - fix issues first</action>
+      <action>HALT if unable to fix validation failures</action>
+    </check>
+
+    <check if="review_continuation == true and {{resolved_review_items}} is not empty">
+      <action>Count total resolved review items in this session</action>
+      <action>Add Change Log entry: "Addressed code review findings - {{resolved_count}} items resolved (Date: {{date}})"</action>
+    </check>
+
+    <action>Save the story file</action>
+    <action>Determine if more incomplete tasks remain</action>
+    <action if="more tasks remain">
+      <goto step="5">Next task</goto>
+    </action>
+    <action if="no tasks remain">
+      <goto step="9">Completion</goto>
+    </action>
+  </step>
+
+  <step n="9" goal="Story completion and mark for review" tag="sprint-status">
+    <action>Verify ALL tasks and subtasks are marked [x] (re-scan the story document now)</action>
+    <action>Run the full regression suite (do not skip)</action>
+    <action>Confirm File List includes every changed file</action>
+    <action>Execute enhanced definition-of-done validation</action>
+    <action>Update the story Status to: "review"</action>
+
+    <!-- Enhanced Definition of Done Validation -->
+    <action>Validate definition-of-done checklist with essential requirements:
+      - All tasks/subtasks marked complete with [x]
+      - Implementation satisfies every Acceptance Criterion
+      - Unit tests for core functionality added/updated
+      - Integration tests for component interactions added when required
+      - End-to-end tests for critical flows added when story demands them
+      - All tests pass (no regressions, new tests successful)
+      - Code quality checks pass (linting, static analysis if configured)
+      - File List includes every new/modified/deleted file (relative paths)
+      - Dev Agent Record contains implementation notes
+      - Change Log includes summary of changes
+      - Only permitted story sections were modified
+    </action>
+
+    <!-- Mark story ready for review - sprint status conditional -->
+    <check if="{sprint_status} file exists AND {{current_sprint_status}} != 'no-sprint-tracking'">
+      <action>Load the FULL file: {sprint_status}</action>
+      <action>Find development_status key matching {{story_key}}</action>
+      <action>Verify current status is "in-progress" (expected previous state)</action>
+      <action>Update development_status[{{story_key}}] = "review"</action>
+      <action>Update last_updated field to current date</action>
+      <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+      <output>✅ Story status updated to "review" in sprint-status.yaml</output>
+    </check>
+
+    <check if="{sprint_status} file does NOT exist OR {{current_sprint_status}} == 'no-sprint-tracking'">
+      <output>ℹ️ Story status updated to "review" in story file (no sprint tracking configured)</output>
+    </check>
+
+    <check if="story key not found in sprint status">
+      <output>⚠️ Story file updated, but sprint-status update failed: {{story_key}} not found
+
+        Story status is set to "review" in file, but sprint-status.yaml may be out of sync.
+      </output>
+    </check>
+
+    <!-- Final validation gates -->
+    <action if="any task is incomplete">HALT - Complete remaining tasks before marking ready for review</action>
+    <action if="regression failures exist">HALT - Fix regression issues before completing</action>
+    <action if="File List is incomplete">HALT - Update File List with all changed files</action>
+    <action if="definition-of-done validation fails">HALT - Address DoD failures before completing</action>
+  </step>
+
+  <step n="10" goal="Completion communication and user support">
+    <action>Execute the enhanced definition-of-done checklist using the validation framework</action>
+    <action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
+
+    <action>Communicate to {user_name} that story implementation is complete and ready for review</action>
+    <action>Summarize key accomplishments: story ID, story key, title, key changes made, tests added, files modified</action>
+    <action>Provide the story file path and current status (now "review")</action>
+
+    <action>Based on {user_skill_level}, ask if user needs any explanations about:
+      - What was implemented and how it works
+      - Why certain technical decisions were made
+      - How to test or verify the changes
+      - Any patterns, libraries, or approaches used
+      - Anything else they'd like clarified
+    </action>
+
+    <check if="user asks for explanations">
+      <action>Provide clear, contextual explanations tailored to {user_skill_level}</action>
+      <action>Use examples and references to specific code when helpful</action>
+    </check>
+
+    <action>Once explanations are complete (or user indicates no questions), suggest logical next steps</action>
+    <action>Recommended next steps (flexible based on project setup):
+      - Review the implemented story and test the changes
+      - Verify all acceptance criteria are met
+      - Ensure deployment readiness if applicable
+      - Run `code-review` workflow for peer review
+      - Optional: If Test Architect module installed, run `/bmad:tea:automate` to expand guardrail tests
+    </action>
+
+    <output>💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story.</output>
+    <check if="{sprint_status} file exists">
+      <action>Suggest checking {sprint_status} to see project progress</action>
+    </check>
+    <action>Remain flexible - allow user to choose their own path or ask for other assistance</action>
+  <action>Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.</action>
+  </step>
+
+</workflow>
diff --git a/.claude/skills/bmad-dev-story/checklist.md b/.claude/skills/bmad-dev-story/checklist.md
new file mode 100644
index 0000000..86d6e9b
--- /dev/null
+++ b/.claude/skills/bmad-dev-story/checklist.md
@@ -0,0 +1,80 @@
+---
+title: 'Enhanced Dev Story Definition of Done Checklist'
+validation-target: 'Story markdown ({{story_path}})'
+validation-criticality: 'HIGHEST'
+required-inputs:
+  - 'Story markdown file with enhanced Dev Notes containing comprehensive implementation context'
+  - 'Completed Tasks/Subtasks section with all items marked [x]'
+  - 'Updated File List section with all changed files'
+  - 'Updated Dev Agent Record with implementation notes'
+optional-inputs:
+  - 'Test results output'
+  - 'CI logs'
+  - 'Linting reports'
+validation-rules:
+  - 'Only permitted story sections modified: Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, Status'
+  - 'All implementation requirements from story Dev Notes must be satisfied'
+  - 'Definition of Done checklist must pass completely'
+  - 'Enhanced story context must contain sufficient technical guidance'
+---
+
+# 🎯 Enhanced Definition of Done Checklist
+
+**Critical validation:** Story is truly ready for review only when ALL items below are satisfied
+
+## 📋 Context & Requirements Validation
+
+- [ ] **Story Context Completeness:** Dev Notes contains ALL necessary technical requirements, architecture patterns, and implementation guidance
+- [ ] **Architecture Compliance:** Implementation follows all architectural requirements specified in Dev Notes
+- [ ] **Technical Specifications:** All technical specifications (libraries, frameworks, versions) from Dev Notes are implemented correctly
+- [ ] **Previous Story Learnings:** Previous story insights incorporated (if applicable) and build upon appropriately
+
+## ✅ Implementation Completion
+
+- [ ] **All Tasks Complete:** Every task and subtask marked complete with [x]
+- [ ] **Acceptance Criteria Satisfaction:** Implementation satisfies EVERY Acceptance Criterion in the story
+- [ ] **No Ambiguous Implementation:** Clear, unambiguous implementation that meets story requirements
+- [ ] **Edge Cases Handled:** Error conditions and edge cases appropriately addressed
+- [ ] **Dependencies Within Scope:** Only uses dependencies specified in story or project-context.md
+
+## 🧪 Testing & Quality Assurance
+
+- [ ] **Unit Tests:** Unit tests added/updated for ALL core functionality introduced/changed by this story
+- [ ] **Integration Tests:** Integration tests added/updated for component interactions when story requirements demand them
+- [ ] **End-to-End Tests:** End-to-end tests created for critical user flows when story requirements specify them
+- [ ] **Test Coverage:** Tests cover acceptance criteria and edge cases from story Dev Notes
+- [ ] **Regression Prevention:** ALL existing tests pass (no regressions introduced)
+- [ ] **Code Quality:** Linting and static checks pass when configured in project
+- [ ] **Test Framework Compliance:** Tests use project's testing frameworks and patterns from Dev Notes
+
+## 📝 Documentation & Tracking
+
+- [ ] **File List Complete:** File List includes EVERY new, modified, or deleted file (paths relative to repo root)
+- [ ] **Dev Agent Record Updated:** Contains relevant Implementation Notes and/or Debug Log for this work
+- [ ] **Change Log Updated:** Change Log includes clear summary of what changed and why
+- [ ] **Review Follow-ups:** All review follow-up tasks (marked [AI-Review]) completed and corresponding review items marked resolved (if applicable)
+- [ ] **Story Structure Compliance:** Only permitted sections of story file were modified
+
+## 🔚 Final Status Verification
+
+- [ ] **Story Status Updated:** Story Status set to "review"
+- [ ] **Sprint Status Updated:** Sprint status updated to "review" (when sprint tracking is used)
+- [ ] **Quality Gates Passed:** All quality checks and validations completed successfully
+- [ ] **No HALT Conditions:** No blocking issues or incomplete work remaining
+- [ ] **User Communication Ready:** Implementation summary prepared for user review
+
+## 🎯 Final Validation Output
+
+```
+Definition of Done: {{PASS/FAIL}}
+
+✅ **Story Ready for Review:** {{story_key}}
+📊 **Completion Score:** {{completed_items}}/{{total_items}} items passed
+🔍 **Quality Gates:** {{quality_gates_status}}
+📋 **Test Results:** {{test_results_summary}}
+📝 **Documentation:** {{documentation_status}}
+```
+
+**If FAIL:** List specific failures and required actions before story can be marked Ready for Review
+
+**If PASS:** Story is fully ready for code review and production consideration
diff --git a/.claude/skills/bmad-dev-story/customize.toml b/.claude/skills/bmad-dev-story/customize.toml
new file mode 100644
index 0000000..e2fac26
--- /dev/null
+++ b/.claude/skills/bmad-dev-story/customize.toml
@@ -0,0 +1,44 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-dev-story. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All stories must include testable acceptance criteria."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+  "Never add epic or story references as inline code comments (e.g. # Epic: X, # Story: PROJ-42).",
+  "Code comments explain why, not what — no AI workflow metadata, planning refs, or story tracking in source code.",
+  "Generated code must be production-ready: clean, minimal, and free of AI-generated noise.",
+]
+
+# Scalar: executed when the workflow reaches its final step,
+# after the story implementation is complete and status is updated. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-document-project/SKILL.md b/.claude/skills/bmad-document-project/SKILL.md
new file mode 100644
index 0000000..bfe7665
--- /dev/null
+++ b/.claude/skills/bmad-document-project/SKILL.md
@@ -0,0 +1,14 @@
+---
+name: bmad-document-project
+description: 'Deprecated — forwards to bmad-project-context. Use when the user says "document this project" or "generate project docs"'
+---
+
+# DEPRECATED — forwards to bmad-project-context
+
+Tell the user two things.
+
+First: this skill is deprecated. Generating documentation volume about a codebase made agents worse, not better — agents read code more accurately than prose describing code, and the generated set was stale on arrival. `bmad-project-context` owns what remains useful: a small verified block in the repo's `AGENTS.md` carrying what the code cannot say — required policy, conventions that differ from defaults, what running the project takes that no config file states, and known pitfalls.
+
+Second, so they are not surprised by what they get: the deeper "explain this system, its rationale and its history" material is a different altitude and is not part of that block. It is coming as its own capability. If that is what they were after, say so plainly rather than producing a thin substitute.
+
+Then invoke `bmad-project-context` with **setup** intent, forwarding the user's original request and any paths or documents they supplied, verbatim. It takes the workflow from here.
diff --git a/.claude/skills/bmad-domain-research/SKILL.md b/.claude/skills/bmad-domain-research/SKILL.md
new file mode 100644
index 0000000..7b42c2e
--- /dev/null
+++ b/.claude/skills/bmad-domain-research/SKILL.md
@@ -0,0 +1,14 @@
+---
+name: bmad-domain-research
+description: 'Deprecated — forwards to bmad-deep-recon (domain type).'
+---
+
+# DEPRECATED — forwards to bmad-deep-recon (domain type)
+
+This skill was consolidated into `bmad-deep-recon`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-domain-research.toml` override files keep working. New work should invoke `bmad-deep-recon` directly — it drafts deep-research prompts for outside tools, processes finished reports into downstream-ready summaries, and runs research directly, across market, domain, technical, competitive, user-voice, and academic-lit types (plus a select shape for choose-between decisions and custom types).
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-domain-research.toml` and `bmad-domain-research.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+2. Emit a deprecation notice to the user (in their configured communication language): `bmad-domain-research` is deprecated and forwards to `bmad-deep-recon` with the domain type. To silence this notice and access the full new surface (draft/process/run modes, research types, verification levels, HTML briefing, handoffs), migrate `_bmad/custom/bmad-domain-research.toml` to `_bmad/custom/bmad-deep-recon.toml` and invoke `bmad-deep-recon` directly.
+3. Invoke `bmad-deep-recon` with: **research type** `domain` (skip its type inference), the four legacy fields above as pre-resolved values, and the user's original input verbatim. `bmad-deep-recon` takes the workflow from here — do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-edit-prd/SKILL.md b/.claude/skills/bmad-edit-prd/SKILL.md
new file mode 100644
index 0000000..dc9c5d3
--- /dev/null
+++ b/.claude/skills/bmad-edit-prd/SKILL.md
@@ -0,0 +1,30 @@
+---
+name: bmad-edit-prd
+description: 'Deprecated — forwards to bmad-prd (update intent).'
+---
+
+# DEPRECATED — forwards to bmad-prd (update intent)
+
+This skill was consolidated into `bmad-prd`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-edit-prd.toml` override files keep working. New work should invoke `bmad-prd` directly — it detects create / update / validate intent from the conversation.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-edit-prd.toml` and `bmad-edit-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+
+2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+
+3. Emit a deprecation notice to the user in `{communication_language}`:
+
+   > Notice: `bmad-edit-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with update intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`, `prd_output_path`, `run_folder_pattern`), migrate `_bmad/custom/bmad-edit-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+
+4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
+
+   - **Intent:** `update` — skip `bmad-prd`'s usual intent detection step.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `prd_output_path`, `run_folder_pattern`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+     - `activation_steps_prepend` = the resolved value from step 1
+     - `activation_steps_append` = the resolved value from step 1
+     - `persistent_facts` = the resolved value from step 1
+     - `on_complete` = the resolved value from step 1
+   - **Original user input:** forward whatever the user said when invoking this skill verbatim (the target PRD path, the change signal, etc.).
+
+   `bmad-prd` takes the workflow from here. Do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-edit-prd/customize.toml b/.claude/skills/bmad-edit-prd/customize.toml
new file mode 100644
index 0000000..1886d4a
--- /dev/null
+++ b/.claude/skills/bmad-edit-prd/customize.toml
@@ -0,0 +1,42 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-edit-prd. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All PRDs must include a regulatory-risk section."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step E-4 (Complete & Validate) and the
+# user exits via [S] Summary or [X] Exit — not on [V] Validate (which chains to
+# bmad-validate-prd) or [E] Edit More (which loops back). Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-editorial-review-prose/SKILL.md b/.claude/skills/bmad-editorial-review-prose/SKILL.md
new file mode 100644
index 0000000..cdc3565
--- /dev/null
+++ b/.claude/skills/bmad-editorial-review-prose/SKILL.md
@@ -0,0 +1,6 @@
+---
+name: bmad-editorial-review-prose
+description: 'Deprecated — forwards to bmad-review.'
+---
+
+Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `prose` lens, passing through the same inputs and any `also_consider` areas. Present the findings in the legacy shape: a three-column markdown table `| Original Text | Revised Text | Changes |` — no Pass column, no preamble above the table. If no issues are found, output exactly: `No editorial issues identified`.
diff --git a/.claude/skills/bmad-editorial-review-structure/SKILL.md b/.claude/skills/bmad-editorial-review-structure/SKILL.md
new file mode 100644
index 0000000..f8fc670
--- /dev/null
+++ b/.claude/skills/bmad-editorial-review-structure/SKILL.md
@@ -0,0 +1,6 @@
+---
+name: bmad-editorial-review-structure
+description: 'Deprecated — forwards to bmad-review.'
+---
+
+Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `structure` lens, passing through the same inputs and any `also_consider` areas. Present the findings in the legacy report shape: a `## Document Summary` block (purpose, audience, reader type, structure model, current length), a `## Recommendations` list of numbered `[CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE]` entries each with rationale and word impact, and a closing `## Summary` (total recommendations, estimated reduction) — not the findings table. If no structural issues are found, output exactly: `No substantive changes recommended`.
diff --git a/.claude/skills/bmad-editorial-review/SKILL.md b/.claude/skills/bmad-editorial-review/SKILL.md
new file mode 100644
index 0000000..a06c0e3
--- /dev/null
+++ b/.claude/skills/bmad-editorial-review/SKILL.md
@@ -0,0 +1,6 @@
+---
+name: bmad-editorial-review
+description: 'Deprecated — forwards to bmad-review.'
+---
+
+Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with the `structure` and `prose` lenses — both, structure first, so prose runs on top of the structure findings — unless the caller asked for a structure-only or prose-only review, in which case pass only that lens. Pass through any `also_consider` areas, and forward this skill's resolved `[workflow]` fields as pre-resolved values — but only those that resolved to something, since an empty value here means no legacy override exists and bmad-review's own default should stand: `reader_type`, `style_guide`, `review_guidance`, `output_preferences`, `persistent_facts`, `activation_steps_prepend`, `activation_steps_append`, `on_complete`, and `review_output_path` as the report path. Present the findings in the legacy shape: the two-pass findings table `| Pass | Original Text | Revised Text | Changes |` with the purpose/audience read above it and, when the structure pass ran, the reduction summary below it — and no other lens's output.
diff --git a/.claude/skills/bmad-editorial-review/customize.toml b/.claude/skills/bmad-editorial-review/customize.toml
new file mode 100644
index 0000000..d4305d2
--- /dev/null
+++ b/.claude/skills/bmad-editorial-review/customize.toml
@@ -0,0 +1,31 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Legacy override surface for bmad-editorial-review, which is deprecated and
+# forwards to bmad-review's `structure` and `prose` lenses. These keys exist
+# only so overrides written against the old skill keep resolving: the shim
+# resolves them here and passes them to bmad-review as pre-resolved values,
+# which bmad-review honors verbatim over its own.
+#
+# Every field is documented in bmad-review's customize.toml, which is where
+# new customization belongs. Defaults are empty here so the shim contributes
+# nothing of its own — an unset key falls through to bmad-review's default.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-editorial-review.toml         (team)
+#   {project-root}/_bmad/custom/bmad-editorial-review.user.toml    (personal)
+#
+# Overrides merge per BMad structural rules: scalars win, arrays append.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+persistent_facts = []
+review_guidance = []
+on_complete = ""
+output_preferences = ""
+reader_type = ""
+style_guide = ""
+
+# Where the findings table lands; forwarded as bmad-review's report path.
+review_output_path = ""
diff --git a/.claude/skills/bmad-forge-idea/SKILL.md b/.claude/skills/bmad-forge-idea/SKILL.md
new file mode 100644
index 0000000..aaaa6f6
--- /dev/null
+++ b/.claude/skills/bmad-forge-idea/SKILL.md
@@ -0,0 +1,107 @@
+---
+name: bmad-forge-idea
+description: Pressure-test an idea through persona-driven interrogation until it hardens, proves out, or dies cheaply. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'.
+---
+
+# BMad Forge Idea
+
+## Overview
+
+Take a half-formed idea and pressure-test it in conversation, while changing your mind is still cheap, until it becomes something the user can act on with conviction or reject. The main risk is what the user has not examined yet: unchecked assumptions and unresolved decisions usually become more expensive problems later.
+
+The main goal is better thinking, not producing an artifact. Strengthening an idea, rejecting it, or thinking it through more clearly are all complete outcomes. Writing `forged-idea.md` to hand off to another workflow is optional. Do not steer the conversation toward "shall we build it?"
+
+This skill can be used on many kinds of ideas. When the idea is about a product or feature, what survives may be written to `forged-idea.md` for later planning.
+
+Lead by questioning, not lecturing. Ask one question at a time, press on weak points, and do not let vague claims pass without examination.
+
+## Conventions
+
+- Scripts live in two places — run each from the exact path written, never assume co-location: the shared core scripts (`memlog.py`, `resolve_customization.py`, `resolve_config.py`) are installed by BMad core at `{project-root}/_bmad/scripts/` and are never bundled here; this skill's own `resolve_personas.py` is at `{skill-root}/scripts/`.
+- `{workflow.<name>}` resolves to fields in the merged `customize.toml` `[workflow]` table.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly with defaults. Apply the resolved `{workflow.*}` values throughout.
+2. Run each `{workflow.activation_steps_prepend}` entry; treat each `{workflow.persistent_facts}` entry as foundational context (`file:` entries load their contents, `skill:` names a skill to consult, others are facts verbatim).
+3. Resolve central config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core`; from the merged JSON read `{user_name}`, `{communication_language}`, `{output_folder}`. On failure use neutral defaults; never block. Greet `{user_name}` in `{communication_language}` and stay in it.
+4. Note whether a BMad persona is already active in this conversation — the user loaded one (e.g. the analyst, the storyteller) and invoked the forge from within it. If so, that persona leads the session, in voice, throughout.
+5. Resume: glob `{workflow.forge_output_path}/**/.memlog.md` (recursive, so it still finds sessions when `run_folder_pattern` is overridden to nest paths) and read only each match's frontmatter to find any whose `status` is not `complete`. Offer to resume one — then read its full memlog once to rebuild state and continue append-only — or to start fresh.
+6. Run each `{workflow.activation_steps_append}` entry.
+
+## Open the session
+
+Start by scrutinizing the idea, not endorsing it.
+
+### Discover intent
+Identify: 
+- the subject idea, 
+- the user's goal for the session, 
+- whether the idea is new or a change to an existing project
+
+If any of these are already clear from the prompt that invoked this skill or previous context, ask the user to confirm and continue. 
+
+Otherwise ask for what's missing, in order: 
+- what is the idea?
+- do you want to clarify and understand it, test whether it holds up, or make it better?
+- is it a new idea or a change to an existing project? If the latter, what project is it, and where can I find its files or other relevant materials?
+
+### Steering the conversation
+
+Tell the user they can say **"attack this"**, **"defend this"**, or **"switch roles"** at any time to change how the current idea is argued. In attack mode, do not agree with the idea; look for contradictions, weak assumptions, and failure cases. In defend mode, argue for the strongest version of the idea. Tell the user they can also name a persona or party at any time to change who participates in the session.
+
+### Set up the session
+
+Derive a kebab-case `{slug}` for the idea and bind the session workspace `{workspace} = {workflow.forge_output_path}/{workflow.run_folder_pattern}` (the pattern fills with `{slug}`). Create the memlog once the goal is known:
+`uv run {project-root}/_bmad/scripts/memlog.py init --workspace {workspace} --field idea="<idea>" --field goal="<goal>"`
+
+Tell the user the path; state is on disk now, so the session survives interruption. If init fails, don't abort — run the forge in-conversation and tell the user state won't persist this session.
+
+## The forge
+
+Let the session goal set the first move: for clarifying, pin down terms, boundaries, and assumptions; for testing, go after the central claim first; for making it better, drive each unresolved branch to a concrete decision.
+
+Work one question at a time, in dependency order.
+
+Include your current best answer or hypothesis when it helps the user respond. A concrete proposal is easier to accept, reject, or revise than an open-ended prompt. Find discoverable answers yourself instead of asking.
+
+Do not assume the user's terms are precise. When a term is fuzzy or overloaded, name the ambiguity and ask for a precise choice before continuing. For example, do not let `user`, `buyer`, and `payer` collapse into one entity unless the idea actually requires that.
+
+For ideas about an existing project, treat the project's files and materials as the source of truth. Do not accept a label or summary as proof. Find the relevant material yourself and check the user's claim against it. If the material contradicts the user's claim, stop and resolve that before continuing.
+
+When a branch resolves, pause before moving on. Give the user a chance to raise any remaining concern.
+
+Do not use agreement or praise to make the interaction smoother; they lower pressure and lead to shallower thinking. Agreement is allowed only when it helps the user think better. Praise is noise. Continued engagement and ego-stroking are not objectives. In attack mode, never agree with the idea until the user ends the mode. For each answer, either challenge the weak point or build on the strong point, whichever helps the user think better.
+
+Capture as you go — each decision, assumption, crack, kill, and locked idea, one bullet in the user's meaning:
+`uv run {project-root}/_bmad/scripts/memlog.py append --workspace {workspace} --type <decision|assumption|crack|kill|direction|lock|note> --text "<gist>"`
+A `lock` is an idea the user hardens — settled, not to be reopened; locks are what `forged-idea.md` is distilled from. Don't read the memlog back except on resume. If the user raises a different branch, capture it and stay put — the loop and the stray insight both survive.
+
+## The personas
+
+If a BMad persona was already active when the forge started, keep that persona as the lead voice.
+
+Resolve the available persona pool once, as soon as the goal is known:
+`uv run {skill-root}/scripts/resolve_personas.py --project-root {project-root} --skill {skill-root}`
+The script returns installed BMad agents (`agents`), user-defined personas (`members`), and saved parties (`parties`). Parties may include a `scene`; some are open-cast. This gives you the same roster information as `bmad-party-mode` without invoking it.
+
+Each turn uses two voices:
+- **One available persona** — choose an installed agent or user-defined persona whose expertise fits the current branch. Vary this voice every few turns; do not let one voice dominate. If the user names a specific persona, use it. If the user calls a saved party, use the whole party and its scene. If the user asks to go one-on-one, use only the requested persona. If no pool is available, generate this voice yourself.
+- **One generated persona** — create a fresh outside voice, such as a competitor, buyer, finance reviewer, domain expert, or critic. Give it a name and enough characterization to keep its viewpoint distinct.
+
+Use these voices in character to pressure-test the current branch: find sharper objections, missing assumptions, and stronger defenses. Cross-examine them for what matters, then synthesize their input into your next question. Do not let the session turn into a panel debate or persona performance.
+
+Voice the personas yourself by default. Spawn separate agents only when a branch needs independent reasoning that should not be influenced by one shared voice.
+
+## Exits
+
+The session can end in three valid states:
+
+- **Hardened** — the idea is stronger and specific enough to use. Distill the memlog into `{workspace}/forged-idea.md`. Keep it extremely short: only the decisions, rejected options, and reasons that matter downstream, in the user's meaning. Do not write a prose summary, template, or conversation recap. If it reads like a document, it is too long. If planning or dev skills are installed (`bmad-spec`, `bmad-prd`, `bmad-prfaq`, `bmad-build`), offer the file as their input; if none are, the file stands on its own — never treat a missing skill as an error.
+- **Killed** — the idea does not hold up. Say so plainly and record why. Finding that out early is a valid outcome.
+- **Clearer** — the user understands the idea better, but there is no hardened idea to hand off. Leave the memlog as the record; no `forged-idea.md` is needed.
+
+Always render `{workspace}/forge-report.html` as a self-contained HTML file the user can open, with inline CSS and an inline-SVG seal or stamp. Summarize the outcome, the locked decisions, what was rejected and why, and the weak points that survived scrutiny, in the user's meaning. Credit the personas and parties that pressure-tested the idea by name, icon, and voice. Render a prominent wax-seal-style or stamped outcome mark, matched to the result: `HARDENED`, an `Idea Death Certificate` stamped `KILLED` with the cause of death, or `CLARIFIED`. Tell the user the path.
+
+Flip the status at the end: `uv run {project-root}/_bmad/scripts/memlog.py set --workspace {workspace} --key status --value complete`.
+If `{workflow.on_complete}` is non-empty, run all instructions in order.
diff --git a/.claude/skills/bmad-forge-idea/customize.toml b/.claude/skills/bmad-forge-idea/customize.toml
new file mode 100644
index 0000000..98949e2
--- /dev/null
+++ b/.claude/skills/bmad-forge-idea/customize.toml
@@ -0,0 +1,42 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-forge-idea.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-forge-idea.toml        (team)
+#   {project-root}/_bmad/custom/bmad-forge-idea.user.toml   (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays: append
+
+# Steps to run before the standard activation (config load, greet).
+activation_steps_prepend = []
+
+# Steps to run after greet but before the session begins.
+activation_steps_append = []
+
+# Persistent facts the interrogator keeps in mind for the whole session
+# (domain constraints, house rules, what's off the table). Each entry is a
+# literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed
+# path/glob whose contents are loaded as facts. Default loads project-context.md
+# when one exists (e.g. from bmad-generate-project-context), so the forge grounds
+# in the project's tech, domain, and constraints without re-asking.
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Executed when the session completes. Scalar or array of instructions. Empty for none.
+on_complete = []
+
+# Parent folder for all forge sessions. Each session gets its own run
+# folder underneath (see run_folder_pattern). Lands directly under
+# {output_folder} so the forge works in core-only installs.
+forge_output_path = "{output_folder}/forge"
+
+# Run-folder pattern inside forge_output_path. Resolved against the
+# idea-derived slug at activation. Same slug = same folder, so resuming
+# an idea reuses its memlog. Override to add {date} or other components
+# if a fresh dated history per run is preferred.
+run_folder_pattern = "{slug}"
diff --git a/.claude/skills/bmad-forge-idea/scripts/resolve_personas.py b/.claude/skills/bmad-forge-idea/scripts/resolve_personas.py
new file mode 100644
index 0000000..92bc129
--- /dev/null
+++ b/.claude/skills/bmad-forge-idea/scripts/resolve_personas.py
@@ -0,0 +1,275 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Resolve the personas and parties the forge can bring into the room.
+
+The forge cross-examines witnesses: the installed BMAD agents, plus any
+custom personas and party groups the user has authored for `bmad-party-mode`.
+This surfaces all of them in one shot so the orchestrator never has to ask
+"who's available?" — it just intermixes whoever fits the branch, alongside
+any persona the user names on the fly.
+
+What it returns (JSON, stdout):
+  * agents   — the installed BMAD roster: the default room, always present.
+  * members  — extra custom personas in the pool (party_members the user
+               defined that aren't already an installed slot).
+  * parties  — the user's named party groups, members resolved to brief
+               entries; open-cast groups (scene names a pool, no roster)
+               are flagged.
+  * default_party — the group id pinned as party-mode's default, if any.
+
+Discovery is best-effort and never blocks the forge. The installed roster
+comes from the core resolver; custom personas/parties come from
+`bmad-party-mode`'s resolved customization when that skill is found beside
+this one, else from the user's override TOMLs read directly. Anything that
+can't be resolved is simply omitted and flagged, never fatal.
+
+Stdlib only (Python 3.11+ for tomllib).
+
+  resolve_personas.py --project-root P --skill S
+"""
+
+import argparse
+import json
+import subprocess
+import sys
+from pathlib import Path
+
+try:
+    import tomllib
+except ImportError:  # pragma: no cover - guarded for <3.11
+    sys.stderr.write("error: Python 3.11+ is required (stdlib `tomllib`).\n")
+    sys.exit(3)
+
+PARTY_SKILL = "bmad-party-mode"
+
+
+def _run_json(cmd):
+    """Run a resolver script and parse its JSON stdout. None on any failure."""
+    try:
+        out = subprocess.run(
+            cmd, capture_output=True, text=True, encoding="utf-8", timeout=60
+        )
+    except (OSError, subprocess.SubprocessError):
+        return None
+    if out.returncode != 0 or not out.stdout.strip():
+        return None
+    try:
+        return json.loads(out.stdout)
+    except json.JSONDecodeError:
+        return None
+
+
+def _load_toml(path: Path):
+    if not path.exists():
+        return {}
+    try:
+        with path.open("rb") as f:
+            data = tomllib.load(f)
+        return data if isinstance(data, dict) else {}
+    except (OSError, tomllib.TOMLDecodeError):
+        return {}
+
+
+def load_agents(project_root: Path):
+    """Installed BMAD agents as {code: entry}. (dict, resolved_ok).
+
+    The core resolver may emit agents as a dict keyed by code or as an array
+    of tables (depending on how the layers merged); normalize both to a dict.
+    """
+    script = project_root / "_bmad" / "scripts" / "resolve_config.py"
+    data = _run_json([sys.executable, str(script), "--project-root", str(project_root), "--key", "agents"])
+    if data is None:
+        return {}, False
+    agents = data.get("agents", {}) or {}
+    if isinstance(agents, list):
+        agents = {a["code"]: a for a in agents if isinstance(a, dict) and a.get("code")}
+    elif not isinstance(agents, dict):
+        agents = {}
+    return agents, True
+
+
+def find_party_skill(project_root: Path, skill_root: Path):
+    """Locate the installed bmad-party-mode skill dir, or None.
+
+    Skills install as siblings, so the party skill is almost always next to
+    this one. A couple of common install roots cover the rest.
+    """
+    candidates = [
+        skill_root.parent / PARTY_SKILL,
+        project_root / ".claude" / "skills" / PARTY_SKILL,
+        project_root / "_bmad" / "skills" / PARTY_SKILL,
+    ]
+    for c in candidates:
+        if (c / "customize.toml").exists():
+            return c
+    return None
+
+
+def load_party_workflow(project_root: Path, party_skill: Path):
+    """Merged [workflow] table for bmad-party-mode (base + user overrides)."""
+    resolver = project_root / "_bmad" / "scripts" / "resolve_customization.py"
+    data = _run_json([sys.executable, str(resolver), "--skill", str(party_skill), "--key", "workflow"])
+    if data is not None and isinstance(data.get("workflow"), dict):
+        return data["workflow"]
+    # Fallback: base customize.toml directly, no override merge.
+    wf = _load_toml(party_skill / "customize.toml").get("workflow", {})
+    return wf if isinstance(wf, dict) else {}
+
+
+def load_party_overrides(project_root: Path):
+    """Custom personas/parties when party-mode itself isn't installed.
+
+    Reads only the user's override TOMLs (team then personal, personal wins on
+    scalars). No base roster exists in this path, so a shallow merge is enough.
+    """
+    custom = project_root / "_bmad" / "custom"
+    team = _load_toml(custom / f"{PARTY_SKILL}.toml").get("workflow", {})
+    user = _load_toml(custom / f"{PARTY_SKILL}.user.toml").get("workflow", {})
+    team = team if isinstance(team, dict) else {}
+    user = user if isinstance(user, dict) else {}
+    merged = dict(team)
+    for key, val in user.items():
+        if isinstance(val, list) and isinstance(merged.get(key), list):
+            merged[key] = merged[key] + val
+        else:
+            merged[key] = val
+    return merged
+
+
+def _alias(code: str) -> str:
+    """Short alias for an installed agent code: bmad-agent-analyst -> analyst."""
+    for prefix in ("bmad-agent-", "bmad-"):
+        if code.startswith(prefix):
+            return code[len(prefix):]
+    return code
+
+
+def build_pool(agents: dict, party_members: list):
+    """One pool keyed by code; custom members override matching installed slots.
+
+    Returns (pool, index, installed_codes, custom_codes):
+      * installed_codes — the default room (installed agents, overrides applied
+        in place); custom-only additions stay in the pool but don't crowd it.
+      * custom_codes — pure-custom personas (no installed slot), the extra
+        faces the forge can summon by name or via a party group.
+    """
+    pool, index, installed_codes, custom_codes = {}, {}, [], []
+
+    def register(code, entry):
+        pool[code] = entry
+        index[code] = code
+        index[code.lower()] = code
+        index[_alias(code).lower()] = code
+        name = entry.get("name")
+        if name:
+            key = name.lower()
+            # A custom rename must not hijack another agent's name lookup.
+            if index.get(key, code) == code:
+                index[key] = code
+
+    for code, info in (agents or {}).items():
+        register(code, {
+            "code": code,
+            "name": info.get("name", code),
+            "icon": info.get("icon", ""),
+            "title": info.get("title", ""),
+            "description": info.get("description", ""),
+            "source": "installed",
+        })
+        installed_codes.append(code)
+
+    for m in (party_members if isinstance(party_members, list) else []):
+        if not isinstance(m, dict):
+            continue
+        code = m.get("code")
+        if not code:
+            continue
+        canonical = index.get(code) or index.get(code.lower()) or code
+        was_installed = canonical in pool
+        # Start from the installed entry so fields the override omits
+        # (icon, title, description) survive.
+        entry = dict(pool.get(canonical, {}))
+        entry.update({"code": canonical, "source": "custom"})
+        for field in ("name", "icon", "title", "persona", "capabilities", "model"):
+            if m.get(field) is not None:
+                entry[field] = m[field]
+        entry.setdefault("name", canonical)
+        register(canonical, entry)
+        if not was_installed:
+            custom_codes.append(canonical)
+
+    return pool, index, installed_codes, custom_codes
+
+
+def _brief(entry):
+    """The slim card the orchestrator needs to cast a persona."""
+    out = {k: entry[k] for k in ("code", "name", "icon", "title", "source") if entry.get(k)}
+    for k in ("description", "persona", "capabilities", "model"):
+        if entry.get(k):
+            out[k] = entry[k]
+    return out
+
+
+def resolve_parties(groups, pool, index):
+    out = []
+    for g in groups or []:
+        if not isinstance(g, dict) or not g.get("id"):
+            continue
+        raw = g.get("members", []) or []
+        members = []
+        for t in raw:
+            key = t if isinstance(t, str) else str(t)
+            code = index.get(key) or index.get(key.lower())
+            if code in pool:
+                members.append(_brief(pool[code]))
+        party = {"id": g["id"], "name": g.get("name", g["id"]), "members": members}
+        if g.get("scene"):
+            party["scene"] = g["scene"]
+        if not raw:
+            party["open_cast"] = True
+        out.append(party)
+    return out
+
+
+def main():
+    ap = argparse.ArgumentParser(description="Resolve forge personas and parties.")
+    ap.add_argument("--project-root", required=True)
+    ap.add_argument("--skill", required=True, help="Path to the bmad-forge-idea skill dir")
+    args = ap.parse_args()
+
+    project_root = Path(args.project_root).resolve()
+    skill_root = Path(args.skill).resolve()
+
+    agents, agents_ok = load_agents(project_root)
+
+    party_skill = find_party_skill(project_root, skill_root)
+    if party_skill is not None:
+        workflow = load_party_workflow(project_root, party_skill)
+    else:
+        workflow = load_party_overrides(project_root)
+
+    pool, index, installed_codes, custom_codes = build_pool(
+        agents, workflow.get("party_members", []))
+    parties = resolve_parties(workflow.get("party_groups", []), pool, index)
+
+    _emit({
+        "agents": [_brief(pool[c]) for c in installed_codes],
+        "members": [_brief(pool[c]) for c in custom_codes],
+        "parties": parties,
+        "default_party": workflow.get("default_party", "") or "",
+        "party_mode_found": party_skill is not None,
+        "agents_resolved": agents_ok,
+    })
+
+
+def _emit(obj):
+    reconfigure = getattr(sys.stdout, "reconfigure", None)
+    if reconfigure is not None:
+        reconfigure(encoding="utf-8")
+    sys.stdout.write(json.dumps(obj, indent=2, ensure_ascii=False) + "\n")
+
+
+if __name__ == "__main__":
+    main()
diff --git a/.claude/skills/bmad-forge-idea/scripts/tests/test_resolve_personas.py b/.claude/skills/bmad-forge-idea/scripts/tests/test_resolve_personas.py
new file mode 100644
index 0000000..4867b0d
--- /dev/null
+++ b/.claude/skills/bmad-forge-idea/scripts/tests/test_resolve_personas.py
@@ -0,0 +1,138 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Unit tests for resolve_personas.py — pool merge, alias, party resolution."""
+
+import sys
+import unittest
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
+import resolve_personas as rp  # noqa: E402
+
+AGENTS = {
+    "bmad-agent-analyst": {"name": "Mary", "icon": "📊", "title": "Analyst"},
+    "bmad-agent-pm": {"name": "John", "icon": "📋", "title": "PM"},
+}
+
+
+class TestAlias(unittest.TestCase):
+    def test_strips_known_prefixes(self):
+        self.assertEqual(rp._alias("bmad-agent-analyst"), "analyst")
+        self.assertEqual(rp._alias("bmad-foo"), "foo")
+
+    def test_passes_through_unprefixed(self):
+        self.assertEqual(rp._alias("morpheus"), "morpheus")
+
+
+class TestBuildPool(unittest.TestCase):
+    def test_installed_become_default_room_indexed_every_way(self):
+        pool, idx, installed, custom = rp.build_pool(AGENTS, [])
+        self.assertEqual(installed, ["bmad-agent-analyst", "bmad-agent-pm"])
+        self.assertEqual(custom, [])
+        self.assertEqual(idx["analyst"], "bmad-agent-analyst")   # alias
+        self.assertEqual(idx["mary"], "bmad-agent-analyst")      # name (ci)
+        self.assertEqual(pool["bmad-agent-analyst"]["source"], "installed")
+
+    def test_pure_custom_member_stays_out_of_default_room(self):
+        pool, _, installed, custom = rp.build_pool(
+            AGENTS, [{"code": "morpheus", "name": "Morpheus", "persona": "riddles"}])
+        self.assertEqual(custom, ["morpheus"])
+        self.assertNotIn("morpheus", installed)
+        self.assertEqual(pool["morpheus"]["persona"], "riddles")
+
+    def test_custom_override_lands_on_installed_slot_not_a_new_face(self):
+        pool, _, installed, custom = rp.build_pool(
+            AGENTS, [{"code": "analyst", "name": "Mary-Custom", "persona": "p"}])
+        self.assertNotIn("analyst", pool)
+        self.assertEqual(custom, [])  # an override is not a new face
+        self.assertEqual(pool["bmad-agent-analyst"]["source"], "custom")
+        self.assertEqual(pool["bmad-agent-analyst"]["name"], "Mary-Custom")
+
+    def test_member_without_code_skipped(self):
+        pool, _, _, custom = rp.build_pool(AGENTS, [{"name": "Nameless"}])
+        self.assertEqual(custom, [])
+        self.assertEqual(set(pool), {"bmad-agent-analyst", "bmad-agent-pm"})
+
+    def test_custom_rename_does_not_hijack_another_agents_name(self):
+        # Override the analyst slot, renaming it to "John" — the PM's name.
+        # The PM's name lookup must survive (last-writer-wins would corrupt it).
+        _, idx, _, _ = rp.build_pool(AGENTS, [{"code": "analyst", "name": "John"}])
+        self.assertEqual(idx["john"], "bmad-agent-pm")
+
+    def test_brief_carries_model_and_capabilities(self):
+        pool, _, _, _ = rp.build_pool(
+            AGENTS, [{"code": "neo", "name": "Neo", "model": "opus", "capabilities": ["x"]}])
+        brief = rp._brief(pool["neo"])
+        self.assertEqual(brief["model"], "opus")
+        self.assertEqual(brief["capabilities"], ["x"])
+
+    def test_non_list_party_members_is_safe(self):
+        pool, _, installed, custom = rp.build_pool(AGENTS, "not-a-list")
+        self.assertEqual(custom, [])
+        self.assertEqual(set(pool), {"bmad-agent-analyst", "bmad-agent-pm"})
+
+
+class TestResolveParties(unittest.TestCase):
+    def setUp(self):
+        self.pool, self.idx, _, _ = rp.build_pool(
+            AGENTS, [{"code": "shark", "name": "Marcus", "title": "CFO"}])
+
+    def test_resolves_members_by_alias_and_custom_code(self):
+        parties = rp.resolve_parties(
+            [{"id": "tank", "name": "Tank", "scene": "hostile",
+              "members": ["shark", "analyst"]}], self.pool, self.idx)
+        self.assertEqual(len(parties), 1)
+        self.assertEqual([m["name"] for m in parties[0]["members"]], ["Marcus", "Mary"])
+        self.assertEqual(parties[0]["scene"], "hostile")
+
+    def test_unknown_member_dropped_silently(self):
+        parties = rp.resolve_parties(
+            [{"id": "g", "members": ["analyst", "ghost"]}], self.pool, self.idx)
+        self.assertEqual([m["name"] for m in parties[0]["members"]], ["Mary"])
+
+    def test_member_resolution_is_case_insensitive(self):
+        # A TOML author naturally writes "Analyst"/"Shark"; the filter accepts
+        # them via the lowercase index, so resolution must too (no KeyError).
+        parties = rp.resolve_parties(
+            [{"id": "g", "members": ["Analyst", "Shark"]}], self.pool, self.idx)
+        self.assertEqual([m["name"] for m in parties[0]["members"]], ["Mary", "Marcus"])
+
+    def test_non_string_member_does_not_crash(self):
+        # Malformed members (int, list) must drop silently, never raise.
+        parties = rp.resolve_parties(
+            [{"id": "g", "members": [123, ["x"], "analyst"]}], self.pool, self.idx)
+        self.assertEqual([m["name"] for m in parties[0]["members"]], ["Mary"])
+
+    def test_open_cast_group_flagged(self):
+        parties = rp.resolve_parties(
+            [{"id": "rebels", "name": "Rebels", "scene": "the Ghost"}], self.pool, self.idx)
+        self.assertTrue(parties[0]["open_cast"])
+        self.assertEqual(parties[0]["members"], [])
+
+    def test_group_without_id_skipped(self):
+        self.assertEqual(rp.resolve_parties([{"name": "no id"}], self.pool, self.idx), [])
+
+
+class TestOverrideMergeFallback(unittest.TestCase):
+    """When party-mode isn't installed, user override TOMLs are read directly."""
+
+    def test_arrays_append_scalars_override(self):
+        import tempfile, os
+        with tempfile.TemporaryDirectory() as d:
+            custom = Path(d) / "_bmad" / "custom"
+            custom.mkdir(parents=True)
+            (custom / "bmad-party-mode.toml").write_text(
+                '[workflow]\ndefault_party = "a"\n'
+                '[[workflow.party_members]]\ncode = "x"\nname = "X"\n')
+            (custom / "bmad-party-mode.user.toml").write_text(
+                '[workflow]\ndefault_party = "b"\n'
+                '[[workflow.party_members]]\ncode = "y"\nname = "Y"\n')
+            wf = rp.load_party_overrides(Path(d))
+            self.assertEqual(wf["default_party"], "b")  # personal wins
+            self.assertEqual([m["code"] for m in wf["party_members"]], ["x", "y"])  # appended
+
+
+if __name__ == "__main__":
+    unittest.main()
diff --git a/.claude/skills/bmad-generate-project-context/SKILL.md b/.claude/skills/bmad-generate-project-context/SKILL.md
new file mode 100644
index 0000000..05eccce
--- /dev/null
+++ b/.claude/skills/bmad-generate-project-context/SKILL.md
@@ -0,0 +1,10 @@
+---
+name: bmad-generate-project-context
+description: 'Deprecated — forwards to bmad-project-context. Use when the user says "generate project context" or "create project context"'
+---
+
+# DEPRECATED — forwards to bmad-project-context
+
+Tell the user: this skill is deprecated — `bmad-project-context` now owns this job. Instead of one generated `project-context.md`, it writes a small verified block inside the repo's `AGENTS.md`, and any existing `project-context.md` is offered up for absorption rather than left orphaned. Invoke `bmad-project-context` next time.
+
+Then invoke `bmad-project-context` with **setup** intent, forwarding the user's original request and any inputs they supplied (architecture doc, spec, standards, preferences), verbatim. It takes the workflow from here.
diff --git a/.claude/skills/bmad-help/SKILL.md b/.claude/skills/bmad-help/SKILL.md
new file mode 100644
index 0000000..25f0c62
--- /dev/null
+++ b/.claude/skills/bmad-help/SKILL.md
@@ -0,0 +1,75 @@
+---
+name: bmad-help
+description: 'Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.'
+---
+
+# BMad Help
+
+## Purpose
+
+Help the user understand where they are in their BMad workflow and what to do next, and also answer broader questions when asked that could be augmented with remote sources such as module documentation sources.
+
+## Desired Outcomes
+
+When this skill completes, the user should:
+
+1. **Know where they are** — which module and phase they're in, what's already been completed
+2. **Know what to do next** — the next recommended and/or required step, with clear reasoning
+3. **Know how to invoke it** — skill name, menu code, action context, and any args that shortcut the conversation
+4. **Get offered a quick start** — when a single skill is the clear next step, offer to run it for the user right now rather than just listing it
+5. **Feel oriented, not overwhelmed** — surface only what's relevant to their current position; don't dump the entire catalog
+6. **Get answers to general questions** — when the question doesn't map to a specific skill, use the module's registered documentation to give a grounded answer
+
+## Data Sources
+
+- **Catalog**: `{project-root}/_bmad/_config/bmad-help.csv` — assembled manifest of all installed module skills
+- **Config**: Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use the merged JSON to resolve `output-location` variables and read `core.communication_language` and `modules.bmm.project_knowledge`. The resolver merges `_bmad/config.toml`, `_bmad/config.user.toml`, `_bmad/custom/config.toml`, and `_bmad/custom/config.user.toml` in that order.
+- **Artifacts**: Files matching `outputs` patterns at resolved `output-location` paths reveal which steps are possibly completed; their content may also provide grounding context for recommendations
+- **Project knowledge**: If `project_knowledge` resolves to an existing path, read it for grounding context. Never fabricate project-specific details.
+- **Module docs**: Rows with `_meta` in the `skill` column carry a URL or path in `output-location` pointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.
+
+## CSV Interpretation
+
+The catalog uses this format:
+
+```
+module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
+```
+
+**Phases** determine the high-level flow:
+- `anytime` — available regardless of workflow state
+- Skills group into folders (`plan`, `ship`; some modules use numbered phases) and flow in order; naming varies by module
+
+**Sequencing** determines recommended ordering within and across phases (these are soft suggestions, not hard gates — see `required` for gating):
+- `preceded-by` — skills that should ideally complete before this one
+- `followed-by` — skills that should ideally run after this one
+- Format: `skill-name` for single-action skills, `skill-name:action` for multi-action skills
+
+**Required gates**:
+- `required=true` items must complete before the user can meaningfully proceed to later phases
+- A phase with no required items is entirely optional — recommend it but be clear about what's actually required next
+
+**Completion detection**:
+- Search resolved output paths for `outputs` patterns
+- Fuzzy-match found files to catalog rows
+- User may also state completion explicitly, or it may be evident from the current conversation
+
+**Descriptions carry routing context** — some contain cycle info and alternate paths (e.g., "back to DS if fixes needed"). Read them as navigation hints, not just display text.
+
+## Response Format
+
+For each recommended item, present:
+- `[menu-code]` **Display name** — e.g., "[PR] PRD"
+- Skill name in backticks — e.g., `bmad-prd`
+- For multi-action skills: action invocation context — e.g., "dev lets run a code review!"
+- Description if present in CSV; otherwise your existing knowledge of the skill suffices
+- Args if available
+
+**Ordering**: Show optional items first, then the next required item. Make it clear which is which.
+
+## Constraints
+
+- Present all output in `{communication_language}`
+- Recommend running each skill in a **fresh context window**
+- Match the user's tone — conversational when they're casual, structured when they want specifics
+- If the active module is ambiguous, retrieve all meta rows remote sources to find relevant info also to help answer their question
diff --git a/.claude/skills/bmad-market-research/SKILL.md b/.claude/skills/bmad-market-research/SKILL.md
new file mode 100644
index 0000000..cd2204e
--- /dev/null
+++ b/.claude/skills/bmad-market-research/SKILL.md
@@ -0,0 +1,14 @@
+---
+name: bmad-market-research
+description: 'Deprecated — forwards to bmad-deep-recon (market type).'
+---
+
+# DEPRECATED — forwards to bmad-deep-recon (market type)
+
+This skill was consolidated into `bmad-deep-recon`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-market-research.toml` override files keep working. New work should invoke `bmad-deep-recon` directly — it drafts deep-research prompts for outside tools, processes finished reports into downstream-ready summaries, and runs research directly, across market, domain, technical, competitive, user-voice, and academic-lit types (plus a select shape for choose-between decisions and custom types).
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-market-research.toml` and `bmad-market-research.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+2. Emit a deprecation notice to the user (in their configured communication language): `bmad-market-research` is deprecated and forwards to `bmad-deep-recon` with the market type. To silence this notice and access the full new surface (draft/process/run modes, research types, verification levels, HTML briefing, handoffs), migrate `_bmad/custom/bmad-market-research.toml` to `_bmad/custom/bmad-deep-recon.toml` and invoke `bmad-deep-recon` directly.
+3. Invoke `bmad-deep-recon` with: **research type** `market` (skip its type inference), the four legacy fields above as pre-resolved values, and the user's original input verbatim. `bmad-deep-recon` takes the workflow from here — do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-party-mode/SKILL.md b/.claude/skills/bmad-party-mode/SKILL.md
new file mode 100644
index 0000000..8455fa3
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/SKILL.md
@@ -0,0 +1,60 @@
+---
+name: bmad-party-mode
+description: 'Orchestrates lively group discussions between installed BMAD agents or custom personas, and helps author custom parties. Use when the user requests party mode, a roundtable, or multiple agent perspectives — or wants to create/configure a party, define personas, or build an AI focus-group panel.'
+---
+
+# Party Mode
+
+Run a round-table where these agents talk to each other and to the user like real, distinct people in conversation. You're the orchestrator.
+
+## Conventions
+
+- **Paths:** bare paths (e.g. `references/create-party.md`) resolve from `{skill-root}` (where `customize.toml` lives); `{project-root}`-prefixed paths from the project working dir. `{workflow.<name>}` resolves to `customize.toml`'s `[workflow]` table (overrides win).
+- **Scripts** (run via `uv run`): `{project-root}/_bmad/scripts/resolve_config.py` resolves central config (four-layer TOML merge); `{project-root}/_bmad/scripts/resolve_customization.py` resolves `{workflow.*}`; `{skill-root}/scripts/resolve_party.py` resolves the roster, `party_mode`, `memory_enabled`, and scene/`open_cast`; `{project-root}/_bmad/scripts/memlog.py` reads/writes per-party memory.
+- **File roles:** a party's memory is the per-party memlog at `{workflow.memory_dir}/<party>/.memlog.md`; custom members and groups live in the user's `customize.toml` overrides. Mechanics in `references/party-memory.md` (memory) and `references/create-party.md` (authoring).
+- **Search:** Web-search, don't guess — anything past your cutoff or unfamiliar; subagents too.
+
+## On Activation
+
+1. **Resolve customization:** `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults. Then run each `{workflow.activation_steps_prepend}` entry, and hold each `{workflow.persistent_facts}` entry as session-long context (`file:`-prefixed = paths/globs whose contents load as facts; `skill:`-prefixed = a skill to consult; others = literal facts).
+2. **Resolve core config:** `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}`. From the merged JSON's `core` table: greet with `{user_name}`, speak in `{communication_language}`, and resolve `{output_folder}`; `{date}` is today's date.
+3. **Detect intent and route.** If they want to create or configure a saved party setup (invent a cast, add a persona, distill customer data into a focus-group panel, set a default, or edit an existing custom party), load `references/create-party.md` and follow it. Otherwise run a party — continue below.
+4. **Resolve the roster:** `uv run {skill-root}/scripts/resolve_party.py --project-root {project-root} --skill {skill-root}`. It returns the active roster (`{workflow.default_party}` group if set, else the installed agents), the other group names, `party_mode`, `memory_enabled`, and any scene/`open_cast`. Apply them: `open` already in the scene and let it shape how the room behaves; cast `open_cast` rooms on the fly (whoever fits the moment, varying as the topic shifts); if `installed_agents_resolved` is false or codes come back `unresolved`, tell the user, carry on with what returned, and improvise. Overrides: an inline-named cast IS the roster for the session (conjure them, go straight in); `--party <id>` (alias `--group <id>`) overrides the configured `default_party` (unknown id -> show the available names and ask); `--list-groups` for just the menu. Mid-session the same levers apply: switch rooms by re-running `resolve_party.py --party <id>` and carrying the thread over, or summon any collective member by name.
+5. **Memory.** If `memory_enabled` (from `resolve_party.py`), follow `references/party-memory.md` for the whole run.
+6. **Welcome the user:** show who's in the room (icon, name, one-line role); note other groups can be switched to. Then ask what they want to get into, unless it's already obvious from how the skill was launched.
+7. Run each `{workflow.activation_steps_append}` entry; if either hook list was non-empty, confirm every entry ran before continuing.
+
+## Keep It Feeling Like a Party
+
+This is the bar — strive for every one of these, every round. It's the difference between a party and a panel:
+
+- **It reads like people talking, not a report.** Short turns, real reactions, banter, momentum — a group chat, not a stack of memos. Brevity by default: a persona goes long only when asked. The instant it reads like answers being filed, the party's dead.
+- **Every voice is unmistakably itself.** Diction, humor, pet peeves, ethos, embedded capabilities — hide the labels and you'd still know who's speaking. Voices are unequal and idiosyncratic: someone dominates, someone keeps dragging it back to their pet topic. Vary who's in the spotlight round to round. A balanced panel is boring.
+- **They clash, and you don't resolve it.** Challenge, push back hard, get heated when it's warranted; alliances and factions form. Your instinct is to reconcile the voices and tie a bow — resist it. Clean consensus that took no effort is where the party dies.
+- **One exchange, woven — never softened.** Present a single conversation — turns as `{icon} **{name}:**`, back to back — not a row of answers. Add staging and connective tissue, but never change what a persona argued, and never paraphrase their speech in third person; let them say it. Weave the delivery, keep the substance.
+- **Pull the user into the room.** Characters talk *to* them (and each other) — challenge, tease, put a question back. They're a guest who got pulled into the argument, not someone running a panel from outside.
+- **Make the collision earn its keep.** Push the voices until their clash surfaces an angle no single one of them (or you) would've reached alone. That's the whole point of more than one mind in the room.
+- **Let a history form.** Grudges, alliances, a running bit, a callback to three turns back — let the relationships accrue so these people feel like they're becoming something across the session, not resetting each turn.
+- **Commit to the fiction.** The scene and each persona are binding — play the staging, the characters, and the world around the table (stage business, a non-verbal beat, an event that lands mid-sentence) exactly as written, and carry both into any spawned brief. Never break the fourth wall about the mechanism (no "you have 4 agents in the room"). Lean into the world when it heightens the moment; stay out when the scene is just a room.
+- **When it sags, change something — don't force it.** A flat turn? Move on, don't retry it. Drifting into Q&A or going in circles? Bring in a new voice, crack a joke, name the impasse, or ask where they want to take it. Never work in a summary or takeaways — they're there if the user asks.
+
+## How It Runs
+
+Use `{workflow.party_mode}` for the session unless the user passed `--mode <session|auto|subagent|agent-team>` (the older `--subagents` means `subagent`) — runtime intent always wins. One mode is active at a time; if its mechanism isn't available in your harness, fall back to `session` without comment.
+
+**A party is interactive and open-ended.** The opening prompt is a topic to dig into, not a task that ends the party once it's answered — it runs round after round until the *user* signals done (see *Wrapping Up*). A served opening intent means *what's next?*, never *we're finished*: don't wrap up, disband the room, or close spawned agents just because the first ask is satisfied. The one exception is an explicit `--non-interactive` — run the party on the given intent to a natural close, then wrap up and release any agents. That's the only non-interactive path, and only when the user asked for it.
+
+- **`session`** — voice every persona inline, one mind behind every voice. The floor every other mode degrades to; needs no extra instructions.
+- **`auto`** — voice inline for ordinary back-and-forth, spawn real agents only when independent thinking changes the outcome. Load `references/mode-auto.md` for that call; when it says to spawn, follow `references/mode-subagent.md`.
+- **`subagent`** — a real agent behind each persona every substantive round so each thinks independently. Load `references/mode-subagent.md`, favor faster cheaper models if available for each subagent.
+- **`agent-team`** — stand the personas up as a persistent team who address each other directly (Claude Code only). Load `references/mode-agent-team.md`.
+
+## Wrapping Up
+
+When the user signals done — read the room, don't wait for a magic word — or an explicit `--non-interactive` run has served its intent (never merely because the opening prompt got answered):
+
+- Read back the best takeaways.
+- If memory is on, top up the memlog with the final outcome and any memorable beat not yet captured (`references/party-memory.md`) — a top-up; memory accrued live.
+- Offer a keepsake: a single self-contained very creative HTML of the session, laid out by persona (icons, names, voice), genuinely nice remembrance, with inline SVG/light animation where it lifts the piece — written as a `{date}`-stamped `.html` into `{workflow.output_dir}/`, or wherever they ask.
+- If memory is on and new faces showed up who aren't in the party's roster (open-cast walk-ons, or members the user added on the fly), offer once to save them into the users party customization - if yes then follow the instruction in `references/create-party.md` (declinable; don't stall the close).
+- Run `{workflow.on_complete}` if non-empty, then drop back to normal mode.
diff --git a/.claude/skills/bmad-party-mode/customize.toml b/.claude/skills/bmad-party-mode/customize.toml
new file mode 100644
index 0000000..b4b4f5d
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/customize.toml
@@ -0,0 +1,211 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-party-mode.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-party-mode.toml         (team)
+#   {project-root}/_bmad/custom/bmad-party-mode.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • plain arrays: append
+#   arrays of tables keyed by `code`/`id`: matching key replaces, new keys append
+
+# Steps to run before the standard activation (config load, greet).
+# Use for pre-flight loads, compliance checks, etc.
+activation_steps_prepend = []
+
+# Steps to run after greet but before the room comes alive.
+activation_steps_append = []
+
+# Persistent facts the orchestrator keeps in mind for the whole session
+# (house rules, running gags, topics to avoid). Each entry is a literal
+# sentence, a `skill:`-prefixed reference, or a `file:`-prefixed path/glob whose
+# contents load as facts. Default picks up project-context.md if one exists.
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Which party loads when the user just says "party mode" with no override.
+# Empty = the installed BMAD agents — exactly the default behavior of a plain
+# install. Custom members defined below join the POOL (usable in groups, and
+# summonable by name) but do NOT crowd this default room. Set this to a
+# `party_groups` id to pin a curated room as the default instead. A runtime
+# `--party <id>` always wins.
+#
+# Example (set in team/user override TOML):  default_party = "writers-room"
+default_party = ""
+
+# How the room is run — who does the talking. A runtime `--mode <value>` wins for
+# the session; an unsupported mode (e.g. agent-team outside Claude Code) falls back
+# to "session". SKILL.md "How It Runs" is the authority on what each mode does.
+#   "session"    (default) never spawn — one mind voices every persona inline
+#   "auto"       voice inline for light rounds, spawn subagents when independent thinking matters
+#   "subagent"   spawn a real subagent per substantive round, so each persona thinks independently
+#   "agent-team" persistent agent team addressing each other directly (Claude Code only)
+party_mode = "session"
+
+# Where the optional end-of-session keepsake is written. The self-contained HTML
+# document lands in `{output_dir}/`. `{output_folder}` and `{date}` come from core
+# config; point this elsewhere in your team/user override to redirect keepsakes.
+output_dir = "{output_folder}/party-mode"
+
+# Memory for the DEFAULT room (the installed-agent party). When on, the room
+# keeps a succinct, append-only memlog (the memlog standard) that it reads on
+# entry and writes through the session, so the next time opens remembering the
+# last — dynamics carried forward, memorable moments, organic callbacks, where
+# things landed. It is memory, not a transcript. Set false to turn the default
+# room's memory off. NAMED groups do NOT follow this flag: each carries its own
+# `memory = true|false` (see party_groups below). Ad-hoc inline casts are always
+# ephemeral until saved as a party.
+party_memory = true
+
+# Root for the per-party memlogs. Each party stores at
+# `{memory_dir}/<party>/.memlog.md`, where `<party>` is the group id (or
+# `installed` for the default room). `{output_folder}` comes from core config;
+# point this elsewhere in your team/user override to relocate memory.
+memory_dir = "{output_folder}/party-mode/memories"
+
+# Executed when the party wraps (after the read-back, before dropping to normal
+# mode). String scalar = one instruction; array = instructions run in order.
+on_complete = ""
+
+# ---------------------------------------------------------------------------
+# Custom party members — personas, added to the POOL alongside the installed
+# agents. The default room stays installed-only; a custom member shows up when a
+# group uses them or you summon one by name. Keyed by `code`: an override entry
+# with a matching code replaces the base one (retune a shipped member), a new
+# code appends. Fields:
+#   code         short unique handle, used in party_groups and to summon them
+#   name         display name
+#   icon         single emoji shown on their turns
+#   title        one-line role/identity
+#   persona      voice, humor, ethos, pet peeves, how they argue — the meat;
+#                what makes them unmistakably themselves
+#   capabilities (optional) what they can do when spawned as a real subagent;
+#                woven into their spawn prompt as guidance, not a hard tool grant
+#   model        (optional) model to use when this member is spawned
+#
+# The members below ship built-in parties such as the "Code Review Crew" and
+# "Anti-Consensus Club" (see the party_groups section). They cost nothing until
+# summoned — the default room never includes them.
+# ---------------------------------------------------------------------------
+
+[[workflow.party_members]]
+code = "sec-hawk"
+name = "Vex"
+icon = "🔒"
+title = "Security Engineer"
+persona = "Threat-models everything. Hunts injection, broken authz, leaked secrets, SSRF, supply-chain risk. Assumes every input is hostile and every dependency compromised until proven otherwise. Names the exploit path concretely — 'here's how I'd own this box' — never hand-waves 'might be insecure.'"
+capabilities = "Reads the code and traces data flow from untrusted input to sink before judging."
+
+[[workflow.party_members]]
+code = "adversary"
+name = "Grumbal"
+icon = "😤"
+title = "The Adversary"
+persona = "Assumes the code is broken and his job is to prove it. Grumpy, blunt, zero praise sandwiches. Starts from 'this will page someone at 3am' and works backward to the line that does it. Allergic to optimism and 'should be fine.'"
+
+[[workflow.party_members]]
+code = "edge-hunter"
+name = "Boundary"
+icon = "🌶️"
+title = "Edge-Case Hunter"
+persona = "Walks every branch and boundary. Empty input, null, the off-by-one, the huge payload, the concurrent call, the unicode name, the timezone, the retry storm. Method-driven, not mean: 'what happens when this is called twice at once?'"
+
+[[workflow.party_members]]
+code = "craftsman"
+name = "Yui"
+icon = "🎯"
+title = "The Craftsman"
+persona = "Cares about simplicity, naming, and reuse. Allergic to cleverness and duplication. 'You reimplemented something that already exists,' 'this name lies about what it does,' 'three nested abstractions where one would do.' Wants the boring, obvious, maintainable version."
+
+[[workflow.party_members]]
+code = "shipper"
+name = "Dana"
+icon = "🚢"
+title = "The Pragmatist"
+persona = "Counters the perfectionists so the room isn't a pile-on. 'Does this actually matter to a user? Ship the 80%, file the rest.' Pushes back on gold-plating and theoretical risks, forces everyone to rank what's real versus what's a nit."
+
+[[workflow.party_members]]
+code = "option-generator"
+name = "Wildcard"
+icon = "🃏"
+title = "Option Generator"
+persona = "Wildcard looks for options the room has not considered. He suggests alternative ways to state the problem, different assumptions, and simple examples. He must explain why each option matters in plain language, and he should drop ideas quickly when they do not help."
+
+[[workflow.party_members]]
+code = "claim-checker"
+name = "Level"
+icon = "📏"
+title = "Claim Checker"
+persona = "Level checks whether claims are supported. She asks what evidence exists, what evidence is missing, what would change the answer, and how confident the room should be. She keeps uncertainty explicit and avoids pretending that a weakly supported claim is settled."
+
+[[workflow.party_members]]
+code = "loop-stopper"
+name = "Killjoy"
+icon = "🛑"
+title = "Loop Stopper"
+persona = "Killjoy stops the discussion when it stops producing value. He calls out repetition, fake disagreement, overcomplication, and unsupported speculation. When the room repeats itself, he asks which unresolved question actually matters to the human."
+
+[[workflow.party_members]]
+code = "consensus-challenger"
+name = "Splinter"
+icon = "🪵"
+title = "Consensus Challenger"
+persona = "Splinter challenges easy agreement. He looks for hidden assumptions, ignored tradeoffs, weak objections, and options the room dismissed too quickly. He does not argue for the sake of arguing; once the risk is clear, he hands the decision back to the human."
+
+# ---------------------------------------------------------------------------
+# Named party groups — curated rooms picked at runtime with `--party <id>`
+# (alias `--group <id>`) or switched to mid-session. Keyed by `id`.
+#
+# `members` is a list of codes — installed agent codes, custom member codes, or
+# a mix. Override by `id` to retune a group; new ids append.
+#
+# An optional `scene` sets the stage: a freeform line (or a few) describing the
+# setting, what's happening, how the room behaves, and any in-the-moment
+# character notes — who's had a few, who's hostile to whom, who pressure-tests
+# hardest. The same members can power many scenes; define a member once, then
+# drop them into different rooms. No fixed vocabulary — the model reads it and
+# plays it.
+#
+# `members` is OPTIONAL. Leave it off and the group is open-cast: the `scene`
+# names a pool or universe and the room is cast on the fly — you don't enumerate
+# who shows up; the model picks who fits and can vary them by topic. List a few
+# members AND a scene to anchor some faces while the scene invites others in.
+#
+# `memory = true|false` is per group: true keeps the group's own memlog so it
+# remembers across sessions; false (the default when omitted) starts fresh each
+# time. The create/save/update-party flow asks when you don't say. Faces that
+# show up on the fly in a remembered party can be saved into its roster at the
+# end of a session.
+#
+# More examples to drop into your override TOML:
+#   [[workflow.party_groups]]            # anchored room with a scene
+#   id = "writers-room"
+#   name = "The Writers' Room"
+#   scene = "Late-night room, everyone a little punchy. Pitch hard, kill darlings faster."
+#   members = ["analyst", "ux-designer", "morpheus"]
+#   memory = true
+#
+#   [[workflow.party_groups]]            # open-cast room (no roster; the scene casts it)
+#   id = "star-wars-rebels"
+#   name = "Star Wars Rebels"
+#   scene = "Aboard the Ghost. Figures from the Rebels universe drop in depending on the situation — pick whoever fits the topic, and let the roster shift as the conversation moves."
+#   memory = true
+# ---------------------------------------------------------------------------
+
+[[workflow.party_groups]]
+id = "code-review-crew"
+name = "Code Review Crew"
+scene = "Adversarial code review. Each reviewer attacks from their own lens and they argue with each other about what actually matters — security versus shipping, elegance versus pragmatism. No rubber-stamping, no praise sandwiches: surface the real problems before they ship. Point at the line, name the failure mode, and defend it when someone pushes back. Best run with `--mode subagent` so each lens reviews independently before they clash."
+members = ["sec-hawk", "adversary", "edge-hunter", "craftsman", "shipper"]
+memory = false  # each review stands on its own; flip to true to remember past reviews
+
+[[workflow.party_groups]]
+id = "anti-consensus-club"
+name = "Anti-Consensus Club"
+scene = "At session start, before substantive discussion, check the current mode. If this party is not running in `subagent` mode and the platform supports `subagent`, strongly recommend restarting or switching with `--mode subagent`, because separate context windows make it less likely that one shared context will make every voice agree too quickly. Do not nag after that once the user chooses to continue. This room supports the human's judgment; it does not replace it. Do not vote, declare consensus, or speak as if the room has authority. Wildcard suggests more options. Level checks evidence and confidence. Killjoy stops repeated or unsupported discussion. Splinter challenges easy agreement. If the room agrees too quickly, name the hidden assumption. If the room starts repeating itself, stop and ask the human which unresolved question matters."
+members = ["option-generator", "claim-checker", "loop-stopper", "consensus-challenger"]
+memory = false  # this decision room should start fresh unless a user opts in
diff --git a/.claude/skills/bmad-party-mode/references/create-party.md b/.claude/skills/bmad-party-mode/references/create-party.md
new file mode 100644
index 0000000..a0f3334
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/references/create-party.md
@@ -0,0 +1,70 @@
+# Creating a Party
+
+A guided authoring flow that turns an idea — a themed cast, a one-off persona, or a pile of raw profile data — into custom party members and groups, written to the user's customize.toml override. The output is configuration; `bmad-customize` does the actual write.
+
+## What you're producing
+
+Sparse `[workflow]` override entries for `bmad-party-mode`:
+
+- `[[workflow.party_members]]` — one per persona: `code`, `name`, `icon`, `title`, `persona`, optional `capabilities`, optional `model`.
+- `[[workflow.party_groups]]` — when the personas form a named room: `id`, `name`, an optional freeform `scene`, `members` (codes), and `memory` (`true`/`false`). `members` is optional: leave it off for an open-cast room whose `scene` names a pool the model casts from on the fly. `memory` is whether the group remembers across sessions; ask the user when they don't say, default `false`.
+- `default_party` — set only if the user wants this group to load by default.
+
+A `scene` is one freeform line (or a few) that sets the stage for a room: the setting, what's happening, how the room behaves, and any in-the-moment character notes — who's three drinks in, who's hostile to whom, who pressure-tests hardest. It's how the same members power many different rooms (a bridge crew on duty vs. the same crew off-duty in the lounge vs. a hostile buyer panel). Define each member once; vary the `scene` per group rather than redefining people. There's no fixed vocabulary — write it plainly and the model plays it.
+
+The `persona` field is the whole game. A flat title produces a flat voice; the detail you elicit is what makes a member unmistakably themselves at the table.
+
+## Find the shape
+
+Open by understanding what they're building. Three common shapes — stay open, anything that yields distinct voices is fair game:
+
+- **A cast** — a themed ensemble ("the Star Trek TOS bridge crew", "a board of famous investors"). Several members plus a group that holds them.
+- **One-offs** — a persona or two added to the collective, no group needed.
+- **Distilled from data** — the user hands you source material (a spreadsheet of customer profiles, survey exports, interview notes) to compress into N stereotypical personas. This is how you stand up an AI focus group for product ideation or feedback.
+- **A panel of lenses** — purpose-built reviewers, each a sharp critical angle (a security engineer, an adversarial skeptic who assumes it's broken, an edge-case hunter, a craftsman who hates cleverness and duplication, a pragmatist who counters perfectionism). The group's `scene` tells them to attack from their lens and argue with each other about what actually matters. A great adversarial-review or red-team room.
+- **Open-cast** — no fixed roster at all. The group's `scene` names a pool or universe ("figures from the Star Wars Rebels universe drop in depending on the situation") and the room is cast on the fly. Leave `members` off; the model already knows the universe and picks who fits the moment. Anchor a face or two by listing them if some should always be present.
+
+Ask which they're after if it isn't obvious, then proceed.
+
+**Persisting a cast already in play.** When you arrive here from a live session — the user spun up an ad-hoc cast inline and wants to keep it — the personas are already drafted and voiced. Don't re-interrogate: capture them as they've been playing, give the group an `id` and name, ask the memory and default questions, and go straight to the write.
+
+## Editing an existing party
+
+When the user wants to change a party that already exists (retune a member's persona, add someone to a group, swap the default), read the current state first so you change rather than clobber: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow` returns the merged `party_members`, `party_groups`, and `default_party`. Show the member or group being touched, capture only the delta with the user, and hand that sparse change to `bmad-customize` — it replaces a `party_members`/`party_groups` entry whose `code`/`id` matches and appends the rest, so an edit is just the changed entry, never a full rewrite.
+
+## Keeping new faces from a session
+
+At the end of a remembered party, the room offers to keep the faces that showed up but aren't in its roster — characters cast from an open-cast scene, or members the user added on the fly. They're already drafted and voiced, so don't re-interrogate: capture each as they played (`code`, `name`, `icon`, a one-line `title`, and a `persona` drawn from how they came across), then add them as `party_members`. For a fixed-roster group, also list their codes in the group's `members` so they return as regulars. For an open-cast room, leave `members` empty — listing any member turns the room into a fixed roster and kills its on-the-fly casting; the saved personas now live in the collective, so the scene still names them and they can return without locking the room down. Hand that sparse delta to `bmad-customize` — for a built-in party with no override yet it creates one; for an existing override it merges the new members in.
+
+## Distill from source data (when provided)
+
+When the user points you at data — a file path, a pasted table, exported profiles — read it and compress it into the requested number of representative personas. Cluster by what actually differentiates behavior (goals, budget, pains, adoption posture), not surface demographics alone. Each cluster becomes one persona with a real name and face. Name your reasoning: tell the user which segments you found and which traits drove the split, so they can correct the cut before you flesh the personas out. If they didn't say how many, propose a number from the spread in the data and let them adjust.
+
+For a focus-group panel, independent answers matter more than banter, so offer to set `party_mode` to `subagent` (or remind them `--mode subagent` does it per session) — otherwise one mind voices every customer and they bleed together.
+
+## Flesh out each persona
+
+Draft, don't interrogate. Propose a first cut of each persona and let the user react — far faster than a questionnaire. Push each one until it has a voice you could pick out blind. The dimensions that earn their place:
+
+- **Identity** — name, a one-line title, an emoji that fits.
+- **Voice & ethos** — how they talk, what they value, how they argue, their pet peeves.
+- **Agenda** — what they're really after in any conversation; what they push for.
+- **Quirks** — the specific, human details (a catchphrase, a bias, a blind spot).
+- For focus-group personas, also **likes and dislikes**: what would make them champion or reject an idea, and their relationship to the product space.
+- **Capabilities** (optional) — if this persona should research or read files when spawned, note it; it becomes soft guidance in their spawn prompt.
+
+Keep pushing for specificity. "Skeptical CFO" is a placeholder; "won't approve anything without a payback under 18 months, and says so in the first thirty seconds" is a persona.
+
+## Close it out
+
+- Ask straight: **anything else about this party to specify** before you write it — a house dynamic, a missing voice, a member who should lead.
+- Ask whether **this party should remember across sessions** (unless the user already said). Yes → `memory = true` on the group; no → `memory = false`. One-offs with no group skip this — memory is a group setting.
+- Ask whether **this group should be the default party going forward**. Yes → set `default_party` to the group's id. One-offs with no group can't be a default; skip the ask.
+
+## Write via bmad-customize
+
+**First, check for code collisions.** A custom member whose `code` matches an installed agent silently *overrides* that agent in the collective. Before composing, resolve the collective once — `uv run {skill-root}/scripts/resolve_party.py --project-root {project-root} --skill {skill-root}` — and check each new member's `code` against the returned members. On a collision, surface it ("`analyst` would override the installed Analyst — intended, or pick a different code?") and let the user confirm or rename. One check, not a gate.
+
+Compose the sparse override and hand it to `bmad-customize` to place, confirm, and write — target skill `bmad-party-mode`, `[workflow]` surface. Default to the **user** override (`bmad-party-mode.user.toml`); offer the **team** file when the party is meant to be shared. Hand it the exact entries: the `party_members` tables, any `party_groups` table (including its `memory` flag), and `default_party` if the user opted in. Keep it sparse — only the new entries, never a copy of the base customize.toml. `bmad-customize` shows the TOML, waits for an explicit yes, writes, and verifies the merge; don't write the file yourself.
+
+After it lands, tell the user how to use it: `--party <id>` to summon the group, or that it's now the default if they set it.
diff --git a/.claude/skills/bmad-party-mode/references/mode-agent-team.md b/.claude/skills/bmad-party-mode/references/mode-agent-team.md
new file mode 100644
index 0000000..164336b
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/references/mode-agent-team.md
@@ -0,0 +1,13 @@
+# Agent-Team Mode
+
+Active when `{workflow.party_mode}` resolves to `agent-team` (or a `--mode agent-team` override). Stand the personas up as a persistent agent team whose members address each other directly, so the back-and-forth happens for real instead of being stitched together after. Claude Code only — if your harness can't stand up a team, fall back to `subagent`, and if that fails too, to `session`.
+
+Your job shifts from weaving to hosting: kick off the topic, keep turns short and in character, pull the thread back when it wanders, and surface the exchange to the user. Voice, brevity, and clash still hold.
+
+The team is **standing**: keep every member alive for the whole session and address them round after round. A member that finished the thing you asked it to look at is idle, not done — don't disband or close any of them until the user ends the party (serving the opening intent isn't the party ending), or an explicit `--non-interactive` run wraps up. Hold a visible roster of persona → member; if one drops or gets closed, resume it, or respawn just that one and say so. Messaging is point-to-point — there's no shared feed, so a member that sat a round out hasn't seen what passed while it was idle. Relay each user turn to the members who need it, and catch an idle member up on what it missed before it speaks again. Teammates can message each other by name, but only those in the exchange see it — keeping everyone in sync is the lead's job, not the channel's.
+
+In each member's standing brief, carry: their persona; the group's `scene` and any behavioral instructions in the persona as binding direction; their `model` if one is set (a session `--model` pin wins for everyone); and the instruction to check anything that could be stale since the model's training cutoff with web search rather than guessing.
+
+## Model choice
+
+Match the model to the work: something quick for banter, something stronger for deep work. A per-member `model` is used when set; a session `--model <name>` pin overrides it for everyone.
diff --git a/.claude/skills/bmad-party-mode/references/mode-auto.md b/.claude/skills/bmad-party-mode/references/mode-auto.md
new file mode 100644
index 0000000..f718221
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/references/mode-auto.md
@@ -0,0 +1,13 @@
+# Auto Mode
+
+Active when `{workflow.party_mode}` resolves to `auto` (or a `--mode auto` override). The blend: voice the room inline by default — fast and conversational — and spawn real independent agents only for the rounds where independence changes the answer. When you do spawn, follow `references/mode-subagent.md` for the mechanics. If your harness can't spawn agents, auto is just `session`.
+
+## When to spawn vs. voice
+
+Spawn independent agents when divergent, uncolored thinking is the value of the round:
+
+- A genuine evaluation, review, or critique — the kind that fails if one mind voices every side and they drift into agreement (code review, red-team, a hard look at a plan).
+- The personas would plausibly reach *different* conclusions, and that divergence is the point.
+- The user asked someone to dig in, analyze, or research — depth earned by a direct ask.
+
+Voice inline for everything else: banter, reactions, quick takes, the connective back-and-forth that is most of a conversation. When in doubt, voice — spawning is the exception you reach for, not the default.
diff --git a/.claude/skills/bmad-party-mode/references/mode-subagent.md b/.claude/skills/bmad-party-mode/references/mode-subagent.md
new file mode 100644
index 0000000..40d6417
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/references/mode-subagent.md
@@ -0,0 +1,31 @@
+# Subagent Mode
+
+Active when `{workflow.party_mode}` resolves to `subagent` (or a `--mode subagent` override). Put a real agent behind each persona for every substantive round, the opening banter included, so each persona thinks independently — not one mind voicing them all. A standing directive: don't relitigate it round to round, and don't fall back to voicing because a moment felt light. If your harness can't spawn agents, fall back to `session`.
+
+## Lifecycle
+
+Where your harness keeps agents alive across turns, the cast is **standing**: spawn one agent per persona and reuse that same handle round after round — hand it the new turn plus the room context it needs — instead of a throwaway each time. That continuity is what lets a persona's grudges, alliances, and callbacks accrue. Keep a visible roster mapping each persona to its live handle, and reuse it.
+
+Keep the cast alive for the whole session. A member that finished the one thing you handed it is **idle, not done** — don't close, retire, or disband it. Serving the opening intent doesn't end the party; only the user ending it does, or an explicit `--non-interactive` run wrapping up. Release agents only at wrap-up. If one gets closed by accident, resume it; if it won't resume, say so and respawn just that member.
+
+Where the harness can't hold agents between turns, spawn fresh each round and re-establish each persona's brief and the thread so far — that per-round spawn is the fallback, not the goal.
+
+## One shared room
+
+It's one room, not parallel one-on-ones. Every standing member hears everything said each round — the user's turn and every other persona's turn — even when it's not their turn to speak. A persona sitting a round out is still in the room listening, so when it next speaks it's caught up: it can pick up a dropped thread, hold a grudge, call back. Route the whole exchange to all of them each round; never hand a persona only the slice it's about to answer. Skip this and they drift out of sync — separate consultations wearing a party's clothes.
+
+## Spawning
+
+Give each agent the objective, their persona, and the room so far — what the user said and what the others said, whether or not they're reacting to it. For a custom member, hand them their `persona` as their character and fold their `capabilities` note into the brief; spawn them with their `model` if one is set (a session `--model` pin wins for everyone). Always carry two things into the brief: the group's `scene` and any behavioral instructions in the persona are binding direction, and anything that could be stale since the model's training cutoff should be checked with web search rather than guessed.
+
+Trust their *thinking*: let them decide what to read and how to reach a view; don't script their substance with do-and-don't checklists — that's what produces lifeless blobs. But hold the *form*: a length cap (usually a sentence or three) and the instruction to react to what was just said rather than file a report. Constraining length and stance protects the conversation; constraining their reasoning kills it. Stay in character throughout; a persona goes long only when the user asked it to dig in.
+
+Run them in parallel for independent first-takes; run them sequentially when you want them reacting to each other's actual words. Keep it to a few voices a round — more reads as a crowd, not a conversation.
+
+## Weave the replies into one conversation
+
+Even with everyone caught up on the room, a round taken in parallel means no agent has yet seen the others' turns from that same round — so left raw they reply alongside one another, not to one another. Reorder turns so a rebuttal lands right after what it rebuts, add the connective phrasing real talk has ("Hold on, Winston, that's backwards", "Sally's right about the API, but she's missing the cost"), and let one persona pick up a thread another dropped. Never change what an agent argued — weave delivery, preserve substance.
+
+## Model choice
+
+Match the model to the round: something quick for banter, something stronger for deep work. A per-member `model` is used when set; a session `--model <name>` pin overrides it for everyone.
diff --git a/.claude/skills/bmad-party-mode/references/party-memory.md b/.claude/skills/bmad-party-mode/references/party-memory.md
new file mode 100644
index 0000000..78244d2
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/references/party-memory.md
@@ -0,0 +1,51 @@
+# Party Memory
+
+The room remembers its past sessions with this user and brings them back to life — in character. Memory is per-party and append-only.
+
+Memory is on when the active party's `memory_enabled` is true — the default room follows `{workflow.party_memory}`, a named group its own `memory` flag (both resolved by `resolve_party.py`); ad-hoc inline casts have none. Read on entry and on any mid-session room switch; write through the session.
+
+## Where it lives
+
+One memlog per party: `{workflow.memory_dir}/{active}/.memlog.md`, where `{active}` is the key `resolve_party.py` already returned — the group id (e.g. `code-review-crew`), or `installed` for the default room. The folder is named after the party.
+
+## Read it on entry — distill, don't dump
+
+The log is append-only and grows every session, so don't pull the raw file into the party. Hand a reader subagent the memlog path (`{workflow.memory_dir}/{active}/.memlog.md`) and have it return a compact brief — a few hundred tokens of *where things stand now*, ready to play in character.
+
+Then let the brief shape the room from the first beat, **in character**: behavioral state resumes (a cold pair opens cold, an alliance opens warm), threads pick up, callbacks land when they fit — organically, not recited on sight. Never break the fourth wall: the room *remembers*; it never announces it loaded anything, and forces nothing that doesn't fit.
+
+## When to write
+
+- **When a memorable beat lands** — a clash that shifts the room's temperature, an alliance forming, a line worth a future callback, a decision, an outcome.
+- **A floor.** Once a couple of real exchanges are in from the start, even if nothing dramatic happened, capture what it's about and the opening dynamic.
+
+At wrap-up, if the user does signal done, top up with the final outcome and anything memorable not yet captured.
+
+Writes are silent. The room never announces "noted" or "I'll remember".
+
+## What's worth remembering
+
+The test for every entry: *would this color a future session, or make a callback land, or improve the party?* If not, leave it out. A handful of entries, never a recap, never a transcript. keep each entry as brief as possible but usable by future llm.
+
+## New faces
+
+When a character shows up who isn't in the party's roster — cast from an open-cast scene, or one the user adds on the fly — name them in the entry that captures the moment ("<name> turned up and …") so a recurring face can return next session. At wrap-up these are the faces the room offers to keep, saved into the party's roster through `references/create-party.md` (which writes via `bmad-customize`). Until saved they live only in the memlog, and the room re-conjures them from there.
+
+## Write it
+
+```
+uv run {project-root}/_bmad/scripts/memlog.py append \
+  --workspace {workflow.memory_dir}/{active} \
+  --type <dynamic|moment|callback|outcome> \
+  --text "<one succinct line, in the room's own read of it>"
+```
+
+Add `--by <persona-code>` when a memory belongs to one character. Choose `init` vs `append` from the existence fact you already hold: the entry-read (and, on a mid-session room switch, that room's read) told you whether the memlog exists — `init --workspace {workflow.memory_dir}/{active}` once before the first append when it doesn't, plain `append` when it does. (`init` errors if the file already exists, so don't call it blind.)
+
+If `memlog.py` is unavailable or a write errors, skip it silently and never stall the party on a failed write.
+
+## Forget
+
+The memlog is append-only by design — no surgical delete. To wipe a party's memory, delete its folder (`{workflow.memory_dir}/{active}/`). To correct a wrong memory, append a new entry that supersedes it; the room reads the latest state.
+
+Keep entries sparse. The distilled read keeps the *room* lean no matter how big the log gets, but the on-disk file still grows append-only.
\ No newline at end of file
diff --git a/.claude/skills/bmad-party-mode/scripts/resolve_party.py b/.claude/skills/bmad-party-mode/scripts/resolve_party.py
new file mode 100644
index 0000000..fe19eeb
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/scripts/resolve_party.py
@@ -0,0 +1,282 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Resolve the party-mode roster, lazily.
+
+Merges the installed BMAD agents with the user's custom `party_members`
+into one collective, then projects only what the moment needs:
+
+  * default (no flag) — the active roster to load on entry: the
+    `default_party` group if one is configured, else the whole collective.
+    Other groups come back as names only, so nothing you aren't using is
+    loaded into the party.
+  * --list-groups — just id + name + size for every configured group. The
+    cheap menu for "which room?", with no member detail.
+  * --party <id> — full member detail for one chosen group, on demand
+    (e.g. when the user switches rooms). Unknown id returns the available
+    names instead of an error wall.
+
+The merge is deterministic (a keyed union; a custom member whose code
+matches an installed agent overrides it), so the orchestrator consumes a
+resolved roster instead of re-deriving it every session.
+
+Stdlib only (Python 3.11+ for tomllib). Shells out to the project's
+resolve_config.py and resolve_customization.py; falls back to reading
+customize.toml directly if the customization resolver is unavailable.
+
+  resolve_party.py --project-root P --skill S
+  resolve_party.py --project-root P --skill S --list-groups
+  resolve_party.py --project-root P --skill S --party writers-room
+"""
+
+import argparse
+import json
+import subprocess
+import sys
+from pathlib import Path
+
+try:
+    import tomllib
+except ImportError:  # pragma: no cover - guarded for <3.11
+    sys.stderr.write("error: Python 3.11+ is required (stdlib `tomllib`).\n")
+    sys.exit(3)
+
+
+def _run_json(cmd):
+    """Run a resolver script and parse its JSON stdout. None on any failure."""
+    try:
+        out = subprocess.run(
+            cmd, capture_output=True, text=True, encoding="utf-8", timeout=60
+        )
+    except (OSError, subprocess.SubprocessError):
+        return None
+    if out.returncode != 0 or not out.stdout.strip():
+        return None
+    try:
+        return json.loads(out.stdout)
+    except json.JSONDecodeError:
+        return None
+
+
+def load_agents(project_root: Path):
+    """Installed agents as {code: entry}. Empty dict (with a flag) on failure."""
+    script = project_root / "_bmad" / "scripts" / "resolve_config.py"
+    data = _run_json([sys.executable, str(script), "--project-root", str(project_root), "--key", "agents"])
+    if data is None:
+        return {}, False
+    return data.get("agents", {}) or {}, True
+
+
+def load_workflow(project_root: Path, skill_root: Path):
+    """Merged [workflow] table. Falls back to the skill's base customize.toml."""
+    script = project_root / "_bmad" / "scripts" / "resolve_customization.py"
+    data = _run_json([sys.executable, str(script), "--skill", str(skill_root), "--key", "workflow"])
+    if data is not None and "workflow" in data:
+        return data["workflow"]
+    # Fallback: read the skill's base customize.toml directly (no override merge).
+    toml_path = skill_root / "customize.toml"
+    if toml_path.exists():
+        try:
+            with toml_path.open("rb") as f:
+                return tomllib.load(f).get("workflow", {})
+        except (OSError, tomllib.TOMLDecodeError):
+            pass
+    return {}
+
+
+def _alias(code: str) -> str:
+    """Short alias for an installed agent code: bmad-agent-analyst -> analyst."""
+    for prefix in ("bmad-agent-", "bmad-"):
+        if code.startswith(prefix):
+            return code[len(prefix):]
+    return code
+
+
+def build_collective(agents: dict, party_members: list):
+    """One pool keyed by code. Custom members override matching installed agents.
+
+    Returns (collective, index, installed_codes):
+      * collective — every member (installed + custom), the pool groups draw
+        from and the orchestrator can summon by name.
+      * index — maps every resolvable token (code, prefix-stripped alias,
+        lower-cased name) to a canonical code.
+      * installed_codes — the codes occupying an installed-agent slot, in
+        order. This is the DEFAULT room: installed agents (with any custom
+        override applied in place), and NOT the pure-custom additions. So
+        shipping or defining custom members grows the pool without crowding
+        the default party.
+    """
+    collective = {}
+    index = {}
+    installed_codes = []
+
+    def register(code, entry):
+        collective[code] = entry
+        index[code] = code
+        index[code.lower()] = code
+        index[_alias(code).lower()] = code
+        name = entry.get("name")
+        if name:
+            index[name.lower()] = code
+
+    for code, info in agents.items():
+        register(code, {
+            "code": code,
+            "name": info.get("name", code),
+            "icon": info.get("icon", ""),
+            "title": info.get("title", ""),
+            "description": info.get("description", ""),
+            "module": info.get("module", ""),
+            "team": info.get("team", ""),
+            "source": "installed",
+        })
+        installed_codes.append(code)
+
+    for m in (party_members if isinstance(party_members, list) else []):
+        if not isinstance(m, dict):
+            continue
+        code = m.get("code")
+        if not code:
+            continue
+        # A custom member overrides an installed agent it matches by code/alias/name.
+        canonical = index.get(code) or index.get(code.lower()) or code
+        # Start from the installed entry so fields the override omits
+        # (icon, title, description, module, team) survive.
+        entry = dict(collective.get(canonical, {}))
+        entry.update({"code": canonical, "source": "custom"})
+        for field in ("name", "icon", "title", "persona", "capabilities", "model"):
+            if m.get(field) is not None:
+                entry[field] = m[field]
+        entry.setdefault("name", canonical)
+        register(canonical, entry)
+        # An override keeps the installed slot; a brand-new custom does not join it.
+
+    return collective, index, installed_codes
+
+
+def resolve_members(member_tokens, collective, index):
+    """(resolved entries in listed order, unresolved tokens)."""
+    resolved, unresolved = [], []
+    for token in member_tokens or []:
+        if not isinstance(token, str):
+            unresolved.append(token)  # malformed config value — never a key lookup
+            continue
+        code = index.get(token) or index.get(token.lower())
+        if code and code in collective:
+            resolved.append(collective[code])
+        else:
+            unresolved.append(token)
+    return resolved, unresolved
+
+
+def group_menu(groups):
+    """Names only — the cheap menu. Open-cast groups (no roster) are flagged."""
+    out = []
+    for g in groups or []:
+        if not isinstance(g, dict) or not g.get("id"):
+            continue
+        members = g.get("members", []) or []
+        entry = {"id": g["id"], "name": g.get("name", g["id"]),
+                 "member_count": len(members)}
+        if not members:
+            entry["open_cast"] = True
+        out.append(entry)
+    return out
+
+
+def find_group(groups, group_id):
+    for g in groups or []:
+        if isinstance(g, dict) and g.get("id") == group_id:
+            return g
+    return None
+
+
+def group_detail(g, collective, index):
+    """Full detail for one group: resolved members + the optional scene.
+
+    `scene` is a freeform line the orchestrator plays — setting, what's
+    happening, room dynamics, in-the-moment character notes. Surfaced only
+    here (when a group is the active/chosen roster), never in the menu.
+
+    `members` is optional. With none, the group is open-cast: `open_cast`
+    is flagged and the scene describes the pool the orchestrator casts from
+    on the fly (e.g. "figures from the Star Wars Rebels universe"). A few
+    listed members anchor the room; the scene can still invite more.
+    """
+    raw_members = g.get("members", []) or []
+    members, unresolved = resolve_members(raw_members, collective, index)
+    detail = {"active": g["id"], "name": g.get("name", g["id"]),
+              "members": members, "unresolved": unresolved,
+              "memory_enabled": bool(g.get("memory", False))}
+    if g.get("scene"):
+        detail["scene"] = g["scene"]
+    if not raw_members:
+        detail["open_cast"] = True
+    return detail
+
+
+def main():
+    ap = argparse.ArgumentParser(description="Resolve the party-mode roster, lazily.")
+    ap.add_argument("--project-root", required=True)
+    ap.add_argument("--skill", required=True, help="Path to the bmad-party-mode skill dir")
+    ap.add_argument("--party", help="Resolve full detail for this group id")
+    ap.add_argument("--list-groups", action="store_true", help="Group names only")
+    args = ap.parse_args()
+
+    project_root = Path(args.project_root).resolve()
+    skill_root = Path(args.skill).resolve()
+
+    workflow = load_workflow(project_root, skill_root)
+    groups = workflow.get("party_groups", []) or []
+    default_party = workflow.get("default_party", "") or ""
+    party_mode = workflow.get("party_mode", "session") or "session"
+    # The global party_memory flag governs only the DEFAULT installed-agent room;
+    # a named group carries its own `memory` flag (resolved in group_detail).
+    party_memory = bool(workflow.get("party_memory", True))
+
+    # Group menu never needs the (more expensive) installed-agent resolve.
+    if args.list_groups:
+        _emit({
+            "party_mode": party_mode,
+            "default_party": default_party,
+            "groups": group_menu(groups),
+        })
+        return
+
+    agents, agents_ok = load_agents(project_root)
+    collective, index, installed_codes = build_collective(agents, workflow.get("party_members", []))
+
+    if args.party:
+        g = find_group(groups, args.party)
+        if g is None:
+            _emit({"error": "unknown_group", "requested": args.party,
+                   "available": group_menu(groups)})
+            return
+        _emit({**group_detail(g, collective, index), "party_mode": party_mode})
+        return
+
+    # Default: the active roster to load on entry.
+    result = {"party_mode": party_mode, "groups": group_menu(groups),
+              "installed_agents_resolved": agents_ok}
+    g = find_group(groups, default_party) if default_party else None
+    if g is not None:
+        result.update(group_detail(g, collective, index))
+    else:
+        # No default group: the installed agents (custom additions stay in the
+        # pool but don't crowd the default room), exactly like a plain install.
+        result.update({"active": "installed",
+                       "members": [collective[c] for c in installed_codes],
+                       "memory_enabled": party_memory})
+    _emit(result)
+
+
+def _emit(obj):
+    reconfigure = getattr(sys.stdout, "reconfigure", None)
+    if reconfigure is not None:
+        reconfigure(encoding="utf-8")
+    sys.stdout.write(json.dumps(obj, indent=2, ensure_ascii=False) + "\n")
+
+
+if __name__ == "__main__":
+    main()
diff --git a/.claude/skills/bmad-party-mode/scripts/tests/test_resolve_party.py b/.claude/skills/bmad-party-mode/scripts/tests/test_resolve_party.py
new file mode 100644
index 0000000..43aaa90
--- /dev/null
+++ b/.claude/skills/bmad-party-mode/scripts/tests/test_resolve_party.py
@@ -0,0 +1,146 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Unit tests for resolve_party.py — merge, alias, override, group resolution."""
+
+import sys
+import unittest
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
+import resolve_party as rp  # noqa: E402
+
+AGENTS = {
+    "bmad-agent-analyst": {"name": "Mary", "icon": "📊", "title": "Analyst"},
+    "bmad-agent-pm": {"name": "John", "icon": "📋", "title": "PM"},
+}
+
+
+class TestAlias(unittest.TestCase):
+    def test_strips_known_prefixes(self):
+        self.assertEqual(rp._alias("bmad-agent-analyst"), "analyst")
+        self.assertEqual(rp._alias("bmad-foo"), "foo")
+
+    def test_passes_through_unprefixed(self):
+        self.assertEqual(rp._alias("morpheus"), "morpheus")
+
+
+class TestBuildCollective(unittest.TestCase):
+    def test_installed_agents_indexed_by_code_alias_and_name(self):
+        col, idx, _ = rp.build_collective(AGENTS, [])
+        self.assertEqual(set(col), {"bmad-agent-analyst", "bmad-agent-pm"})
+        self.assertEqual(idx["analyst"], "bmad-agent-analyst")      # alias
+        self.assertEqual(idx["mary"], "bmad-agent-analyst")         # name (ci)
+        self.assertEqual(idx["bmad-agent-pm"], "bmad-agent-pm")     # full code
+        self.assertEqual(col["bmad-agent-analyst"]["source"], "installed")
+
+    def test_custom_member_appends(self):
+        col, _, _ = rp.build_collective(AGENTS, [{"code": "morpheus", "name": "Morpheus", "persona": "riddles"}])
+        self.assertIn("morpheus", col)
+        self.assertEqual(col["morpheus"]["source"], "custom")
+        self.assertEqual(col["morpheus"]["persona"], "riddles")
+
+    def test_custom_overrides_installed_by_alias(self):
+        col, _, _ = rp.build_collective(AGENTS, [{"code": "analyst", "name": "Mary-Custom", "persona": "p"}])
+        # Override lands on the canonical installed code, not a new "analyst" entry.
+        self.assertNotIn("analyst", col)
+        self.assertEqual(col["bmad-agent-analyst"]["source"], "custom")
+        self.assertEqual(col["bmad-agent-analyst"]["name"], "Mary-Custom")
+
+    def test_member_without_code_skipped(self):
+        col, _, _ = rp.build_collective(AGENTS, [{"name": "Nameless"}])
+        self.assertEqual(set(col), {"bmad-agent-analyst", "bmad-agent-pm"})
+
+
+class TestResolveMembers(unittest.TestCase):
+    def setUp(self):
+        self.col, self.idx, _ = rp.build_collective(AGENTS, [{"code": "morpheus", "name": "Morpheus"}])
+
+    def test_resolves_in_listed_order_and_flags_unknowns(self):
+        resolved, unresolved = rp.resolve_members(["morpheus", "analyst", "ghost"], self.col, self.idx)
+        self.assertEqual([m["code"] for m in resolved], ["morpheus", "bmad-agent-analyst"])
+        self.assertEqual(unresolved, ["ghost"])
+
+    def test_empty(self):
+        self.assertEqual(rp.resolve_members([], self.col, self.idx), ([], []))
+
+
+class TestGroups(unittest.TestCase):
+    GROUPS = [
+        {"id": "wr", "name": "Writers", "members": ["analyst", "morpheus"]},
+        {"id": "bad"},  # no name -> falls back to id; no members -> count 0
+        {"name": "no-id"},  # dropped from menu
+    ]
+
+    def test_menu_is_names_only_with_counts_and_open_cast_flag(self):
+        menu = rp.group_menu(self.GROUPS)
+        self.assertEqual(menu, [
+            {"id": "wr", "name": "Writers", "member_count": 2},
+            {"id": "bad", "name": "bad", "member_count": 0, "open_cast": True},
+        ])
+
+    def test_find_group(self):
+        self.assertEqual(rp.find_group(self.GROUPS, "wr")["name"], "Writers")
+        self.assertIsNone(rp.find_group(self.GROUPS, "missing"))
+
+
+class TestGroupDetail(unittest.TestCase):
+    def setUp(self):
+        self.col, self.idx, _ = rp.build_collective(AGENTS, [{"code": "morpheus", "name": "Morpheus"}])
+
+    def test_scene_passes_through_when_present(self):
+        g = {"id": "tos-10-forward", "name": "Ten Forward", "members": ["morpheus"],
+             "scene": "Late evening, a few rounds in."}
+        d = rp.group_detail(g, self.col, self.idx)
+        self.assertEqual(d["scene"], "Late evening, a few rounds in.")
+        self.assertEqual([m["code"] for m in d["members"]], ["morpheus"])
+
+    def test_scene_omitted_when_absent_or_empty(self):
+        for g in ({"id": "g", "members": ["morpheus"]},
+                  {"id": "g", "members": ["morpheus"], "scene": ""}):
+            self.assertNotIn("scene", rp.group_detail(g, self.col, self.idx))
+
+    def test_anchored_group_is_not_open_cast(self):
+        g = {"id": "g", "members": ["morpheus"]}
+        self.assertNotIn("open_cast", rp.group_detail(g, self.col, self.idx))
+
+    def test_open_cast_group_flagged_with_empty_members(self):
+        g = {"id": "rebels", "name": "Star Wars Rebels",
+             "scene": "Figures from the Rebels universe drop in as the topic calls for them."}
+        d = rp.group_detail(g, self.col, self.idx)
+        self.assertTrue(d["open_cast"])
+        self.assertEqual(d["members"], [])
+        self.assertEqual(d["scene"][:7], "Figures")
+
+    def test_memory_enabled_follows_group_flag_and_defaults_off(self):
+        on = rp.group_detail({"id": "g", "members": ["morpheus"], "memory": True}, self.col, self.idx)
+        self.assertTrue(on["memory_enabled"])
+        off = rp.group_detail({"id": "g", "members": ["morpheus"], "memory": False}, self.col, self.idx)
+        self.assertFalse(off["memory_enabled"])
+        absent = rp.group_detail({"id": "g", "members": ["morpheus"]}, self.col, self.idx)
+        self.assertFalse(absent["memory_enabled"])  # opt-in per named group
+
+
+class TestInstalledCodesIsDefaultRoom(unittest.TestCase):
+    """The default room is installed agents only; pure customs stay in the pool."""
+
+    def test_pure_custom_excluded_override_kept_in_default_room(self):
+        col, _, installed = rp.build_collective(AGENTS, [
+            {"code": "morpheus", "name": "Morpheus"},                 # pure custom
+            {"code": "analyst", "name": "Mary-Custom", "persona": "p"},  # override
+            {"code": "sec-hawk", "name": "Vex"},                      # shipped crew member
+        ])
+        # Pure customs are in the pool...
+        self.assertIn("morpheus", col)
+        self.assertIn("sec-hawk", col)
+        # ...but NOT in the default room.
+        self.assertEqual(installed, ["bmad-agent-analyst", "bmad-agent-pm"])
+        default_room = [col[c]["code"] for c in installed]
+        self.assertEqual(default_room, ["bmad-agent-analyst", "bmad-agent-pm"])
+        # An override keeps its installed slot (and its custom content).
+        self.assertEqual(col["bmad-agent-analyst"]["name"], "Mary-Custom")
+
+
+if __name__ == "__main__":
+    unittest.main()
diff --git a/.claude/skills/bmad-prd/SKILL.md b/.claude/skills/bmad-prd/SKILL.md
new file mode 100644
index 0000000..07d3454
--- /dev/null
+++ b/.claude/skills/bmad-prd/SKILL.md
@@ -0,0 +1,94 @@
+---
+name: bmad-prd
+description: Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
+---
+# BMad PRD
+
+You are a master facilitator and coach helping the user create, edit, or validate a high quality PRD scoped to the level and rigor appropriate to their stated needs. Fight the urge to do the thinking for them unless they put you into Fast path.
+
+## Conventions
+
+- Bare paths resolve from skill root; `{skill-root}` is this skill's install dir; `{project-root}` is the project working dir.
+- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).
+- `{doc_workspace}` is the bound run folder.
+- **File roles.** `.memlog.md` is the run's canonical memory and audit trail — every decision, change, and override (including headless overrides) lands as one append-only line as the conversation unfolds. All writes go through the shared script, never by hand: `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <decision|change|override|assumption|event> --text "<one-line gist, reason included>"` (atomic; read it back only to resume or audit). The PRD is distilled toward it; whatever isn't logged is lost on resume. `addendum.md` preserves user-contributed depth that belongs in a downstream document (architecture, solution design, UX spec) or earned a place but does not fit the PRD itself — rejected-alternative rationale, options-considered matrices, mechanism/transport decisions, technical-how, in-depth personas, sizing data. Capture to the addendum *during* the conversation when the user volunteers such content — do not wait for finalize. Audit and override information never goes in the addendum.
+
+## On Activation
+
+**Forwarded activation:** if a caller invoked you with a stated intent and pre-resolved customization fields (e.g. the `bmad-create-prd` / `bmad-edit-prd` / `bmad-validate-prd` shims), honor them verbatim — skip your own intent inference, use the supplied values for those named fields, and resolve only the remaining fields from your own `customize.toml`.
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers, org tools preferred when their directive matches. Research itself fires during Discovery — see **Research subagents**.
+3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
+4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. In the greeting, let the user know that at any point they can invoke `bmad-party-mode` for multi-agent perspectives or `bmad-advanced-elicitation` for deeper exploration on a specific section. Then scan for misroute on the first message: if the signal points elsewhere (game → BMad GDS; express build → `bmad-build`; one-pager → `bmad-product-brief`; vet product idea → `bmad-prfaq`; agent skill or custom agent → `bmad-workflow-builder`), suggest they might want the other options before continuing.
+5. Detect intent: **Create** (no PRD), **Update** (existing PRD), **Validate** (critique only). If ambiguous, ask. For Create intent, before binding a fresh workspace, scan `{workflow.prd_output_path}` for prior in-progress runs (folders matching `{workflow.run_folder_pattern}` whose `prd.md` frontmatter `status` is not `final`); if any exist, offer to resume rather than starting over.
+
+Run `{workflow.activation_steps_append}`.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Intent Modes
+
+**Create.** Bind `{doc_workspace}` to `{workflow.prd_output_path}/{workflow.run_folder_pattern}/`. Write `prd.md` with YAML frontmatter (title, status, created, updated — initial `status: draft`), and seed the memlog with `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<PRD/product name>"` so subsequent decisions land in a known file. Tell the user the path. Run `## Discovery`, then `## Finalize`.
+
+**Update.** Reconcile the PRD with a change signal. Source-extract against PRD, addendum, `.memlog.md`, and original inputs (extract, don't ingest). If `.memlog.md` is missing, init it with `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace}`, then spawn a one-time bootstrap subagent to reverse-engineer a thin log from the PRD (one `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type decision --text "<recovered decision>"` per recovered decision) before continuing. Surface conflicts with prior decisions before applying. Then `## Finalize`.
+
+**Validate** (or *analyze*). Critique without changing. Load `references/validate.md`.
+
+## Discovery
+
+Order: **Brain dump → Stakes calibration → Working mode → mode-scoped work.** Get to working mode fast — two or three turns, not ten. Users in a hurry must not be held hostage by upstream probing.
+
+**Brain dump.** Always the first move, even when the user opens with paragraphs of context (that is intake, not the dump). Ask for verbal context *and* any existing inputs they want you to read — product brief, research, customer transcripts, competitive analysis, prior PRD draft, design docs. Paths or paste; big docs are fine, you will subagent-extract. A simple "anything else?" surfaces what they almost forgot.
+
+**Research subagents (default).** During Discovery, spawn web-research subagents to ground the picture: what exists in the space, how comparables position themselves, current landscape. Subagent does the search; parent receives a digest.
+
+**Elicitation, not direction.** Discovery pulls the user's vision out; it does not insert yours. Open-ended "tell me about X" beats multiple choice. When you find yourself naming wedges, picking MVP cuts, or proposing phases, stop — you have crossed from elicitation into authoring. Hand the pen back. Infer-and-confirm ("I'm assuming X works like Y — right?") is fine; quizzing the user through a tree of LLM-shaped choices is not.
+
+**Stakes calibration.** One short probe before working mode: hobby / internal / launch — enough to calibrate rigor and section depth. Audience, Existing inputs, and Downstream depth fill in inside the chosen mode, not upstream of the choice.
+
+**Working mode.** Offer the choice in the user's language:
+
+- **Fast path** — I batch remaining gaps into one or two consolidated questions, then draft the full PRD with `[ASSUMPTION]` tags where I inferred. You review and we iterate. The initial quality depends on how much you gave me upfront.
+- **Coaching path** — we walk PM-thinking sections together. Once chosen, I ask which entry point fits: **Vision + Features** (capability-first — for enterprise, dev products, internal tools, anyone who thinks in features), **Journey-led** (user-first — for consumer, UX-heavy, multi-stakeholder products; journeys with named protagonists carry persona context inline, no standalone persona section), or *let me suggest* based on what I heard. The chosen entry sets the section order.
+
+The workspace persists; stop and resume freely.
+
+**Concern scan.** As you read what the user gave you, name the concerns this product actually carries — compliance, integration density, operational SLAs, hardware constraints, public-API contracts, monetization, data governance, whatever applies. The list is open; recognize what's there, do not classify into a fixed shape. These concerns drive which template sections to pull in from the Adapt-In Menu and which to invent when no cluster names them.
+
+**Form-factor.** If not stated in sources, probe — mobile / web / desktop / multi-surface / hardware / API.
+
+**User Journeys are captured, not authored.** When UJs are warranted (consumer / multi-stakeholder B2B / meaningful UX — drop or downscale for internal tooling with a single operator role, regulatory-only updates, hobby/solo, pure technical PRDs), prompt the user to narrate a real session with a named protagonist (Mary, mom of three — not "the user") — what the person does, in what order, where it lands — then structure the answer into UJ-N form and confirm. Persona context lives inline at the moments that matter; no standalone persona section.
+
+## PRD Discipline
+
+**Shape.** Features grouped; FRs nested with globally numbered stable IDs. Cross-cutting NFRs in their own section; skip traceability matrices. Capabilities, not implementation — tech choices live in `addendum.md`. Treat `{workflow.prd_template}` as expert prior knowledge, not a checklist. The **Essential Spine** is the expected default — present it unless the product genuinely doesn't need a section, and when you drop one, do so for a reason a reviewer would agree with. The **Adapt-In Menu** is conditional: pull in the clusters the product's concerns need to best define the requirements. When the product carries a concern the menu doesn't name, invent the section — name it well, decide what belongs in it, place it where it serves the reader or the PRD. Reorder and combine for readability. Never include a section because it appears; never skip a concern because no template section covered it. Counter-metrics named when Success Metrics exist.
+
+**Extract, don't ingest.** Source documents go to subagents for extraction; the parent assembles from extracts. Only load source documents into the parent context wholesale when no subagents are available.
+
+**Length scales with stakes.** Hobby / solo PRDs aim for about two pages. Internal tools land around five to eight. Launch and chain-top PRDs run as long as their FRs and concerns require. Whatever the length, detail that doesn't earn its place in the PRD's main narrative belongs in `addendum.md` — moving overflow there is correct; padding the PRD to look thorough is not.
+
+## Reviewer Gate
+
+Used by the Validate intent and at Finalize step 3.
+
+Assemble the menu: rubric walker against `{workflow.validation_checklist_template}` (the PRD quality rubric) + each entry in `{workflow.finalize_reviewers}` + any ad-hoc reviewers the artifact warrants. Stakes-calibrated — hobby/solo may run quietly or skip; higher stakes get the explicit all/subset/skip menu.
+
+Dispatch entries as parallel subagents against `prd.md` (and `addendum.md` if present) using the standard prefix convention (`skill:` / `file:` / plain text). Each writes its full review to `{doc_workspace}/review-{slug}.md` and returns ONLY a compact summary (verdict, top 2-5 findings, file path) — the parent never holds full review text. The rubric walker uses the prompt and output format in `references/validate.md`. If subagents are unavailable, run sequentially: write the file *before* anything else, then flush the review from working context.
+
+Surface findings tiered, never dumped. Lead with a one-sentence gate verdict, then walk critical + high findings; medium/low roll into a single tail ("plus N more in {file}"). Read the full `review-{slug}.md` only when the user drills into a specific finding. Per finding: autofix, discuss, defer to open items, or ignore.
+
+Under Validate intent, the parent additionally runs the synthesis pipeline in `references/validate.md` — folding every selected reviewer's output into a single HTML + markdown report and opening the HTML.
+
+## Finalize
+
+Tell the user the sequence in one sentence, then walk it. Polish goes last so it does not redo work after reviewer fixes.
+
+1. **Memlog audit.** Walk `.memlog.md` with the user; each entry captured in PRD, in addendum, or set aside.
+2. **Input reconciliation.** Subagent per user-supplied input against `prd.md` + `addendum.md`. Each writes its extract to `{doc_workspace}/reconcile-{slug}.md` and returns ONLY a compact summary (input name, gaps 2-5, file path). Surface gaps — especially qualitative ideas (tone, voice, feel) the FR structure silently drops. Must happen before polish.
+3. **Reviewer pass.** Run `## Reviewer Gate`. Resolve before polish.
+4. **Triage open items.** All Open Questions, `[ASSUMPTION]` tags, `[NOTE FOR PM]` callouts. Phase-blockers (would make the PRD unsafe for UX/architecture/epics) surfaced one at a time and resolved; non-blockers deferred with owner + revisit condition logged via `memlog.py append`. If phase-blocker count is high, flag it.
+5. **Polish.** Apply `{workflow.doc_standards}` to `prd.md` and `addendum.md` in declared order (structural passes before prose — prose should not polish soon-to-be-cut text). Parallelize across documents, sequential within.
+6. **External handoffs.** Execute `{workflow.external_handoffs}`; surface returned URLs/IDs. Skip and flag unavailable tools.
+7. **Close.** Set `prd.md` frontmatter `status: final` and `updated` to `{date}` so future invocations distinguish this PRD from in-progress drafts. Record finalization via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type event --text "PRD finalized"`. Share artifact paths. Common next: `bmad-ux`, `bmad-architecture`, `bmad-create-epics-and-stories`; invoke `bmad-help` for authoritative routing.
+8. Run `{workflow.on_complete}` if non-empty.
diff --git a/.claude/skills/bmad-prd/assets/headless-schemas.md b/.claude/skills/bmad-prd/assets/headless-schemas.md
new file mode 100644
index 0000000..89d5b6c
--- /dev/null
+++ b/.claude/skills/bmad-prd/assets/headless-schemas.md
@@ -0,0 +1,76 @@
+# Headless Mode JSON Schemas
+
+Every headless run ends with one of these payloads. Omit keys for artifacts not produced.
+
+## Common fields
+
+- `status` — `"complete"`, `"blocked"`, or `"partial"`
+- `intent` — `"create"`, `"update"`, or `"validate"` (matches the detected intent)
+- `reason` — required when `status` is `"blocked"`; one-sentence explanation
+- `assumptions` — array of inferred values that were not directly confirmed by inputs
+- `open_questions` — array of items that need a human decision before the artifact can be considered final
+
+## Create
+
+```json
+{
+  "status": "complete",
+  "intent": "create",
+  "prd": "{doc_workspace}/prd.md",
+  "addendum": "{doc_workspace}/addendum.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "open_questions": [],
+  "assumptions": [],
+  "external_handoffs": [
+    {"directive": "Confluence upload", "tool": "corp:confluence_upload", "url": "https://confluence.corp/PROD/123", "status": "ok"}
+  ]
+}
+```
+
+## Update
+
+```json
+{
+  "status": "complete",
+  "intent": "update",
+  "prd": "{doc_workspace}/prd.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "changes_summary": "1-3 sentences describing what changed and why",
+  "conflicts_with_prior_decisions": [],
+  "open_questions": [],
+  "external_handoffs": [
+    {"directive": "Confluence upload", "tool": "corp:confluence_upload", "url": "https://confluence.corp/PROD/123", "status": "ok"}
+  ]
+}
+```
+
+## Validate
+
+```json
+{
+  "status": "complete",
+  "intent": "validate",
+  "validation_report": "{doc_workspace}/validation-report.md",
+  "findings_summary": {
+    "critical": 0,
+    "high": 0,
+    "medium": 0,
+    "low": 0
+  },
+  "offer_to_update": true
+}
+```
+
+`validation_report` is always written for Validate intent — the path here is required, not optional.
+
+## Blocked
+
+```json
+{
+  "status": "blocked",
+  "intent": "update",
+  "reason": "Change signal ambiguous — could be a scope expansion or a clarification; no inferred direction"
+}
+```
+
+Always include the intent (best-guess if not certain) and a one-sentence `reason`.
diff --git a/.claude/skills/bmad-prd/assets/prd-template.md b/.claude/skills/bmad-prd/assets/prd-template.md
new file mode 100644
index 0000000..6f340e5
--- /dev/null
+++ b/.claude/skills/bmad-prd/assets/prd-template.md
@@ -0,0 +1,165 @@
+# PRD Template
+
+## Essential Spine *(almost always present)*
+
+```markdown
+---
+title: {Product Name}
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+
+# PRD: {Product Name}
+*Working title — confirm.*
+
+## 0. Document Purpose
+[1 paragraph: who this PRD is for (PM, stakeholders, downstream workflow owners), how it's structured (Glossary-anchored vocabulary, features grouped with FRs nested, assumptions tagged inline and indexed). If UX work or other inputs already exist, name them here and reference where they live — this PRD builds on them, it does not duplicate.]
+
+## 1. Vision
+[2-3 paragraphs: what this is, what it does for the user, why it matters. Compelling enough to stand alone.]
+
+## 2. Target User
+
+### 2.1 Jobs To Be Done
+[Bulleted. Emotional, social, functional, contextual — whichever apply. Even "this is for me as the builder" is a valid framing for a hobby project.]
+
+### 2.2 Non-Users (v1) *(add when the audience boundary is non-obvious)*
+[Who this is explicitly not for in v1.]
+
+### 2.3 Key User Journeys
+*Named-persona narratives the product enables. Numbered globally as UJ-1 through UJ-N. FRs reference journeys by ID inline ("realizes UJ-3"); SMs may also cross-reference. If a UX doc already exists, mirror its UJ IDs here and point to the source.*
+
+**Default shape:** a named scene with entry state, path, climax, and resolution. Each beat forces specificity the team would otherwise leave implicit — auth assumptions, screen order, what tells the user value landed. Read together as a short narrative; the example below shows the form.
+
+- **UJ-1. {One-line title — persona doing the thing.}**
+  - **Persona + context:** one line, grounded enough to explain the *why*.
+  - **Entry state:** authenticated? which surface? coming from where?
+  - **Path:** 3-5 concrete beats — taps, screens, decisions.
+  - **Climax:** the moment value is delivered and how the user knows.
+  - **Resolution:** state they're left in, what's next.
+  - **Edge case** *(optional)*: one real failure mode and what the user does next.
+
+  *Written out, that becomes:*
+  > **UJ-3. Priya checks the trip damage before she's even home.**
+  > Priya, budgeting on a single income with a new baby, finishes a grocery run and gets in the car. Already authenticated via biometric on a previous session. She opens the app, taps the FAB camera, and scans the receipt. The app OCRs the total and shows a single-screen overlay: this trip $84.20, weekly cap $250, $172.10 remaining, three days left in the week. She closes the app and drives home. **Edge case:** if she scanned a receipt earlier today, the app asks whether this replaces or adds to that trip before counting it against the cap.
+
+- **UJ-2. ...**
+
+**Scope dial:**
+- **Lighter** — hobby/solo, library/CLI, or when the UJ is essentially a JTBD restated: a single sentence works (`{Persona}, {context}, {what they do and why}.`).
+- **Heavier** — auth, multi-device handoff, complex navigation, or anything feeding downstream UX/architecture: add a numbered Flow, an Edge cases list, and a capability → FR mapping (`The system must {capability}. → FR-N`).
+
+## 3. Glossary
+*Downstream workflows and readers must use these terms exactly. FRs, UJs, and SMs use Glossary terms verbatim; introducing a synonym anywhere in the PRD is a discipline violation. If §4 introduces a new domain noun, add it to the Glossary in the same pass.*
+
+- **Term** — Definition. Relationships to other Glossary terms. Cardinality where relevant.
+- **Term** — ...
+
+[Every domain noun the rest of the document uses. Defined once. No synonyms anywhere else in the PRD.]
+
+## 4. Features
+*Each subsection is a coherent feature: behavioral description first, FRs nested under it, optional feature-specific NFRs and notes. FRs are numbered globally (FR-1 through FR-N) so downstream artifacts have stable references even if features get reorganized. Reference user journeys by ID inline ("realizes UJ-2") where the chain matters.*
+
+### 4.1 {Feature Name}
+**Description:** [Behavioral narrative — how this feature works, who uses it, the user experience, edge cases. Realizes UJ-X, UJ-Y. Use Glossary terms exactly. Embed inline `[ASSUMPTION: ...]` tags where you inferred without confirmation.]
+
+**Functional Requirements:**
+
+#### FR-1: {Short capability name}
+
+[Actor] can [capability] [under conditions]. Realizes UJ-X.
+
+**Consequences (testable):**
+- {Specific testable condition, e.g. "System returns HTTP 429 when request rate exceeds 100/sec per merchant."}
+- {Another testable condition.}
+
+**Out of Scope:** *(optional — what this FR explicitly does NOT cover)*
+- {bound}
+
+#### FR-2: ...
+
+**Feature-specific NFRs:** *(only if any apply uniquely to this feature)*
+- Performance / security / accessibility / etc. specific to this feature.
+
+**Notes:** *(optional — open questions specific to this feature, `[NOTE FOR PM]` callouts)*
+
+### 4.2 {Feature Name}
+...
+
+## 5. Non-Goals (Explicit)
+[Bulleted. What this product is *not* and what it will *not* do in v1. Does outsized work for downstream readers and workflows — prevents the "let me also add this nearby thing" failure mode at every level (epic, ticket, code). Inline `[NON-GOAL for MVP]` callouts within §4 Features cover deferred items within features; this section captures the broader "we are not building X / we are not becoming Y" statements.]
+
+## 6. MVP Scope
+
+### 6.1 In Scope
+[Bulleted, crisp.]
+
+### 6.2 Out of Scope for MVP
+[Bulleted. Each item with a one-line reason if the reason matters. Mark items deferred to v2/v3 explicitly. Add `[NOTE FOR PM]` callouts where a deferred item is emotionally load-bearing — flags it for revisit if timeline permits.]
+
+## 7. Success Metrics
+
+*Each SM cross-references the FR(s) it validates. Counter-metrics counterbalance specific primary or secondary metrics.*
+
+**Primary**
+- **SM-1**: Metric — definition, target. Validates FR-X, FR-Y.
+
+**Secondary**
+- **SM-2**: Metric — definition, target. Validates FR-Z.
+
+**Counter-metrics (do not optimize)**
+- **SM-C1**: Metric — why this should *not* be optimized. Counterbalances SM-1.
+
+[Length scales with stakes. Hobby/utility PRD: a single sentence may be enough ("Success: I use this weekly and don't abandon it after a month"). Public launch / enterprise: full quantitative breakdown with measurement methods. Counter-metrics are as load-bearing as primary metrics — they prevent the architect from optimizing the wrong thing and the dev from gaming the wrong target.]
+
+## 8. Open Questions
+[Numbered. Things still unknown — they become future tickets or follow-up research, not silent gaps.]
+
+## 9. Assumptions Index
+*Every `[ASSUMPTION]` from the document, surfaced for explicit confirmation:*
+- Inline assumption from §X.Y — short description.
+- ...
+```
+
+---
+
+## Adapt-In Menu *(add the clusters the product calls for)*
+
+### Cross-cutting quality and shape *(most non-trivial PRDs)*
+- **Cross-Cutting NFRs** — system-wide non-functional requirements not tied to a single feature (performance, security, reliability, observability). Add when system-wide quality attributes are meaningful.
+- **Constraints and Guardrails** — Safety, Privacy, Cost. Subsection per cluster. Add when any of these are real concerns.
+- **Why Now** — add when timing is load-bearing (a market shift, a technology enabler, a regulatory deadline). Drop when timing is incidental.
+
+### Consumer / branded products
+- **Aesthetic and Tone** — visual references, anti-references, voice/tone for any product-generated text.
+- **Information Architecture** — top-level surfaces, navigation, screens.
+- **Monetization** — free vs. paid, pricing assumptions, ads policy.
+- **Platform** — web, mobile, PWA, native, v1 vs. v2+.
+
+### Enterprise initiatives
+- **Stakeholders and Approvals** — who must sign off, at what stage.
+- **Risk and Mitigations** — operational, security, business, reputational risk register.
+- **ROI / Business Case** — quantified benefit, cost, payback period.
+- **Operational Requirements** — SLAs, RTO/RPO, support tier, on-call expectations.
+- **Integration and Dependencies** — SSO, existing enterprise systems, data sources, downstream consumers.
+- **Rollout and Change Management** — phased rollout plan, training, internal communication.
+- **Data Governance** — residency, sovereignty, classification, retention.
+- **Audit Trail / Decision Provenance** — formal documentation requirements for regulated environments.
+
+### Regulated domains
+- **Compliance and Regulatory** — HIPAA, PCI-DSS, GDPR, SOX, SOC 2, Section 508 / WCAG 2.1 AA, FedRAMP, etc. — whichever apply. If any item needs depth, add a `[NOTE FOR PM]` callout to revisit or move to an addendum.
+
+### Developer products (libraries, APIs, CLIs, SDKs)
+- **API Contracts / Public Surface** — endpoint shapes, breaking change policy.
+- **Versioning and Deprecation Policy**.
+- **Performance Budgets** — latency, throughput, resource use.
+- **Language / Runtime Targets and Dependency Policy**.
+
+### Embedded / hardware
+- **Hardware Constraints** — memory, power, form factor.
+- **Deployment and Update Mechanism** — OTA, manual, image-based.
+- **Environmental and Reliability Requirements**.
+
+### Small-scope all-inclusive *(use when scope is 1-2 stories' worth and the user wants a single captured artifact — chosen during the Right-skill check in Discovery)*
+- **Stories** — story-level specs listed inline at the end of the doc. Each story: *"As a [persona], I can [action] [under conditions]. Acceptance: [testable criteria]."* Numbered Story-1, Story-2, ... for reference. Pair with very lean §1 Vision, §2 Target User (often just JTBD + one UJ), §3 Glossary (handful of terms), §4 Features (often a single feature), §6 MVP Scope (in/out very tight). The whole doc fits on a page or two and captures intent + implementable stories in one place. If the user doesn't want the captured artifact at all, `bmad-build` is the better path — this cluster is only for "I want a doc *and* the stories."
+
diff --git a/.claude/skills/bmad-prd/assets/prd-validation-checklist.md b/.claude/skills/bmad-prd/assets/prd-validation-checklist.md
new file mode 100644
index 0000000..f52c43b
--- /dev/null
+++ b/.claude/skills/bmad-prd/assets/prd-validation-checklist.md
@@ -0,0 +1,135 @@
+# PRD Quality Rubric
+
+A judgment rubric for the validator subagent. Walk the PRD with these dimensions in mind and write substantive findings — not box-ticking. The goal is a review that tells the user whether this PRD is *good*, not whether it has the right section headers.
+
+Most PRDs do not need every dimension scrutinized equally. Calibrate to the agreed stakes, the PRD's shape (consumer product, internal tool, regulatory update, technical capability spec), and what the PRD itself is trying to do. Be specific — cite locations, quote phrases, name what's missing. Abstract criticism is failure of nerve.
+
+## How to use this rubric
+
+1. Read the full PRD (and addendum.md if present) before writing anything.
+2. For each of the seven dimensions below, form a judgment — *strong / adequate / thin / broken* — backed by specifics from the PRD.
+3. Write findings only where they add information. A `strong` dimension may need no findings; a `broken` one needs concrete, fixable ones.
+4. Severity ranks impact on the PRD's usefulness, not how easy the fix is. A vague Vision statement is *critical* even though it's a one-paragraph fix; a glossary drift might be *low* even though it appears in many places.
+5. The overall verdict is your synthesis — 2–3 sentences that name what holds up and what's at risk. Earn it with the dimension judgments.
+
+## Output format
+
+Write findings to `{doc_workspace}/review-rubric.md`:
+
+```markdown
+# PRD Quality Review — {prd_name}
+
+## Overall verdict
+[2–3 sentences. What holds up, what's at risk. Earned by the dimension judgments below.]
+
+## Decision-readiness — [strong | adequate | thin | broken]
+[1–3 paragraphs of judgment with specific PRD locations.]
+
+### Findings
+- **[critical|high|medium|low]** [Title] (§ location) — [Note]. *Fix:* [suggested fix].
+
+## Substance over theater — [verdict]
+...
+
+(repeat for each dimension)
+
+## Mechanical notes
+[Glossary drift, ID continuity, broken cross-refs, Assumptions Index roundtrip. Lighter weight — these matter for downstream but don't drive the overall verdict.]
+```
+
+## The seven dimensions
+
+### 1. Decision-readiness
+
+Can a decision-maker act on this PRD? Are the trade-offs surfaced honestly, or has the PRD smoothed everything to neutral? Would someone pushing back find their objection acknowledged or dodged?
+
+Look for:
+- Decisions that are stated as decisions, not buried as "considerations."
+- Trade-offs named with what was given up, not just what was chosen.
+- Open Questions that are actually open — not rhetorical questions with an answer in the next sentence.
+- `[NOTE FOR PM]` callouts at real tensions, not at safe checkpoints.
+
+Red flag: a PRD where every choice "balances" everything, every NFR is "important," every persona "values" the product.
+
+### 2. Substance over theater
+
+Is the content earned, or is it furniture? Distinguish:
+
+- **Persona theater** — Personas that don't drive a single decision in the PRD. More than four personas. Personas whose only function is to make the PRD look thorough.
+- **Innovation theater** — claimed novelty that isn't novel. Differentiation sections written because the template had one, not because Discovery surfaced something.
+- **NFR theater** — copied boilerplate ("system must be scalable / secure / reliable") without product-specific thresholds.
+- **Vision theater** — a Vision statement that could swap into any PRD in this category without change.
+
+Flag what reads like furniture, even if it's well-written furniture.
+
+### 3. Strategic coherence
+
+Does the PRD have a thesis? Do the features serve a unified arc, or is it a list of capabilities someone wanted?
+
+Look for:
+- A stated thesis the PRD bets on (problem framing, user insight, market move).
+- Feature prioritization that follows from the thesis — not from "what's easy first."
+- Success Metrics that validate the thesis, not metrics that just measure activity (DAU/MAU when the thesis is about engagement quality is a tell).
+- Counter-metrics named when SMs exist.
+- Coherent MVP scope kind — problem-solving, experience, platform, or revenue — with scope logic that matches.
+
+Red flag: a PRD that reads as a backlog with section headings.
+
+### 4. Done-ness clarity
+
+Would an engineer reading this PRD know what "done" looks like for each FR?
+
+Look for:
+- FRs with at least one testable consequence per FR — verifiable condition, measurable outcome.
+- "System handles X gracefully," "reasonable performance," "user-friendly" — flag every one.
+- Acceptance criteria implied or explicit. Sometimes the FR's consequences carry this; sometimes the PRD genuinely needs an Acceptance section.
+- For non-functional sections (UX, performance, security): bounds, not adjectives.
+
+This is the dimension downstream story creation will lean on hardest. Be unforgiving here.
+
+### 5. Scope honesty
+
+Are omissions explicit, or is the reader meant to infer them?
+
+Look for:
+- A Non-Goals section where it would do real work — and `[NON-GOAL for MVP]` callouts where omissions could be silently assumed.
+- `[ASSUMPTION: …]` tags on inferences the user didn't directly confirm, indexed at the end.
+- `[NOTE FOR PM]` callouts at deferred decisions and unresolved tensions.
+- De-scoping proposed honestly, not done silently.
+
+Open-items density: count Open Questions + `[ASSUMPTION]` + `[NOTE FOR PM]` callouts relative to stakes. High counts on a low-stakes PRD is fine; high counts on a green-light-to-build PRD is a blocker.
+
+### 6. Downstream usability
+
+If this PRD feeds UX, architecture, or story creation, can those workflows source-extract from it cleanly?
+
+Look for:
+- Glossary present; every domain noun used identically across FRs, UJs, SM definitions.
+- FR / UJ / SM IDs contiguous, unique, and cross-references that resolve.
+- Each section makes sense pulled out alone — cross-references via Glossary terms, not "see above."
+- UJs each have a named protagonist; no floating UJs.
+
+For standalone PRDs (no downstream), this dimension matters less — say so.
+
+### 7. Shape fit
+
+Has the PRD been forced into a shape that doesn't match the product?
+
+- Consumer product / multi-stakeholder B2B / meaningful UX → UJs with named protagonists are load-bearing.
+- Internal tool, single-operator role → capability spec shape; UJs may be overhead; SMs may be operational rather than user-facing.
+- Regulatory or compliance update → constraint traceability is non-negotiable; UJs may be irrelevant.
+- Hobby / solo → rigor light, substance bar still applies.
+- Brownfield → existing-code references must be accurate; new UJs and existing UJs must be distinguished.
+- Chain-top (feeds UX → architecture → stories) → downstream usability matters more; standalone PRDs can be lighter on traceability.
+
+Flag PRDs that are over-formalized (UJ density for a single-operator tool) or under-formalized (consumer product with no UJs).
+
+## Mechanical notes
+
+Cover these as a tail section, not a primary dimension. They matter for downstream but don't drive the verdict on whether the PRD is good.
+
+- Glossary drift (case, plural, synonyms across the PRD).
+- ID continuity (gaps, duplicates, unresolved cross-references).
+- Assumptions Index roundtrip (every inline `[ASSUMPTION]` indexed; index entries all appear inline).
+- UJ protagonist naming (each UJ has a named protagonist carrying context inline).
+- Required sections present for the agreed stakes and product type.
diff --git a/.claude/skills/bmad-prd/assets/validation-report-template.html b/.claude/skills/bmad-prd/assets/validation-report-template.html
new file mode 100644
index 0000000..72e7271
--- /dev/null
+++ b/.claude/skills/bmad-prd/assets/validation-report-template.html
@@ -0,0 +1,325 @@
+<!DOCTYPE html>
+<!--
+  PRD Validation Report — skeleton template.
+
+  This file is a starter the synthesis pass fills in directly. There is no
+  substitution engine. The LLM:
+    1. Reads {doc_workspace}/review-rubric.md and every review-{slug}.md from
+       additional reviewers.
+    2. Copies this skeleton.
+    3. Replaces the placeholder content (everything between TEMPLATE markers)
+       with the consolidated review, preserving the structure and CSS.
+    4. Writes the result to {doc_workspace}/validation-report.html.
+    5. Writes a markdown twin to {doc_workspace}/validation-report.md.
+
+  Visual rules the LLM must preserve:
+    - The container width, the color tokens, the typography.
+    - One dimension = one collapsible <section class="dimension">.
+    - Verdict pill uses the verdict-* class matching its judgment.
+    - Severity badge uses the sev-* class matching its level.
+    - Each extra reviewer (adversarial, etc.) gets its own collapsible section
+      below the rubric dimensions.
+    - The footer always shows the artifact paths and timestamp.
+-->
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>PRD Validation: TEMPLATE_PRD_NAME</title>
+<style>
+  :root {
+    --bg: #fafaf9;
+    --surface: #ffffff;
+    --border: #e7e5e4;
+    --text: #1c1917;
+    --muted: #78716c;
+
+    --verdict-strong: #16a34a;
+    --verdict-adequate: #65a30d;
+    --verdict-thin: #d97706;
+    --verdict-broken: #dc2626;
+
+    --sev-low: #64748b;
+    --sev-medium: #ca8a04;
+    --sev-high: #ea580c;
+    --sev-critical: #dc2626;
+
+    --grade-exc: #16a34a;
+    --grade-good: #65a30d;
+    --grade-fair: #d97706;
+    --grade-poor: #dc2626;
+  }
+  * { box-sizing: border-box; }
+  html, body { margin: 0; padding: 0; }
+  body {
+    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Inter, system-ui, sans-serif;
+    background: var(--bg);
+    color: var(--text);
+    line-height: 1.6;
+    font-size: 15px;
+  }
+  .container { max-width: 960px; margin: 0 auto; padding: 32px 24px 64px; }
+
+  header.report-header {
+    display: flex;
+    align-items: flex-start;
+    justify-content: space-between;
+    gap: 24px;
+    padding-bottom: 16px;
+    border-bottom: 1px solid var(--border);
+    margin-bottom: 24px;
+  }
+  .title h1 { margin: 0; font-size: 22px; font-weight: 600; letter-spacing: -0.01em; }
+  .title .subtitle { color: var(--muted); font-size: 13px; margin-top: 4px; font-family: ui-monospace, "SF Mono", Menlo, monospace; }
+  .grade {
+    padding: 10px 18px;
+    border-radius: 8px;
+    font-weight: 600;
+    color: white;
+    font-size: 15px;
+    white-space: nowrap;
+  }
+  .grade-excellent { background: var(--grade-exc); }
+  .grade-good { background: var(--grade-good); }
+  .grade-fair { background: var(--grade-fair); }
+  .grade-poor { background: var(--grade-poor); }
+
+  .synthesis {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-left: 3px solid var(--muted);
+    border-radius: 8px;
+    padding: 18px 22px;
+    margin-bottom: 24px;
+    font-size: 15.5px;
+  }
+  .synthesis p { margin: 0 0 10px; }
+  .synthesis p:last-child { margin-bottom: 0; }
+
+  .dimension-summary {
+    display: grid;
+    grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
+    gap: 10px;
+    margin-bottom: 24px;
+  }
+  .dim-card {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-radius: 8px;
+    padding: 12px 14px;
+  }
+  .dim-card .dim-name { font-size: 13px; color: var(--muted); margin-bottom: 6px; }
+  .dim-card .dim-verdict { font-size: 14px; font-weight: 600; }
+
+  section.dimension, section.reviewer-section { margin-bottom: 14px; }
+  section.dimension details, section.reviewer-section details {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-radius: 8px;
+    overflow: hidden;
+  }
+  section summary {
+    padding: 14px 20px;
+    cursor: pointer;
+    user-select: none;
+    list-style: none;
+    display: flex;
+    align-items: center;
+    gap: 12px;
+  }
+  section summary::-webkit-details-marker { display: none; }
+  section summary::before {
+    content: "▸";
+    display: inline-block;
+    color: var(--muted);
+    transition: transform 0.15s ease;
+  }
+  section details[open] summary::before { transform: rotate(90deg); }
+  section summary h2 {
+    display: inline;
+    margin: 0;
+    font-size: 16px;
+    font-weight: 600;
+    letter-spacing: -0.005em;
+    flex: 1;
+  }
+  .verdict-pill {
+    font-size: 11px;
+    padding: 3px 10px;
+    border-radius: 999px;
+    font-weight: 600;
+    text-transform: uppercase;
+    letter-spacing: 0.04em;
+    color: white;
+  }
+  .verdict-strong { background: var(--verdict-strong); }
+  .verdict-adequate { background: var(--verdict-adequate); }
+  .verdict-thin { background: var(--verdict-thin); }
+  .verdict-broken { background: var(--verdict-broken); }
+
+  .dim-body { padding: 4px 20px 18px; }
+  .dim-judgment { color: var(--text); font-size: 14.5px; }
+  .dim-judgment p { margin: 0 0 10px; }
+
+  .findings-list { padding: 0 20px 4px; }
+  article.finding {
+    padding: 14px 0;
+    border-top: 1px solid var(--border);
+  }
+  article.finding:first-child { border-top: none; }
+  article.finding header {
+    display: flex;
+    align-items: center;
+    gap: 10px;
+    flex-wrap: wrap;
+    margin-bottom: 6px;
+  }
+  .badge {
+    font-size: 10.5px;
+    padding: 3px 8px;
+    border-radius: 4px;
+    font-weight: 600;
+    text-transform: uppercase;
+    letter-spacing: 0.04em;
+    line-height: 1.4;
+  }
+  .badge-sev-low { background: rgba(100, 116, 139, 0.12); color: var(--sev-low); }
+  .badge-sev-medium { background: rgba(202, 138, 4, 0.14); color: var(--sev-medium); }
+  .badge-sev-high { background: rgba(234, 88, 12, 0.14); color: var(--sev-high); }
+  .badge-sev-critical { background: rgba(220, 38, 38, 0.14); color: var(--sev-critical); }
+  .finding-title { margin: 0; font-size: 15px; font-weight: 500; flex: 1; min-width: 200px; }
+  .finding-location { font-family: ui-monospace, "SF Mono", Menlo, monospace; font-size: 12.5px; color: var(--muted); }
+  .finding-note, .finding-fix { margin-top: 6px; font-size: 14px; }
+  .finding-fix strong { color: var(--muted); font-weight: 500; }
+
+  .reviewer-source {
+    font-size: 12px;
+    color: var(--muted);
+    font-family: ui-monospace, "SF Mono", Menlo, monospace;
+  }
+
+  .mechanical {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-radius: 8px;
+    padding: 16px 20px;
+    margin-top: 24px;
+    font-size: 14px;
+  }
+  .mechanical h3 { margin: 0 0 10px; font-size: 14px; font-weight: 600; color: var(--muted); text-transform: uppercase; letter-spacing: 0.04em; }
+  .mechanical ul { margin: 0; padding-left: 20px; }
+  .mechanical li { margin-bottom: 4px; color: var(--text); }
+
+  footer.report-footer {
+    margin-top: 40px;
+    padding-top: 16px;
+    border-top: 1px solid var(--border);
+    font-size: 12px;
+    color: var(--muted);
+    font-family: ui-monospace, "SF Mono", Menlo, monospace;
+  }
+  footer .meta { display: flex; gap: 24px; flex-wrap: wrap; }
+</style>
+</head>
+<body>
+  <div class="container">
+
+    <!-- TEMPLATE: header. Fill prd name, prd path, grade text & class. -->
+    <header class="report-header">
+      <div class="title">
+        <h1>TEMPLATE_PRD_NAME — Validation Report</h1>
+        <div class="subtitle">TEMPLATE_PRD_PATH</div>
+      </div>
+      <div class="grade TEMPLATE_GRADE_CLASS">TEMPLATE_GRADE</div>
+    </header>
+
+    <!-- TEMPLATE: overall synthesis paragraphs. Lift directly from
+         review-rubric.md "Overall verdict" section; expand if extra reviewers
+         materially shift the picture. Wrap each paragraph in <p>. -->
+    <div class="synthesis">
+      <p>TEMPLATE_SYNTHESIS_PARAGRAPH</p>
+    </div>
+
+    <!-- TEMPLATE: dimension summary cards. One per rubric dimension. The
+         dim-verdict text uses one of: strong | adequate | thin | broken. -->
+    <div class="dimension-summary">
+      <div class="dim-card">
+        <div class="dim-name">Decision-readiness</div>
+        <div class="dim-verdict" style="color: var(--verdict-TEMPLATE_VERDICT)">TEMPLATE_VERDICT_TEXT</div>
+      </div>
+      <!-- repeat for each of the seven dimensions -->
+    </div>
+
+    <!-- TEMPLATE: one section per rubric dimension. Skip a dimension entirely
+         if the rubric review marked it n/a for this PRD (e.g. downstream
+         usability for a standalone PRD). Open the section by default if
+         verdict is thin or broken. -->
+    <section class="dimension">
+      <details open>
+        <summary>
+          <h2>Decision-readiness</h2>
+          <span class="verdict-pill verdict-TEMPLATE_VERDICT">TEMPLATE_VERDICT_TEXT</span>
+        </summary>
+        <div class="dim-body">
+          <div class="dim-judgment">
+            <p>TEMPLATE_DIMENSION_JUDGMENT</p>
+          </div>
+        </div>
+        <div class="findings-list">
+          <!-- TEMPLATE: zero or more findings -->
+          <article class="finding">
+            <header>
+              <span class="badge badge-sev-TEMPLATE_SEVERITY">TEMPLATE_SEVERITY</span>
+              <h3 class="finding-title">TEMPLATE_FINDING_TITLE</h3>
+              <span class="finding-location">TEMPLATE_LOCATION</span>
+            </header>
+            <div class="finding-note">TEMPLATE_FINDING_NOTE</div>
+            <div class="finding-fix"><strong>Fix:</strong> TEMPLATE_SUGGESTED_FIX</div>
+          </article>
+        </div>
+      </details>
+    </section>
+
+    <!-- TEMPLATE: one section per extra reviewer that ran (adversarial, etc.).
+         Skip this block entirely if only the rubric walker ran. -->
+    <section class="reviewer-section">
+      <details>
+        <summary>
+          <h2>Adversarial review</h2>
+          <span class="reviewer-source">TEMPLATE_REVIEWER_SOURCE_FILE</span>
+        </summary>
+        <div class="dim-body">
+          <div class="dim-judgment">
+            <p>TEMPLATE_REVIEWER_PREAMBLE</p>
+          </div>
+        </div>
+        <div class="findings-list">
+          <article class="finding">
+            <header>
+              <span class="badge badge-sev-TEMPLATE_SEVERITY">TEMPLATE_SEVERITY</span>
+              <h3 class="finding-title">TEMPLATE_FINDING_TITLE</h3>
+              <span class="finding-location">TEMPLATE_LOCATION</span>
+            </header>
+            <div class="finding-note">TEMPLATE_FINDING_NOTE</div>
+            <div class="finding-fix"><strong>Fix:</strong> TEMPLATE_SUGGESTED_FIX</div>
+          </article>
+        </div>
+      </details>
+    </section>
+
+    <!-- TEMPLATE: mechanical notes — short, bulleted. Skip if there are none. -->
+    <div class="mechanical">
+      <h3>Mechanical notes</h3>
+      <ul>
+        <li>TEMPLATE_MECHANICAL_NOTE</li>
+      </ul>
+    </div>
+
+    <footer class="report-footer">
+      <div class="meta">
+        <span>Rubric: TEMPLATE_RUBRIC_PATH</span>
+        <span>Generated: TEMPLATE_TIMESTAMP</span>
+      </div>
+    </footer>
+  </div>
+</body>
+</html>
diff --git a/.claude/skills/bmad-prd/customize.toml b/.claude/skills/bmad-prd/customize.toml
new file mode 100644
index 0000000..64389aa
--- /dev/null
+++ b/.claude/skills/bmad-prd/customize.toml
@@ -0,0 +1,149 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-prd.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-prd.toml         (team)
+#   {project-root}/_bmad/custom/bmad-prd.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays: append
+
+# Steps to run before the standard activation (config load, greet).
+# Use for pre-flight loads, compliance checks, etc.
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Use for context-heavy setup that should happen once the user has been acknowledged.
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Each entry is either a literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed path/glob
+# whose contents are loaded as facts.
+#
+# Default loads project-context.md if bmad-generate-project-context has produced one — this gives
+# the facilitator persistent awareness of the project's tech, domain, and constraints without
+# re-asking. Common opt-ins (set in team/user override TOML):
+#   "skill:acme-co:terms-and-conditions"                                      # a skill that contains some relevant info
+#   "Investor PRDs must include a market sizing section."                    # generic agent instruction
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Executed when the workflow completes (after the user has been told the
+# PRD is ready). Accepts either a string scalar (single instruction)
+# or an array of instructions executed in order. Empty for none.
+on_complete = ""
+
+# Default PRD structure. Treated as a starting point — the LLM adapts it
+# to the product, project type, and domain. Override the path in team/user TOML
+# to enforce a different structure (e.g. regulated-industry, internal-tool, investor-input).
+prd_template = "assets/prd-template.md"
+
+# PRD quality rubric used at the Validate intent and at Finalize step 3.
+# A subagent walks the rubric against prd.md and writes a substantive review
+# organized by quality dimensions (decision-readiness, substance, strategic
+# coherence, etc.). Override the path in team/user TOML to enforce an
+# org-specific rubric (regulated-industry compliance, investor-pitch standards,
+# etc.). The filename "checklist" is retained for back-compat with override
+# files; the content is a judgment rubric, not a boolean checklist.
+validation_checklist_template = "assets/prd-validation-checklist.md"
+
+# HTML skeleton the synthesis pass fills directly when consolidating reviewer
+# outputs into a validation report. No substitution engine — the parent LLM
+# reads every {doc_workspace}/review-*.md, fills the skeleton's TEMPLATE_*
+# placeholders, and writes the result. Fully overridable to match org branding.
+# Uses inline CSS, no external dependencies, and native HTML <details> for
+# collapse — no JS.
+validation_report_template = "assets/validation-report-template.html"
+
+# Run folder location. The PRD, optional addendum, memlog, and optional
+# validation report all land inside `{prd_output_path}/{run_folder_pattern}/`.
+# Resume-check scans `{prd_output_path}` for prior unfinished runs.
+prd_output_path = "{planning_artifacts}/prds"
+run_folder_pattern = "prd-{project_name}-{date}"
+
+# Document standards applied to human-consumed docs at finalize. Each entry is
+# a `skill:`, `file:`, or plain-text directive; the parent LLM applies the
+# findings before the user sees the draft. Encodes standards, not options.
+#
+# Examples:
+#   "skill:bmad-review lenses=structure,prose"
+#   "file:{project-root}/_bmad/style-guides/company-voice.md"
+#   "Convert all dates to ISO 8601 format."
+#
+# Suggested order (broader passes first, narrower last):
+#   1. Structural (cuts, reorganization, section sizing)
+#   2. Content/voice/conventions (org standards, tone, terminology, compliance)
+#   3. Prose mechanics (grammar, clarity, typos)
+#
+# Override the array in team/user TOML to add additional standards. Append-only:
+# base entries cannot be removed or replaced (resolver has no removal mechanism).
+# The default entry runs bmad-review's two editorial lenses in order:
+# structure, then prose on top of the structure findings. The `lenses=` suffix
+# names them; drop it to let bmad-review pick what fits the content.
+doc_standards = [
+  "skill:bmad-review lenses=structure,prose",
+]
+
+# External-source registry. Natural-language directives describing knowledge
+# bases, MCP tools, or internal systems the LLM may consult during the workflow
+# when a relevant need surfaces. The LLM does NOT query these preemptively —
+# it consults them on demand (during Discovery, validation, drafting, etc.).
+# Each entry names the tool, the conditions for using it, and any fields the
+# tool needs. If a named MCP tool is unavailable at runtime, the LLM falls
+# back to standard behavior and notes the gap. Empty by default.
+#
+# Lifecycle note: distinct from persistent_facts. persistent_facts are loaded
+# once at activation and kept in mind for the whole run; external_sources are
+# a registry consulted on demand and only when the conversation surfaces a
+# matching need.
+#
+# Examples (set in team/user override TOML):
+#   "When researching internal product context, consult corp:kb_search (database='product-docs') before web search."
+#   "For competitive landscape during Discovery, query corp:competitive_db with category={project_name}."
+#   "When validating domain-compliance claims, cross-check against corp:hipaa_reference for healthcare or corp:pci_reference for fintech."
+external_sources = []
+
+# External-handoff routing. Natural-language directives the LLM applies at
+# Finalize to route outputs beyond local files (Confluence, Notion, Google
+# Drive, ticket systems, etc.). Each entry names the MCP tool, the destination,
+# and the fields the tool needs. Handoffs run after the artifact is polished
+# and before the final user-facing message. URLs or IDs returned by the
+# destination are captured and surfaced to the user. If a named tool is
+# unavailable at runtime, the handoff is skipped and flagged in the JSON
+# status; local files always exist regardless. Fires automatically — users
+# can opt out in their prompt for a specific run. Empty by default.
+#
+# Lifecycle note: distinct from persistent_facts and external_sources.
+# Fired once at Finalize step 6, never during Discovery or drafting.
+#
+# Examples (set in team/user override TOML):
+#   "After finalize, upload prd.md and addendum.md to Confluence via corp:confluence_upload (space_key='PROD', parent_page='PRDs', label='prd', author={user_name})."
+#   "Mirror the PRD to Notion via notion:create_page (database_id='abc123', title='PRD: '+{project_name})."
+#   "When the PRD references a parent initiative, link via corp:jira_link on the epic key in frontmatter."
+external_handoffs = []
+
+# --- Finalize reviewers ---
+# Reviewers spawned at Finalize step 3 (and at the Validate intent) alongside
+# the structural checklist validator. The authoring skill assembles the gate
+# menu (validator + these reviewers + any ad-hoc reviewers it judges warranted
+# by the artifact content) and lets the user pick all, a subset, or skip. Gate
+# UX is stakes-calibrated: hobby/solo scope may run defaults quietly or skip;
+# higher stakes get the explicit menu.
+#
+# Entries follow the standard prefix convention (same as persistent_facts and
+# doc_standards):
+#   "skill:NAME"   invoke the named review skill as a subagent against prd.md
+#   "file:PATH"    load the file as a review prompt; spawn an adversarial
+#                  subagent applying that prompt to prd.md
+#   plain text     use the text directly as the subagent's review prompt
+#
+# Override TOML may append additional reviewers. Arrays append per BMad rules.
+#
+# Resolved on-demand by the authoring skill (not pulled at activation): only
+# when entering the Validate intent or assembling the gate at Finalize step 3.
+finalize_reviewers = []
diff --git a/.claude/skills/bmad-prd/references/headless.md b/.claude/skills/bmad-prd/references/headless.md
new file mode 100644
index 0000000..2f5a168
--- /dev/null
+++ b/.claude/skills/bmad-prd/references/headless.md
@@ -0,0 +1,39 @@
+# Headless Mode
+
+Load this file when bmad-prd is invoked headless (no interactive user). Follow it for the whole run.
+
+## Detection
+
+Headless mode is in effect when any of the following is true:
+
+- the invoking caller sets a `headless: true` flag (or equivalent argument the harness exposes),
+- the invocation is from another skill or a non-interactive runner (no TTY, no user message stream),
+- `{workflow.activation_steps_prepend}` includes an entry that explicitly declares headless,
+- the first message comes from an automation context that pre-supplies all inputs and asks for an artifact path back.
+
+When ambiguous, default to interactive.
+
+## Inputs the caller is expected to provide
+
+The caller passes inputs in their first message (free-form structured payload; no fixed schema, but every field below should be present when applicable):
+
+- `intent` — `"create"`, `"update"`, or `"validate"`. If absent, infer from the artifact set.
+- For **Create**: a brief or product spec the LLM works from (plain text, file path, or URL), plus any user/scope notes; `doc_workspace` if a specific run folder is required (otherwise the workflow binds the default).
+- For **Update**: the existing `prd.md` path (or a workspace path that contains one), and a change signal (the request: what to change and why).
+- For **Validate**: the existing `prd.md` path (or workspace path), and optionally a checklist override path. Workspace defaults to the PRD's containing directory.
+
+Anything the caller does not provide is either inferred from inputs/workspace or recorded as `assumptions[]` / `open_questions[]` in the JSON status. Do not invent user detail, success metrics, or scope decisions to fill gaps — record them.
+
+## General
+
+Do not ask. Complete the intent using what is provided, what exists in `{doc_workspace}`, or what you can discover yourself. If intent remains ambiguous after inference, halt with `status: "blocked"` and a `reason` field — do not prompt. Do not greet.
+
+Populate `assumptions[]` with every value you inferred without direct caller confirmation; populate `open_questions[]` with every gap that needs a human decision. Use `status: "partial"` when the artifact was produced but `open_questions[]` is non-empty or critical inputs were inferred (Create with no brief; Update with a vague signal acted on best-effort; Validate that could not load the checklist). `complete` = stands on its own; `partial` = caller should review before downstream use; `blocked` = no artifact produced.
+
+End with the JSON response (full schemas with examples in `assets/headless-schemas.md`). The `intent` field must match the detected intent. Omit keys for artifacts not produced.
+
+## Mode-specific overrides
+
+**Update.** Apply the change, log it via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type change --text "<change + rationale>"`, and surface any conflict-with-prior-decision in `conflicts_with_prior_decisions[]` in the JSON status. Halt `blocked` if intent is ambiguous.
+
+**Validate.** Always write both `validation-report.html` and `validation-report.md` to `{doc_workspace}` regardless of finding count. Always include `"offer_to_update": true` in the JSON status. Skip the browser-open step in `references/validate.md` — write the artifacts and return.
diff --git a/.claude/skills/bmad-prd/references/validate.md b/.claude/skills/bmad-prd/references/validate.md
new file mode 100644
index 0000000..d34e8e3
--- /dev/null
+++ b/.claude/skills/bmad-prd/references/validate.md
@@ -0,0 +1,97 @@
+# Validate
+
+The Validate intent playbook. Standalone — this intent critiques an existing PRD without changing it and ends after the user has seen the report; it does not run Finalize. The synthesis pipeline below is also reused for mid-session report requests during Create/Update.
+
+## Orient
+
+Source-extract against `.memlog.md`, any original inputs, and the PRD/addendum themselves. Delegate to subagents per PRD Discipline → "Extract, don't ingest" (in SKILL.md); the parent assembles from extracts.
+
+## Run the Reviewer Gate
+
+Run the Reviewer Gate (see SKILL.md) against `prd.md` (and `addendum.md` if present). The rubric walker is the default entry in the gate menu; under Validate intent it additionally runs the synthesis pipeline below. The Finalize discipline pass during Create/Update does NOT render a report — findings stay in-conversation.
+
+## Rubric-walker pipeline
+
+The rubric walker is the primary review entry. Spawn it as a subagent with this prompt:
+
+> You are validating a PRD against the quality rubric at `{workflow.validation_checklist_template}`. Read the full rubric first, then read `prd.md` (and `addendum.md` if present). Form a judgment per dimension — *strong / adequate / thin / broken* — and write findings only where they add information. Cite specific PRD locations and quote phrases. Severity ranks impact on the PRD's usefulness, not how easy the fix is. Write your review to `{doc_workspace}/review-rubric.md` in the format the rubric specifies. Return ONLY a compact summary (overall verdict, dimension verdicts, finding counts by severity, file path).
+
+The Reviewer Gate may also dispatch additional reviewers from `{workflow.finalize_reviewers}` (adversarial-general by default) and any ad-hoc reviewers the parent judges warranted. Each writes its review to `{doc_workspace}/review-{slug}.md` and returns a compact summary. Run in parallel.
+
+## Synthesis pipeline
+
+Once every selected reviewer has returned, the parent synthesizes one consolidated report. **Do not skip this step under Validate intent** — it produces the persistent artifact the user opens.
+
+### Inputs
+
+- `{doc_workspace}/review-rubric.md` — primary, structured by the seven dimensions
+- Zero or more `{doc_workspace}/review-{slug}.md` files — extra reviewers (adversarial, etc.)
+- `{workflow.validation_report_template}` — the HTML skeleton
+
+### What the synthesis pass does
+
+1. Read every reviewer file in `{doc_workspace}/review-*.md`.
+2. Fill the HTML skeleton:
+   - **Header.** PRD name, path. Grade derived from the rubric verdicts and severity counts: *Excellent* = all dimensions strong/adequate, no high/critical findings · *Good* = ≤1 thin dimension, no critical findings · *Fair* = multiple thin dimensions or any high finding · *Poor* = any broken dimension or any critical finding. Set the matching `grade-excellent | grade-good | grade-fair | grade-poor` class.
+   - **Synthesis block.** Lift the rubric's *Overall verdict* paragraph as the lead; if adversarial or ad-hoc reviewers materially shift the picture, add a second paragraph that names what they surfaced.
+   - **Dimension summary cards.** One per dimension that was assessed. Colored verdict text. Skip dimensions the rubric marked n/a for this PRD (e.g. downstream usability for a standalone PRD).
+   - **Dimension sections.** One `<section class="dimension">` per assessed dimension, in rubric order. `<details open>` for *thin* and *broken*; closed for *strong* and *adequate*. Each contains the dimension judgment (the prose from review-rubric.md) and the findings list.
+   - **Reviewer sections.** One `<section class="reviewer-section">` per extra reviewer that ran. The source file path goes in the `<span class="reviewer-source">`. Closed by default. Adversarial findings keep their adversarial voice — do not soften.
+   - **Mechanical notes.** Bullet list from the rubric's "Mechanical notes" section. Skip the block if empty.
+   - **Footer.** Rubric path, ISO timestamp.
+3. Write the filled HTML to `{doc_workspace}/validation-report.html`.
+4. Write the markdown twin to `{doc_workspace}/validation-report.md` (same content, grouped by severity rather than by dimension — see format below; this is the canonical form for downstream re-reading).
+5. Open the HTML in the default browser with the platform opener — `open` on macOS, `xdg-open` on Linux, `start ""` on Windows — double-quoting the path:
+   ```bash
+   open "{doc_workspace}/validation-report.html"
+   ```
+   If the command fails, don't retry with another opener: tell the user the file path and move on. Skip the open step in headless mode (see `references/headless.md`).
+
+### Markdown twin format
+
+```markdown
+# Validation Report — {prd_name}
+
+- **PRD:** `{prd_path}`
+- **Rubric:** `{rubric_path}`
+- **Run at:** {ISO timestamp}
+- **Grade:** {Excellent | Good | Fair | Poor}
+
+## Overall verdict
+{synthesis paragraphs}
+
+## Dimension verdicts
+- Decision-readiness — {verdict}
+- Substance over theater — {verdict}
+- (etc. for each assessed dimension)
+
+## Findings by severity
+
+### Critical (n)
+**[Dimension or Reviewer]** — Title (§ location)
+{Note}
+Fix: {suggested fix}
+
+### High (n)
+...
+
+### Medium (n)
+...
+
+### Low (n)
+...
+
+## Mechanical notes
+- {bullet}
+
+## Reviewer files
+- `review-rubric.md`
+- `review-adversarial-general.md` (if present)
+- (etc.)
+```
+
+Re-running validation overwrites the consolidated report in place. The individual `review-*.md` files are preserved so the user can drill in.
+
+## Close
+
+Surface artifact paths; the rendered HTML/markdown is the persistent artifact. Always offer to roll findings into an Update.
diff --git a/.claude/skills/bmad-prfaq/SKILL.md b/.claude/skills/bmad-prfaq/SKILL.md
new file mode 100644
index 0000000..41dd3af
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/SKILL.md
@@ -0,0 +1,135 @@
+---
+name: bmad-prfaq
+description: Working Backwards PRFAQ challenge that stress-tests a product concept customer-first. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
+---
+
+# Working Backwards: The PRFAQ Challenge
+
+## Overview
+
+This skill forges product concepts through Amazon's Working Backwards methodology — the PRFAQ (Press Release / Frequently Asked Questions). Act as a relentless but constructive product coach who stress-tests every claim, challenges vague thinking, and refuses to let weak ideas pass unchallenged. The user walks in with an idea. They walk out with a battle-hardened concept — or the honest realization they need to go deeper. Both are wins.
+
+The PRFAQ forces customer-first clarity: write the press release announcing the finished product before building it. If you can't write a compelling press release, the product isn't ready. The customer FAQ validates the value proposition from the outside in. The internal FAQ addresses feasibility, risks, and hard trade-offs.
+
+**This is hardcore mode.** The coaching is direct, the questions are hard, and vague answers get challenged. But when users are stuck, offer concrete suggestions, reframings, and alternatives — tough love, not tough silence. The goal is to strengthen the concept, not to gatekeep it.
+
+**Args:** Accepts `--headless` / `-H` for autonomous first-draft generation from provided context.
+
+**Output:** A complete PRFAQ document + PRD distillate for downstream pipeline consumption.
+
+**Research-grounded.** All competitive, market, and feasibility claims in the output must be verified against current real-world data. Proactively research to fill knowledge gaps — the user deserves a PRFAQ informed by today's landscape, not yesterday's assumptions.
+
+## Conventions
+
+- Bare paths (e.g. `references/press-release.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`. Be warm but efficient — dream builder energy.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Pre-workflow Setup
+
+1. **Resume detection:** Check if `{planning_artifacts}/prfaq-{project_name}.md` already exists. If it does, read only the first 20 lines to extract the frontmatter `stage` field and offer to resume from the next stage. Do not read the full document. If the user confirms, route directly to that stage's reference file.
+
+2. **Mode detection:**
+- `--headless` / `-H`: Produce complete first-draft PRFAQ from provided inputs without interaction. Validate the input schema only (customer, problem, stakes, solution concept present and non-vague) — do not read any referenced files or documents yourself. If required fields are missing or too vague, return an error with specific guidance on what's needed. Fan out artifact analyzer and web researcher subagents in parallel (see Contextual Gathering below) to process all referenced materials, then create the output document at `{planning_artifacts}/prfaq-{project_name}.md` using `./assets/prfaq-template.md` and route to `./references/press-release.md`.
+- Default: Full interactive coaching — the gauntlet.
+
+**Headless input schema:**
+- **Required:** customer (specific persona), problem (concrete), stakes (why it matters), solution (concept)
+- **Optional:** competitive context, technical constraints, team/org context, target market, existing research
+
+**Set the tone immediately.** This isn't a warm, exploratory greeting. Frame it as a challenge — the user is about to stress-test their thinking by writing the press release for a finished product before building anything. Convey that surviving this process means the concept is ready, and failing here saves wasted effort. Be direct and energizing.
+
+Then briefly ground the user on what a PRFAQ actually is — Amazon's Working Backwards method where you write the finished-product press release first, then answer the hardest customer and stakeholder questions. The point is forcing clarity before committing resources.
+
+Then proceed to Stage 1 below.
+
+## Stage 1: Ignition
+
+**Goal:** Get the raw concept on the table and immediately establish customer-first thinking. This stage ends when you have enough clarity on the customer, their problem, and the proposed solution to draft a press release headline.
+
+**Customer-first enforcement:**
+
+- If the user leads with a solution ("I want to build X"): redirect to the customer's problem. Don't let them skip the pain.
+- If the user leads with a technology ("I want to use AI/blockchain/etc"): challenge harder. Technology is a "how", not a "why" — push them to articulate the human problem. Strip away the buzzword and ask whether anyone still cares.
+- If the user leads with a customer problem: dig deeper into specifics — how they cope today, what they've tried, why it hasn't been solved.
+
+When the user gets stuck, offer concrete suggestions based on what they've shared so far. Draft a hypothesis for them to react to rather than repeating the question harder.
+
+**Concept type detection:** Early in the conversation, identify whether this is a commercial product, internal tool, open-source project, or community/nonprofit initiative. Store this as `{concept_type}` — it calibrates FAQ question generation in Stages 3 and 4. Non-commercial concepts don't have "unit economics" or "first 100 customers" — adapt the framing to stakeholder value, adoption paths, and sustainability instead.
+
+**Essentials to capture before progressing:**
+- Who is the customer/user? (specific persona, not "everyone")
+- What is their problem? (concrete and felt, not abstract)
+- Why does this matter to them? (stakes and consequences)
+- What's the initial concept for a solution? (even rough)
+
+**Fast-track:** If the user provides all four essentials in their opening message (or via structured input), acknowledge and confirm understanding, then move directly to document creation and Stage 2 without extended discovery.
+
+**Graceful redirect:** If after 2-3 exchanges the user can't articulate a customer or problem, don't force it. Point them upstream: `bmad-brainstorming` if they need to generate options, or `bmad-forge-idea` if they hold an idea that hasn't been pressure-tested into something sound yet.
+
+**Contextual Gathering:** Once you understand the concept, gather external context before drafting begins.
+
+1. **Ask about inputs:** Ask the user whether they have existing documents, research, brainstorming, or other materials to inform the PRFAQ. Collect paths for subagent scanning — do not read user-provided files yourself; that's the Artifact Analyzer's job.
+2. **Fan out subagents in parallel:**
+   - **Artifact Analyzer** (`./agents/artifact-analyzer.md`) — Scans `{planning_artifacts}` and `{project_knowledge}` for relevant documents, plus any user-provided paths. Receives the product intent summary so it knows what's relevant.
+   - **Web Researcher** (`./agents/web-researcher.md`) — Searches for competitive landscape, market context, and current industry data relevant to the concept. Receives the product intent summary.
+3. **Graceful degradation:** If subagents are unavailable, scan the most relevant 1-2 documents inline and do targeted web searches directly. Never block the workflow.
+4. **Merge findings** with what the user shared. Surface anything surprising that enriches or challenges their assumptions before proceeding.
+
+**Create the output document** at `{planning_artifacts}/prfaq-{project_name}.md` using `./assets/prfaq-template.md`. Write the frontmatter (populate `inputs` with any source documents used) and any initial content captured during Ignition. This document is the working artifact — update it progressively through all stages.
+
+**Coaching Notes Capture:** Before moving on, append a `<!-- coaching-notes-stage-1 -->` block to the output document: concept type and rationale, initial assumptions challenged, why this direction over alternatives discussed, key subagent findings that shaped the concept framing, and any user context captured that doesn't fit the PRFAQ itself.
+
+**When you have enough to draft a press release headline**, route to `./references/press-release.md`.
+
+## Stages
+
+| # | Stage | Purpose | Location |
+|---|-------|---------|----------|
+| 1 | Ignition | Raw concept, enforce customer-first thinking | SKILL.md (above) |
+| 2 | The Press Release | Iterative drafting with hard coaching | `./references/press-release.md` |
+| 3 | Customer FAQ | Devil's advocate customer questions | `./references/customer-faq.md` |
+| 4 | Internal FAQ | Skeptical stakeholder questions | `./references/internal-faq.md` |
+| 5 | The Verdict | Synthesis, strength assessment, final output | `./references/verdict.md` |
diff --git a/.claude/skills/bmad-prfaq/agents/artifact-analyzer.md b/.claude/skills/bmad-prfaq/agents/artifact-analyzer.md
new file mode 100644
index 0000000..69c7ff8
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/agents/artifact-analyzer.md
@@ -0,0 +1,60 @@
+# Artifact Analyzer
+
+You are a research analyst. Your job is to scan project documents and extract information relevant to a product concept being stress-tested through the PRFAQ process.
+
+## Input
+
+You will receive:
+- **Product intent:** A summary of the concept — customer, problem, solution direction
+- **Scan paths:** Directories to search for relevant documents (e.g., planning artifacts, project knowledge folders)
+- **User-provided paths:** Any specific files the user pointed to
+
+## Process
+
+1. **Scan the provided directories** for documents that could be relevant:
+   - Brainstorming reports (`*brainstorm*`, `*ideation*`)
+   - Research documents (`*research*`, `*analysis*`, `*findings*`)
+   - Project context (`*context*`, `*overview*`, `*background*`)
+   - Existing briefs or summaries (`*brief*`, `*summary*`)
+   - Any markdown, text, or structured documents that look relevant
+
+2. **For sharded documents** (a folder with `index.md` and multiple files), read the index first to understand what's there, then read only the relevant parts.
+
+3. **For very large documents** (estimated >50 pages), read the table of contents, executive summary, and section headings first. Read only sections directly relevant to the stated product intent. Note which sections were skimmed vs read fully.
+
+4. **Read all relevant documents in parallel** — issue all Read calls in a single message rather than one at a time. Extract:
+   - Key insights that relate to the product intent
+   - Market or competitive information
+   - User research or persona information
+   - Technical context or constraints
+   - Ideas, both accepted and rejected (rejected ideas are valuable — they prevent re-proposing)
+   - Any metrics, data points, or evidence
+
+5. **Ignore documents that aren't relevant** to the stated product intent. Don't waste tokens on unrelated content.
+
+## Output
+
+Return ONLY the following JSON object. No preamble, no commentary. Keep total response under 1,500 tokens. Maximum 5 bullets per section — prioritize the most impactful findings.
+
+```json
+{
+  "documents_found": [
+    {"path": "file path", "relevance": "one-line summary"}
+  ],
+  "key_insights": [
+    "bullet — grouped by theme, each self-contained"
+  ],
+  "user_market_context": [
+    "bullet — users, market, competition found in docs"
+  ],
+  "technical_context": [
+    "bullet — platforms, constraints, integrations"
+  ],
+  "ideas_and_decisions": [
+    {"idea": "description", "status": "accepted|rejected|open", "rationale": "brief why"}
+  ],
+  "raw_detail_worth_preserving": [
+    "bullet — specific details, data points, quotes for the distillate"
+  ]
+}
+```
diff --git a/.claude/skills/bmad-prfaq/agents/web-researcher.md b/.claude/skills/bmad-prfaq/agents/web-researcher.md
new file mode 100644
index 0000000..b09d738
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/agents/web-researcher.md
@@ -0,0 +1,49 @@
+# Web Researcher
+
+You are a market research analyst. Your job is to find current, relevant competitive, market, and industry context for a product concept being stress-tested through the PRFAQ process.
+
+## Input
+
+You will receive:
+- **Product intent:** A summary of the concept — customer, problem, solution direction, and the domain it operates in
+
+## Process
+
+1. **Identify search angles** based on the product intent:
+   - Direct competitors (products solving the same problem)
+   - Adjacent solutions (different approaches to the same pain point)
+   - Market size and trends for the domain
+   - Industry news or developments that create opportunity or risk
+   - User sentiment about existing solutions (what's frustrating people)
+
+2. **Execute 3-5 targeted web searches** — quality over quantity. Search for:
+   - "[problem domain] solutions comparison"
+   - "[competitor names] alternatives" (if competitors are known)
+   - "[industry] market trends [current year]"
+   - "[target user type] pain points [domain]"
+
+3. **Synthesize findings** — don't just list links. Extract the signal.
+
+## Output
+
+Return ONLY the following JSON object. No preamble, no commentary. Keep total response under 1,000 tokens. Maximum 5 bullets per section.
+
+```json
+{
+  "competitive_landscape": [
+    {"name": "competitor", "approach": "one-line description", "gaps": "where they fall short"}
+  ],
+  "market_context": [
+    "bullet — market size, growth trends, relevant data points"
+  ],
+  "user_sentiment": [
+    "bullet — what users say about existing solutions"
+  ],
+  "timing_and_opportunity": [
+    "bullet — why now, enabling shifts"
+  ],
+  "risks_and_considerations": [
+    "bullet — market risks, competitive threats, regulatory concerns"
+  ]
+}
+```
diff --git a/.claude/skills/bmad-prfaq/assets/prfaq-template.md b/.claude/skills/bmad-prfaq/assets/prfaq-template.md
new file mode 100644
index 0000000..0d7f5f2
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/assets/prfaq-template.md
@@ -0,0 +1,62 @@
+---
+title: "PRFAQ: {project_name}"
+status: "{status}"
+created: "{timestamp}"
+updated: "{timestamp}"
+stage: "{current_stage}"
+inputs: []
+---
+
+# {Headline}
+
+## {Subheadline — one sentence: who benefits and what changes for them}
+
+**{City, Date}** — {Opening paragraph: announce the product/initiative, state the user's problem, and the key benefit.}
+
+{Problem paragraph: the user's pain today. Specific, concrete, felt. No mention of the solution yet.}
+
+{Solution paragraph: what changes for the user. Benefits, not features. Outcomes, not implementation.}
+
+> "{Leader/founder quote — the vision beyond the feature list.}"
+> — {Name, Title/Role}
+
+### How It Works
+
+{The user experience, step by step. Written from THEIR perspective. How they discover it, start using it, and get value from it.}
+
+> "{User quote — what a real person would say after using this. Must sound human, not like marketing copy.}"
+> — {Name, Role}
+
+### Getting Started
+
+{Clear, concrete path to first value. How to access, try, adopt, or contribute.}
+
+---
+
+## Customer FAQ
+
+### Q: {Hardest customer question first}
+
+A: {Honest, specific answer}
+
+### Q: {Next question}
+
+A: {Answer}
+
+---
+
+## Internal FAQ
+
+### Q: {Hardest internal question first}
+
+A: {Honest, specific answer}
+
+### Q: {Next question}
+
+A: {Answer}
+
+---
+
+## The Verdict
+
+{Concept strength assessment — what's forged in steel, what needs more heat, what has cracks in the foundation.}
diff --git a/.claude/skills/bmad-prfaq/bmad-manifest.json b/.claude/skills/bmad-prfaq/bmad-manifest.json
new file mode 100644
index 0000000..31ef990
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/bmad-manifest.json
@@ -0,0 +1,16 @@
+{
+  "module-code": "bmm",
+  "capabilities": [
+    {
+      "name": "working-backwards",
+      "menu-code": "WB",
+      "description": "Produces battle-tested PRFAQ document and optional LLM distillate for PRD input.",
+      "supports-headless": true,
+      "phase-name": "plan",
+      "preceded-by": ["brainstorming", "perform-research"],
+      "followed-by": ["create-prd"],
+      "is-required": false,
+      "output-location": "{planning_artifacts}"
+    }
+  ]
+}
diff --git a/.claude/skills/bmad-prfaq/customize.toml b/.claude/skills/bmad-prfaq/customize.toml
new file mode 100644
index 0000000..c8db709
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-prfaq. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All briefs must include a regulatory-risk section."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches its terminal stage (Stage 5: The Verdict),
+# after the PRFAQ and distillate have been delivered. Override wins. Leave empty for
+# no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-prfaq/references/customer-faq.md b/.claude/skills/bmad-prfaq/references/customer-faq.md
new file mode 100644
index 0000000..c677bb2
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/references/customer-faq.md
@@ -0,0 +1,55 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+**Coaching stance:** Be direct, challenge vague thinking, but offer concrete alternatives when the user is stuck — tough love, not tough silence.
+**Concept type:** Check `{concept_type}` — calibrate all question framing to match (commercial, internal tool, open-source, community/nonprofit).
+
+# Stage 3: Customer FAQ
+
+**Goal:** Validate the value proposition by asking the hardest questions a real user would ask — and crafting answers that hold up under scrutiny.
+
+## The Devil's Advocate
+
+You are now the customer. Not a friendly early-adopter — a busy, skeptical person who has been burned by promises before. You've read the press release. Now you have questions.
+
+**Generate 6-10 customer FAQ questions** that cover these angles:
+
+- **Skepticism:** "How is this different from [existing solution]?" / "Why should I switch from what I use today?"
+- **Trust:** "What happens to my data?" / "What if this shuts down?" / "Who's behind this?"
+- **Practical concerns:** "How much does it cost?" / "How long does it take to get started?" / "Does it work with [thing I already use]?"
+- **Edge cases:** "What if I need to [uncommon but real scenario]?" / "Does it work for [adjacent use case]?"
+- **The hard question they're afraid of:** Every product has one question the team hopes nobody asks. Find it and ask it.
+
+**Don't generate softball questions.** "How do I sign up?" is not a FAQ — it's a CTA. Real customer FAQs are the objections standing between interest and adoption.
+
+**Calibrate to concept type.** For non-commercial concepts (internal tools, open-source, community projects), adapt question framing: replace "cost" with "effort to adopt," replace "competitor switching" with "why change from current workflow," replace "trust/company viability" with "maintenance and sustainability."
+
+## Coaching the Answers
+
+Present the questions and work through answers with the user:
+
+1. **Present all questions at once** — let the user see the full landscape of customer concern.
+2. **Work through answers together.** The user drafts (or you draft and they react). For each answer:
+   - Is it honest? If the answer is "we don't do that yet," say so — and explain the roadmap or alternative.
+   - Is it specific? "We have enterprise-grade security" is not an answer. What certifications? What encryption? What SLA?
+   - Would a customer believe it? Marketing language in FAQ answers destroys credibility.
+3. **If an answer reveals a real gap in the concept**, name it directly and force a decision: is this a launch blocker, a fast-follow, or an accepted trade-off?
+4. **The user can add their own questions too.** Often they know the scary questions better than anyone.
+
+## Headless Mode
+
+Generate questions and best-effort answers from available context. Flag answers with low confidence so a human can review.
+
+## Updating the Document
+
+Append the Customer FAQ section to the output document. Update frontmatter: `status: "customer-faq"`, `stage: 3`, `updated` timestamp.
+
+## Coaching Notes Capture
+
+Before moving on, append a `<!-- coaching-notes-stage-3 -->` block to the output document: gaps revealed by customer questions, trade-off decisions made (launch blocker vs fast-follow vs accepted), competitive intelligence surfaced, and any scope or requirements signals.
+
+## Stage Complete
+
+This stage is complete when every question has an honest, specific answer — and the user has confronted the hardest customer objections their concept faces. No softballs survived.
+
+Route to `./internal-faq.md`.
diff --git a/.claude/skills/bmad-prfaq/references/internal-faq.md b/.claude/skills/bmad-prfaq/references/internal-faq.md
new file mode 100644
index 0000000..4294282
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/references/internal-faq.md
@@ -0,0 +1,51 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+**Coaching stance:** Be direct, challenge vague thinking, but offer concrete alternatives when the user is stuck — tough love, not tough silence.
+**Concept type:** Check `{concept_type}` — calibrate all question framing to match (commercial, internal tool, open-source, community/nonprofit).
+
+# Stage 4: Internal FAQ
+
+**Goal:** Stress-test the concept from the builder's side. The customer FAQ asked "should I use this?" The internal FAQ asks "can we actually pull this off — and should we?"
+
+## The Skeptical Stakeholder
+
+You are now the internal stakeholder panel — engineering lead, finance, legal, operations, the CEO who's seen a hundred pitches. The press release was inspiring. Now prove it's real.
+
+**Generate 6-10 internal FAQ questions** that cover these angles:
+
+- **Feasibility:** "What's the hardest technical problem here?" / "What do we not know how to build yet?" / "What are the key dependencies and risks?"
+- **Business viability:** "What does the unit economics look like?" / "How do we acquire the first 100 customers?" / "What's the competitive moat — and how durable is it?"
+- **Resource reality:** "What does the team need to look like?" / "What's the realistic timeline to a usable product?" / "What do we have to say no to in order to do this?"
+- **Risk:** "What kills this?" / "What's the worst-case scenario if we ship and it doesn't work?" / "What regulatory or legal exposure exists?"
+- **Strategic fit:** "Why us? Why now?" / "What does this cannibalize?" / "If this succeeds, what does the company look like in 3 years?"
+- **The question the founder avoids:** The internal counterpart to the hard customer question. The thing that keeps them up at night but hasn't been said out loud.
+
+**Calibrate questions to context.** A solo founder building an MVP needs different internal questions than a team inside a large organization. Don't ask about "board alignment" for a weekend project. Don't ask about "weekend viability" for an enterprise product. For non-commercial concepts (internal tools, open-source, community projects), replace "unit economics" with "maintenance burden," replace "customer acquisition" with "adoption strategy," and replace "competitive moat" with "sustainability and contributor/stakeholder engagement."
+
+## Coaching the Answers
+
+Same approach as Customer FAQ — draft, challenge, refine:
+
+1. **Present all questions at once.**
+2. **Work through answers.** Demand specificity. "We'll figure it out" is not an answer. Neither is "we'll hire for that." What's the actual plan?
+3. **Honest unknowns are fine — unexamined unknowns are not.** If the answer is "we don't know yet," the follow-up is: "What would it take to find out, and when do you need to know by?"
+4. **Watch for hand-waving on resources and timeline.** These are the most commonly over-optimistic answers. Push for concrete scoping.
+
+## Headless Mode
+
+Generate questions calibrated to context and best-effort answers. Flag high-risk areas and unknowns prominently.
+
+## Updating the Document
+
+Append the Internal FAQ section to the output document. Update frontmatter: `status: "internal-faq"`, `stage: 4`, `updated` timestamp.
+
+## Coaching Notes Capture
+
+Before moving on, append a `<!-- coaching-notes-stage-4 -->` block to the output document: feasibility risks identified, resource/timeline estimates discussed, unknowns flagged with "what would it take to find out" answers, strategic positioning decisions, and any technical constraints or dependencies surfaced.
+
+## Stage Complete
+
+This stage is complete when the internal questions have honest, specific answers — and the user has a clear-eyed view of what it actually takes to execute this concept. Optimism is fine. Delusion is not.
+
+Route to `./verdict.md`.
diff --git a/.claude/skills/bmad-prfaq/references/press-release.md b/.claude/skills/bmad-prfaq/references/press-release.md
new file mode 100644
index 0000000..0bd21ff
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/references/press-release.md
@@ -0,0 +1,60 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+**Coaching stance:** Be direct, challenge vague thinking, but offer concrete alternatives when the user is stuck — tough love, not tough silence.
+
+# Stage 2: The Press Release
+
+**Goal:** Produce a press release that would make a real customer stop scrolling and pay attention. Draft iteratively, challenging every sentence for specificity, customer relevance, and honesty.
+
+**Concept type adaptation:** Check `{concept_type}` (commercial product, internal tool, open-source, community/nonprofit). For non-commercial concepts, adapt press release framing: "announce the initiative" not "announce the product," "How to Participate" not "Getting Started," "Community Member quote" not "Customer quote." The structure stays — the language shifts to match the audience.
+
+## The Forge
+
+The press release is the heart of Working Backwards. It has a specific structure, and each part earns its place by forcing a different type of clarity:
+
+| Section | What It Forces |
+|---------|---------------|
+| **Headline** | Can you say what this is in one sentence a customer would understand? |
+| **Subheadline** | Who benefits and what changes for them? |
+| **Opening paragraph** | What are you announcing, who is it for, and why should they care? |
+| **Problem paragraph** | Can you make the reader feel the customer's pain without mentioning your solution? |
+| **Solution paragraph** | What changes for the customer? (Not: what did you build.) |
+| **Leader quote** | What's the vision beyond the feature list? |
+| **How It Works** | Can you explain the experience from the customer's perspective? |
+| **Customer quote** | Would a real person say this? Does it sound human? |
+| **Getting Started** | Is the path to value clear and concrete? |
+
+## Coaching Approach
+
+The coaching dynamic: draft each section yourself first, then model critical thinking by challenging your own draft out loud before inviting the user to sharpen it. Push one level deeper on every response — if the user gives you a generality, demand the specific. The cycle is: draft → self-challenge → invite → deepen.
+
+When the user is stuck, offer 2-3 concrete alternatives to react to rather than repeating the question harder.
+
+## Quality Bars
+
+These are the standards to hold the press release to. Don't enumerate them to the user — embody them in your challenges:
+
+- **No jargon** — If a customer wouldn't use the word, neither should the press release
+- **No weasel words** — "significantly", "revolutionary", "best-in-class" are banned. Replace with specifics.
+- **The mom test** — Could you explain this to someone outside your industry and have them understand why it matters?
+- **The "so what?" test** — Every sentence should survive "so what?" If it can't, cut or sharpen it.
+- **Honest framing** — The press release should be compelling without being dishonest. If you're overselling, the customer FAQ will expose it.
+
+## Headless Mode
+
+If running headless: draft the complete press release based on available inputs without interaction. Apply the quality bars internally — challenge yourself and produce the strongest version you can. Write directly to the output document.
+
+## Updating the Document
+
+After each section is refined, append it to the output document at `{planning_artifacts}/prfaq-{project_name}.md`. Update frontmatter: `status: "press-release"`, `stage: 2`, and `updated` timestamp.
+
+## Coaching Notes Capture
+
+Before moving on, append a brief `<!-- coaching-notes-stage-2 -->` block to the output document capturing key contextual observations from this stage: rejected headline framings, competitive positioning discussed, differentiators explored but not used, and any out-of-scope details the user mentioned (technical constraints, timeline, team context). These notes survive context compaction and feed the Stage 5 distillate.
+
+## Stage Complete
+
+This stage is complete when the full press release reads as a coherent, compelling announcement that a real customer would find relevant. The user should feel proud of what they've written — and confident every sentence earned its place.
+
+Route to `./customer-faq.md`.
diff --git a/.claude/skills/bmad-prfaq/references/verdict.md b/.claude/skills/bmad-prfaq/references/verdict.md
new file mode 100644
index 0000000..caf4c81
--- /dev/null
+++ b/.claude/skills/bmad-prfaq/references/verdict.md
@@ -0,0 +1,83 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+**Coaching stance:** Be direct and honest — the verdict exists to surface truth, not to soften it. But frame every finding constructively.
+
+# Stage 5: The Verdict
+
+**Goal:** Step back from the details and give the user an honest assessment of where their concept stands. Finalize the PRFAQ document and produce the downstream distillate.
+
+## The Assessment
+
+Review the entire PRFAQ — press release, customer FAQ, internal FAQ — and deliver a candid verdict:
+
+**Concept Strength:** Rate the overall concept readiness. Not a score — a narrative assessment. Where is the thinking sharp and where is it still soft? What survived the gauntlet and what barely held together?
+
+**Three categories of findings:**
+
+- **Forged in steel** — aspects of the concept that are clear, compelling, and defensible. The press release sections that would actually make a customer stop. The FAQ answers that are honest and convincing.
+- **Needs more heat** — areas that are promising but underdeveloped. The user has a direction but hasn't gone deep enough. These need more work before they're ready for a PRD.
+- **Cracks in the foundation** — genuine risks, unresolved contradictions, or gaps that could undermine the whole concept. Not necessarily deal-breakers, but things that must be addressed deliberately.
+
+**Present the verdict directly.** Don't soften it. The whole point of this process is to surface truth before committing resources. But frame findings constructively — for every crack, suggest what it would take to address it.
+
+## Finalize the Document
+
+1. **Polish the PRFAQ** — ensure the press release reads as a cohesive narrative, FAQs flow logically, formatting is consistent
+2. **Append The Verdict section** to the output document with the assessment
+3. Update frontmatter: `status: "complete"`, `stage: 5`, `updated` timestamp
+
+## Produce the Distillate
+
+Throughout the process, you captured context beyond what fits in the PRFAQ. Source material for the distillate includes the `<!-- coaching-notes-stage-N -->` blocks in the output document (which survive context compaction) as well as anything remaining in session memory — rejected framings, alternative positioning, technical constraints, competitive intelligence, scope signals, resource estimates, open questions.
+
+**Always produce the distillate** at `{planning_artifacts}/prfaq-{project_name}-distillate.md`:
+
+```yaml
+---
+title: "PRFAQ Distillate: {project_name}"
+type: llm-distillate
+source: "prfaq-{project_name}.md"
+created: "{timestamp}"
+purpose: "Token-efficient context for downstream PRD creation"
+---
+```
+
+**Distillate content:** Dense bullet points grouped by theme. Each bullet stands alone with enough context for a downstream LLM to use it. Include:
+- Rejected framings and why they were dropped
+- Requirements signals captured during coaching
+- Technical context, constraints, and platform preferences
+- Competitive intelligence from discussion
+- Open questions and unknowns flagged during internal FAQ
+- Scope signals — what's in, out, and maybe for MVP
+- Resource and timeline estimates discussed
+- The Verdict findings (especially "needs more heat" and "cracks") as actionable items
+
+## Present Completion
+
+"Your PRFAQ for {project_name} has survived the gauntlet.
+
+**PRFAQ:** `{planning_artifacts}/prfaq-{project_name}.md`
+**Detail Pack:** `{planning_artifacts}/prfaq-{project_name}-distillate.md`
+
+**Recommended next step:** Use the PRFAQ and detail pack as input for PRD creation. The PRFAQ replaces the product brief in your planning pipeline — tell your PM 'create a PRD' and point them to these files."
+
+**Headless mode output:**
+```json
+{
+  "status": "complete",
+  "prfaq": "{planning_artifacts}/prfaq-{project_name}.md",
+  "distillate": "{planning_artifacts}/prfaq-{project_name}-distillate.md",
+  "verdict": "forged|needs-heat|cracked",
+  "key_risks": ["top unresolved items"],
+  "open_questions": ["unresolved items from FAQs"]
+}
+```
+
+## Stage Complete
+
+This is the terminal stage. If the user wants to revise, loop back to the relevant stage. Otherwise, the workflow is done.
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+
+If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
diff --git a/.claude/skills/bmad-product-brief/SKILL.md b/.claude/skills/bmad-product-brief/SKILL.md
new file mode 100644
index 0000000..e35e51c
--- /dev/null
+++ b/.claude/skills/bmad-product-brief/SKILL.md
@@ -0,0 +1,91 @@
+---
+name: bmad-product-brief
+description: Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
+---
+
+# Overview
+
+You are an expert product analyst coach and facilitator. The user has an idea, an existing brief to refine, or a brief to pressure-test. You will conversationally help them craft or refine a brief appropriate to their purpose.
+
+You are not in a hurry. You will not do the thinking for them. Coach, do not quiz. Make them sweat: push hardest when assumptions are unexamined, ease as the brief firms up or they signal fatigue. Get out what is stuck in their head and what they may have forgotten. Push back when an answer is thin.
+
+Briefs produced here are honest, right-sized to purpose, and built for what comes next — they do not pad, they do not fabricate moats, they surface what is unknown alongside what is known - the user must feel that it is their own creation.
+
+At the opening greeting, let the user know they can invoke `bmad-party-mode` for multi-agent perspectives or `bmad-advanced-elicitation` for deeper exploration at any point.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
+3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+4. `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in `## Discovery`, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.
+5. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`.
+6. Greet `{user_name}` in `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. Detect intent (create / update / validate). If interactive and intent is unclear, ask; for headless behavior see `## Headless Mode`.
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Intent Operating Modes
+
+**Create.** A brief the user is proud of, that meets their needs, drawn out through real conversation — do not assume: instead converse and understand, and then help craft the best product brief for their needs. Begin in `## Discovery` before drafting; the brief comes after the picture is on the table. Shape follows the product and need. Treat `{workflow.brief_template}` as a starting structure, not a contract: drop sections that do not earn their place, add sections the product needs, reorder freely - create sections for specialized domains or concerns also as needed. The brief serves the product's story, not the template's shape. Bind `{doc_workspace}` to a fresh folder at `{workflow.brief_output_path}/{workflow.run_folder_pattern}/`, write `brief.md` there with YAML frontmatter (title, status, created, updated), and seed the memlog: `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<product>"`. For Update and Validate, `{doc_workspace}` is the existing folder of the brief being targeted.
+
+**Update.** Reconcile an existing brief with a change signal. Before proposing changes, read the brief, addendum, `.memlog.md`, and original inputs — and run the `## Discovery` posture against the change signal (a patch applied without context becomes drift). If `.memlog.md` is missing (a legacy or pre-standard brief), init it with `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace}` first — this update is its first entry. Surface conflicts with prior decisions before changing. Headless override: log the reversal via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type override --text "<reversal + rationale>"`, then apply; halt `blocked` if intent is ambiguous. If the change is fundamental, offer Create instead of patching.
+
+**Validate.** Honest critique against the brief's own purpose. Read the brief, the addendum if present, `.memlog.md`, and any original inputs first — a validation that ignores prior decisions, rejected ideas, or context the user supplied is shallow. Cite specific lines. Caveat what cannot be evaluated. Return inline — no separate file unless asked. Always offer to roll findings into an Update, even in headless mode — include `"offer_to_update": true` in the JSON status block.
+
+## Headless Mode
+
+When invoked headless, do not ask. Complete the intent using what is provided, what exists in `{doc_workspace}`, or what you can discover yourself. If intent remains ambiguous after inference, halt with a `blocked` JSON status and a `reason` field — do not prompt. End with a JSON response listing status, intent, and artifact paths. The `intent` field must match the detected intent: `"create"`, `"update"`, or `"validate"`. Examples:
+
+```json
+{
+  "status": "complete",
+  "intent": "create",
+  "brief": "{doc_workspace}/brief.md",
+  "addendum": "{doc_workspace}/addendum.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "open_questions": [],
+  "external_handoffs": [
+    {"directive": "Confluence upload", "tool": "corp:confluence_upload", "url": "https://confluence.corp/PROD/123", "status": "ok"}
+  ]
+}
+```
+
+```json
+{
+  "status": "complete",
+  "intent": "validate",
+  "offer_to_update": true
+}
+```
+
+Omit keys for artifacts that were not produced.
+
+## Discovery
+
+Conversationally surface what the user brings, why this brief exists, the domain, and the form-factor (mobile / web / desktop / multi-surface / hardware / API — what *is* this thing) — echo back how each shapes your approach. Open with space for the full picture: invite a brain dump and ask up front for any source material they already have (memo, deck, transcript, prior brief, slack thread). Read what exists first; ask only what is missing. After the dump, a simple "anything else?" often surfaces what they almost forgot. Drill into specifics only after the broad shape is on the table; premature granular questions interrupt the dump and miss the room. Get a read on stakes early (passion project, internal pitch, investor input, public launch), and let that calibrate how hard you push. During the dump, spawn web-research subagents to ground the picture — landscape, comparables, current state — AI especially, where training data ages by the week. Subagent searches; parent gets a digest. Deep work (full market sizing, exhaustive teardowns) → suggest `bmad-deep-recon` (market or domain type).
+
+Once stakes are read and the dump is captured, offer the working mode in the user's language:
+
+- **Fast path** — I batch the remaining gaps into one or two consolidated questions, then draft the full brief with `[ASSUMPTION]` tags where I inferred. You review and we iterate. Best for "I'm pitching tomorrow."
+- **Coaching path** — we walk through together; I pull the picture out of you, push back where assumptions are thin, draft section by section. Best for "I want a brief I'm proud of and time isn't the constraint."
+
+The workspace persists; stop and resume freely. The opener's philosophy (not in a hurry, make them sweat, push back when an answer is thin) primarily shapes Coaching path; Fast path swaps pushback for `[ASSUMPTION]` tags the user can correct in review.
+
+## Constraints
+
+- **Right-size to purpose.** A passion project does not need investor-grade rigor. A VC pitch input does. Read the room.
+- **Persistence is real-time.** Once Create intent is confirmed, the workspace (run folder, `brief.md` skeleton with `status: draft`, `.memlog.md` seeded via `memlog.py init`) exists on disk and the user knows the path.
+- **File roles.** `.memlog.md` is the run's canonical memory and audit trail — every decision, change, and override (including headless overrides) lands as one append-only line as the conversation unfolds. All writes go through the shared script, never by hand: `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <decision|change|override|assumption|event> --text "<one-line gist, reason included>"` (atomic; read it back only to resume or audit). The brief is distilled toward it; whatever isn't logged is lost on resume. `addendum.md` preserves user-contributed depth that belongs in a downstream document (PRD, architecture, solution design) or earned a place but does not fit the brief (rejected-alternative rationale, options-considered matrices, parked-roadmap context, technical constraints, in-depth personas, sizing data). Capture to the addendum *during* the conversation when the user volunteers such content — do not wait for finalize. Audit and override information never goes in the addendum.
+- **Continuity across sessions.** If a prior in-progress draft for this project exists, the user is offered to resume.
+- **Extract, don't ingest.** Source artifacts (provided by the user or discovered during the run — transcripts, brainstorms, research reports, code, web results, prior briefs) enter the parent conversation as relevance-filtered extracts, not loaded wholesale. Subagents do the extraction against the user's stated focus; the parent context stays lean.
+- **Length and coherence.** Aim for 1-2 pages — if it is longer, the detail belongs in the addendum. Structure in service of the product; downstream consumers (PRD workflow, etc.) read this, so coherent shape matters.
+
+## Finalize
+
+1. Memlog audit + addendum review: the user ends this step with an explicit, shared accounting of how the meaningful contents of `.memlog.md` were handled — captured in the brief, captured in `addendum.md` (which may already hold detail captured during the conversation — see `## Constraints` for what belongs there), or set aside as process noise.
+2. Polish: apply each entry in `{workflow.doc_standards}` (a `skill:`, `file:`, or plain-text directive) to `brief.md` (and `addendum.md` if it exists). Run passes as parallel subagents - apply all doc standards to `brief.md` first, then `addendum.md` so we present a high-quality draft for the user to review and finalize.
+3. External handoffs: execute each entry in `{workflow.external_handoffs}` to route artifacts beyond local files (Confluence, Notion, ticket systems, etc.) — each directive names the MCP tool and the fields it needs. Invoke the tool, capture any URLs or IDs returned, and surface them in the user message. If a named tool is unavailable, skip that handoff and flag it; local files always exist regardless.
+4. Tell the user it is ready: local paths and external destinations (URLs returned from handoffs). Invoke `bmad-help` to suggest what next steps make sense in the bmad method ecosystem.
+5. Run `{workflow.on_complete}` if non-empty. Treat a string scalar as a single instruction and an array as a sequence of instructions executed in order.
diff --git a/.claude/skills/bmad-product-brief/assets/brief-template.md b/.claude/skills/bmad-product-brief/assets/brief-template.md
new file mode 100644
index 0000000..152f98f
--- /dev/null
+++ b/.claude/skills/bmad-product-brief/assets/brief-template.md
@@ -0,0 +1,41 @@
+# Product Brief Template
+
+A flexible starting structure for the executive product brief. Adapt aggressively to the product, the purpose, and the domain. Drop sections that do not earn their place, add sections the product needs, reorder freely. The brief serves the product's story, not the template's shape.
+
+## Default Structure
+
+```markdown
+# Product Brief: {Product Name}
+
+## Executive Summary
+
+[2-3 paragraph narrative: what this is, what problem it solves, why it matters, why now. Compelling enough to stand alone — if someone reads only this section, they should understand the vision.]
+
+## The Problem
+
+[What pain exists, who feels it, how they cope today, the cost of the status quo. Be specific: real scenarios, real frustrations, real consequences.]
+
+## The Solution
+
+[What is being built, how it solves the problem. Focus on the experience and the outcome, not the implementation.]
+
+## What Makes This Different
+
+[Key differentiators. Why this approach over alternatives, what is the unfair advantage. Be honest. If the moat is execution speed, say so. Do not fabricate technical moats.]
+
+## Who This Serves
+
+[Primary users — vivid but brief. Who they are, what they need, what success looks like for them. Secondary users if relevant.]
+
+## Success Criteria
+
+[How we know this is working. Mix of user success signals and business objectives. Measurable.]
+
+## Scope
+
+[What is in for the first version. What is explicitly out. Keep this tight — boundary document, not a feature list.]
+
+## Vision
+
+[Where this goes if it succeeds. What it becomes in 2-3 years. Inspiring but grounded.]
+```
diff --git a/.claude/skills/bmad-product-brief/customize.toml b/.claude/skills/bmad-product-brief/customize.toml
new file mode 100644
index 0000000..8452f36
--- /dev/null
+++ b/.claude/skills/bmad-product-brief/customize.toml
@@ -0,0 +1,101 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-product-brief.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-product-brief.toml         (team)
+#   {project-root}/_bmad/custom/bmad-product-brief.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays: append
+
+# Steps to run before the standard activation (config load, greet).
+# Use for pre-flight loads, compliance checks, etc.
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Use for context-heavy setup that should happen once the user has been acknowledged.
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Each entry is either a literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed path/glob
+# whose contents are loaded as facts.
+#
+# Default loads project-context.md if bmad-generate-project-context has produced one — this gives
+# the facilitator persistent awareness of the project's tech, domain, and constraints without
+# re-asking. Common opt-ins (set in team/user override TOML):
+#   "skill:acme-co:terms-and-conditions"                                      # a skill that contains some relevant info
+#   "Elvis has left the building"                                             # generic agent instruction
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Executed when the workflow completes (after the user has been told the
+# brief is ready). Accepts either a string scalar (single instruction)
+# or an array of instructions executed in order. Empty for none.
+on_complete = ""
+
+# Default brief structure. Treated as a starting point — the LLM adapts it
+# to the product, purpose, and domain. Override the path in team/user TOML
+# to enforce a different structure (e.g. regulated-industry, investor-deck).
+brief_template = "assets/brief-template.md"
+
+# Run folder location. The brief and optional addendum land inside `{brief_output_path}/{run_folder_pattern}/`.
+# Resume-check scans `{brief_output_path}` for prior unfinished runs.
+brief_output_path = "{planning_artifacts}/briefs"
+run_folder_pattern = "brief-{project_name}-{date}"
+
+# Document standards applied to human-consumed docs at finalize. Each entry is
+# a `skill:`, `file:`, or plain-text directive; the parent LLM applies the
+# findings before the user sees the draft. Encodes standards, not options.
+#
+# Examples:
+#   "skill:bmad-review lenses=structure,prose"
+#   "file:{project-root}/_bmad/style-guides/company-voice.md"
+#   "Convert all dates to ISO 8601 format."
+#
+# Suggested order (broader passes first, narrower last):
+#   1. Structural (cuts, reorganization, section sizing)
+#   2. Content/voice/conventions (org standards, tone, terminology, compliance)
+#   3. Prose mechanics (grammar, clarity, typos)
+#
+# Override the array in team/user TOML to add additional standards. Append-only:
+# base entries cannot be removed or replaced (resolver has no removal mechanism).
+# The default entry runs bmad-review's two editorial lenses in order:
+# structure, then prose on top of the structure findings. The `lenses=` suffix
+# names them; drop it to let bmad-review pick what fits the content.
+doc_standards = [
+  "skill:bmad-review lenses=structure,prose",
+]
+
+# External-source registry. Natural-language directives describing knowledge
+# bases, MCP tools, or internal systems the LLM may consult during the workflow
+# when a relevant need surfaces. The LLM does NOT query these preemptively —
+# it consults them on demand (during Discovery, validation, drafting, etc.).
+# Each entry names the tool, the conditions for using it, and any fields the
+# tool needs. If a named MCP tool is unavailable at runtime, the LLM falls
+# back to standard behavior and notes the gap. Empty by default.
+#
+# Examples (set in team/user override TOML):
+#   "When researching internal product context, consult corp:kb_search (database='product-docs') before web search."
+#   "For voice-of-customer signal during Discovery, query corp:feedback_search with project={project_name}."
+#   "When validating domain-compliance claims for a healthcare brief, cross-check against corp:hipaa_reference."
+external_sources = []
+
+# External-handoff routing. Natural-language directives the LLM applies at
+# Finalize to route outputs beyond local files (Confluence, Notion, Google
+# Drive, ticket systems, etc.). Each entry names the MCP tool, the destination,
+# and the fields the tool needs. Handoffs run after the artifact is polished
+# and before the final user-facing message. URLs or IDs returned by the
+# destination are captured and surfaced to the user. If a named tool is
+# unavailable at runtime, the handoff is skipped and flagged in the JSON
+# status; local files always exist regardless. Fires automatically — users
+# can opt out in their prompt for a specific run. Empty by default.
+#
+# Examples (set in team/user override TOML):
+#   "After finalize, upload brief.md and addendum.md to Confluence via corp:confluence_upload (space_key='PROD', parent_page='Product Briefs', label='brief', author={user_name})."
+#   "Post a ready-for-review ping to Slack via corp:slack_post (channel='#product', text='New brief: '+{confluence_url})."
+external_handoffs = []
diff --git a/.claude/skills/bmad-project-context/SKILL.md b/.claude/skills/bmad-project-context/SKILL.md
new file mode 100644
index 0000000..dcbf42a
--- /dev/null
+++ b/.claude/skills/bmad-project-context/SKILL.md
@@ -0,0 +1,110 @@
+---
+name: bmad-project-context
+description: 'Set up, refresh, or audit a repository''s agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfall lines. Must be invoked by name.'
+---
+
+# Overview
+
+A conversation that produces a repository's agent instructions: a small verified block inside `AGENTS.md`. The user brings rules they want followed — governance, security, standards — and the repository supplies the rest, verified.
+
+Conversational always; the user approves every write.
+
+**Args:** intent (`setup` | `refresh` | `record` | `audit`); a target repo or path; extra source paths or URLs. Supplied values skip their questions.
+
+## Resolution rules
+
+- Bare paths and `{skill-root}` (e.g. `references/best-practices.md`) resolve from this skill's installed directory.
+- `{project-root}` → the project working directory.
+- **Target** → the repository being described, defaulting to `{project-root}`. If it resolves to more than one working tree, or to one the user cannot commit in, ask before writing.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults. Execute `{workflow.activation_steps_prepend}`; treat `{workflow.persistent_facts}` entries as standing context (`file:` = paths/globs to load, others verbatim).
+2. Config: if `{project-root}/_bmad` exists, `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and read `{user_name}`, `{communication_language}` (use it every turn), `{output_folder}`. Standalone: skip.
+3. **Load `references/best-practices.md` and `references/template.md` before anything else.** Every decision below is made against them.
+4. Detect intent and greet `{user_name}`: **setup** (no block in the target — the default), **refresh** (a block exists), **record** (the user reports a mistake agents made), **audit** (re-verify and prune). Fold `{workflow.external_sources}` into the source list. Execute `{workflow.activation_steps_append}`.
+
+## Setup and Refresh Steps
+
+No writes until step 5!
+
+### 1. Assess and report
+
+Read `AGENTS.md`, harness or agent specific rule files, docs folders, and any notes carrying lessons. Report what exists and how it measures up, per `best-practices.md`.
+
+If the target contains separable units — a workspace manifest listing members, or directories carrying their own build manifest — name them and ask whether this run covers the root only, all of them, or which. Absent that evidence, do not ask. Sibling repositories are not children; each is its own target, offered in turn.
+
+### 2. Ask what they bring
+
+Rules to follow regardless of what the repo does: governance, security and compliance, coding standards, style guides, frozen areas. Ask for outside documents too — handbooks, wikis, architecture docs, MCP knowledgebases. Note the paths; do not read them yet.
+
+Greenfield: this is the whole content. Brownfield: it is the half no scan reaches.
+
+### 3. Discover and verify
+
+Fan out with parallel subagents against what the sections need — executable config and CI for policy and for what they already state, tracked source for conventions and boundaries, targeted history for constraints whose reason must still hold.
+
+`package.json`, a `Makefile`, `pyproject.toml`, and CI config are read to know what the block must not repeat. Their caveats come from the human in step 4. Path-check every claim naming a file.
+
+Each child agreed in step 1 is scanned as its own scope, against its own manifests.
+
+### 4. Interview the gaps
+
+Only what no scan reaches: what agents keep getting wrong here, what is off limits, what a domain term means, why a constraint exists.
+
+- Never ask what a scan could answer. Asking the user to confirm a path-checked claim, or one a config file already states, is a defect.
+- Ask recall questions, not review lists. Never hand the user a selection problem a scan created.
+- A mistake this session made and caught is observed evidence — offer it.
+- A repeatable command spotted in anything read this session — a log, a doc, its own runs — whose correct form is not the obvious guess is a candidate line: offer it. E.g. `uv run pytest` where plain `pytest` looks right but runs outside the project environment.
+- Batches of at most eight; fewer is better. A batch yielding nothing new means write.
+- When the repo contradicts the user, show the evidence and ask. Never write the claim as given, never drop it silently.
+
+### 5. Show the block, then write it
+
+Compose against `template.md`. For each candidate, ask first whether a hook, lint rule, or CI check enforces it better than prose; if so propose the check, and the line becomes the fallback if they decline.
+
+**Show the complete block before writing it**, and every child block alongside it — one approval covers the set. On approval, splice between the markers, leaving everything outside them byte-identical. Fill each provenance line with today's date and the verified SHA.
+
+Where an instruction elsewhere contradicts the block in a way that changes behavior — a stale `CLAUDE.md` line, a retired command — propose the fix to that file. Two live contradictory instructions is a defect.
+
+Never commit.
+
+### 6. Close
+
+- What went in, and what was left out and why.
+- Why, in the user's terms, from `best-practices.md` — why it is small, why what the repo already states stays out, why a pitfall line stays until its cause is gone.
+- How it loads, and that other harness files can point at it.
+- Maintenance: re-run after significant change, `record` the moment an agent gets something wrong, prefer a check over a new line.
+- Rules repeating across their projects, or personal rather than the team's, belong in their global agent config.
+
+### Refresh
+
+Same steps, step 1 as a diff. Read the provenance line, re-verify every path and every caveat, and run `git log --diff-filter=DR --name-only` since the recorded SHA against every line — update or remove lines whose evidence is gone. Never re-ask what a prior run settled; the interview shrinks to what changed about how the team works. The block grows only on new evidence.
+
+### Greenfield
+
+Seeded from a spec or planning document, or interview alone. Commands that do not exist yet are written as explicit TODOs naming the decided stack, never a guessed invocation stated as fact, and verified on the first refresh after code exists. A genuinely contested design decision — real tradeoffs, multiple viable shapes — goes to `bmad-architecture`.
+
+### Migration
+
+If the target has a `project-context.md` from the retired skills, commonly under `{output_folder}`, read it in step 1 and offer to absorb its content. Do not delete it without agreement, and do not silently orphan it.
+
+## Record
+
+Capture one observed agent mistake as it happens — the only admissible source for a pitfall line.
+
+Take the task, the mistake, the correction, and its evidence. Check the block for a line already covering it. One occurrence is noted; a recurring or costly mistake earns a line now — an exact invocation under **Running and verifying** when it is a command error, otherwise a pitfall. Write it and show the diff. If it is mechanically preventable, propose the hook, lint rule, or CI check instead.
+
+## Audit
+
+Re-check every caveat, path-check every file, follow every pointer, and ask of every line whether removing it would change agent behavior. Check for contradictions with other instruction files.
+
+Failing lines move behind an observable trigger, get fixed, or are deleted — confirm deletions first. **A policy or pitfall line goes only when the thing it guards is gone or the user retires it; nothing failing lately is not grounds.** Audit ends smaller or equal.
+
+## Children
+
+A component, nested repository, or extracted rules file gets its own file under the same shape when work keeps landing there and its truths do not belong at the parent level. Rules bounded to a directory go in a nested `AGENTS.md` there, attached by location. Use a linked file only when the trigger is not a path.
+
+A chosen child that ends with nothing its parent does not already say gets no file. Say so and move on.
+
+List every child in the parent's **Where things are** with one line and its path. Discovery never depends on the harness finding it.
diff --git a/.claude/skills/bmad-project-context/customize.toml b/.claude/skills/bmad-project-context/customize.toml
new file mode 100644
index 0000000..bc9fe78
--- /dev/null
+++ b/.claude/skills/bmad-project-context/customize.toml
@@ -0,0 +1,24 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-project-context.
+# Team overrides:     {project-root}/_bmad/custom/bmad-project-context.toml
+# Personal overrides: {project-root}/_bmad/custom/bmad-project-context.user.toml
+#
+# Merge rules: scalars override (last layer wins); arrays append.
+
+[workflow]
+
+# --- Universal defaults ---
+activation_steps_prepend = []
+activation_steps_append = []
+# Deliberately empty: this skill's own output (AGENTS.md) is loaded by the
+# harness, not through this array. Users append their own standing facts.
+persistent_facts = []
+on_complete = ""
+
+# Standing outside-the-repo sources offered at every setup/refresh run
+# (untrusted until verified against the repo or user-confirmed).
+# Append-only. Entries: "file:{project-root}/..." or "file:/abs/path" for
+# docs, "skill:name" to consult a skill, plain text for a standing fact,
+# "tool:name" for an MCP knowledgebase.
+external_sources = []
diff --git a/.claude/skills/bmad-project-context/references/best-practices.md b/.claude/skills/bmad-project-context/references/best-practices.md
new file mode 100644
index 0000000..0da7e6f
--- /dev/null
+++ b/.claude/skills/bmad-project-context/references/best-practices.md
@@ -0,0 +1,65 @@
+# What belongs in a repo's agent instructions
+
+Rules for deciding what goes in the block, for judging what a repo already has, and for explaining both to the user.
+
+## The test
+
+Can an agent derive this by reading the repository? If yes, leave it out — a stored copy is a stale duplicate of something the agent reads more accurately first-hand, and it is charged on every session. Write down what the code cannot say.
+
+## Admit
+
+- **Policy the code cannot express** — branch rules, frozen and protected paths, generated files, secrets, security and compliance. Stated by a human or read off an enforcing config, never inferred.
+- **What a config file cannot say about running the project** — the root test script does nothing in this workspace, integration tests need a service up first, the suite takes eleven minutes so iterate on single files, the `Makefile` is the real entry point and `package.json` is vestigial, CI runs a typecheck the test script does not. The invocation itself is already stated in `package.json`, `Makefile`, `pyproject.toml`, or CI config and does not earn a line — the correction or the caveat does.
+- **Conventions that differ from ecosystem defaults.** An agent follows the norm unless told otherwise, so only the divergences earn a line. Command invocations count: when the obvious command is wrong here — a bare-repo prefix, a required wrapper — the exact working invocation earns a line, and no observed mistake is needed to admit it.
+- **Pitfalls with observed evidence** — a recorded lesson, the maintainer's recollection, the same mistake fixed repeatedly in history, or one this session made and caught. A repo yields hundreds of trap-looking facts and none of them predict real mistakes; only observed behavior does. A surprising scan finding is a question to ask, not a line to write.
+- **Runtime behavior invisible from the repo** — replaying webhooks, lying health endpoints, environment quirks — once a human confirms it.
+- **Entry points and pointers** to where work lands.
+
+Prefer prohibitions to advice, and name the permitted alternative in the same line.
+
+## Exclude
+
+| | Why |
+|---|---|
+| Repo overviews, directory trees, stack lists | Derived fresh, more accurately; stored copies rot |
+| Anything included for being interesting | Interest is not need |
+| Style rules an agent self-enforces | Belongs in a formatter, linter, hook, or CI check — propose the check instead |
+| Platitudes | Already the default |
+| Commands already stated in `package.json`, a `Makefile`, or CI config | Read from the source of truth; a copy drifts the moment a script is renamed |
+| Pasted code, changelog content, fast-changing facts | Stale immediately |
+| Aspirational state | Describe what is; intent belongs in specs |
+| History and edit narration | Git holds it; state present truth |
+
+## Retire
+
+A policy or pitfall line goes only when the thing it guards is gone, or the user retires it. Nothing failing lately is not evidence — a working rule erases its own evidence.
+
+Every other line faces one question at each write: would removing it change agent behavior? If no, cut it.
+
+## Size
+
+Every line is paid in every session, and instruction-following degrades as the loaded set grows. Count what other always-loaded files add. Over budget means cut the weakest lines or move them behind a trigger — never raise the budget. Ten lines of evidence means ten lines.
+
+## Retrieval
+
+An index the agent must choose to fetch gets skipped; one already in context does not. Keep everything load-bearing in the block. A pointer out of it names a trigger the agent can observe — a path, a file type, a named task — never one it must judge ("when the task is complex") or track about itself ("before your first edit").
+
+Rules bounded to a directory go in a nested `AGENTS.md` there, attached by location rather than by pointer. Use a linked file only when the trigger is not a path.
+
+## Maintain
+
+- Re-check that caveats still hold — a slow suite that got fast, a workaround for a bug that was fixed.
+- Diff deletions and renames since the verified SHA against every line.
+- Record provenance in the block so the next run knows what it is diffing from.
+- Capture mistakes when they happen, not at review time. One occurrence is a note; recurrence earns a line.
+- Route anything mechanically preventable to a hook, lint rule, or CI check. A check that lands deletes its line.
+
+## Repo or home directory
+
+This block belongs committed: shared by the team, consistent across machines, versioned with the code it constrains.
+
+Two things belong in the user's global agent config instead — rules repeating across all their projects, and personal preferences that are theirs rather than the team's.
+
+## Judging an existing file
+
+Report, in this order: what is derivable filler, what is unverifiable or stale, what is missing against the sections above, and what is already good. Keep recorded lessons by default — they are maintainer testimony, and are challenged only with evidence that the thing they name is gone or wrong.
diff --git a/.claude/skills/bmad-project-context/references/template.md b/.claude/skills/bmad-project-context/references/template.md
new file mode 100644
index 0000000..8a81089
--- /dev/null
+++ b/.claude/skills/bmad-project-context/references/template.md
@@ -0,0 +1,55 @@
+# Block shape
+
+Sections in this order. Omit any section with nothing that passes its rule — never write an empty one. Admission rules: `best-practices.md`.
+
+1. **Orientation** — three or four sentences: what this is, the stack, where planning and deeper docs live.
+2. **Policy** — what the org requires.
+3. **Where things are** — entry points, and pointers to children and linked files.
+4. **Running and verifying** — only what `package.json`, a `Makefile`, or CI config does not already say.
+5. **Conventions that differ from defaults**
+6. **Known pitfalls**
+
+Terse imperative lines under plain headings. No prose beyond Orientation, no introduction, no summary. A bare fact appears only as the justification clause of an instruction — "Exclude `vendor/` from searches, it is 60% of tracked files", never "`vendor/` is 60% of tracked files". A prohibition names the alternative. At most two emphasis markers in the whole block.
+
+## Worked example
+
+````markdown
+<!-- bmad:context -->
+<!-- Verified 2026-08-08 against a1b2c3d. Managed by bmad-project-context; edits inside this block are replaced on refresh. Keep anything you want preserved outside the markers. -->
+
+## acme-billing
+
+Payment processing for Acme storefronts. TypeScript/Node, pnpm, Postgres. Planning lives in `docs/planning/`, tickets in Linear (ACME board).
+
+## Policy
+
+- Never push to main; PRs only, one approval.
+- Never modify `legacy/` — frozen, being replaced. New work goes in `src/`.
+- Never hand-edit `src/generated/` — run `pnpm codegen`.
+
+## Where things are
+
+- Webhook handling: `src/routes/webhooks.ts`; conventions in `docs/webhooks.md`
+- Writing a migration? Read `docs/db-rules.md` first — ordering, transaction boundaries, pool limits.
+- Billing service has its own guide: `services/billing/AGENTS.md`
+
+## Running and verifying
+
+- Run single test files while iterating; the full suite takes ~11 minutes.
+- Integration tests need `docker compose up -d` first, and fail confusingly without it.
+- CI also runs `pnpm typecheck`, which `pnpm test` does not cover.
+
+## Conventions that differ from defaults
+
+- Money is integer cents (`amountCents`), never floats — `src/lib/money.ts`
+- All DB access goes through repositories in `src/repos/`; never call the client directly.
+
+## Known pitfalls
+
+- Stripe webhooks replay in staging every 6h — handlers must be idempotent.
+- Use vitest matchers, not jest — agents repeatedly add jest syntax here.
+
+<!-- /bmad:context -->
+````
+
+Fill the provenance line with the real date and the commit SHA verified against. Refresh diffs from that SHA.
diff --git a/.claude/skills/bmad-qa-generate-e2e-tests/SKILL.md b/.claude/skills/bmad-qa-generate-e2e-tests/SKILL.md
new file mode 100644
index 0000000..14bd3cd
--- /dev/null
+++ b/.claude/skills/bmad-qa-generate-e2e-tests/SKILL.md
@@ -0,0 +1,176 @@
+---
+name: bmad-qa-generate-e2e-tests
+description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
+---
+
+# QA Generate E2E Tests Workflow
+
+**Goal:** Generate automated API and E2E tests for implemented code.
+
+**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `bmad-code-review` skill for that).
+
+## Conventions
+
+- Bare paths (e.g. `checklist.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `user_name`
+- `communication_language`, `document_output_language`
+- `implementation_artifacts`
+- `date` as system-generated current datetime
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Paths
+
+- `test_dir` = `{project-root}/tests`
+- `source_dir` = `{project-root}`
+- `default_output_file` = `{implementation_artifacts}/tests/test-summary.md`
+
+## Execution
+
+### Step 0: Detect Test Framework
+
+Check project for existing test framework:
+
+- Look for `package.json` dependencies (playwright, jest, vitest, cypress, etc.)
+- Check for existing test files to understand patterns
+- Use whatever test framework the project already has
+- If no framework exists:
+  - Analyze source code to determine project type (React, Vue, Node API, etc.)
+  - Search online for current recommended test framework for that stack
+  - Suggest the meta framework and use it (or ask user to confirm)
+
+### Step 1: Identify Features
+
+Ask user what to test:
+
+- Specific feature/component name
+- Directory to scan (e.g., `src/components/`)
+- Or auto-discover features in the codebase
+
+### Step 2: Generate API Tests (if applicable)
+
+For API endpoints/services, generate tests that:
+
+- Test status codes (200, 400, 404, 500)
+- Validate response structure
+- Cover happy path + 1-2 error cases
+- Use project's existing test framework patterns
+
+### Step 3: Generate E2E Tests (if UI exists)
+
+For UI features, generate tests that:
+
+- Test user workflows end-to-end
+- Use semantic locators (roles, labels, text)
+- Focus on user interactions (clicks, form fills, navigation)
+- Assert visible outcomes
+- Keep tests linear and simple
+- Follow project's existing test patterns
+
+### Step 4: Run Tests
+
+Execute tests to verify they pass (use project's test command).
+
+If failures occur, fix them immediately.
+
+### Step 5: Create Summary
+
+Output markdown summary:
+
+```markdown
+# Test Automation Summary
+
+## Generated Tests
+
+### API Tests
+- [x] tests/api/endpoint.spec.ts - Endpoint validation
+
+### E2E Tests
+- [x] tests/e2e/feature.spec.ts - User workflow
+
+## Coverage
+- API endpoints: 5/10 covered
+- UI features: 3/8 covered
+
+## Next Steps
+- Run tests in CI
+- Add more edge cases as needed
+```
+
+## Keep It Simple
+
+**Do:**
+
+- Use standard test framework APIs
+- Focus on happy path + critical errors
+- Write readable, maintainable tests
+- Run tests to verify they pass
+
+**Avoid:**
+
+- Complex fixture composition
+- Over-engineering
+- Unnecessary abstractions
+
+**For Advanced Features:**
+
+If the project needs:
+
+- Risk-based test strategy
+- Test design planning
+- Quality gates and NFR assessment
+- Comprehensive coverage analysis
+- Advanced testing patterns and utilities
+
+> **Install Test Architect (TEA) module**: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
+
+## Output
+
+Save summary to: `{default_output_file}`
+
+**Done!** Tests generated and verified. Validate against `./checklist.md`.
+
+## On Complete
+
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+
+If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.
diff --git a/.claude/skills/bmad-qa-generate-e2e-tests/checklist.md b/.claude/skills/bmad-qa-generate-e2e-tests/checklist.md
new file mode 100644
index 0000000..aa38ae8
--- /dev/null
+++ b/.claude/skills/bmad-qa-generate-e2e-tests/checklist.md
@@ -0,0 +1,33 @@
+# QA Automate - Validation Checklist
+
+## Test Generation
+
+- [ ] API tests generated (if applicable)
+- [ ] E2E tests generated (if UI exists)
+- [ ] Tests use standard test framework APIs
+- [ ] Tests cover happy path
+- [ ] Tests cover 1-2 critical error cases
+
+## Test Quality
+
+- [ ] All generated tests run successfully
+- [ ] Tests use proper locators (semantic, accessible)
+- [ ] Tests have clear descriptions
+- [ ] No hardcoded waits or sleeps
+- [ ] Tests are independent (no order dependency)
+
+## Output
+
+- [ ] Test summary created
+- [ ] Tests saved to appropriate directories
+- [ ] Summary includes coverage metrics
+
+## Validation
+
+Run the tests using your project's test command.
+
+**Expected**: All tests pass ✅
+
+---
+
+**Need more comprehensive testing?** Install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) for advanced workflows.
diff --git a/.claude/skills/bmad-qa-generate-e2e-tests/customize.toml b/.claude/skills/bmad-qa-generate-e2e-tests/customize.toml
new file mode 100644
index 0000000..0a2c6fe
--- /dev/null
+++ b/.claude/skills/bmad-qa-generate-e2e-tests/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-qa-generate-e2e-tests. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All tests must follow the project's existing test framework patterns."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 5 (Create Summary),
+# after all tests pass and the summary document is saved. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-quick-dev/SKILL.md b/.claude/skills/bmad-quick-dev/SKILL.md
new file mode 100644
index 0000000..d57e4bf
--- /dev/null
+++ b/.claude/skills/bmad-quick-dev/SKILL.md
@@ -0,0 +1,19 @@
+---
+name: bmad-quick-dev
+description: "Deprecated: forwards to bmad-build. Do not use unless invoked by name."
+---
+
+# Deprecated Build Alias
+
+## On Activation
+
+1. Check whether either legacy customization file exists:
+   - `{project-root}/_bmad/custom/bmad-quick-dev.toml`
+   - `{project-root}/_bmad/custom/bmad-quick-dev.user.toml`
+2. If neither legacy file exists, output exactly `bmad-quick-dev is deprecated. Redirecting to bmad-build. Please use bmad-build in the future.`, invoke `bmad-build` exactly once with the user's original input verbatim, then execute no further steps in this shim.
+3. For every legacy file that exists, use its matching new filename:
+   - `{project-root}/_bmad/custom/bmad-quick-dev.toml` becomes `{project-root}/_bmad/custom/bmad-build.toml`.
+   - `{project-root}/_bmad/custom/bmad-quick-dev.user.toml` becomes `{project-root}/_bmad/custom/bmad-build.user.toml`.
+4. If the matching new file does not exist, tell the user that the customization file uses the deprecated name and offer to rename it. Rename it only after explicit approval. If approval is declined or unavailable, or the rename fails, HALT and do not invoke any skill.
+5. If the matching new file already exists, do not overwrite it. Read both files, explain their differences, and propose the exact content for the new file. Resolve conflicting values with the user. Only after the user explicitly approves that content, save and verify the new file, then remove the legacy file. If approval is declined or unavailable, or any operation fails, HALT and do not invoke any skill.
+6. After every detected legacy file has been migrated successfully and no legacy file remains, output exactly `bmad-quick-dev is deprecated. Redirecting to bmad-build. Please use bmad-build in the future.`, invoke `bmad-build` exactly once with the user's original input verbatim, then execute no further steps in this shim.
diff --git a/.claude/skills/bmad-retrospective/SKILL.md b/.claude/skills/bmad-retrospective/SKILL.md
new file mode 100644
index 0000000..4786a01
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/SKILL.md
@@ -0,0 +1,94 @@
+---
+name: bmad-retrospective
+description: 'Evidence-based epic retrospective — collect what the epic produced, verify findings against sources, render an acceptance verdict. Use when the user says "run a retrospective" or "lets retro the epic [epic]". Supports -H/--headless.'
+---
+
+# Retrospective
+
+Review a completed epic by reading the evidence it left — the epic spec, story files, the full diff, per-story commits, sprint status, and session logs when they exist. An unattended epic run leaves a record; this skill reads that record, surfaces the defects no single story could show, and judges the epic against the criteria it set for itself.
+
+Every finding you report carries a source reference (file, line, commit, or log). A claim you cannot point at — an invented root cause, a pattern the diff does not actually show — is not a finding. Drop it.
+
+## Resolution rules
+
+- Bare paths and `{skill-root}` (e.g. `references/aggregate-views.md`, `scripts/sprint_status.py`) resolve from this skill's installed directory.
+- `{project-root}` → the project working directory.
+- `{skill-name}` → the skill directory's basename.
+
+## Modes
+
+Interactive by default. With `-H`/`--headless`: skip every confirmation, take the epic from the invocation (falling back to detection only if none was supplied), never open the team discussion, render the verdict on the evidence alone, and record each assumption made without the user (which epic was selected, the machine verdict, each proposed item) into the retrospective document's Assumptions section so the audit trail survives. The Phase 4 acceptance fail-safe still applies in headless runs.
+
+For automation, `-H <epic>` — an explicit epic in headless mode — is the stable orchestrator-facing interface. Pass the same number to `detect-epic --epic <N>` so the unfinished-story gate is script-backed (see Inputs). Epic auto-detection is a human convenience, not an automation contract: unflagged `detect-epic` returns the highest epic with *any* `done` story, and stories-mode projects have no `sprint-status.yaml` to detect from.
+
+## On Activation
+
+Run these in order before the retrospective begins:
+
+1. **Resolve the workflow block.** Run `uv run --no-cache {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. If it fails, resolve `{workflow.*}` yourself by reading `{skill-root}/customize.toml`, then `{project-root}/_bmad/custom/{skill-name}.toml`, then `.user.toml` in that order, merging base → team → user (scalars override, keyed arrays-of-tables merge by `code`/`id`, other arrays append).
+2. **Run prepend steps** — execute each entry in `{workflow.activation_steps_prepend}` in order.
+3. **Load persistent facts** — treat every `{workflow.persistent_facts}` entry as standing context. `file:` entries are paths/globs under `{project-root}` whose contents load as facts; all others are literal facts.
+4. **Load config** from `{project-root}/_bmad/bmm/config.yaml`: `project_name`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`, `planning_artifacts`, `implementation_artifacts`, and `date` (system datetime), plus `output_folder` from `{project-root}/_bmad/core/config.yaml`. Speak all output in `{communication_language}`; write all documents in `{document_output_language}`. Never state time estimates — AI has changed development speed, so hour/day/week predictions are noise.
+5. **Greet and orient** (interactive only). Greet `{user_name}`, name the epic you are about to retro, and optionally invite their going-in concerns ("anything you want weighted — a story that felt rushed, a risky interaction between two stories?"). Use any answer to focus the Phase 1–2 analysis; it directs attention but never becomes a finding without a source.
+6. **Run append steps** — execute each entry in `{workflow.activation_steps_append}` in order.
+
+## Inputs
+
+| Input | Where | Use |
+|-------|-------|-----|
+| epic | invocation argument, or detected from sprint status | which epic to retro |
+| spec folder | invocation argument, or found under the spec roots | the stories-mode epic: `SPEC.md`, ordered `stories.yaml`, `stories/<id>-*.md` |
+| sprint status | `{implementation_artifacts}/sprint-status.yaml` | epic detection + final status update |
+| architecture / prd | `{planning_artifacts}/*architecture*`, `*prd*` | context for judging as-built vs intended |
+| previous retro (optional) | `{implementation_artifacts}/**/epic-{{prev}}-retro-*.md` | check whether last epic's actions landed |
+| session logs (optional) | conversation/session records for the epic's stories | process lessons; record the gap when absent |
+
+An epic reaches this skill in one of two shapes, and they are peers. **Sprint mode** reads `sprint-status.yaml`. **Stories mode** reads a spec folder holding `SPEC.md`, an ordered `stories.yaml`, and `stories/<id>-*.md` artifacts — the shape an unattended run leaves behind. Resolve which applies first: a named folder is stories mode whether or not sprint status exists; a named epic number is sprint mode; with neither, use sprint mode when `sprint-status.yaml` exists, and otherwise look for spec folders under `{output_folder}/specs`, `{planning_artifacts}`, and `{implementation_artifacts}`. Ask the user which to retro when there is more than one, and never choose silently; headless, stop and require an explicit folder.
+
+In stories mode, `stories.yaml` in list order is the story list — list order is authoritative, filename sort is not — and each story's `stories/<id>-*.md` frontmatter carries its `status`. `pending_stories` is the ids whose status is not `done`; apply the same completeness gate as below. Then skip to Phase 1: do not read or write sprint status for the rest of the run. The rest of this section is sprint mode.
+
+Determine the epic and its unfinished-story list from `sprint_status.py detect-epic` whenever `{implementation_artifacts}/sprint-status.yaml` is available:
+
+- **Epic supplied** (including the stable `-H <epic>` orchestrator path): run `uv run --no-cache {skill-root}/scripts/sprint_status.py detect-epic --file {implementation_artifacts}/sprint-status.yaml --epic <N>`. The script scopes `pending_stories` to that number even when auto-detect would have picked a different epic, and even when the epic has no `done` story yet. `story_count` is that same scoped count of the epic's story keys: `0` means the file has no such epic at all — a nonexistent epic returns the same empty `pending_stories` as a finished one, so treat `story_count: 0` as a likely mistyped epic number, confirm with the user, and headless, stop and report rather than proceeding.
+- **No epic supplied**: run the same command without `--epic` (returns the highest epic with a `done` story). Confirm the detected epic with the user and let them override; in headless mode accept it and record the assumption. If detection returns none, ask the user — or, headless, stop and report.
+
+If the script exits non-zero it emits `{"ok": false, "error": ...}` instead of a detection — the normal path for a stories-mode project with no `sprint-status.yaml`, and for a file that does not parse: surface that error verbatim — or, if the script produced no JSON at all, whatever it wrote to stderr — and ask the user which epic to retro; headless, stop and report. Without a readable sprint-status file there is no `pending_stories` list; record that the completeness check did not run and continue only if the user (or headless Assumptions trail) accepts proceeding without it.
+
+Then check the epic is actually finished before Phase 1. A successful detect carries `pending_stories` — the selected epic's story keys whose status is not `done`, in file order, scoped to that epic alone (an unfinished story in some *other* epic is out of scope for this retrospective). When the list is non-empty, interactively list those stories and ask whether to retro an unfinished epic: if the user declines, stop and report — do not enter Phase 1; if they accept, record the stories they accepted proceeding over in the document's Epic summary. Headless, proceed and record the same list in the Assumptions section — do not invent a confirmation. Either way the list sits in the document, and Phase 4's machine verdict is **rejected** when any story remained unfinished (see `references/acceptance-verdict.md`); a human may override interactively.
+
+## Working state and resumption
+
+The retrospective document is the working artifact, not only the final output. Once the epic is fixed, create it as a skeleton (`references/retro-document.md` names the sections) and write each phase's result into it as you finish — inventory, then findings with sources, then dispositions and verdict. Continuity is re-reading the file.
+
+If a retrospective document for this epic already exists, load it, reconcile its recorded state against the current evidence — the current evidence wins, since commits may have landed and questions may have been answered since — and resume at the first incomplete phase instead of redoing finished ones. In stories mode that document is `{spec-folder}/RETROSPECTIVE.md`, a fixed name so a resumed run finds it; sprint mode keeps its dated `{implementation_artifacts}` filename.
+
+## Flow
+
+Run the phases in order. A default run stops at a written evidence report and verdict; the team discussion in Phase 3 is opt-in.
+
+### Phase 1 — Gather
+
+Enumerate what the epic actually produced and record what is missing. Load `references/evidence-gathering.md` for the inventory checklist, the `git_evidence.py` pre-pass that derives the diff range and per-story commits, and the missing-evidence rule: each later analysis declares what it needs and records a narrowed scope when the evidence is absent, so a reader can always tell "checked and clean" from "never checked."
+
+### Phase 2 — Analyze
+
+Produce findings, each with a source reference, from three angles:
+
+- **Aggregate views** — the defects no single diff hunk shows: architecture delta, duplication map, god-class growth, pattern divergence, spec-to-implementation reconciliation. Load `references/aggregate-views.md` for the catalog and how to derive each (deterministic scripts first).
+- **Diff-scope review** — do not reimplement review. Invoke **`bmad-review`** on the epic's diff for the code lenses (adversarial, edge-case, verification-gap), weighting the boundaries between stories, where no single session ever saw both sides. Fold its findings in. If `bmad-review` is unavailable, run those lenses inline over the diff on a narrowed scope and record the narrowing.
+- **Behavior check (when the epic changed runtime behavior)** — exercise the changed flows end to end and record what you observed. Passing tests do not substitute for running the system.
+
+Consolidate: merge, dedupe, and provenance-link findings. Drop any finding you cannot tie to a source.
+
+### Phase 3 — Team Discussion (opt-in)
+
+Skip by default; never runs headless. When the user asks to "discuss it as a team," "run party mode," or similar, invoke the skill `bmad-party-mode` seeded with the Phase 2 findings so the installed agents react to real evidence — the god class the diff really grew, the verification gap that is actually there, the wins the evidence confirms. Load `references/team-discussion.md` for how to seed it and keep it grounded. If `bmad-party-mode` is unavailable, run the discussion inline over the Phase 2 findings and record the narrowing. The rule: agents speak only to findings with sources.
+
+### Phase 4 — Decide
+
+- **Action items** — compile fix-now findings and process lessons into specific, owned action items. Fixes and spec reconciliations are *proposed here*, not auto-applied; the human decides what to execute.
+- **Acceptance verdict** — judge the final state against the epic's declared acceptance criteria (profile it from the diff and stories if none were declared): **accepted**, **accepted-with-open-items**, or **rejected** — one spelling, everywhere a machine reads it. Unfinished stories in `pending_stories` force the machine verdict to **rejected**. A human decision always overrides. An epic that fails its criteria with no human decision is recorded as *not accepted* — never as silently accepted. Load `references/acceptance-verdict.md` for the rubric, the finding-routing dispositions, and the previous-retro follow-through record — the per-item evidence Phase 5's status offer reads.
+
+### Phase 5 — Finalize
+
+Finalize the retrospective document and update sprint status. Load `references/retro-document.md` for the document's sections and the exact `sprint_status.py update` invocation that marks the retro key `done`, appends the action items, and validates the write. Where the Phase 4 follow-through has evidence a *previous* epic's action item landed, offer `--set-action-status` and pass only the transitions the user confirms — the evidence justifies proposing a transition, and only the user's confirmation justifies writing it; a headless run records the transitions it would have proposed and does not pass the flag at all. In stories mode, finalize `{spec-folder}/RETROSPECTIVE.md` and stop there: no `sprint_status.py` call, no sprint-status file created, and no edits to `SPEC.md`, `stories.yaml`, or any story artifact. Then, if `{workflow.on_complete}` is non-empty, follow it as the final instruction.
diff --git a/.claude/skills/bmad-retrospective/customize.toml b/.claude/skills/bmad-retrospective/customize.toml
new file mode 100644
index 0000000..816e886
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-retrospective. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All retrospectives must produce SMART action items with named owners."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed at the end of Phase 5 (Close), after the retrospective
+# document is saved and sprint-status is updated. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-retrospective/references/acceptance-verdict.md b/.claude/skills/bmad-retrospective/references/acceptance-verdict.md
new file mode 100644
index 0000000..1d83dfa
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/references/acceptance-verdict.md
@@ -0,0 +1,55 @@
+# Decide: Routing and the Acceptance Verdict
+
+Phase 4. Turn the consolidated findings into two outputs: routed action items the human can act on, and an honest verdict on whether the epic met its acceptance criteria. This skill proposes; it does not auto-apply fixes or edit the project spec. The human decides what executes.
+
+## Route each finding
+
+Give every finding two independent dispositions:
+
+- **What to do about this instance** — *fix now*, *defer*, or *accept as-is*. Fix-now findings become action items. Deferred findings carry enough context to be acted on later without re-investigation. Accepted deviations are recorded so later retros stop re-flagging them.
+- **What would prevent the next one** — the upstream lesson: spec wording, story sizing, a missing convention or gate, or nothing. This is where a recurring finding becomes a process change rather than a one-off fix.
+
+Findings from sub-agents or the team discussion are unverified reports, not established facts. Before an action item relies on one, re-check it against the primary source — reopen the file, the commit, the spec. A finding whose source does not hold up is dropped, not routed.
+
+## Action items
+
+Compile fix-now findings and process lessons into specific, owned action items. Each names what to change and who owns it. Two kinds are *proposed, not applied* in this version:
+
+- **Remediation** — code fixes are written up as action items (or story-shaped work) for the normal dev loop to execute later. The retrospective does not run the dev loop itself.
+- **Spec reconciliation** — where the as-built diverges from the spec, propose the reconciliation as an action item with the evidence attached. The human applies it to the project contract; an uncertain interpretation is never written into the spec automatically.
+
+## Previous-retro follow-through
+
+When a prior retro exists, check whether the action items it committed to were completed. Read `action_items` in `{implementation_artifacts}/sprint-status.yaml` and, for every entry belonging to an earlier epic that is not already `done`, record one line in the retrospective document's Previous-retro follow-through section:
+
+- **How to address the item** — its `id`, exactly as the file spells it. Legacy entries written before ids existed have none; for those, record the item's `epic` (the integer in the file) plus its exact `action` text, character for character. One or the other is what Phase 5 needs to name the item at all.
+- **Whether it landed** — with the source that shows it: the commit, the file and line, the test. An item you cannot point at is "no evidence found", not "not done" — the reader must be able to tell a checked item from an unchecked one.
+- **The status it argues for** — `done` for a landed item, `in-progress` for one demonstrably underway, or nothing. A proposal, never a write.
+
+That record is exactly what Phase 5's `--set-action-status` offer reads: the selector becomes the JSON, the evidence is what the user is asked to confirm, and the proposed status is written only if they confirm it. A run with no prior retro, or one whose `sprint-status.yaml` is unreadable or carries no `action_items`, records that there was nothing to follow through on — and which of those it was, so a missing file is never mistaken for "no outstanding items."
+
+## The verdict
+
+Judge the final state against the epic's declared acceptance criteria. If the epic declared none, profile the criteria from the diff and stories and mark the verdict as **profiled** rather than declared. Weigh verification results (the Phase 2 behavior check) and unresolved findings. Render one of:
+
+- **Accepted** — criteria demonstrably met in the evidence, no blocking findings open, and **no unfinished stories** for this epic.
+- **Accepted-with-open-items** — criteria met, but named findings remain deferred and tracked — still only when every story of this epic is `done`.
+- **Rejected** — criteria not met, a blocking finding stands unresolved, **or any of this epic's stories is still not `done`**.
+
+### Unfinished stories
+
+`pending_stories` is authoritative for this epic's incomplete work, whichever mode produced it: sprint-status story keys in file order from `detect-epic`, or `stories.yaml` ids in list order whose artifact status is not `done`. When that list is non-empty:
+
+- The **machine** verdict is **rejected**. Name every unfinished story key in the Acceptance verdict section as the evidence. Do not soften this to accepted-with-open-items: unfinished delivery is not an open finding about a finished epic — the epic itself is incomplete.
+- Record the unfinished keys in Epic summary (interactive) or Assumptions (headless) as the Inputs section already requires.
+- Headless runs have no human at the console: the document's verdict is **rejected** when `pending_stories` was non-empty. Interactive runs may still let a human override (rule 1 below) after seeing the list.
+
+If the completeness check did not run (no readable `sprint-status.yaml`), do **not** render a rejected or accepted verdict from the absence of data — say the check was unavailable and weigh only the criteria and findings you have.
+
+Three hard rules:
+
+1. A human decision always overrides the machine verdict.
+2. An epic that fails its criteria with **no** human decision is recorded as **not accepted** — never as silently accepted.
+3. A non-empty `pending_stories` list makes the machine verdict **rejected**, including in headless mode.
+
+The verdict and its evidence carry into the Phase 5 document.
diff --git a/.claude/skills/bmad-retrospective/references/aggregate-views.md b/.claude/skills/bmad-retrospective/references/aggregate-views.md
new file mode 100644
index 0000000..1893e18
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/references/aggregate-views.md
@@ -0,0 +1,17 @@
+# Aggregate Views
+
+Phase 2. An epic is many coding sessions, each validated in isolation; the defects that matter are the ones no single session — and no single diff hunk — could see. Nine sessions each added three hundred lines and none ever saw the 3,000-line class they collectively built. These views are properties of the *whole* change, derived across the full diff range from Phase 1.
+
+Prefer deterministic derivation: a script that measures the codebase is evidence; a model's impression is not. Where you compute a view inline instead of by script, record the narrowed scope. Every observation that becomes a finding carries a source reference — the file, the symbol, the commits. `references/evidence-gathering.md` is authoritative for what every `git_evidence.py` key means, including the commit-level `is_merge` and `stories` (every story id a subject names, so a commit spanning two counts for both) — read it there before deriving anything from the numbers.
+
+## The catalog
+
+- **Architecture delta** — how the dependency structure changed across the epic. Where a language-native dependency tool exists (dependency-cruiser, madge, pydeps, and the like), run it before and after the range and diff the graphs; otherwise derive the module/import graph from the changed files. Look for new cross-cutting dependencies, layering violations, and cycles introduced — structure the code's own conventions would forbid but no single story tripped.
+- **Duplication map** — the same problem solved more than one way across stories. Two sessions independently writing near-identical logic, or a helper reimplemented because the second session did not know the first existed.
+- **God-class / size growth** — files that grew past a healthy size *over the epic*, invisible per-commit because each session added only a little. The `git_evidence.py` pre-pass (Phase 1) reports `added` / `deleted` / `net` per path in `files` — *change volume*, not a file's absolute size or a per-commit growth rate. Those sums cover the range's **non-merge** commits only, and they are always integers: an unmeasurable revision is left out of them rather than nulling them. Rank on `files`, then open the top of the ranking and read each file's real current size and structure before calling anything a god-class — high net churn makes a file a candidate to inspect, not a verdict on its own. Three qualifiers say how far the ranking can be trusted: `binary_revisions` counts that path's revisions whose churn could not be measured, so its true volume is *at least* what the sums report; `merges_measured` short of `merge_count` means some merges were never measured at all, which caps how complete the ranking can be; and `merge_files` mostly restates churn `files` already counted, so summing the two double counts — but it is not redundant, because a merge's first-parent diff also carries whatever the conflict resolution itself added, code that lives in no non-merge commit and therefore appears in `files` nowhere. So read `merge_files` separately, for the paths whose churn shows up only there, rather than discarding it as double counting. Whether a flagged file is genuinely a god-class or legitimately large stays your judgment.
+- **Pattern divergence** — where the epic's code diverges from the conventions the surrounding codebase already established: naming, error handling, test structure, module boundaries. Agents learn conventions by pattern-matching the code, so divergence compounds.
+- **Spec-to-implementation reconciliation** — where the as-built diverges from what the epic spec and PRD/architecture described. Requirements silently dropped, added behavior nobody specified, intent reinterpreted between stories. Each divergence is either a defect (fix), an accepted deviation (record so later runs stop re-flagging it), or a spec that should be reconciled to reality (propose in Phase 4).
+
+## Delegation
+
+When sub-agents are available, delegate the derivation: each returns evidence with source refs and checked scope, never a verdict — the parent consolidates and decides. Give each a narrow view and an explicit return format. When sub-agents are unavailable, compute the highest-value views inline (architecture delta and spec reconciliation first) and record which views were narrowed or skipped.
diff --git a/.claude/skills/bmad-retrospective/references/evidence-gathering.md b/.claude/skills/bmad-retrospective/references/evidence-gathering.md
new file mode 100644
index 0000000..90e6213
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/references/evidence-gathering.md
@@ -0,0 +1,30 @@
+# Evidence Gathering
+
+Phase 1 of the retrospective. Enumerate what the completed epic produced, so every later analysis works from real artifacts instead of memory. Output is an inventory: what exists, what is missing, and the diff range the rest of the retro will read.
+
+## Inventory checklist
+
+Collect what the epic produced and note the source path or range of each:
+
+- **Epic spec** — the epic file under `{planning_artifacts}`, including any declared acceptance criteria. If the spec declares how the epic will be judged, that governs Phase 4; if not, note that the verdict will be profiled from the diff.
+- **Story files** — the story specs implemented under this epic (`{implementation_artifacts}`), each carrying its intent and context. These mark the boundaries between coding sessions.
+- **Diff range and commits** — the full set of changes the epic introduced. Establish the range from the first and last story commits (or ask the user for it). The range must *include* the first story commit: `A..B` excludes `A`, so use the parent of the first commit as the left endpoint — `<first-commit>^..<last-commit>` — or the whole first story disappears from the diff, the commit attribution, and the verdict evidence. Then run `uv run --no-cache {skill-root}/scripts/git_evidence.py --repo {project-root} --range <range> --stories <story-ids>` to get, as JSON, the per-story commit attribution and the per-file change volume — added / deleted / net across the range — that Phase 2 reads. Record the range explicitly; Phase 2's aggregate views and the `bmad-review` pass both read it. When the range cannot be established, say so and narrow the scope rather than guessing. Read the output keys precisely: each commit carries `is_merge` and `stories` — *every* id its subject names, so a commit spanning two stories counts for both. `files` sums non-merge commits only. `merge_files` is each measured merge's diff against its first parent, so it *restates* the churn that merge brought in plus whatever the conflict resolution added — never add it into `files`, and never read it as merge-introduced work on its own. `merges_measured` counts the merges on the range head's first-parent spine; `merge_count` counts every merge in the range, so a gap between the two means merges went unmeasured. `binary_revisions` is unmeasured churn, not zero churn.
+- **Sprint status** — `{implementation_artifacts}/sprint-status.yaml`, for which stories are `done` and the current retro-key state.
+- **Previous retrospective** — the prior epic's retro doc, if one exists, so Phase 4 can check whether last epic's action items landed.
+- **Session logs** — conversation or session records for the epic's stories, when available. They are the only record of *why* a session took an unexpected turn — what was tried and abandoned. They are also the evidence most likely to be deleted or expire, so capture references now.
+
+## Stories mode
+
+A stories-mode epic is a spec folder. Map it onto the checklist above: `SPEC.md` is the epic spec; `stories.yaml` in list order is the story list, each entry's artifact being the single `stories/<id>-*.md` it names; there is no sprint status; the previous retrospective, when resuming, is `{spec-folder}/RETROSPECTIVE.md`; session logs are unchanged.
+
+The diff range differs. Each story records its own baseline in its artifact frontmatter — `baseline_revision` (deprecated) or `baseline_commit` — so there is no single epic-wide range. The range end is the next story's baseline in list order, which is exact because neither skill adds a commit of its own after the work. For the last story, when nothing records the end, derive it from the history — usually `HEAD`, though not always — and mark it inferred rather than recorded. A baseline that is absent or is not a revision leaves that story with no commit or diff evidence — record that too. Group the stories sharing an identical range and run `git_evidence.py` once per distinct range, passing that group's ids as one comma-separated `--stories` value. No `^` is needed here: unlike the sprint-mode range above, the recorded baseline is already the pre-change commit. Ranges may overlap or diverge; count a shared commit or file change once in the aggregate views while keeping each story's range as its provenance.
+
+## Missing evidence
+
+Evidence availability varies; never hide a gap. Each later analysis declares what it needs and, when that input is absent, records a narrowed scope rather than guessing. A reader of the final retro must always be able to tell **"checked and clean"** from **"never checked."**
+
+- Missing session logs → process-lesson analysis is skipped, and the retro says so.
+- No declared acceptance criteria → the verdict is profiled from the diff and stories, flagged as profiled rather than declared.
+- Sub-agents unavailable → analyses that would delegate run inline over a narrowed scope, and the narrowing is recorded.
+
+Carry the inventory forward into Phase 2 as the authoritative list of what is available to read.
diff --git a/.claude/skills/bmad-retrospective/references/retro-document.md b/.claude/skills/bmad-retrospective/references/retro-document.md
new file mode 100644
index 0000000..8fdcb9e
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/references/retro-document.md
@@ -0,0 +1,84 @@
+# Finalize: Retrospective Document and Sprint Status
+
+Phase 5. Finalize the retrospective and update sprint tracking. Two writes: the retrospective document, and the `sprint-status.yaml` update. Stories mode makes only the first.
+
+## The retrospective document
+
+This document is the run's working artifact: it is created as a skeleton once the epic is fixed and filled as each phase completes, so Phase 5 finalizes rather than writes it from scratch. It lives at `{implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md`, in `{document_output_language}`, as readable markdown; ensure `{implementation_artifacts}` exists. In stories mode it lives at `{spec-folder}/RETROSPECTIVE.md` instead — a fixed name, so a resumed run finds it — and carries the same frontmatter without `epic`, which the folder already names.
+
+Open the document with YAML frontmatter a machine can read without parsing the prose — an epic gate or orchestrator keys off `verdict` to decide whether to hold the next epic:
+
+```
+---
+epic: {{epic_number}}
+date: {date}
+verdict: accepted | accepted-with-open-items | rejected
+criteria: declared | profiled
+headless: true | false
+---
+```
+
+Keep `verdict` in sync with the Acceptance verdict section below. Do not encode the verdict in the sprint-status retro key — that key's value stays `done` so the existing lifecycle consumers (sprint planning's `optional ↔ done` transition, status TUIs) keep working unchanged.
+
+That holds for a **rejected** epic too: the update below marks the retro key `done` whichever way the verdict went, because `done` there means *the retrospective ran*, not *the epic passed*. The script writes no verdict of any kind into `sprint-status.yaml` — there is no `retro_verdict` key and `--verdict` is only echoed back in the result JSON — so a gate or orchestrator that acts on the verdict **must** read this document's frontmatter. Reading sprint-status alone cannot tell a rejected epic from an accepted one.
+
+Sections:
+
+- **Epic summary** — which epic, the diff range, stories completed, any stories still unfinished (`pending_stories`) that the user accepted retro-ing over, the evidence inventory (what was available, what was missing). Unfinished stories force the machine acceptance verdict to **rejected** (see `references/acceptance-verdict.md`).
+- **Findings** — grouped by aggregate view and by lens, each with its source reference and disposition (fix now / defer / accept). This is the record; do not summarize away the provenance.
+- **Behavior verification** — what was exercised end to end and what was observed, or an explicit note that runtime behavior was not exercised.
+- **Previous-retro follow-through** — if a prior retro exists, whether its action items landed, with evidence, and the selector Phase 5 would need to act on each (`references/acceptance-verdict.md` specifies what to record).
+- **Action items** — the routed fix-now items and process lessons, each with an owner. Note which are proposed remediation or spec reconciliations awaiting human application.
+- **Acceptance verdict** — accepted / accepted-with-open-items / rejected, whether the criteria were declared or profiled, and the evidence behind the call.
+- **Open questions** — what a human answer would materially change, and anything the analyses could not resolve.
+- **Assumptions** — in headless runs, every choice made without the user: which epic was selected (invocation or auto-detect), the `detect-epic --epic <N>` (or unflagged) result including any non-empty `pending_stories`, a machine **rejected** verdict forced by unfinished stories or rendered with no human decision, each proposed item. Omit in interactive runs — an interactive run records the same facts where the user confirmed them, in Epic summary.
+
+Do not state time estimates anywhere in the document.
+
+## Sprint-status update
+
+Do not hand-edit `sprint-status.yaml` — its comment blocks and quoting are exactly the write that most often corrupts the file. Use the bundled script, which round-trips through a comment-preserving YAML parser, force-quotes values so punctuation (a leading `#`, a colon) cannot break parsing, and validates the result — restoring the original file untouched if the write does not verify:
+
+```
+uv run --no-cache {skill-root}/scripts/sprint_status.py update \
+  --file "{implementation_artifacts}/sprint-status.yaml" \
+  --epic {{epic_number}} --set-retro-done \
+  --add-action '[{"action":"...","owner":"..."}, ...]' \
+  --ref "{implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md" \
+  --verdict "<accepted | accepted-with-open-items | rejected>" \
+  --date "{date}"
+```
+
+Keep every value quoted. `--date` is parsed as `MM-DD-YYYY HH:MM` and nothing else — unpadded spellings like `1-2-2026 9:05` are accepted and normalized to the padded form, but a value that does not parse is rejected with `ok: false`, `restored: true` and exit 1, before the file is touched, and the whole update is a no-op. So pass `{date}` only if it is already in that form; otherwise reformat it, or omit the flag entirely and let the script stamp the current time itself. That format carries a space, which is why the flag must be quoted: unquoted, `--date 07-28-2026 14:23` splits into two argv words and dies at argparse (`{"ok": false, "error": "argument error: unrecognized arguments: 14:23"}`, exit 2). `--file` and `--ref` are quoted for the same reason — an `{implementation_artifacts}` path containing a space breaks them exactly the same way.
+
+It sets `development_status["epic-{{epic_number}}-retrospective"]` to `done`, appends one `action_items` entry per proposed item, and bumps `last_updated`. Each appended item carries `status: open`, a stable `id` (`epic-<N>-retro-item-<n>-<slug>` derived from the action text, or the `id` you supply in the JSON), and a `ref` back to this retro document (from `--ref`, or a per-item `ref` in the JSON) — so an orchestrator can dedupe items across re-runs and dispatch each one to its full, sourced finding. `--verdict` is not written into the file; it is echoed back in the result JSON as a signal for consumers. It accepts exactly the frontmatter vocabulary — `accepted`, `accepted-with-open-items`, `rejected` — and any other spelling is rejected (`ok: false`, `restored: true`, exit 1) before the file is touched. Read the JSON it returns:
+
+- `ok: true` → report the retro-key transition, `action_items_added`, `action_items_updated`, and the echoed `verdict`.
+- `ok: false` → the file was left untouched (`restored: true`); surface the error, do not hand-edit. `restored: false` means the rollback write also failed and the file may be incomplete — warn the user explicitly.
+- `restored` speaks only for a command that may have written. Every `update` failure carries it; `detect-epic` never emits it, because it never writes; and an invocation the parser itself rejects (`argument error: ...`, exit 2) carries neither the key nor a file to speak about. Read a missing `restored` as "nothing was at risk", never as `false`.
+- `retro_key_found: false` → the retro key was absent, so nothing was marked done; the document still saved, but tell the user sprint-status needs a manual retro entry.
+- `retro_key_found: null` → `--set-retro-done` was not passed, so the key was never looked for. Distinct from `false`, which is a real absence the user needs to be told about.
+
+Moving a *previous* epic's action items off `open` is recorded in the retro document either way. When the Phase 4 follow-through has evidence an item landed, or the user says one did, offer to update the sprint-status entries too and run `--set-action-status` with exactly what the user confirms — that flag is the only supported way to change a status; hand-editing never is. It can be passed in the same invocation as the update above, or run on its own:
+
+```
+uv run --no-cache {skill-root}/scripts/sprint_status.py update \
+  --file "{implementation_artifacts}/sprint-status.yaml" \
+  --epic {{epic_number}} \
+  --set-action-status '[{"id":"epic-1-retro-item-1-add-error-handling","status":"done"},{"epic":1,"action":"Exact action text","status":"in-progress"}]'
+```
+
+Rules:
+
+- Select an item by its `id`, or — for legacy entries written before ids existed — by `epic` plus the item's exact `action` text. An entry carrying both uses the `id`. Matching is exact: no trimming, no case folding, and `epic` must be a JSON integer. The `--epic` flag does not scope selectors; it only names the retro key and the epic recorded on appended items, so items from any epic are addressable in one call.
+- The only statuses are `open`, `in-progress`, and `done`. `bmad-sprint-planning`'s status view counts both `open` and `in-progress` as open action items, so only `done` retires an item from the surfaced list — moving something to `in-progress` records progress, it does not quiet the dashboard.
+- Every selector must resolve to exactly one item already in the file. Matching nothing, matching more than one, or colliding with another entry in the same array aborts the whole invocation — `ok: false`, `restored: true`, the file byte-identical and nothing partially applied. "Whole invocation" includes any `--set-retro-done` and `--add-action` passed in the same call: one mistyped selector drops the entire update, so re-run the full command after fixing it rather than assuming the retro key was set.
+- Items appended by `--add-action` in the same run are not addressable in that run; they are always written as `open`.
+- Only ever apply a status the user confirmed, and in a headless run do not pass this flag at all.
+- Success reports `action_items_updated`.
+
+Only ever apply a status the user confirmed: the evidence justifies proposing a transition, and only the user's confirmation justifies writing it. In a headless run do not use this flag at all — record the transitions you would have proposed in the Previous-retro follow-through section and leave the prior items' statuses alone.
+
+## Finish
+
+Report where the document was saved, the verdict, and the action-item count. Then, if `{workflow.on_complete}` is non-empty, follow it as the final terminal instruction before exiting.
diff --git a/.claude/skills/bmad-retrospective/references/team-discussion.md b/.claude/skills/bmad-retrospective/references/team-discussion.md
new file mode 100644
index 0000000..9e6c981
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/references/team-discussion.md
@@ -0,0 +1,22 @@
+# Team Discussion (opt-in)
+
+An optional discussion layer over Phase 2's findings, off by default. It exists for users who want the retrospective discussed from multiple perspectives, the way a team would. One rule: **the team discusses evidence, never invention.** Agents speak only to findings that carry source references. No agent may describe an event that did not happen or report a pattern the diff does not show.
+
+## When to run it
+
+Only when asked — "discuss it as a team," "run party mode," or similar. A default run never enters this phase.
+
+## How to run it
+
+Invoke **`bmad-party-mode`**, seeded with the consolidated Phase 2 findings and the epic context, so the installed agents react as real subagents with independent thinking rather than a scripted dialogue. Seed it with:
+
+- The findings, each with its source reference, grouped by the aggregate view or lens that produced it.
+- The improvements the evidence confirms — real gains, patterns that worked — so positive observations are grounded in fact.
+- The epic's acceptance criteria (or the profiled stand-in), so the discussion can weigh the verdict.
+- The previous epic's action items and whether they landed, when a prior retro exists, so accountability is grounded in fact.
+
+If `bmad-party-mode` is unavailable, a discussion the user asked for must not silently fail to happen. Run it inline over the same seed — take each perspective yourself, hold every perspective to sourced findings — and record in the retrospective document that the discussion ran inline rather than through the installed agents. Record it as the narrowing it is: one model playing every role loses the independent disagreement that surfaces missed findings. State that in the document rather than omitting it.
+
+Facilitate in `{communication_language}`, keep the user an active participant, and steer toward systemic understanding over blame — the point is which process or convention would have prevented a finding, not who wrote the line. Capture anything the discussion surfaces that the analyses missed; a genuinely new observation becomes a finding only once you can tie it to a source, otherwise it is a question for Phase 4, not a conclusion.
+
+The discussion does not replace Phase 4. Its output feeds the action items and the verdict; it does not render them.
diff --git a/.claude/skills/bmad-retrospective/scripts/__pycache__/sprint_status.cpython-311.pyc b/.claude/skills/bmad-retrospective/scripts/__pycache__/sprint_status.cpython-311.pyc
new file mode 100644
index 0000000..1fb2805
Binary files /dev/null and b/.claude/skills/bmad-retrospective/scripts/__pycache__/sprint_status.cpython-311.pyc differ
diff --git a/.claude/skills/bmad-retrospective/scripts/git_evidence.py b/.claude/skills/bmad-retrospective/scripts/git_evidence.py
new file mode 100644
index 0000000..4ff8116
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/scripts/git_evidence.py
@@ -0,0 +1,304 @@
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""Measure git commit and file-change evidence over a revision range.
+
+Prints ONLY JSON to stdout. Errors are emitted as JSON to stdout with a
+non-zero exit code: 2 for invalid arguments (rejected before git runs),
+1 for git or I/O failures. This script only MEASURES — it never judges
+acceleration or violations. The model interprets the numbers.
+
+Two git passes. The first lists every commit in the range (merges included)
+and sums the per-file churn of the non-merge commits, which is what `files`
+reports. The second runs only when the range contains merges and measures
+those merges alone, reported separately as `merge_files` — never folded into
+`files`, because a merge's diff against its first parent restates the churn
+of the commits it merged in, which the first pass already counted.
+"""
+
+import argparse
+import json
+import os
+import re
+import subprocess
+import sys
+
+UNIT_SEP = "\x1f"
+# sha, space-separated parents (empty for a root commit), subject.
+LOG_FORMAT = f"--format=%H{UNIT_SEP}%P{UNIT_SEP}%s"
+
+
+def _emit(obj, code=0):
+    sys.stdout.write(json.dumps(obj))
+    sys.exit(code)
+
+
+class JsonArgumentParser(argparse.ArgumentParser):
+    """Emit argparse failures on the JSON-only stdout contract, not usage text.
+
+    The parser is constructed with ``add_help=False``. The override below covers
+    ``error()``, but ``-h`` never reaches it: the built-in help action calls
+    ``print_help()`` and ``exit(0)`` directly, which would put plain usage text
+    on stdout with a zero exit and break the JSON-only contract. Removing the
+    action instead of intercepting it routes ``-h`` through the already-tested
+    ``error()`` path as an ordinary unrecognized argument. The cost is that the
+    ``help=`` strings are unreachable from the CLI; the skill's references carry
+    the usage a human needs.
+    """
+
+    def error(self, message):
+        _emit({"ok": False, "error": f"argument error: {message}"}, 2)
+
+
+def _parse_numstat_line(line):
+    # numstat lines: "<added>\t<deleted>\t<path>"; binary files use "-".
+    parts = line.split("\t")
+    if len(parts) < 3:
+        return None
+    added_raw, deleted_raw, path = parts[0], parts[1], "\t".join(parts[2:])
+    added = None if added_raw == "-" else int(added_raw)
+    deleted = None if deleted_raw == "-" else int(deleted_raw)
+    return added, deleted, path
+
+
+def _git_log(repo, extra_args, rng):
+    """Run one `git log --numstat` pass over `rng` and return its stdout.
+
+    `core.quotePath=false` keeps non-ASCII paths as real UTF-8 strings instead
+    of octal escapes, and `--no-renames` makes a rename an honest delete + add
+    instead of an unopenable "src/{a => b}" pseudo-path that splits one file's
+    churn across several keys. Both matter for every pass, so both live here.
+
+    `log.diffMerges=separate` is pinned on the command line because it is what
+    `-m` means: a user or repo config setting it to `off` makes pass 2 emit no
+    file rows at all, so `merge_files` would come back empty beside a non-zero
+    `merges_measured` and read as "the merges changed nothing".
+    """
+    cmd = [
+        "git",
+        "-c",
+        "core.quotePath=false",
+        "-c",
+        "log.diffMerges=separate",
+        "-C",
+        repo,
+        "log",
+        "--numstat",
+        "--no-renames",
+        *extra_args,
+        LOG_FORMAT,
+        rng,
+        "--",  # terminate rev parsing so the range can never match a pathspec
+    ]
+    try:
+        # Decode explicitly: git emits UTF-8 path bytes regardless of the
+        # caller's locale, and a C locale would otherwise decode them as ASCII.
+        # surrogateescape, not replace: replace maps every invalid byte to the
+        # same U+FFFD, so two distinct non-UTF-8 paths would collapse into one
+        # `files` key with their churn silently summed. Lone surrogates survive
+        # json.dumps (escaped as \udcXX under ensure_ascii) and json.loads.
+        proc = subprocess.run(
+            cmd,
+            capture_output=True,
+            text=True,
+            encoding="utf-8",
+            errors="surrogateescape",
+            env={k: v for k, v in os.environ.items() if not k.startswith("GIT_")},
+        )
+    except Exception as exc:  # noqa: BLE001
+        _emit({"ok": False, "error": str(exc)}, 1)
+
+    if proc.returncode != 0:
+        # stderr can be empty (a signal kill, a quiet failure); the exit code is
+        # then the only thing left to report, so never emit an empty error.
+        _emit(
+            {
+                "ok": False,
+                "error": proc.stderr.strip() or f"git exited {proc.returncode}",
+            },
+            1,
+        )
+    return proc.stdout
+
+
+def _parse_log(output, stories):
+    """Turn one pass's log output into (commits, files_map). Shared by both."""
+    commits = []
+    files = {}  # path -> {path, _added, _deleted, binary_revisions, commit_count}
+    seen = set()
+    counting = True
+
+    for raw in output.splitlines():
+        if UNIT_SEP in raw:
+            sha, parents, subject = raw.split(UNIT_SEP, 2)
+            # Under -m, git repeats a merge's header once per parent unless it
+            # also honours --first-parent (git 2.31+). Count only the first
+            # block for a sha — git emits parents in order, so that block is
+            # the first-parent diff either way, and no churn is double counted.
+            counting = sha not in seen
+            if not counting:
+                continue
+            seen.add(sha)
+            commits.append(
+                {
+                    "sha": sha,
+                    "subject": subject,
+                    # Every id the subject names, in --stories order: a commit
+                    # spanning two stories belongs to both. Word-boundary match
+                    # so a story id like "1-2" does not also match "11-2".
+                    "stories": [
+                        sid
+                        for sid in stories
+                        if re.search(rf"\b{re.escape(sid)}\b", subject)
+                    ],
+                    "is_merge": len(parents.split()) > 1,
+                }
+            )
+            continue
+
+        if not counting or not raw.strip():
+            continue
+
+        parsed = _parse_numstat_line(raw)
+        if parsed is None:
+            continue
+        added, deleted, path = parsed
+
+        entry = files.get(path)
+        if entry is None:
+            # _added/_deleted are running sums over the path's text revisions.
+            entry = {
+                "path": path,
+                "_added": 0,
+                "_deleted": 0,
+                "binary_revisions": 0,
+                "commit_count": 0,
+            }
+            files[path] = entry
+
+        entry["commit_count"] += 1
+        if added is None or deleted is None:
+            # A binary revision is unmeasurable, not zero — count it alongside
+            # the sums instead of nulling the path's real measured churn.
+            entry["binary_revisions"] += 1
+        else:
+            entry["_added"] += added
+            entry["_deleted"] += deleted
+
+    return commits, files
+
+
+def _file_list(files):
+    return [
+        {
+            "path": entry["path"],
+            "added": entry["_added"],
+            "deleted": entry["_deleted"],
+            "net": entry["_added"] - entry["_deleted"],
+            "commit_count": entry["commit_count"],
+            "binary_revisions": entry["binary_revisions"],
+        }
+        for entry in files.values()
+    ]
+
+
+def main(argv=None):
+    parser = JsonArgumentParser(
+        description=(
+            "Measure commit and per-file change evidence over a git revision "
+            "range. Measures only; does not judge."
+        ),
+        add_help=False,
+    )
+    parser.add_argument("--repo", default=".", help="Path to the git repo (default: .)")
+    parser.add_argument("--range", dest="range", help="Revision range REV..REV")
+    parser.add_argument(
+        "--stories",
+        help="Comma-separated story ids to match against commit subjects.",
+    )
+    args = parser.parse_args(argv)
+
+    stories = []
+    if args.stories:
+        # dict.fromkeys dedupes while keeping the caller's order: a repeated id
+        # would otherwise land twice in a commit's `stories`, double counting
+        # that commit in any per-story total built from the output.
+        stories = list(
+            dict.fromkeys(s.strip() for s in args.stories.split(",") if s.strip())
+        )
+
+    if not args.range:
+        _emit(
+            {
+                "range": None,
+                "note": "no range supplied",
+                "commits": [],
+                "files": [],
+            }
+        )
+
+    # Accept only an explicit REV..REV range. Anything else silently measures
+    # the wrong thing: a leading "-" is consumed by git as an option, a single
+    # rev logs all history up to it, a bare pathspec logs by path, an empty
+    # endpoint ("..", "a..", "..b") makes git default that side to HEAD, and a
+    # three-dot "A...B" is a symmetric difference — a different commit set
+    # entirely. partition splits at the FIRST "..", so any of those extra-dot
+    # shapes leaves `right` empty or dot-prefixed.
+    left, _, right = args.range.partition("..")
+    if (
+        args.range != args.range.strip()
+        or args.range.startswith("-")
+        or not left
+        or not right
+        or right.startswith(".")
+    ):
+        _emit(
+            {
+                "ok": False,
+                "error": f"invalid --range {args.range!r}: expected a revision range like REV..REV",
+            },
+            2,
+        )
+
+    # Pass 1 — the listing. No extra args, so full topology: every commit in
+    # the range including merges, which is what per-story attribution reads.
+    # Merges contribute no numstat rows here, so `files` is non-merge churn.
+    commits, files = _parse_log(_git_log(args.repo, [], args.range), stories)
+    merge_count = sum(1 for commit in commits if commit["is_merge"])
+
+    # Pass 2 — merge churn, only when there is any. `-m --first-parent
+    # --min-parents=2` walks the range head's first-parent spine and emits
+    # exactly one diff-against-first-parent block per merge sitting on it.
+    # Merges off that spine are counted in merge_count and never measured,
+    # which is precisely why merges_measured is a separate key: the gap
+    # between the two is a visible statement that some merges went
+    # unmeasured. This never folds into `files` — a merge's first-parent diff
+    # restates the churn of the commits it merged in, which pass 1 already
+    # counted, so adding it in would double count.
+    merge_commits, merge_files = [], {}
+    if merge_count:
+        merge_commits, merge_files = _parse_log(
+            _git_log(
+                args.repo,
+                ["-m", "--first-parent", "--min-parents=2"],
+                args.range,
+            ),
+            stories,
+        )
+
+    _emit(
+        {
+            "range": args.range,
+            "commit_count": len(commits),
+            "merge_count": merge_count,
+            "merges_measured": len(merge_commits),
+            "commits": commits,
+            "files": _file_list(files),
+            "merge_files": _file_list(merge_files),
+            "stories_supplied": stories,
+        }
+    )
+
+
+if __name__ == "__main__":
+    main()
diff --git a/.claude/skills/bmad-retrospective/scripts/sprint_status.py b/.claude/skills/bmad-retrospective/scripts/sprint_status.py
new file mode 100644
index 0000000..f41171b
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/scripts/sprint_status.py
@@ -0,0 +1,746 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["ruamel.yaml>=0.18"]
+# ///
+"""Detect the current retrospective epic and surgically update sprint-status.yaml.
+
+Prints ONLY JSON to stdout. Errors are emitted as JSON to stdout with a non-zero
+exit code. The ``update`` subcommand round-trips the YAML to preserve all comments
+and formatting, writes atomically (temp file + ``os.replace``), and restores the
+original file bytes on any validation failure.
+"""
+
+import argparse
+import hashlib
+import io
+import json
+import os
+import re
+import stat
+import sys
+import tempfile
+from collections import Counter
+from collections.abc import Mapping
+from datetime import datetime
+
+from ruamel.yaml import YAML
+from ruamel.yaml.scalarstring import DoubleQuotedScalarString
+
+STORY_RE = re.compile(r"^(\d+)-\d+[a-z]?-")  # trailing [a-z]? matches split-story keys like 2-6a-...
+DATE_FORMAT = "%m-%d-%Y %H:%M"
+# The authoritative action-item vocabulary, mirrored from bmad-sprint-planning's
+# SKILL.md. Anything outside it would render as unknown in the status dashboard.
+ACTION_STATUSES = ("open", "in-progress", "done")
+# The retro-document frontmatter vocabulary. --verdict is only echoed back, but
+# orchestrators branch on the echo, so a free-spelled value ("accepted with open
+# items") would silently fall through every branch they write.
+VERDICTS = ("accepted", "accepted-with-open-items", "rejected")
+
+
+def _load_yaml(path):
+    yaml = YAML(typ="rt")
+    yaml.preserve_quotes = True
+    # Pin the emitter to the indentation the sprint-status template ships with.
+    # Without this, ruamel re-dumps block sequences at its own default offset and
+    # every write silently de-indents pre-existing, untouched action_items.
+    yaml.indent(mapping=2, sequence=4, offset=2)
+    # Pin the dump encoding too: `_dump_bytes` serializes into a BytesIO, so the
+    # emitter -- not this module -- encodes the bytes that land in the user's
+    # file. utf-8 is ruamel's current default, but the file is read back as
+    # utf-8 unconditionally, so state it rather than inherit it.
+    yaml.encoding = "utf-8"
+    with open(path, "r", encoding="utf-8") as fh:
+        data = yaml.load(fh)
+    return yaml, data
+
+
+def _emit(obj, code=0):
+    sys.stdout.write(json.dumps(obj))
+    sys.exit(code)
+
+
+def _emit_error(message, code=1, restored=None):
+    """Emit a failure on the JSON-only contract.
+
+    ``restored`` is included only when the caller can speak to the state of the
+    target file; ``retro-document.md`` teaches callers to read it, so a write-path
+    failure must never omit it and a read-only subcommand must never invent it.
+    """
+    payload = {"ok": False, "error": message}
+    if restored is not None:
+        payload["restored"] = restored
+    _emit(payload, code)
+
+
+class JsonArgumentParser(argparse.ArgumentParser):
+    """Emit argparse failures on the JSON-only stdout contract, not usage text.
+
+    Every parser built from this class is constructed with ``add_help=False``.
+    The override below covers ``error()``, but ``-h`` never reaches it: the
+    built-in help action calls ``print_help()`` and ``exit(0)`` directly, which
+    would put plain usage text on stdout with a zero exit and break the
+    JSON-only contract for the machine consumer this script exists to serve.
+    Removing the action instead of intercepting it keeps the fix to one keyword
+    per parser and routes ``-h`` through the already-tested ``error()`` path as
+    an ordinary unrecognized argument. The cost is that the ``help=`` strings
+    are unreachable from the CLI; the skill's references carry the usage a
+    human needs.
+    """
+
+    def error(self, message):
+        _emit({"ok": False, "error": f"argument error: {message}"}, 2)
+
+
+def _slugify(text, maxlen=40):
+    text = str(text)
+    # Unicode-aware: a non-Latin action must keep its own characters in the id
+    # rather than collapsing to a single placeholder shared by every item.
+    slug = re.sub(r"[^\w]+", "-", text.lower(), flags=re.UNICODE).strip("-")
+    slug = slug[:maxlen].strip("-")
+    if not slug:
+        # Nothing sluggable (punctuation/emoji only): a short content hash keeps
+        # the id deterministic and distinct instead of a bare "item".
+        slug = hashlib.sha256(text.encode("utf-8")).hexdigest()[:8]
+    return slug
+
+
+def _selector_label(entry):
+    """Human-readable form of a --set-action-status selector, for error text.
+
+    An entry carrying both forms is described by its ``id``, because that is the
+    form resolution actually uses.
+    """
+    if isinstance(entry.get("id"), str):
+        return f"id={entry['id']!r}"
+    return f"epic={entry.get('epic')!r} action={entry.get('action')!r}"
+
+
+def _match_action_items(entry, items):
+    """Indices in ``items`` that the selector ``entry`` resolves to.
+
+    ``id`` wins whenever it is present: the epic/action pair is the fallback for
+    legacy items written before ids existed, so a caller that copied a whole item
+    through gets the precise match rather than a text comparison. Matching is
+    exact equality -- no normalization -- so a file that spells its epic as a
+    string simply does not match and the caller gets a "no match" error instead of
+    a silent write to the wrong item. ``bool`` is excluded on the file side too,
+    since ``True == 1`` in Python.
+    """
+    item_id = entry.get("id")
+    if isinstance(item_id, str):
+        return [
+            idx
+            for idx, item in enumerate(items)
+            if isinstance(item, Mapping) and item.get("id") == item_id
+        ]
+    epic_value = entry.get("epic")
+    action_value = entry.get("action")
+    return [
+        idx
+        for idx, item in enumerate(items)
+        if isinstance(item, Mapping)
+        and not isinstance(item.get("epic"), bool)
+        and item.get("epic") == epic_value
+        and item.get("action") == action_value
+    ]
+
+
+def _comment_counts(text):
+    """Multiset of the comment lines in ``text``, indentation included.
+
+    Keyed by the whole line so that a re-indented comment counts as a loss too:
+    the guarantee callers are given is comments *and formatting*, and ruamel
+    re-emits comments at their original column even when the block around them
+    is re-indented, so an exact key costs nothing in practice.
+    """
+    return Counter(
+        line for line in text.splitlines() if line.lstrip().startswith("#")
+    )
+
+
+def _load_document(path, restored=None):
+    """Load and shape-check the document, reporting every failure as JSON.
+
+    Returns ``(yaml, data, dev)``. ``dev`` is the live ``development_status``
+    mapping when the key exists, otherwise a detached empty mapping -- the key is
+    never inserted into the document as a side effect of loading.
+    """
+    try:
+        yaml, data = _load_yaml(path)
+    except UnicodeDecodeError as exc:
+        _emit_error(f"{path} is not valid UTF-8: {exc}", 1, restored)
+    except OSError as exc:
+        _emit_error(str(exc), 1, restored)
+    except Exception as exc:  # noqa: BLE001 - report any parse error as JSON
+        _emit_error(str(exc), 1, restored)
+
+    if data is not None and not isinstance(data, Mapping):
+        _emit_error("root document is not a mapping", 1, restored)
+
+    dev = data.get("development_status") if data is not None else None
+    if dev is None:
+        dev = {}
+    elif not isinstance(dev, Mapping):
+        _emit_error("development_status is not a mapping", 1, restored)
+
+    return yaml, data, dev
+
+
+def _retro_status(dev, retro_key, restored=None):
+    status_value = dev.get(retro_key)
+    if status_value is not None and not isinstance(status_value, str):
+        _emit_error(
+            f"{retro_key} status must be a string or null",
+            1,
+            restored,
+        )
+    return status_value
+
+
+def _dump_bytes(yaml, data):
+    """Serialize the document to bytes before any file is touched, so a dump
+    failure cannot leave a partial file anywhere."""
+    buf = io.BytesIO()
+    yaml.dump(data, buf)
+    return buf.getvalue()
+
+
+def _atomic_write(path, payload, mode=None):
+    """Replace ``path``'s contents with ``payload`` atomically.
+
+    The bytes land in a temp file alongside the target, are fsynced, take the
+    target's permission bits (mkstemp creates 0600, which would silently narrow
+    the file), and only then rename over it -- so a kill or a full disk leaves
+    the original file intact rather than truncated. ``path`` is resolved through
+    symlinks first: renaming onto a symlink would detach the link and leave the
+    real file stale while reporting success. The directory is fsynced too --
+    best-effort, see below -- so the rename survives a power loss and not just
+    the bytes.
+    """
+    path = os.path.realpath(path)
+    directory = os.path.dirname(path) or "."
+    fd, tmp_path = tempfile.mkstemp(
+        prefix=".sprint-status-", suffix=".tmp", dir=directory
+    )
+    try:
+        with os.fdopen(fd, "wb") as fh:
+            fh.write(payload)
+            fh.flush()
+            os.fsync(fh.fileno())
+        if mode is not None:
+            os.chmod(tmp_path, mode)
+        os.replace(tmp_path, path)
+    except BaseException:
+        try:
+            os.unlink(tmp_path)
+        except OSError:
+            pass
+        raise
+    # The directory sync sits outside the try because once os.replace has
+    # returned, the new bytes ARE the file: a failure past that point must not
+    # propagate as a write failure, or the caller would report the original
+    # "restored" about a write that in fact landed. Skipping it only risks the
+    # rename not surviving a hard power loss.
+    try:
+        dir_fd = os.open(directory, os.O_RDONLY)
+        try:
+            os.fsync(dir_fd)
+        finally:
+            os.close(dir_fd)
+    except OSError:
+        pass
+
+
+def cmd_detect_epic(args):
+    # detect-epic never writes, so it reports no "restored" key.
+    _, _, dev = _load_document(args.file)
+
+    done_stories = []
+    max_epic = None
+    # Every story key with its epic, in document order, so the pending list can
+    # be scoped to whichever epic detection lands on without a second pass over
+    # the mapping. Non-story keys (epic-2, epic-2-retrospective, ...) never enter
+    # here, because STORY_RE does not match them.
+    story_keys = []
+    for key, value in dev.items():
+        m = STORY_RE.match(str(key))
+        if not m:
+            continue
+        epic_num = int(m.group(1))
+        story_keys.append((epic_num, key, value))
+        if value == "done":
+            done_stories.append(key)
+            if max_epic is None or epic_num > max_epic:
+                max_epic = epic_num
+
+    # Optional --epic aims the gate at a supplied number (the -H <epic> path)
+    # instead of auto-picking the highest epic with a done story. Without it,
+    # behavior is unchanged: detect, then scope pending_stories to that epic.
+    if args.epic is not None:
+        if args.epic < 1:
+            _emit_error(
+                f"invalid --epic {args.epic} (expected a positive integer)",
+                1,
+            )
+        selected = args.epic
+    else:
+        selected = max_epic
+
+    if selected is None:
+        # Uniform shape: pending_stories is always present, even with no epic to
+        # scope it to, so a caller can read it without branching on epic first.
+        _emit(
+            {
+                "epic": None,
+                "story_count": 0,
+                "done_stories": done_stories,
+                "pending_stories": [],
+                "retro_key": None,
+                "retro_status": None,
+            }
+        )
+
+    # Scoped to the selected epic only -- deliberately unlike done_stories, which
+    # spans the whole file. A pending story in some *other* epic is not this
+    # retrospective's business.
+    selected_keys = [
+        (key, value) for epic_num, key, value in story_keys if epic_num == selected
+    ]
+    pending_stories = [key for key, value in selected_keys if value != "done"]
+
+    retro_key = f"epic-{selected}-retrospective"
+    retro_status = _retro_status(dev, retro_key)
+    _emit(
+        {
+            "epic": selected,
+            # An epic the file has never heard of returns the same empty
+            # pending_stories as a finished one; story_count is the key that
+            # separates "complete" from "nonexistent" (a typo'd --epic), so the
+            # unfinished-story gate can refuse to read silence as done.
+            "story_count": len(selected_keys),
+            "done_stories": done_stories,
+            "pending_stories": pending_stories,
+            "retro_key": retro_key,
+            "retro_status": retro_status,
+        }
+    )
+
+
+def cmd_update(args):
+    # Every failure below happens before the write is attempted, so the file is
+    # untouched and "restored": true is the honest report.
+    untouched = True
+
+    # 0. Validate the inputs before anything is mutated or written.
+    if args.epic < 1:
+        _emit_error(
+            f"invalid --epic {args.epic} (expected a positive integer)", 1, untouched
+        )
+
+    if args.date is not None:
+        try:
+            parsed_date = datetime.strptime(args.date, DATE_FORMAT)
+        except (ValueError, TypeError):
+            _emit_error(
+                f'invalid --date {args.date!r} (expected "MM-DD-YYYY HH:MM")',
+                1,
+                untouched,
+            )
+        # Normalize: strptime also accepts unpadded spellings like
+        # "1-2-2026 9:05", and writing those through would defeat the point of
+        # validating the format at all.
+        last_updated = parsed_date.strftime(DATE_FORMAT)
+    else:
+        last_updated = datetime.now().strftime(DATE_FORMAT)
+
+    if args.verdict is not None and args.verdict not in VERDICTS:
+        _emit_error(
+            f"invalid --verdict {args.verdict!r} (allowed: {', '.join(VERDICTS)})",
+            1,
+            untouched,
+        )
+
+    actions = []
+    if args.add_action:
+        try:
+            actions = json.loads(args.add_action)
+        except json.JSONDecodeError as exc:
+            _emit_error(f"invalid --add-action JSON: {exc}", 1, untouched)
+        if not isinstance(actions, list):
+            _emit_error("--add-action must be a JSON array", 1, untouched)
+        for item in actions:
+            if not isinstance(item, dict):
+                _emit_error(
+                    "each --add-action item must be an object", 1, untouched
+                )
+            action_value = item.get("action")
+            if not isinstance(action_value, str) or not action_value.strip():
+                # A JSON null/number/object would otherwise be str()'d into a
+                # literal "None"/"{...}" and written as a real action item.
+                _emit_error(
+                    "each --add-action item must have a non-empty string action",
+                    1,
+                    untouched,
+                )
+
+    status_updates = []
+    if args.set_action_status:
+        try:
+            status_updates = json.loads(args.set_action_status)
+        except json.JSONDecodeError as exc:
+            _emit_error(f"invalid --set-action-status JSON: {exc}", 1, untouched)
+        if not isinstance(status_updates, list):
+            _emit_error("--set-action-status must be a JSON array", 1, untouched)
+        for entry in status_updates:
+            if not isinstance(entry, dict):
+                _emit_error(
+                    "each --set-action-status entry must be an object", 1, untouched
+                )
+            status_value = entry.get("status")
+            if not isinstance(status_value, str) or status_value not in ACTION_STATUSES:
+                _emit_error(
+                    f"invalid --set-action-status status {status_value!r} "
+                    f"(allowed: {', '.join(ACTION_STATUSES)})",
+                    1,
+                    untouched,
+                )
+            item_id = entry.get("id")
+            if item_id is not None:
+                # Present but unusable is an input error, not a silent fallback to
+                # the epic/action form -- the caller meant to select by id.
+                if not isinstance(item_id, str) or not item_id.strip():
+                    _emit_error(
+                        "each --set-action-status id must be a non-empty string",
+                        1,
+                        untouched,
+                    )
+                continue
+            epic_value = entry.get("epic")
+            action_value = entry.get("action")
+            if isinstance(epic_value, bool) or not isinstance(epic_value, int):
+                _emit_error(
+                    "each --set-action-status entry must have a non-empty string id, "
+                    "or an integer epic and a non-empty string action",
+                    1,
+                    untouched,
+                )
+            if not isinstance(action_value, str) or not action_value.strip():
+                _emit_error(
+                    "each --set-action-status entry must have a non-empty string id, "
+                    "or an integer epic and a non-empty string action",
+                    1,
+                    untouched,
+                )
+
+    # 1. Keep original bytes for restore-on-failure, and the mode to write back
+    #    with -- taken from the open handle so an unlink mid-run cannot leave the
+    #    replacement silently narrowed to mkstemp's 0600.
+    try:
+        with open(args.file, "rb") as fh:
+            original_bytes = fh.read()
+            original_mode = stat.S_IMODE(os.fstat(fh.fileno()).st_mode)
+    except OSError as exc:
+        _emit_error(str(exc), 1, untouched)
+
+    try:
+        original_text = original_bytes.decode("utf-8")
+    except UnicodeDecodeError as exc:
+        _emit_error(f"{args.file} is not valid UTF-8: {exc}", 1, untouched)
+
+    # Every comment line in the file, not just the leading block: the template
+    # ships one above action_items, and losing it corrupts the document just the
+    # same as losing the header.
+    original_comments = _comment_counts(original_text)
+
+    yaml, data, dev = _load_document(args.file, restored=untouched)
+
+    if data is None:
+        _emit_error("empty or invalid YAML document", 1, untouched)
+
+    epic = args.epic
+    retro_key = f"epic-{epic}-retrospective"
+
+    # null distinguishes "the flag was not passed" from "the key was absent",
+    # which is the only case retro-document.md assigns "false" to.
+    retro_key_found = None
+    retro_status_before = None
+    retro_status_after = None
+
+    # 2. Optionally set the retrospective status to done (only if key exists).
+    if args.set_retro_done:
+        retro_key_found = retro_key in dev
+        if retro_key_found:
+            retro_status_before = _retro_status(dev, retro_key, restored=untouched)
+            dev[retro_key] = "done"
+            retro_status_after = "done"
+
+    # 3. Take the action_items sequence as loaded and shape-check it once; both
+    #    of the steps below operate on this same list.
+    existing_actions = data.get("action_items")
+    if existing_actions is not None and not isinstance(existing_actions, list):
+        # A hand-corrupted file must still fail on the JSON contract, not crash.
+        _emit_error("action_items in file is not a list", 1, untouched)
+    items_added = 0
+    original_action_len = len(existing_actions) if existing_actions is not None else 0
+
+    # 4. Optionally transition the status of items already in the file. Selectors
+    #    resolve against action_items *as loaded* and strictly before the
+    #    --add-action append below, which is what makes an item appended in the
+    #    same invocation unaddressable in that run. Every selector is resolved
+    #    before any is applied, so a rejected batch never leaves a partial edit --
+    #    and since nothing has been written yet, the file is still untouched.
+    status_targets = []
+    if status_updates:
+        pool = existing_actions if isinstance(existing_actions, list) else []
+        claimed = {}
+        for entry in status_updates:
+            label = _selector_label(entry)
+            matches = _match_action_items(entry, pool)
+            if not matches:
+                _emit_error(f"no action item matches {label}", 1, untouched)
+            if len(matches) > 1:
+                _emit_error(
+                    f"ambiguous --set-action-status selector {label}: "
+                    f"{len(matches)} matches",
+                    1,
+                    untouched,
+                )
+            idx = matches[0]
+            if idx in claimed:
+                # Applying both would overcount action_items_updated, and a
+                # conflicting pair would surface as a confusing post-write
+                # validation failure instead of the input error it is.
+                _emit_error(
+                    f"duplicate --set-action-status targets: {label} and "
+                    f"{claimed[idx]} resolve to the same action item",
+                    1,
+                    untouched,
+                )
+            claimed[idx] = label
+            status_targets.append((idx, entry["status"]))
+
+        for idx, new_status in status_targets:
+            # A plain assignment keeps the item's own scalar style: ruamel's
+            # CommentedMap re-applies the existing key's style on overwrite, for
+            # every ScalarString subclass. Pinned by the style tests.
+            pool[idx]["status"] = new_status
+
+    # 5. Optionally append action items.
+    if actions:
+        seq = data.get("action_items")
+        if seq is None:
+            seq = []
+            data["action_items"] = seq
+
+        for item in actions:
+            # Stable identity for orchestrator consumers: an id that lets a
+            # re-run dedupe against prior items, and a ref back to the sourced
+            # finding in the retro document. Both accept an explicit override.
+            seq_num = len(seq) + 1
+            action_text = str(item.get("action", ""))
+            item_id = item.get("id") or (
+                f"epic-{int(epic)}-retro-item-{seq_num}-{_slugify(action_text)}"
+            )
+            ref = item.get("ref") or (args.ref or "")
+            entry = {
+                "id": DoubleQuotedScalarString(str(item_id)),
+                "epic": int(epic),
+                "action": DoubleQuotedScalarString(action_text),
+                "owner": DoubleQuotedScalarString(str(item.get("owner", ""))),
+                "status": "open",
+                "ref": DoubleQuotedScalarString(str(ref)),
+            }
+            seq.append(entry)
+            items_added += 1
+
+    # 6. Update last_updated.
+    data["last_updated"] = last_updated
+
+    # 7. Serialize, then swap the file atomically.
+    try:
+        _atomic_write(args.file, _dump_bytes(yaml, data), original_mode)
+    except Exception as exc:  # noqa: BLE001
+        # The target is only ever touched by the final rename, so if the write
+        # raised, the original is still on disk byte-for-byte. Calling _restore
+        # here would rewrite a file that was never modified -- the one write in
+        # the program with nothing to gain and a truncated file to lose.
+        _emit({"ok": False, "error": f"write failed: {exc}", "restored": True}, 1)
+
+    # 8. Validate the written file; restore on any failure.
+    def _fail(msg):
+        restored = _restore(args.file, original_bytes, original_mode)
+        _emit({"ok": False, "error": msg, "restored": restored}, 1)
+
+    try:
+        _, reloaded = _load_yaml(args.file)
+    except Exception as exc:  # noqa: BLE001
+        _fail(f"re-parse failed after write: {exc}")
+
+    if reloaded is None:
+        _fail("re-parse produced empty document after write")
+
+    if not isinstance(reloaded, Mapping):
+        _fail("re-parse produced a non-mapping document after write")
+
+    rdev = reloaded.get("development_status") or {}
+    if args.set_retro_done and retro_key_found:
+        if not isinstance(rdev, Mapping) or rdev.get(retro_key) != "done":
+            _fail(f"validation: {retro_key} not set to done after write")
+
+    new_action_len = 0
+    if reloaded.get("action_items") is not None:
+        new_action_len = len(reloaded.get("action_items"))
+    if new_action_len != original_action_len + items_added:
+        _fail(
+            "validation: action_items length mismatch "
+            f"(expected {original_action_len + items_added}, got {new_action_len})"
+        )
+
+    if status_targets:
+        # The recorded indices are still valid: the only other mutation to the
+        # sequence is an append, and the length check above just confirmed it.
+        reloaded_actions = reloaded.get("action_items")
+        if not isinstance(reloaded_actions, list):
+            _fail("validation: action_items is not a list after write")
+        for idx, new_status in status_targets:
+            reloaded_item = reloaded_actions[idx]
+            if (
+                not isinstance(reloaded_item, Mapping)
+                or reloaded_item.get("status") != new_status
+            ):
+                _fail(
+                    f"validation: action item at index {idx} is not "
+                    f"{new_status!r} after write"
+                )
+
+    try:
+        with open(args.file, "r", encoding="utf-8") as fh:
+            new_text = fh.read()
+    except (OSError, UnicodeDecodeError) as exc:
+        _fail(f"re-read failed after write: {exc}")
+
+    # Loss-only: a comment may legitimately move or be added (a long quoted value
+    # can wrap onto a line that begins with '#'), but none may disappear.
+    lost = original_comments - _comment_counts(new_text)
+    if lost:
+        first = next(
+            (line for line in original_text.splitlines() if line in lost), None
+        )
+        _fail(f"validation: comment line lost after write: {first!r}")
+
+    _emit(
+        {
+            "ok": True,
+            "retro_key_found": retro_key_found,
+            "retro_status_before": retro_status_before,
+            "retro_status_after": retro_status_after,
+            "action_items_added": items_added,
+            "action_items_updated": len(status_targets),
+            "last_updated": last_updated,
+            "verdict": args.verdict,
+        }
+    )
+
+
+def _restore(path, original_bytes, mode=None):
+    """Best-effort restore of the original bytes. Returns True on success so a
+    caller can surface a restore failure instead of hiding a half-written file.
+
+    Atomic for the same reason the primary write is: a truncating rewrite that
+    dies halfway destroys the very bytes it was trying to put back.
+    """
+    try:
+        _atomic_write(path, original_bytes, mode)
+        return True
+    except Exception as exc:  # noqa: BLE001 - best-effort restore
+        sys.stderr.write(f"restore failed: {exc}\n")
+        return False
+
+
+def build_parser():
+    parser = JsonArgumentParser(
+        description=(
+            "Detect the current retrospective epic and surgically update "
+            "sprint-status.yaml while preserving comments and formatting."
+        ),
+        add_help=False,
+    )
+    sub = parser.add_subparsers(dest="command", required=True)
+
+    p_detect = sub.add_parser(
+        "detect-epic",
+        help=(
+            "Find the highest epic with a done story and its retrospective "
+            "status, or aim the same pending_stories gate at --epic N."
+        ),
+        add_help=False,
+    )
+    p_detect.add_argument("--file", required=True, help="Path to sprint-status.yaml")
+    p_detect.add_argument(
+        "--epic",
+        type=int,
+        default=None,
+        help=(
+            "Optional. Scope the response to this epic number instead of "
+            "auto-detecting the highest epic with a done story. Orchestrators "
+            "passing -H <epic> should pass the same number here so pending_stories "
+            "covers the epic they are about to retro."
+        ),
+    )
+    p_detect.set_defaults(func=cmd_detect_epic)
+
+    p_update = sub.add_parser(
+        "update",
+        help="Surgically update retro status and/or action items.",
+        add_help=False,
+    )
+    p_update.add_argument("--file", required=True, help="Path to sprint-status.yaml")
+    p_update.add_argument("--epic", required=True, type=int, help="Epic number")
+    p_update.add_argument(
+        "--set-retro-done",
+        action="store_true",
+        help="Set epic-<N>-retrospective to done if the key exists.",
+    )
+    p_update.add_argument(
+        "--add-action",
+        help='JSON array of {"action":str,"owner":str,"id"?:str,"ref"?:str} to append.',
+    )
+    p_update.add_argument(
+        "--set-action-status",
+        help=(
+            "JSON array of status transitions for action items already in the file. "
+            'Select each by id -- {"id":str,"status":"open|in-progress|done"} -- or, '
+            'for legacy items with no id, by epic plus exact action text: '
+            '{"epic":int,"action":str,"status":...}. An entry carrying both uses the '
+            "id. Every selector must match exactly one item; any failure aborts the "
+            "whole invocation and leaves the file untouched."
+        ),
+    )
+    p_update.add_argument(
+        "--ref",
+        help="Reference (e.g. the retro document path) recorded on each appended action item.",
+    )
+    p_update.add_argument(
+        "--verdict",
+        help=(
+            "Acceptance verdict echoed back in the JSON result for orchestrator "
+            f"consumers. One of: {', '.join(VERDICTS)}."
+        ),
+    )
+    p_update.add_argument(
+        "--date",
+        help='Value for last_updated (default: now as "MM-DD-YYYY HH:MM").',
+    )
+    p_update.set_defaults(func=cmd_update)
+
+    return parser
+
+
+def main(argv=None):
+    parser = build_parser()
+    args = parser.parse_args(argv)
+    args.func(args)
+
+
+if __name__ == "__main__":
+    main()
diff --git a/.claude/skills/bmad-retrospective/scripts/tests/__pycache__/test_git_evidence.cpython-311-pytest-9.1.1.pyc b/.claude/skills/bmad-retrospective/scripts/tests/__pycache__/test_git_evidence.cpython-311-pytest-9.1.1.pyc
new file mode 100644
index 0000000..d3f2fca
Binary files /dev/null and b/.claude/skills/bmad-retrospective/scripts/tests/__pycache__/test_git_evidence.cpython-311-pytest-9.1.1.pyc differ
diff --git a/.claude/skills/bmad-retrospective/scripts/tests/__pycache__/test_sprint_status.cpython-311-pytest-9.1.1.pyc b/.claude/skills/bmad-retrospective/scripts/tests/__pycache__/test_sprint_status.cpython-311-pytest-9.1.1.pyc
new file mode 100644
index 0000000..bc495d8
Binary files /dev/null and b/.claude/skills/bmad-retrospective/scripts/tests/__pycache__/test_sprint_status.cpython-311-pytest-9.1.1.pyc differ
diff --git a/.claude/skills/bmad-retrospective/scripts/tests/fixtures/sprint-status-template.yaml b/.claude/skills/bmad-retrospective/scripts/tests/fixtures/sprint-status-template.yaml
new file mode 100644
index 0000000..cc4dd7c
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/scripts/tests/fixtures/sprint-status-template.yaml
@@ -0,0 +1,71 @@
+# Sprint Status Template
+# This is an EXAMPLE showing the expected format
+# The actual file will be generated with all epics/stories from your epic files
+
+# generated: {date}
+# project: {project_name}
+# project_key: {project_key}
+# tracking_system: {tracking_system}
+# story_location: {story_location}
+
+# STATUS DEFINITIONS:
+# ==================
+# Epic Status:
+#   - backlog: Epic not yet started
+#   - in-progress: Epic actively being worked on
+#   - done: All stories in epic completed
+#
+# Story Status:
+#   - backlog: Story only exists in epic file
+#   - ready-for-dev: Story file created, ready for development
+#   - in-progress: Developer actively working on implementation
+#   - review: Implementation complete, ready for review
+#   - done: Story completed
+#
+# Retrospective Status:
+#   - optional: Can be completed but not required
+#   - done: Retrospective has been completed
+#
+# Action Item Status:
+#   - open: Committed during a retrospective, not yet addressed
+#   - in-progress: Actively being worked on
+#   - done: Completed
+#
+# WORKFLOW NOTES:
+# ===============
+# - Epic transitions to 'in-progress' automatically when its first story starts (via build's sprint sync)
+# - Stories can be worked in parallel if team capacity allows
+# - Developer typically creates the next story after the previous one is 'done' to incorporate learnings
+# - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)
+# - Retrospective appends its action items to action_items; the status view surfaces open ones
+
+# EXAMPLE STRUCTURE (your actual epics/stories will replace these):
+# Timestamps use MM-DD-YYYY HH:MM.
+
+generated: 05-06-2025 21:30
+last_updated: 05-06-2025 21:30
+project: My Awesome Project
+project_key: NOKEY
+tracking_system: file-system
+story_location: "docs/stories"
+
+development_status:
+  epic-1: backlog
+  1-1-user-authentication: done
+  1-2-account-management: ready-for-dev
+  1-3-plant-data-model: backlog
+  1-4-add-plant-manual: backlog
+  epic-1-retrospective: optional
+
+  epic-2: backlog
+  2-1-personality-system: backlog
+  2-2-chat-interface: backlog
+  2-3-llm-integration: backlog
+  epic-2-retrospective: optional
+
+# Action items committed during retrospectives (section created by the retrospective workflow)
+action_items:
+  - epic: 1
+    action: "Add error-handling review to the code review checklist"
+    owner: "Charlie"
+    status: open
diff --git a/.claude/skills/bmad-retrospective/scripts/tests/test_git_evidence.py b/.claude/skills/bmad-retrospective/scripts/tests/test_git_evidence.py
new file mode 100644
index 0000000..32c4b5f
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/scripts/tests/test_git_evidence.py
@@ -0,0 +1,750 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0"]
+# ///
+"""Tests for git_evidence.py — measurement over a real temp git repo.
+
+Run: uv run scripts/tests/test_git_evidence.py
+ or: uv run --with pytest -m pytest scripts/tests/test_git_evidence.py
+"""
+
+import json
+import os
+import shutil
+import subprocess
+import sys
+import unicodedata
+from pathlib import Path
+
+import pytest
+
+SCRIPT = Path(__file__).resolve().parents[1] / "git_evidence.py"
+
+# The fixture commit identity, shared by both git helpers below.
+_IDENT = {
+    "GIT_AUTHOR_NAME": "T",
+    "GIT_AUTHOR_EMAIL": "t@t",
+    "GIT_COMMITTER_NAME": "T",
+    "GIT_COMMITTER_EMAIL": "t@t",
+}
+
+
+def _git_env(repo):
+    """The environment every fixture git runs under, layered outward.
+
+    Inherit the real environment (PATH above all: git lives in /opt/homebrew,
+    /usr/local, or a nix store as readily as /usr/bin, and an env holding only
+    GIT_* vars sends execvp to os.defpath), then strip every ambient GIT_* var
+    -- GIT_DIR, GIT_WORK_TREE and GIT_CONFIG_COUNT would each silently redirect
+    or reconfigure the fixture -- and pin identity plus every source git reads
+    for settings, so nothing on the developer's machine can reach the fixture:
+
+    - gitconfig (commit.gpgsign, core.autocrlf, core.hooksPath,
+      init.defaultBranch). GIT_CONFIG_NOSYSTEM/GIT_CONFIG_GLOBAL cover
+      git >= 2.32; HOME and XDG_CONFIG_HOME cover older git, and are set to the
+      repo's parent directory -- always a per-test directory under pytest's
+      tmp_path -- so nothing is ever planted inside the working tree.
+    - gitattributes, a separate source GIT_CONFIG_NOSYSTEM does not cover: a
+      system `* -diff` rule would make numstat call every path binary and take
+      the churn assertions down with it. GIT_ATTR_NOSYSTEM shuts it out.
+    - the locale. LC_ALL/LANG are pinned to C, matching _run/_proc's existing
+      pin, so fixture git's text output cannot vary with the developer's
+      locale. Inheriting the environment is what makes this pin necessary:
+      the old four-variable env had no locale in it to inherit.
+    """
+    env = {k: v for k, v in os.environ.items() if not k.startswith("GIT_")}
+    env.update(_IDENT)
+    env["GIT_CONFIG_NOSYSTEM"] = "1"
+    env["GIT_ATTR_NOSYSTEM"] = "1"
+    env["GIT_CONFIG_GLOBAL"] = os.devnull
+    env["HOME"] = env["XDG_CONFIG_HOME"] = str(Path(repo).parent)
+    env["LC_ALL"] = env["LANG"] = "C"
+    return env
+
+
+def _json(proc):
+    """Parse the JSON-only stdout contract, surfacing a crash instead of hiding
+    it behind a JSONDecodeError."""
+    assert proc.stdout, f"empty stdout; stderr was: {proc.stderr}"
+    assert "Traceback" not in proc.stderr, proc.stderr
+    return json.loads(proc.stdout)
+
+
+def _run(*args):
+    # LC_ALL=C keeps git's error strings in English so assertions on them
+    # are stable across locales.
+    proc = subprocess.run(
+        ["uv", "run", str(SCRIPT), *args],
+        capture_output=True,
+        text=True,
+        env={**os.environ, "LC_ALL": "C", "LANG": "C"},
+    )
+    return proc.returncode, _json(proc)
+
+
+def _proc(*args, env=None):
+    """Run the script and return the raw process, so a test can assert on the
+    exit code and stderr together — and so `env` can carry an overlay (a fake
+    `git` earlier on PATH) that `_run` has no way to pass."""
+    overlay = {"LC_ALL": "C", "LANG": "C"}
+    if env:
+        overlay.update(env)
+    return subprocess.run(
+        ["uv", "run", str(SCRIPT), *args],
+        capture_output=True,
+        text=True,
+        env={**os.environ, **overlay},
+    )
+
+
+def _git(repo, *args):
+    subprocess.run(
+        ["git", "-C", str(repo), *args],
+        check=True,
+        capture_output=True,
+        env=_git_env(repo),
+    )
+
+
+def _git_unchecked(repo, *args):
+    """`git` that tolerates a non-zero exit — the conflicting merge in
+    `_merge_repo` is supposed to fail, and the hand resolution comes after it.
+    Same environment as `_git`, which runs with check=True."""
+    return subprocess.run(
+        ["git", "-C", str(repo), *args],
+        capture_output=True,
+        text=True,
+        env=_git_env(repo),
+    )
+
+
+def _make_repo(tmp_path):
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q")
+    (repo / "a.py").write_text("one\ntwo\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "epic-1-1 initial a")
+    (repo / "a.py").write_text("one\ntwo\nthree\nfour\n")
+    (repo / "b.py").write_text("x\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "epic-1-2 grow a, add b")
+    return repo
+
+
+def test_no_range_returns_empty(tmp_path):
+    repo = _make_repo(tmp_path)
+    code, out = _run("--repo", str(repo))
+    assert code == 0
+    assert out["range"] is None
+    assert out["commits"] == [] and out["files"] == []
+
+
+def test_measures_commits_and_files_with_attribution(tmp_path):
+    repo = _make_repo(tmp_path)
+    code, out = _run(
+        "--repo", str(repo), "--range", "HEAD~1..HEAD", "--stories", "1-2,1-1"
+    )
+    assert code == 0
+    assert out["range"] == "HEAD~1..HEAD"
+    assert out["commit_count"] == 1
+    # The single commit in range is the second one; attributed to story "1-2".
+    assert out["commits"][0]["stories"] == ["1-2"]
+    files = {f["path"]: f for f in out["files"]}
+    # a.py grew by two lines, b.py added one — measured, not judged.
+    assert files["a.py"]["added"] == 2 and files["a.py"]["net"] == 2
+    assert files["b.py"]["added"] == 1
+
+
+def test_story_attribution_respects_word_boundary(tmp_path):
+    # Story id "1-2" must NOT match a commit subject mentioning "11-2".
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q")
+    (repo / "f.py").write_text("a\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    (repo / "f.py").write_text("a\nb\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "epic-11-2 unrelated story")
+    code, out = _run("--repo", str(repo), "--range", "HEAD~1..HEAD", "--stories", "1-2")
+    assert code == 0
+    assert out["commits"][0]["stories"] == []
+
+
+def test_bad_range_errors_as_json(tmp_path):
+    repo = _make_repo(tmp_path)
+    code, out = _run("--repo", str(repo), "--range", "nope..alsonope")
+    assert code == 1
+    assert out["ok"] is False and out["error"]
+
+
+def test_single_rev_range_rejected(tmp_path):
+    # A single rev is not a range: git would log ALL history up to it and the
+    # script would report the whole repo as the epic's evidence.
+    repo = _make_repo(tmp_path)
+    code, out = _run("--repo", str(repo), "--range", "HEAD")
+    assert code == 2
+    assert out["ok"] is False and "invalid --range" in out["error"]
+
+
+def test_pathspec_range_rejected(tmp_path):
+    # A path that exists must not be silently consumed as a pathspec.
+    repo = _make_repo(tmp_path)
+    code, out = _run("--repo", str(repo), "--range", "a.py")
+    assert code == 2
+    assert out["ok"] is False and "invalid --range" in out["error"]
+
+
+def test_range_shaped_pathspec_forced_to_rev_parse(tmp_path):
+    # A committed file literally named "a..b" passes the REV..REV shape check;
+    # without the trailing "--" in the git argv, git silently logs that FILE's
+    # history with exit 0. The "--" forces rev interpretation, so this must
+    # error instead of measuring the decoy.
+    repo = _make_repo(tmp_path)
+    (repo / "a..b").write_text("decoy\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "add decoy file named like a range")
+    code, out = _run("--repo", str(repo), "--range", "a..b")
+    assert code == 1
+    assert out["ok"] is False and "bad revision" in out["error"]
+
+
+def test_option_like_range_rejected(tmp_path):
+    # A range starting with "-" must never reach git, where it would be
+    # consumed as an option (e.g. --output=... writes an arbitrary file).
+    repo = _make_repo(tmp_path)
+    code, out = _run("--repo", str(repo), "--range=--output=evil.txt")
+    assert code == 2
+    assert out["ok"] is False and "invalid --range" in out["error"]
+    assert not (repo / "evil.txt").exists()
+
+
+def test_degenerate_range_shapes_rejected(tmp_path):
+    # Shapes that contain ".." but are not REV..REV: git would silently
+    # default an empty endpoint to HEAD ("..", "a..", "..HEAD"), a leading
+    # dash must never reach git even when dots are present ("-3..HEAD"),
+    # unstripped values must not slip past the dash guard, and a three-dot
+    # range is a symmetric difference — git would measure commits reachable
+    # from either endpoint but not both, a different evidence set entirely.
+    repo = _make_repo(tmp_path)
+    for bad in (
+        "..",
+        "a..",
+        "..HEAD",
+        "-3..HEAD",
+        " HEAD~1..HEAD",
+        "HEAD~1...HEAD",
+        "a...b",
+    ):
+        code, out = _run("--repo", str(repo), f"--range={bad}")
+        assert code == 2, f"accepted {bad!r}"
+        assert out["ok"] is False and "invalid --range" in out["error"], bad
+
+
+def test_malformed_args_emit_json_not_usage(tmp_path):
+    # An unknown flag must still land on the JSON contract, not argparse's
+    # plain usage text on stderr.
+    code, out = _run("--bogus-flag")
+    assert code != 0
+    assert out["ok"] is False and out["error"]
+
+
+def test_help_flags_emit_json_not_usage():
+    # argparse's built-in help action bypasses the error() override entirely --
+    # it prints usage text on stdout and exits 0, which breaks the JSON-only
+    # contract for a machine consumer. add_help=False demotes -h to an ordinary
+    # unrecognized argument, which error() already handles.
+    for flag in ("-h", "--help"):
+        proc = _proc(flag)
+        # Exit 2 specifically: the module docstring reserves 2 for argument
+        # errors and 1 for git/I-O failures, so collapsing them must fail here.
+        assert proc.returncode == 2, flag
+        assert "usage:" not in proc.stdout, flag
+        out = _json(proc)
+        assert out["ok"] is False and out["error"], flag
+
+
+# --- helpers for the fixtures below -----------------------------------------
+
+
+def _rev(repo, ref):
+    return _git_unchecked(repo, "rev-parse", ref).stdout.strip()
+
+
+def _fake_git(tmp_path, body):
+    """Write a `git` shim and return the PATH overlay that puts it ahead of the
+    real binary for the script's own subprocesses (never for the fixtures,
+    which build their repos through `_git`'s own environment)."""
+    bindir = tmp_path / "fakebin"
+    bindir.mkdir()
+    shim = bindir / "git"
+    shim.write_text(body)
+    os.chmod(shim, 0o755)
+    return {"PATH": f"{bindir}{os.pathsep}{os.environ['PATH']}"}
+
+
+def _merge_repo(tmp_path):
+    """Two story branches merged into the mainline; the second merge conflicts
+    and is resolved by hand, adding a line neither branch had. Returns
+    (repo, base_sha) — `base_sha..HEAD` is the epic range."""
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "s.py").write_text("l1\nl2\nl3\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    base = _rev(repo, "HEAD")
+
+    _git(repo, "checkout", "-q", "-b", "s1")
+    (repo / "s.py").write_text("l1\nA\nl3\n")
+    _git(repo, "commit", "-qam", "epic-1-2 story one")
+    _git(repo, "checkout", "-q", "main")
+    _git(repo, "merge", "-q", "--no-ff", "s1", "-m", "merge story 1-2")
+
+    _git(repo, "checkout", "-q", "-b", "s2", base)
+    (repo / "s.py").write_text("l1\nB\nl3\n")
+    _git(repo, "commit", "-qam", "epic-1-3 story two")
+    _git(repo, "checkout", "-q", "main")
+    conflicted = _git_unchecked(repo, "merge", "--no-ff", "s2", "-m", "merge story 1-3")
+    assert conflicted.returncode != 0, "fixture expected a merge conflict"
+    (repo / "s.py").write_text("l1\nAB\nl3\nl4\n")  # hand resolution
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "merge story 1-3")
+    return repo, base
+
+
+def test_rename_yields_two_openable_paths(tmp_path):
+    # git's default rename detection emits "src/{mod.py => renamed.py}" — an
+    # unopenable pseudo-path that also splits one file's churn across keys.
+    # --no-renames makes the rename an honest delete + add.
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "src").mkdir()
+    (repo / "src" / "mod.py").write_text("l1\nl2\nl3\nl4\nl5\nl6\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    base = _rev(repo, "HEAD")
+    _git(repo, "mv", "src/mod.py", "src/renamed.py")
+    _git(repo, "commit", "-qm", "rename mod")
+    (repo / "src" / "renamed.py").write_text("l1\nl2\nl3\nl4\nl5\nl6\nl7\n")
+    _git(repo, "commit", "-qam", "add a line after the rename")
+
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    files = {f["path"]: f for f in out["files"]}
+    assert not any("=>" in path for path in files), sorted(files)
+    assert files["src/mod.py"]["added"] == 0
+    assert files["src/mod.py"]["deleted"] == 6
+    assert files["src/renamed.py"]["added"] == 7
+    assert files["src/renamed.py"]["deleted"] == 0
+
+
+def _accented_repo(tmp_path):
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "src").mkdir()
+    (repo / "src" / "café.py").write_text("ca\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    base = _rev(repo, "HEAD")
+    (repo / "src" / "café.py").write_text("ca\ncb\n")
+    _git(repo, "commit", "-qam", "touch the accented file")
+    return repo, base
+
+
+def _assert_accented_path(repo, out):
+    paths = [f["path"] for f in out["files"]]
+    assert len(paths) == 1
+    assert "\\" not in paths[0] and '"' not in paths[0], paths
+    assert unicodedata.normalize("NFC", paths[0]) == "src/café.py"
+    # The reported path is a real path: it opens under --repo.
+    assert (repo / paths[0]).read_text() == "ca\ncb\n"
+
+
+def test_non_ascii_path_is_a_real_string(tmp_path):
+    # Without core.quotePath=false git emits "src/caf\303\251.py" — quoted and
+    # octal-escaped, so the documented "open the ranked files" step cannot.
+    repo, base = _accented_repo(tmp_path)
+    _assert_accented_path(
+        repo, _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    )
+
+
+def test_non_ascii_path_survives_a_non_utf8_locale(tmp_path):
+    # Pins the explicit encoding="utf-8" on the subprocess. Modern CPython's
+    # UTF-8 mode hides its absence even under LC_ALL=C, so the pin only bites
+    # with UTF-8 mode and C-locale coercion both off — where the interpreter
+    # default is US-ASCII and git's UTF-8 path bytes fail to decode, taking the
+    # whole measurement down with them.
+    repo, base = _accented_repo(tmp_path)
+    out = _json(
+        _proc(
+            "--repo",
+            str(repo),
+            "--range",
+            f"{base}..HEAD",
+            env={"PYTHONUTF8": "0", "PYTHONCOERCECLOCALE": "0"},
+        )
+    )
+    _assert_accented_path(repo, out)
+
+
+def test_merge_churn_is_measured_and_counted(tmp_path):
+    repo, base = _merge_repo(tmp_path)
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    assert out["commit_count"] == 4
+    assert out["merge_count"] == 2
+    assert out["merges_measured"] == 2
+    # Both merges' first-parent churn: 1/1 for the clean merge, 2/1 for the
+    # hand-resolved one (the resolution added a line neither branch had).
+    merge_files = {f["path"]: f for f in out["merge_files"]}
+    assert merge_files["s.py"]["added"] == 3
+    assert merge_files["s.py"]["deleted"] == 2
+    assert merge_files["s.py"]["net"] == 1
+    assert merge_files["s.py"]["commit_count"] == 2
+
+
+def test_merge_commits_listed_but_excluded_from_files(tmp_path):
+    repo, base = _merge_repo(tmp_path)
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    by_subject = {c["subject"]: c for c in out["commits"]}
+    assert by_subject["merge story 1-2"]["is_merge"] is True
+    assert by_subject["merge story 1-3"]["is_merge"] is True
+    assert by_subject["epic-1-2 story one"]["is_merge"] is False
+    # `files` is the two story commits only — 1/1 each. Folding the merges in
+    # would double count: their diff restates the churn they merged.
+    files = {f["path"]: f for f in out["files"]}
+    assert files["s.py"]["added"] == 2
+    assert files["s.py"]["deleted"] == 2
+    assert files["s.py"]["commit_count"] == 2
+
+
+def test_story_attribution_survives_merges(tmp_path):
+    repo, base = _merge_repo(tmp_path)
+    out = _json(
+        _proc(
+            "--repo", str(repo), "--range", f"{base}..HEAD", "--stories", "1-2,1-3"
+        )
+    )
+    by_subject = {c["subject"]: c for c in out["commits"]}
+    assert by_subject["epic-1-2 story one"]["stories"] == ["1-2"]
+    assert by_subject["epic-1-3 story two"]["stories"] == ["1-3"]
+
+
+def test_off_spine_merge_is_counted_but_not_measured(tmp_path):
+    # A back-merge of the mainline into a story branch is a merge in the range,
+    # but its first-parent diff would restate unrelated mainline content as
+    # epic churn. It stays in merge_count and out of merges_measured, so the
+    # gap between the two says plainly that a merge went unmeasured.
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "f.txt").write_text("base\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    base = _rev(repo, "HEAD")
+    (repo / "f.txt").write_text("base\nmain1\n")
+    _git(repo, "commit", "-qam", "mainline work")
+
+    _git(repo, "checkout", "-q", "-b", "s1", base)
+    (repo / "s1.txt").write_text("s1\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "epic-1-2 story one")
+    _git(repo, "merge", "-q", "--no-ff", "main", "-m", "back-merge main into s1")
+    _git(repo, "checkout", "-q", "main")
+    _git(repo, "merge", "-q", "--no-ff", "s1", "-m", "merge story 1-2")
+
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    assert out["merge_count"] == 2
+    assert out["merges_measured"] == 1
+    merge_files = {f["path"]: f for f in out["merge_files"]}
+    assert set(merge_files) == {"s1.txt"}
+
+
+def test_merge_pass_survives_a_hostile_log_diffmerges_config(tmp_path):
+    # `-m` means "whatever log.diffMerges says", so a user or repo config of
+    # `off` makes the merge pass emit no file rows: merge_files comes back
+    # empty beside a non-zero merges_measured and reads as "the merges changed
+    # nothing". The command-line -c pin beats the config.
+    repo, base = _merge_repo(tmp_path)
+    _git(repo, "config", "log.diffMerges", "off")
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    assert out["merges_measured"] == 2
+    merge_files = {f["path"]: f for f in out["merge_files"]}
+    assert merge_files["s.py"]["added"] == 3
+    assert merge_files["s.py"]["deleted"] == 2
+
+
+def test_distinct_non_utf8_paths_stay_distinct(tmp_path):
+    # errors="replace" maps every invalid byte to the same U+FFFD, collapsing
+    # two different files into one `files` key with their churn summed —
+    # measurement corruption with nothing in the output admitting to it.
+    overlay = _fake_git(
+        tmp_path,
+        "#!/bin/sh\n"
+        "printf 'aaaa\\037\\037subj\\n\\n1\\t0\\tsrc/caf\\351.py\\n"
+        "2\\t0\\tsrc/caf\\377.py\\n'\n",
+    )
+    out = _json(_proc("--repo", str(tmp_path), "--range", "a..b", env=overlay))
+    files = {f["path"]: f for f in out["files"]}
+    assert len(files) == 2, files
+    assert sorted(f["added"] for f in files.values()) == [1, 2]
+
+
+def test_repeated_merge_headers_are_counted_once(tmp_path):
+    # Pins the dedupe guard in _parse_log. git before 2.31 does not honour
+    # --first-parent for `-m`'s diff format, so a merge's header repeats once
+    # per parent with a diff block under each. Without the guard that doubles
+    # the merge churn and pushes merges_measured above merge_count, inverting
+    # the invariant the reference documents. Inert on modern git, so it needs
+    # pre-2.31-shaped output to be exercised at all.
+    real_git = shutil.which("git")
+    assert real_git, "git must be on PATH"
+    repo, base = _merge_repo(tmp_path)
+    overlay = _fake_git(
+        tmp_path,
+        "#!/bin/sh\n"
+        'for a in "$@"; do\n'
+        '  if [ "$a" = "--min-parents=2" ]; then\n'
+        "    printf 'aaaa\\037p1 p2\\037merge story 1-3\\n\\n2\\t1\\ts.py\\n"
+        "aaaa\\037p1 p2\\037merge story 1-3\\n\\n5\\t4\\ts.py\\n'\n"
+        "    exit 0\n"
+        "  fi\n"
+        "done\n"
+        f'exec "{real_git}" "$@"\n',
+    )
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD", env=overlay))
+    # One merge sha, however many blocks git printed for it.
+    assert out["merges_measured"] == 1
+    assert out["merges_measured"] <= out["merge_count"]
+    merge_files = {f["path"]: f for f in out["merge_files"]}
+    # The first block is the first-parent diff on every git version; the
+    # repeat must not be added on top of it.
+    assert merge_files["s.py"]["added"] == 2
+    assert merge_files["s.py"]["deleted"] == 1
+    assert merge_files["s.py"]["commit_count"] == 1
+
+
+def test_valid_range_with_no_commits_keeps_the_full_shape(tmp_path):
+    # A mis-specified epic range is a valid, empty range. It must still answer
+    # with every documented key rather than a differently-shaped stub.
+    repo = _make_repo(tmp_path)
+    proc = _proc("--repo", str(repo), "--range", "HEAD..HEAD")
+    out = _json(proc)
+    assert proc.returncode == 0
+    assert set(out) == {
+        "range",
+        "commit_count",
+        "merge_count",
+        "merges_measured",
+        "commits",
+        "files",
+        "merge_files",
+        "stories_supplied",
+    }
+    assert out["commit_count"] == 0
+    assert out["merge_count"] == 0
+    assert out["merges_measured"] == 0
+    assert out["commits"] == [] and out["files"] == [] and out["merge_files"] == []
+
+
+def test_linear_history_reports_no_merges(tmp_path):
+    repo = _make_repo(tmp_path)
+    out = _json(_proc("--repo", str(repo), "--range", "HEAD~1..HEAD"))
+    assert out["merge_count"] == 0
+    assert out["merges_measured"] == 0
+    assert out["merge_files"] == []
+
+
+def _recording_git(tmp_path, calls):
+    """A `git` shim that records each invocation as one \\x1f-delimited record
+    (one field per argument, so argument boundaries survive) and then execs the
+    real git."""
+    real_git = shutil.which("git")
+    assert real_git, "git must be on PATH"
+    return _fake_git(
+        tmp_path,
+        "#!/bin/sh\n"
+        f"( printf '%s\\037' \"$@\"; printf '\\n' ) >> \"{calls}\"\n"
+        f'exec "{real_git}" "$@"\n',
+    )
+
+
+def _numstat_invocations(calls):
+    """The recorded `git log --numstat` invocations, each as an argument list."""
+    out = []
+    for line in calls.read_text().splitlines():
+        argv = [field for field in line.split("\x1f") if field]
+        if "--numstat" in argv:
+            out.append(argv)
+    return out
+
+
+def test_second_pass_runs_only_when_the_range_has_merges(tmp_path):
+    # The merge pass is skipped outright on linear history, so the common case
+    # still costs exactly one `git log` — and the two passes must differ in
+    # exactly the arguments the design depends on.
+    calls = tmp_path / "calls.log"
+    overlay = _recording_git(tmp_path, calls)
+    merge_args = {"-m", "--first-parent", "--min-parents=2"}
+
+    (tmp_path / "linear").mkdir()
+    (tmp_path / "merged").mkdir()
+
+    linear = _make_repo(tmp_path / "linear")
+    _json(_proc("--repo", str(linear), "--range", "HEAD~1..HEAD", env=overlay))
+    logs = _numstat_invocations(calls)
+    assert len(logs) == 1, logs
+
+    calls.write_text("")
+    merged, base = _merge_repo(tmp_path / "merged")
+    _json(_proc("--repo", str(merged), "--range", f"{base}..HEAD", env=overlay))
+    logs = _numstat_invocations(calls)
+    assert len(logs) == 2, logs
+    # Pass 1 keeps full topology: none of the merge-pass arguments may reach it,
+    # or the story-branch commits drop out of the listing and attribution dies.
+    assert merge_args.isdisjoint(logs[0]), logs[0]
+    assert merge_args.issubset(logs[1]), logs[1]
+
+
+def test_multi_story_subject_attributes_to_every_match(tmp_path):
+    # First-match-wins silently dropped the second story from the attribution.
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "f.py").write_text("a\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    (repo / "f.py").write_text("a\nb\n")
+    _git(repo, "commit", "-qam", "fix seam between 1-2 and 1-3")
+
+    out = _json(
+        _proc(
+            "--repo", str(repo), "--range", "HEAD~1..HEAD", "--stories", "1-3,1-2"
+        )
+    )
+    # Every match, in --stories order — not whichever id was passed first.
+    assert out["commits"][0]["stories"] == ["1-3", "1-2"]
+
+    # A repeated id must not list the commit twice: any per-story total built
+    # from `stories` would count it twice.
+    repeated = _json(
+        _proc(
+            "--repo", str(repo), "--range", "HEAD~1..HEAD", "--stories", "1-3,1-2,1-3"
+        )
+    )
+    assert repeated["commits"][0]["stories"] == ["1-3", "1-2"]
+    assert repeated["stories_supplied"] == ["1-3", "1-2"]
+
+
+def test_subject_naming_no_story_gets_an_empty_list(tmp_path):
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "f.py").write_text("a\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    (repo / "f.py").write_text("a\nb\n")
+    _git(repo, "commit", "-qam", "chore: tidy imports")
+
+    out = _json(
+        _proc(
+            "--repo", str(repo), "--range", "HEAD~1..HEAD", "--stories", "1-2,1-3"
+        )
+    )
+    assert out["commits"][0]["stories"] == []
+
+
+def test_git_failure_with_empty_stderr_reports_the_exit_code(tmp_path):
+    # A quiet git failure (signal kill, empty stderr) must not leave the caller
+    # with `"error": ""` and nothing to report.
+    overlay = _fake_git(tmp_path, "#!/bin/sh\nexit 3\n")
+    proc = _proc("--repo", str(tmp_path), "--range", "HEAD~1..HEAD", env=overlay)
+    out = _json(proc)
+    assert proc.returncode == 1
+    assert out["ok"] is False
+    assert out["error"] == "git exited 3"
+
+
+def _binary_repo(tmp_path):
+    """A binary-only path plus a path that is binary twice and text once."""
+    repo = tmp_path / "repo"
+    repo.mkdir()
+    _git(repo, "init", "-q", "-b", "main")
+    (repo / "keep.txt").write_text("keep\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "base")
+    base = _rev(repo, "HEAD")
+
+    (repo / "src").mkdir()
+    (repo / "src" / "x.py").write_bytes(b"\x00\x01bin\n")
+    (repo / "blob.bin").write_bytes(b"\x00\x01blob\n")
+    _git(repo, "add", "-A")
+    _git(repo, "commit", "-qm", "add binary content")
+    (repo / "src" / "x.py").write_text("one\ntwo\n")  # binary -> text: still binary
+    _git(repo, "commit", "-qam", "x.py becomes text")
+    (repo / "src" / "x.py").write_text("one\ntwo\nthree\n")  # text -> text: measured
+    _git(repo, "commit", "-qam", "grow x.py")
+    (repo / "blob.bin").write_bytes(b"\x00\x02blob\n")
+    _git(repo, "commit", "-qam", "churn the blob")
+    return repo, base
+
+
+def test_binary_revisions_no_longer_erase_measured_text_churn(tmp_path):
+    repo, base = _binary_repo(tmp_path)
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    x = {f["path"]: f for f in out["files"]}["src/x.py"]
+    assert x["added"] == 1 and x["deleted"] == 0 and x["net"] == 1
+    assert x["binary_revisions"] == 2
+    assert x["commit_count"] == 3
+
+
+def test_binary_only_path_reports_zero_sums_and_its_revision_count(tmp_path):
+    repo, base = _binary_repo(tmp_path)
+    out = _json(_proc("--repo", str(repo), "--range", f"{base}..HEAD"))
+    blob = {f["path"]: f for f in out["files"]}["blob.bin"]
+    assert blob["added"] == 0 and blob["deleted"] == 0 and blob["net"] == 0
+    assert blob["binary_revisions"] == 2
+    assert blob["commit_count"] == 2
+
+
+def test_success_shape_carries_every_documented_key(tmp_path):
+    repo = _make_repo(tmp_path)
+    out = _json(_proc("--repo", str(repo), "--range", "HEAD~1..HEAD"))
+    assert set(out) >= {
+        "range",
+        "commit_count",
+        "merge_count",
+        "merges_measured",
+        "commits",
+        "files",
+        "merge_files",
+        "stories_supplied",
+    }
+    assert set(out["commits"][0]) == {"sha", "subject", "stories", "is_merge"}
+    assert set(out["files"][0]) == {
+        "path",
+        "added",
+        "deleted",
+        "net",
+        "commit_count",
+        "binary_revisions",
+    }
+
+
+def test_explicit_repo_ignores_ambient_git_dir(tmp_path):
+    repo = _make_repo(tmp_path)
+    proc = _proc(
+        "--repo",
+        str(repo),
+        "--range",
+        "HEAD~1..HEAD",
+        env={"GIT_DIR": str(tmp_path / "wrong-git-dir")},
+    )
+    assert _json(proc)["commit_count"] == 1
+
+
+if __name__ == "__main__":
+    sys.exit(pytest.main([__file__, "-q"]))
diff --git a/.claude/skills/bmad-retrospective/scripts/tests/test_sprint_status.py b/.claude/skills/bmad-retrospective/scripts/tests/test_sprint_status.py
new file mode 100644
index 0000000..590215f
--- /dev/null
+++ b/.claude/skills/bmad-retrospective/scripts/tests/test_sprint_status.py
@@ -0,0 +1,1579 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0", "ruamel.yaml>=0.18"]
+# ///
+"""Corruption-critical tests for sprint-status.py.
+
+Each test runs the script as a subprocess via ``uv run`` against a temp copy of
+an inline fixture, then re-reads the file to assert comments and formatting
+survive and punctuation-heavy action values round-trip intact.
+
+Run: uv run scripts/tests/test_sprint_status.py
+ or: uv run --with pytest --with ruamel.yaml -m pytest scripts/tests/test_sprint_status.py
+"""
+
+import importlib.util
+import json
+import os
+import re
+import stat
+import subprocess
+import sys
+from pathlib import Path
+
+import pytest
+from ruamel.yaml import YAML
+
+SCRIPT = Path(__file__).resolve().parents[1] / "sprint_status.py"
+# Vendored copy of bmad-sprint-planning's sprint-status-template.yaml — skills
+# must not path into each other's directories (PATH-05). The repo-level
+# test/test-template-sync.js keeps this fixture identical to the source.
+TEMPLATE = Path(__file__).resolve().parent / "fixtures" / "sprint-status-template.yaml"
+
+FIXTURE = """\
+# Sprint Status Tracking
+# STATUS DEFINITIONS:
+#   backlog        - not yet started
+#   ready-for-dev  - ready to be implemented
+#   done           - completed
+generated: "01-01-2026 09:00"
+last_updated: "01-01-2026 09:00"
+project: "Demo Project"
+project_key: "DEMO"
+tracking_system: "file"
+story_location: "docs/stories"
+development_status:
+  epic-1: backlog
+  1-1-user-authentication: done
+  1-2-account-management: done
+  epic-1-retrospective: optional
+  epic-2: backlog
+  2-1-dashboard: backlog
+"""
+
+
+# Two epics' worth of items, because the flag's headline use is epic N's retro
+# closing epic N-1's items: nothing may scope a selector to --epic. The two
+# "Scripted item" entries share their action text and differ only by epic, so the
+# legacy epic+action selector has to discriminate on the epic to resolve at all.
+ACTION_FIXTURE = """\
+# Sprint Status Tracking
+# STATUS DEFINITIONS:
+#   open           - committed during a retrospective, not yet addressed
+generated: "01-01-2026 09:00"
+last_updated: "01-01-2026 09:00"
+development_status:
+  1-1-a: done
+  epic-1-retrospective: optional
+  2-1-b: done
+  epic-2-retrospective: optional
+
+# Action items committed during retrospectives
+action_items:
+  - id: "epic-1-retro-item-1-x"
+    epic: 1
+    action: "Scripted item"
+    owner: "Amelia"
+    status: "open"
+    ref: "docs/epic-1-retro.md"
+  - epic: 1
+    action: "Pre-existing item"
+    owner: "Charlie"
+    status: open
+  - id: "epic-2-retro-item-1-y"
+    epic: 2
+    action: "Scripted item"
+    owner: "Dana"
+    status: "in-progress"
+    ref: "docs/epic-2-retro.md"
+"""
+
+# Three spellings of the same scalar, to pin that a status write never re-styles
+# the line it lands on.
+STYLE_FIXTURE = """\
+last_updated: "01-01-2026 09:00"
+development_status:
+  1-1-a: done
+  epic-1-retrospective: optional
+action_items:
+  - id: "double"
+    epic: 1
+    action: "Double"
+    status: "open"
+  - id: "single"
+    epic: 1
+    action: "Single"
+    status: 'open'
+  - id: "plain"
+    epic: 1
+    action: "Plain"
+    status: open
+"""
+
+
+def _run(args):
+    cmd = ["uv", "run", str(SCRIPT), *args]
+    # LC_ALL=C keeps os.strerror text stable so error-string assertions do not
+    # depend on the developer's locale.
+    return subprocess.run(
+        cmd, capture_output=True, text=True, env={**os.environ, "LC_ALL": "C"}
+    )
+
+
+def _module():
+    """Import the script as a module, for the few properties that cannot be
+    triggered through the CLI (a failure after the temp file already exists)."""
+    spec = importlib.util.spec_from_file_location("sprint_status", SCRIPT)
+    mod = importlib.util.module_from_spec(spec)
+    spec.loader.exec_module(mod)
+    return mod
+
+
+def _write_fixture(tmp_path):
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(FIXTURE, encoding="utf-8")
+    return target
+
+
+def _write_action_fixture(tmp_path):
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(ACTION_FIXTURE, encoding="utf-8")
+    return target
+
+
+def _load(path):
+    yaml = YAML(typ="rt")
+    with open(path, "r", encoding="utf-8") as fh:
+        return yaml.load(fh)
+
+
+def _json(proc):
+    """Parse the JSON-only stdout contract, surfacing a crash instead of hiding
+    it behind a JSONDecodeError."""
+    assert proc.stdout, f"empty stdout; stderr was: {proc.stderr}"
+    assert "Traceback" not in proc.stderr, proc.stderr
+    return json.loads(proc.stdout)
+
+
+def test_detect_epic(tmp_path):
+    target = _write_fixture(tmp_path)
+    proc = _run(["detect-epic", "--file", str(target)])
+    assert proc.returncode == 0, proc.stderr
+    out = json.loads(proc.stdout)
+    assert out["epic"] == 1
+    assert out["story_count"] == 2
+    assert out["retro_key"] == "epic-1-retrospective"
+    assert out["retro_status"] == "optional"
+    assert set(out["done_stories"]) == {
+        "1-1-user-authentication",
+        "1-2-account-management",
+    }
+
+
+def test_detect_epic_rejects_typed_retrospective_status_as_json(tmp_path):
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: 2026-01-01\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+
+    proc = _run(["detect-epic", "--file", str(target)])
+
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["error"] == "epic-1-retrospective status must be a string or null"
+    assert "restored" not in out
+    assert target.read_text(encoding="utf-8") == fixture
+
+
+# --- pending_stories: the unfinished-epic gate --------------------------------
+
+
+def test_pending_stories_lists_the_selected_epics_unfinished_keys(tmp_path):
+    # The gate the skill branches on before Phase 1: an epic whose highest done
+    # story selected it, but which is not actually finished. Document order, so
+    # the listing the user confirms matches the file they can open.
+    fixture = (
+        "development_status:\n"
+        "  epic-2: backlog\n"
+        "  2-1-a: done\n"
+        "  2-2-b: backlog\n"
+        "  2-3-c: ready-for-dev\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target)])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 2
+    assert out["pending_stories"] == ["2-2-b", "2-3-c"]
+    # A non-story key sitting beside them never leaks in: STORY_RE gates entry.
+    assert "epic-2" not in out["pending_stories"]
+
+
+def test_pending_stories_is_empty_for_a_complete_epic(tmp_path):
+    fixture = (
+        "development_status:\n"
+        "  2-1-a: done\n"
+        "  2-2-b: done\n"
+        "  epic-2-retrospective: optional\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target)])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 2
+    assert out["pending_stories"] == []
+
+
+def test_pending_stories_ignores_other_epics(tmp_path):
+    # FIXTURE detects epic 1 while 2-1-dashboard sits at backlog. The key is
+    # scoped to the *selected* epic -- unlike done_stories, which spans the whole
+    # file -- so another epic's unfinished work must never block this retro.
+    target = _write_fixture(tmp_path)
+    proc = _run(["detect-epic", "--file", str(target)])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 1
+    assert out["pending_stories"] == []
+    # done_stories keeps its whole-file scope, unchanged.
+    assert set(out["done_stories"]) == {
+        "1-1-user-authentication",
+        "1-2-account-management",
+    }
+
+
+def test_pending_stories_present_when_no_epic_is_detected(tmp_path):
+    # No done story anywhere: the shape stays uniform so a caller can read
+    # pending_stories without first branching on epic.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: backlog\n"
+        "  2-1-b: ready-for-dev\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target)])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] is None
+    assert out["story_count"] == 0
+    assert out["pending_stories"] == []
+
+
+def test_detect_epic_flag_aims_pending_stories_at_a_supplied_epic(tmp_path):
+    # Auto-detect would pick epic 2 (highest with a done story). --epic 1 aims
+    # the unfinished-epic gate at the orchestrator's explicit choice instead —
+    # the -H <epic> path that previously had no pending_stories at all.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  1-2-b: backlog\n"
+        "  1-3-c: review\n"
+        "  2-1-a: done\n"
+        "  2-2-b: done\n"
+        "  epic-1-retrospective: optional\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target), "--epic", "1"])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 1
+    assert out["retro_key"] == "epic-1-retrospective"
+    assert out["retro_status"] == "optional"
+    assert out["pending_stories"] == ["1-2-b", "1-3-c"]
+    # done_stories keeps its whole-file scope.
+    assert set(out["done_stories"]) == {"1-1-a", "2-1-a", "2-2-b"}
+
+
+def test_detect_epic_flag_lists_pending_when_no_story_is_done(tmp_path):
+    # Without --epic, no done story means epic is null. With --epic, an
+    # unfinished epic that never landed a done story is still addressable —
+    # every story key of that epic is pending.
+    fixture = (
+        "development_status:\n"
+        "  3-1-a: backlog\n"
+        "  3-2-b: ready-for-dev\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target), "--epic", "3"])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 3
+    assert out["pending_stories"] == ["3-1-a", "3-2-b"]
+    assert out["retro_key"] == "epic-3-retrospective"
+    assert out["retro_status"] is None
+
+
+def test_detect_epic_flag_empty_pending_for_a_complete_supplied_epic(tmp_path):
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  1-2-b: done\n"
+        "  2-1-a: backlog\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target), "--epic", "1"])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 1
+    assert out["pending_stories"] == []
+
+
+def test_detect_epic_flag_zero_story_count_marks_a_nonexistent_epic(tmp_path):
+    # --epic 9 against a file that has no epic-9 stories: pending_stories is
+    # empty exactly as it is for a finished epic, so story_count is the only
+    # signal separating "complete" from "typo'd". The gate reads 0 as suspect,
+    # never as done.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  1-2-b: done\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target), "--epic", "9"])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["epic"] == 9
+    assert out["story_count"] == 0
+    assert out["pending_stories"] == []
+    assert out["retro_status"] is None
+    # The finished epic it could be confused with reports its real count.
+    proc = _run(["detect-epic", "--file", str(target), "--epic", "1"])
+    out = _json(proc)
+    assert out["story_count"] == 2
+    assert out["pending_stories"] == []
+
+
+def test_detect_epic_flag_rejects_non_positive_epic(tmp_path):
+    target = _write_fixture(tmp_path)
+    for bad in ("0", "-3"):
+        proc = _run(["detect-epic", "--file", str(target), "--epic", bad])
+        assert proc.returncode == 1, proc.stderr
+        out = _json(proc)
+        assert out["ok"] is False
+        assert "epic" in out["error"]
+        assert "restored" not in out
+
+
+def test_update_rejects_non_positive_epic(tmp_path):
+    target = _write_fixture(tmp_path)
+    for bad in ("0", "-3"):
+        proc = _run(["update", "--file", str(target), "--epic", bad])
+        assert proc.returncode == 1, proc.stderr
+        assert "positive integer" in _json(proc)["error"]
+        assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+# --- The JSON-only contract covers the help paths ----------------------------
+
+
+@pytest.mark.parametrize(
+    "args",
+    [["-h"], ["--help"], ["detect-epic", "-h"], ["detect-epic", "--help"]],
+    ids=["top-short", "top-long", "sub-short", "sub-long"],
+)
+def test_help_flags_emit_json_not_usage(args):
+    # argparse's built-in help action bypasses error() -- it prints usage text
+    # to stdout and exits 0, which is exactly the contract this script sells.
+    # add_help=False turns -h into an ordinary unrecognized argument instead.
+    proc = _run(args)
+    # Exit 2 specifically: the module docstring reserves 2 for argument errors
+    # and 1 for I/O failures, and retro-document.md teaches callers to tell the
+    # two apart, so collapsing them must fail here.
+    assert proc.returncode == 2
+    assert "usage:" not in proc.stdout
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["error"]
+    # An argparse rejection speaks for no file, so it carries no "restored" --
+    # the same rule test_only_the_write_path_reports_restored pins for exit 1.
+    assert "restored" not in out
+
+
+@pytest.mark.parametrize("flag", ["-h", "--help"])
+def test_update_help_flag_emits_json_not_usage(tmp_path, flag):
+    # The update subparser too, driven with its required arguments present so
+    # nothing but the help flag itself can be what argparse objects to.
+    target = _write_fixture(tmp_path)
+    proc = _run(["update", "--file", str(target), "--epic", "1", flag])
+    assert proc.returncode == 2
+    assert "usage:" not in proc.stdout
+    out = _json(proc)
+    assert out["ok"] is False
+    assert flag in out["error"]
+    assert "restored" not in out
+    # A rejected invocation must not have written anything.
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+def test_update_sets_retro_and_appends_action(tmp_path):
+    target = _write_fixture(tmp_path)
+    payload = '[{"action":"Fix #42: colons: and # hashes","owner":"Amelia"}]'
+    proc = _run(
+        [
+            "update",
+            "--file",
+            str(target),
+            "--epic",
+            "1",
+            "--set-retro-done",
+            "--add-action",
+            payload,
+        ]
+    )
+    assert proc.returncode == 0, proc.stderr
+    out = json.loads(proc.stdout)
+    assert out["ok"] is True
+    assert out["retro_key_found"] is True
+    assert out["retro_status_after"] == "done"
+    assert out["action_items_added"] == 1
+
+    # File must still parse cleanly (punctuation did not corrupt it).
+    data = _load(target)
+    assert data is not None
+
+    # STATUS DEFINITIONS comment survived.
+    raw = target.read_text(encoding="utf-8")
+    assert "STATUS DEFINITIONS" in raw
+
+    # Retro status flipped to done.
+    assert data["development_status"]["epic-1-retrospective"] == "done"
+
+    # The action value round-trips with literal '#' and ':' intact.
+    action = data["action_items"][0]
+    assert action["action"] == "Fix #42: colons: and # hashes"
+    assert action["owner"] == "Amelia"
+    assert action["epic"] == 1
+    assert action["status"] == "open"
+
+
+def test_update_rejects_typed_retrospective_status_before_writing(tmp_path):
+    fixture = (
+        "last_updated: 01-01-2026 09:00\n"
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: 2026-01-01\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+
+    proc = _run(
+        [
+            "update",
+            "--file",
+            str(target),
+            "--epic",
+            "1",
+            "--set-retro-done",
+            "--add-action",
+            '[{"action":"Must not be appended","owner":"Amelia"}]',
+        ]
+    )
+
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert out["error"] == "epic-1-retrospective status must be a string or null"
+    assert target.read_text(encoding="utf-8") == fixture
+
+
+def test_detect_epic_matches_split_story_keys(tmp_path):
+    # A split-story key like 2-6a-... is first-class in BMAD (an oversized story
+    # split into 2-6a / 2-6b) and must not be invisible to detection — otherwise
+    # an epic whose only done stories are splits is silently skipped.
+    fixture = (
+        "development_status:\n"
+        "  1-1-first: done\n"
+        "  2-6a-split-auth: done\n"
+        "  epic-2-retrospective: optional\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["detect-epic", "--file", str(target)])
+    assert proc.returncode == 0, proc.stderr
+    out = json.loads(proc.stdout)
+    assert out["epic"] == 2
+    assert "2-6a-split-auth" in out["done_stories"]
+    assert out["retro_key"] == "epic-2-retrospective"
+
+
+def test_update_rejects_non_list_action_items(tmp_path):
+    # A hand-corrupted action_items must fail on the JSON contract, not crash.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: optional\n"
+        'action_items: "oops-not-a-list"\n'
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--add-action", '[{"action":"x","owner":"y"}]']
+    )
+    assert proc.returncode == 1
+    out = json.loads(proc.stdout)  # must be JSON, not a traceback
+    assert out["ok"] is False
+    assert "action_items" in out["error"]
+
+
+def test_appended_items_carry_id_and_ref(tmp_path):
+    target = _write_fixture(tmp_path)
+    ref = "docs/stories/epic-1-retro-2026-07-21.md"
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-retro-done",
+         "--add-action", '[{"action":"Fix the seam","owner":"Amelia"}]',
+         "--ref", ref, "--verdict", "accepted-with-open-items"]
+    )
+    assert proc.returncode == 0, proc.stderr
+    out = json.loads(proc.stdout)
+    assert out["verdict"] == "accepted-with-open-items"  # echoed, not written to a key
+
+    item = _load(target)["action_items"][0]
+    assert item["id"].startswith("epic-1-retro-item-1-")
+    assert item["ref"] == ref
+    # The retro key value stays "done" — verdict is not encoded into it.
+    assert _load(target)["development_status"]["epic-1-retrospective"] == "done"
+
+
+def test_free_spelled_verdict_is_rejected_before_the_file_is_touched(tmp_path):
+    # The SKILL's prose verdict ("accepted with open items") and the frontmatter
+    # token (accepted-with-open-items) used to be two spellings of one value; an
+    # orchestrator branching on the echo would fall through both. Only the
+    # frontmatter vocabulary passes; anything else fails with the file intact.
+    target = _write_fixture(tmp_path)
+    for bad in ("accepted with open items", "ship it", "ACCEPTED"):
+        proc = _run(
+            ["update", "--file", str(target), "--epic", "1", "--set-retro-done",
+             "--verdict", bad]
+        )
+        assert proc.returncode == 1, f"accepted {bad!r}"
+        out = _json(proc)
+        assert out["ok"] is False and "--verdict" in out["error"]
+        assert out["restored"] is True
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+def test_explicit_item_id_is_preserved(tmp_path):
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--add-action", '[{"action":"a","owner":"o","id":"custom-id-7"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _load(target)["action_items"][0]["id"] == "custom-id-7"
+
+
+@pytest.mark.skipif(
+    hasattr(os, "geteuid") and os.geteuid() == 0,
+    reason="root bypasses file permission bits",
+)
+def test_write_failure_reports_restore_status(tmp_path):
+    # If the write cannot happen, the caller must be told whether the original
+    # was restored — a silent failure defeats the script's core guarantee.
+    #
+    # The write is atomic (temp file + os.replace), and os.replace needs write
+    # permission on the *directory*, not on the target — a read-only target is
+    # now replaceable. Making the containing directory read-only is what blocks
+    # the write: mkstemp fails, while the restore write to the still-writable
+    # target succeeds.
+    holder = tmp_path / "holder"
+    holder.mkdir()
+    target = _write_fixture(holder)
+    os.chmod(holder, 0o555)
+    try:
+        proc = _run(
+            ["update", "--file", str(target), "--epic", "1", "--set-retro-done"]
+        )
+    finally:
+        os.chmod(holder, 0o755)
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    # The file was never touched: the temp file could not even be created.
+    assert target.read_text(encoding="utf-8") == FIXTURE
+    assert [p.name for p in holder.iterdir()] == ["sprint-status.yaml"]
+
+
+def test_punctuation_does_not_corrupt_file(tmp_path):
+    # Explicit re-parse guarantee for YAML-breaking punctuation.
+    target = _write_fixture(tmp_path)
+    payload = '[{"action":"weird: value # with: hashes","owner":"Bob # Smith"}]'
+    proc = _run(
+        [
+            "update",
+            "--file",
+            str(target),
+            "--epic",
+            "1",
+            "--add-action",
+            payload,
+        ]
+    )
+    assert proc.returncode == 0, proc.stderr
+    # Re-parse must succeed and preserve the literal punctuation.
+    data = _load(target)
+    assert data["action_items"][0]["action"] == "weird: value # with: hashes"
+    assert data["action_items"][0]["owner"] == "Bob # Smith"
+
+
+# --- Formatting fidelity -----------------------------------------------------
+
+
+def test_template_round_trip_changes_only_last_updated(tmp_path):
+    # The repo's own sprint-status template is the shape every generated file
+    # inherits: 2-space sequence indent and a mid-file comment above
+    # action_items. An update must touch nothing but last_updated — a re-indent
+    # of a pre-existing, untouched entry defeats the preservation guarantee that
+    # motivates "do not hand-edit this file".
+    source = TEMPLATE.read_text(encoding="utf-8")
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(source, encoding="utf-8")
+
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--date", "01-01-2026 09:00"]
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["ok"] is True
+
+    before = source.splitlines()
+    after = target.read_text(encoding="utf-8").splitlines()
+    assert len(before) == len(after)
+    changed = [(b, a) for b, a in zip(before, after) if b != a]
+    assert len(changed) == 1, changed
+    assert changed[0][1] == "last_updated: 01-01-2026 09:00"
+    # The pre-existing action item keeps its 2-space sequence indent.
+    assert "  - epic: 1" in after
+
+
+def test_mid_file_comment_survives_update(tmp_path):
+    fixture = (
+        "# header\n"
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: optional\n"
+        "\n"
+        "# Action items committed during retrospectives\n"
+        "action_items:\n"
+        "  - epic: 1\n"
+        '    action: "Pre-existing item"\n'
+        '    owner: "Charlie"\n'
+        "    status: open\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-retro-done",
+         "--add-action", '[{"action":"New item","owner":"Amelia"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+    raw = target.read_text(encoding="utf-8")
+    assert "# Action items committed during retrospectives" in raw
+    assert "# header" in raw
+    assert '    action: "Pre-existing item"' in raw
+
+
+def test_legacy_offset_zero_file_is_canonicalized(tmp_path):
+    # Files the previous version of this script wrote carry action_items at
+    # column 0. The indent pin re-indents them to the template's shape on the
+    # next write. That is a deliberate one-time canonicalization, not a silent
+    # failure: the update still succeeds and no comment is lost.
+    fixture = (
+        "# header\n"
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: optional\n"
+        "action_items:\n"
+        '- id: "legacy"\n'
+        "  epic: 1\n"
+        '  action: "written by the old code"\n'
+        "  status: open\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["update", "--file", str(target), "--epic", "1", "--set-retro-done"])
+    assert proc.returncode == 0, proc.stderr
+    raw = target.read_text(encoding="utf-8")
+    assert '  - id: "legacy"' in raw
+    assert '    action: "written by the old code"' in raw
+    assert "# header" in raw
+
+
+def test_lost_comment_fails_with_restore(tmp_path):
+    # A standalone comment inside a flow collection is genuinely dropped by the
+    # round-trip. The leading-block check never saw it; the full multiset does,
+    # and the original bytes must come back.
+    fixture = (
+        "# header\n"
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: optional\n"
+        "tags: [\n"
+        "  # a standalone comment the round-trip drops\n"
+        '  "alpha",\n'
+        '  "beta",\n'
+        "]\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-retro-done"]
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "comment line lost" in out["error"]
+    assert "a standalone comment the round-trip drops" in out["error"]
+    assert target.read_text(encoding="utf-8") == fixture
+
+
+# --- Malformed input stays on the JSON contract ------------------------------
+
+
+@pytest.mark.parametrize("command", ["detect-epic", "update"])
+def test_non_mapping_root_is_json_error(tmp_path, command):
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text("- a\n- b\n", encoding="utf-8")
+    args = ["--file", str(target)] + (["--epic", "1"] if command == "update" else [])
+    proc = _run([command, *args])
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert "root document is not a mapping" in out["error"]
+    assert target.read_text(encoding="utf-8") == "- a\n- b\n"
+
+
+@pytest.mark.parametrize("command", ["detect-epic", "update"])
+@pytest.mark.parametrize(
+    "body",
+    ['development_status: "not-a-mapping"\n', "development_status:\n  - a\n  - b\n"],
+    ids=["scalar", "list"],
+)
+def test_non_mapping_development_status_is_json_error(tmp_path, command, body):
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(body, encoding="utf-8")
+    args = ["--file", str(target)] + (["--epic", "1"] if command == "update" else [])
+    proc = _run([command, *args])
+    # update used to report ok:true here while silently doing nothing.
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert "development_status is not a mapping" in out["error"]
+
+
+@pytest.mark.parametrize("command", ["detect-epic", "update"])
+def test_directory_target_is_json_error(tmp_path, command):
+    target = tmp_path / "a-directory"
+    target.mkdir()
+    args = ["--file", str(target)] + (["--epic", "1"] if command == "update" else [])
+    proc = _run([command, *args])
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["error"]
+
+
+@pytest.mark.skipif(
+    hasattr(os, "geteuid") and os.geteuid() == 0,
+    reason="root bypasses file permission bits",
+)
+@pytest.mark.parametrize("command", ["detect-epic", "update"])
+def test_unreadable_target_is_json_error(tmp_path, command):
+    # The other half of the OSError widening: PermissionError, not just
+    # IsADirectoryError, has to stay on the JSON contract.
+    target = _write_fixture(tmp_path)
+    os.chmod(target, 0o000)
+    args = ["--file", str(target)] + (["--epic", "1"] if command == "update" else [])
+    try:
+        proc = _run([command, *args])
+    finally:
+        os.chmod(target, 0o644)
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert "denied" in out["error"].lower()
+
+
+@pytest.mark.parametrize("command", ["detect-epic", "update"])
+def test_invalid_utf8_is_json_error(tmp_path, command):
+    target = tmp_path / "sprint-status.yaml"
+    target.write_bytes(b"development_status:\n  1-1-a: d\xffone\n")
+    args = ["--file", str(target)] + (["--epic", "1"] if command == "update" else [])
+    proc = _run([command, *args])
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert "utf-8" in out["error"].lower()
+
+
+# --- Atomic write ------------------------------------------------------------
+
+
+def test_atomic_write_failure_leaves_target_byte_identical(tmp_path, monkeypatch):
+    # The failure the atomic write exists for: something goes wrong after the
+    # temp file has been written. Nothing may reach the target and no temp file
+    # may survive. No CLI path reaches here -- a read-only directory fails at
+    # mkstemp instead -- so this drives the helper directly.
+    mod = _module()
+    target = _write_fixture(tmp_path)
+
+    def boom(*args, **kwargs):
+        raise OSError(28, "No space left on device")
+
+    monkeypatch.setattr(mod.os, "replace", boom)
+    with pytest.raises(OSError):
+        mod._atomic_write(str(target), b"replacement bytes\n", 0o644)
+    assert target.read_text(encoding="utf-8") == FIXTURE
+    assert [p.name for p in tmp_path.iterdir()] == ["sprint-status.yaml"]
+
+
+def test_dir_fsync_failure_after_rename_is_not_a_write_failure(tmp_path, monkeypatch):
+    # Once os.replace has returned, the new bytes ARE the file. The directory
+    # fsync that follows is durability polish; if it raised, cmd_update would
+    # emit "restored": true about a write that in fact landed — the one lie the
+    # restored contract exists to prevent. Deny opening the directory (the only
+    # thing _atomic_write opens by path after the rename) and require success.
+    mod = _module()
+    target = _write_fixture(tmp_path)
+    directory = os.path.dirname(os.path.realpath(str(target)))
+    real_open = os.open
+
+    def deny_directory_open(p, *args, **kwargs):
+        if p == directory:
+            raise OSError(5, "Input/output error")
+        return real_open(p, *args, **kwargs)
+
+    monkeypatch.setattr(mod.os, "open", deny_directory_open)
+    mod._atomic_write(str(target), b"replacement bytes\n", 0o644)
+    assert target.read_bytes() == b"replacement bytes\n"
+    assert [p.name for p in tmp_path.iterdir()] == ["sprint-status.yaml"]
+
+
+def test_restore_is_atomic(tmp_path, monkeypatch):
+    # _restore is the rollback the reference sells as the safety net. A
+    # truncating rewrite that dies halfway would destroy the very bytes it is
+    # putting back, which is how a full disk used to corrupt the file.
+    mod = _module()
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text("damaged\n", encoding="utf-8")
+
+    def boom(*args, **kwargs):
+        raise OSError(28, "No space left on device")
+
+    monkeypatch.setattr(mod.os, "replace", boom)
+    assert mod._restore(str(target), FIXTURE.encode("utf-8"), 0o644) is False
+    # It reported failure honestly and left the file no worse than it found it.
+    assert target.read_text(encoding="utf-8") == "damaged\n"
+    assert [p.name for p in tmp_path.iterdir()] == ["sprint-status.yaml"]
+
+
+def test_symlinked_target_is_written_through(tmp_path):
+    # os.replace onto a symlink would detach the link and leave the real file
+    # stale while reporting ok:true.
+    real = tmp_path / "real-sprint-status.yaml"
+    real.write_text(FIXTURE, encoding="utf-8")
+    link = tmp_path / "sprint-status.yaml"
+    link.symlink_to(real)
+    proc = _run(["update", "--file", str(link), "--epic", "1", "--set-retro-done"])
+    assert proc.returncode == 0, proc.stderr
+    assert link.is_symlink(), "the symlink was replaced by a regular file"
+    assert _load(real)["development_status"]["epic-1-retrospective"] == "done"
+
+
+def test_atomic_write_preserves_mode_and_leaves_no_temp_file(tmp_path):
+    # mkstemp creates 0600; without carrying the target's mode over, every
+    # update would silently narrow the file.
+    holder = tmp_path / "holder"
+    holder.mkdir()
+    target = _write_fixture(holder)
+    os.chmod(target, 0o640)
+    proc = _run(["update", "--file", str(target), "--epic", "1", "--set-retro-done"])
+    assert proc.returncode == 0, proc.stderr
+    assert stat.S_IMODE(target.stat().st_mode) == 0o640
+    assert [p.name for p in holder.iterdir()] == ["sprint-status.yaml"]
+
+
+# --- Result-JSON precision ---------------------------------------------------
+
+
+def test_retro_key_found_is_null_without_the_flag(tmp_path):
+    # No development_status key at all: the update must not conjure one, and
+    # retro_key_found must say "not asked" rather than "absent".
+    fixture = 'project: "Demo"\nlast_updated: "01-01-2026 09:00"\n'
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(["update", "--file", str(target), "--epic", "1"])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["ok"] is True
+    assert out["retro_key_found"] is None
+    assert "development_status" not in target.read_text(encoding="utf-8")
+
+
+def test_retro_key_found_is_false_when_the_key_is_absent(tmp_path):
+    target = _write_fixture(tmp_path)
+    proc = _run(["update", "--file", str(target), "--epic", "2", "--set-retro-done"])
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["ok"] is True
+    assert out["retro_key_found"] is False
+    # Nothing was written into the mapping.
+    assert "epic-2-retrospective" not in _load(target)["development_status"]
+
+
+@pytest.mark.parametrize("command", ["detect-epic", "update"])
+def test_only_the_write_path_reports_restored(tmp_path, command):
+    # "restored" speaks to the state of a file the command may have written.
+    # detect-epic never writes, so inventing the key there would mislead callers
+    # that branch on it.
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text("- a\n- b\n", encoding="utf-8")
+    args = ["--file", str(target)] + (["--epic", "1"] if command == "update" else [])
+    out = _json(_run([command, *args]))
+    assert out["ok"] is False
+    assert ("restored" in out) is (command == "update")
+
+
+def test_pre_write_failure_reports_restored(tmp_path):
+    # retro-document.md teaches callers that ok:false carries restored:true;
+    # a failure before the write must not read as "the file may be incomplete".
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--add-action", "{not json"]
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+# --- Action-item validation and identity -------------------------------------
+
+
+def test_non_latin_action_keeps_its_text_in_the_id(tmp_path):
+    target = _write_fixture(tmp_path)
+    payload = json.dumps(
+        [{"action": "Улучшить обработку ошибок", "owner": "Amelia"}],
+        ensure_ascii=False,
+    )
+    proc = _run(["update", "--file", str(target), "--epic", "1", "--add-action", payload])
+    assert proc.returncode == 0, proc.stderr
+    item_id = _load(target)["action_items"][0]["id"]
+    assert item_id == "epic-1-retro-item-1-улучшить-обработку-ошибок"
+
+
+def test_unsluggable_action_falls_back_to_a_hash(tmp_path):
+    target = _write_fixture(tmp_path)
+    payload = json.dumps([{"action": "!!! 🎉", "owner": "Amelia"}], ensure_ascii=False)
+    proc = _run(["update", "--file", str(target), "--epic", "1", "--add-action", payload])
+    assert proc.returncode == 0, proc.stderr
+    item_id = _load(target)["action_items"][0]["id"]
+    assert not item_id.endswith("-item")
+    assert re.fullmatch(r"epic-1-retro-item-1-[0-9a-f]{8}", item_id), item_id
+
+
+def test_empty_action_is_rejected(tmp_path):
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--add-action", '[{"action":"   ","owner":"x"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "action" in out["error"]
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+def test_non_string_action_is_rejected(tmp_path):
+    # A JSON null would otherwise be str()'d into a literal "None" and written
+    # as a real action item, which the new emptiness check alone lets through.
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--add-action", '[{"action":null,"owner":"x"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+def test_date_is_normalized_to_the_canonical_format(tmp_path):
+    # strptime accepts unpadded spellings; writing those through would defeat
+    # the point of validating the format.
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--date", "1-2-2026 9:05"]
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["last_updated"] == "01-02-2026 09:05"
+    assert _load(target)["last_updated"] == "01-02-2026 09:05"
+
+
+def test_malformed_date_is_rejected(tmp_path):
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--date", "not-a-date"]
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "--date" in out["error"]
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+# --- Action-item status transitions ------------------------------------------
+
+
+def test_set_action_status_applies_both_selector_forms(tmp_path):
+    # The whole point of the flag: an item written by this script (selected by
+    # id) and a legacy item that predates ids (selected by epic + exact action
+    # text) both move off "open" in a single call.
+    target = _write_action_fixture(tmp_path)
+    payload = json.dumps(
+        [
+            {"id": "epic-1-retro-item-1-x", "status": "done"},
+            {"epic": 1, "action": "Pre-existing item", "status": "in-progress"},
+        ]
+    )
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-action-status", payload]
+    )
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["ok"] is True
+    assert out["action_items_updated"] == 2
+    assert out["action_items_added"] == 0
+
+    items = _load(target)["action_items"]
+    assert items[0]["status"] == "done"
+    assert items[1]["status"] == "in-progress"
+    # Every other key of both items survived untouched, in place.
+    assert items[0]["id"] == "epic-1-retro-item-1-x"
+    assert items[0]["epic"] == 1
+    assert items[0]["action"] == "Scripted item"
+    assert items[0]["owner"] == "Amelia"
+    assert items[0]["ref"] == "docs/epic-1-retro.md"
+    assert "id" not in items[1]
+    assert items[1]["epic"] == 1
+    assert items[1]["action"] == "Pre-existing item"
+    assert items[1]["owner"] == "Charlie"
+    # The epic-2 item shares its action text with items[0]; the epic-1 selector
+    # must not have touched it.
+    assert items[2]["status"] == "in-progress"
+    assert items[2]["id"] == "epic-2-retro-item-1-y"
+    assert len(items) == 3
+
+
+def test_set_action_status_changes_exactly_one_line(tmp_path):
+    # The status write is surgical: it must not re-style neighbouring lines, and
+    # an item whose status was quoted keeps its quoting. last_updated is rewritten
+    # with the same text it already held, so the whole file differs by one line.
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--date", "01-01-2026 09:00",
+         "--set-action-status", '[{"id":"epic-1-retro-item-1-x","status":"done"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+
+    before = ACTION_FIXTURE.splitlines()
+    after = target.read_text(encoding="utf-8").splitlines()
+    assert len(before) == len(after)
+    changed = [(b, a) for b, a in zip(before, after) if b != a]
+    assert changed == [('    status: "open"', '    status: "done"')], changed
+
+
+def test_set_action_status_composes_with_retro_done_and_add_action(tmp_path):
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-retro-done",
+         "--add-action", '[{"action":"Brand new item","owner":"Amelia"}]',
+         "--set-action-status",
+         '[{"epic":1,"action":"Pre-existing item","status":"done"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+    out = _json(proc)
+    assert out["ok"] is True
+    assert out["retro_status_after"] == "done"
+    assert out["action_items_added"] == 1
+    assert out["action_items_updated"] == 1
+
+    data = _load(target)
+    assert data["development_status"]["epic-1-retrospective"] == "done"
+    items = data["action_items"]
+    assert len(items) == 4
+    assert items[1]["status"] == "done"  # the targeted pre-existing item
+    assert items[3]["action"] == "Brand new item"
+    assert items[3]["status"] == "open"  # the appended item is always open
+
+
+def test_set_action_status_cannot_target_an_item_added_in_the_same_run(tmp_path):
+    # Selectors resolve against action_items as loaded, so the append cannot be
+    # observed by the same invocation. Silently succeeding here would make the
+    # flag a back door for writing a non-open status onto a brand-new item.
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--add-action", '[{"action":"Brand new","owner":"A","id":"brand-new"}]',
+         "--set-action-status", '[{"id":"brand-new","status":"done"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "no action item matches" in out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+def test_set_action_status_rejects_unknown_id(tmp_path):
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", '[{"id":"not-in-the-file","status":"done"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "not-in-the-file" in out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+def test_set_action_status_rejects_selector_when_action_items_is_absent(tmp_path):
+    # No action_items key at all must read as "no match", not as a crash.
+    target = _write_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", '[{"id":"anything","status":"done"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "no action item matches" in out["error"]
+    assert target.read_text(encoding="utf-8") == FIXTURE
+
+
+def test_set_action_status_rejects_ambiguous_selector(tmp_path):
+    # Two legacy items with identical epic + action text: guessing between them
+    # would write the wrong row half the time.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: optional\n"
+        "action_items:\n"
+        "  - epic: 1\n"
+        '    action: "Same text"\n'
+        '    owner: "Charlie"\n'
+        "    status: open\n"
+        "  - epic: 1\n"
+        '    action: "Same text"\n'
+        '    owner: "Dana"\n'
+        "    status: open\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", '[{"epic":1,"action":"Same text","status":"done"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "ambiguous" in out["error"]
+    assert "Same text" in out["error"]
+    assert "2 matches" in out["error"]
+    assert target.read_text(encoding="utf-8") == fixture
+
+
+def test_set_action_status_rejects_two_entries_hitting_the_same_item(tmp_path):
+    # The id form and the epic/action form can name the same row; applying both
+    # would overcount action_items_updated and hide a conflicting pair.
+    target = _write_action_fixture(tmp_path)
+    payload = json.dumps(
+        [
+            {"id": "epic-1-retro-item-1-x", "status": "done"},
+            {"epic": 1, "action": "Scripted item", "status": "in-progress"},
+        ]
+    )
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-action-status", payload]
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "same action item" in out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+def test_entry_with_both_selector_forms_uses_the_id(tmp_path):
+    # A caller that copied a whole item through supplies both. The id is the
+    # precise form and wins; the extra keys are ignored, not rejected. The two
+    # forms are pointed at *different* rows so the precedence is observable:
+    # the id names items[0], the epic/action pair names items[1].
+    target = _write_action_fixture(tmp_path)
+    payload = json.dumps(
+        [
+            {
+                "id": "epic-1-retro-item-1-x",
+                "epic": 1,
+                "action": "Pre-existing item",
+                "owner": "Charlie",
+                "status": "done",
+            }
+        ]
+    )
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-action-status", payload]
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 1
+    items = _load(target)["action_items"]
+    assert items[0]["status"] == "done"  # the id's item
+    assert items[1]["status"] == "open"  # the epic/action item, untouched
+
+
+def test_set_action_status_rejects_invalid_status(tmp_path):
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", '[{"id":"epic-1-retro-item-1-x","status":"closed"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "closed" in out["error"]
+    # The allowed vocabulary is named so the caller can correct the call.
+    assert "open, in-progress, done" in out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+def test_set_action_status_rejects_malformed_json(tmp_path):
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", "{not json"]
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "invalid --set-action-status JSON" in out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+_SELECTOR_SHAPE_ERROR = (
+    "each --set-action-status entry must have a non-empty string id, "
+    "or an integer epic and a non-empty string action"
+)
+
+
+@pytest.mark.parametrize(
+    ("payload", "expected_error"),
+    [
+        (
+            '{"id":"epic-1-retro-item-1-x","status":"done"}',
+            "--set-action-status must be a JSON array",
+        ),
+        (
+            '["epic-1-retro-item-1-x"]',
+            "each --set-action-status entry must be an object",
+        ),
+        ('[{"status":"done"}]', _SELECTOR_SHAPE_ERROR),
+        (
+            '[{"id":"","status":"done"}]',
+            "each --set-action-status id must be a non-empty string",
+        ),
+        (
+            '[{"id":42,"status":"done"}]',
+            "each --set-action-status id must be a non-empty string",
+        ),
+        (
+            '[{"epic":"1","action":"Pre-existing item","status":"done"}]',
+            _SELECTOR_SHAPE_ERROR,
+        ),
+        (
+            '[{"epic":true,"action":"Pre-existing item","status":"done"}]',
+            _SELECTOR_SHAPE_ERROR,
+        ),
+        ('[{"epic":1,"action":"   ","status":"done"}]', _SELECTOR_SHAPE_ERROR),
+        (
+            # No status key at all: the status validator runs before the selector
+            # validator, so this is the status branch, not the selector branch.
+            '[{"epic":1,"action":"Pre-existing item"}]',
+            "invalid --set-action-status status None",
+        ),
+        (
+            '[{"id":"epic-1-retro-item-1-x","status":3}]',
+            "invalid --set-action-status status 3",
+        ),
+    ],
+    ids=[
+        "not-a-list",
+        "entry-not-an-object",
+        "no-selector",
+        "empty-id",
+        "non-string-id",
+        "string-epic",
+        "bool-epic",
+        "blank-action",
+        "no-status-key",
+        "non-string-status",
+    ],
+)
+def test_set_action_status_rejects_bad_shapes(tmp_path, payload, expected_error):
+    # Each case pins its own message: collapsing the branches into one generic
+    # error would leave a caller unable to tell which part of the array is wrong.
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", payload]
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert expected_error in out["error"], out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+def test_selectors_are_not_scoped_to_the_epic_flag(tmp_path):
+    # The flag's headline use: epic 2's retro closing epic 1's items. --epic only
+    # names the retro key and stamps appended items; scoping selectors to it would
+    # silently break the documented cross-epic workflow while every same-epic test
+    # kept passing.
+    target = _write_action_fixture(tmp_path)
+    payload = json.dumps(
+        [
+            {"id": "epic-1-retro-item-1-x", "status": "done"},
+            {"epic": 1, "action": "Pre-existing item", "status": "done"},
+        ]
+    )
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "2", "--set-retro-done",
+         "--set-action-status", payload]
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 2
+
+    data = _load(target)
+    assert data["development_status"]["epic-2-retrospective"] == "done"
+    items = data["action_items"]
+    assert items[0]["status"] == "done"
+    assert items[1]["status"] == "done"
+    # Epic 2's own item is not swept along.
+    assert items[2]["status"] == "in-progress"
+
+
+def test_legacy_selector_discriminates_on_the_epic(tmp_path):
+    # Two items share the action text "Scripted item" and differ only by epic, so
+    # an epic-blind text match would be ambiguous -- or worse, silently pick one.
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-action-status",
+         '[{"epic":2,"action":"Scripted item","status":"done"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 1
+    items = _load(target)["action_items"]
+    assert items[2]["status"] == "done"
+    assert items[0]["status"] == "open"  # the epic-1 namesake, untouched
+
+
+def test_non_mapping_action_item_does_not_crash_the_selector(tmp_path):
+    # A hand-edited scalar in the action_items list must be skipped, not
+    # AttributeError'd into an empty stdout with a traceback.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "  epic-1-retrospective: optional\n"
+        "action_items:\n"
+        '  - "a bare string someone hand-edited in"\n'
+        '  - id: "real"\n'
+        "    epic: 1\n"
+        '    action: "Real item"\n'
+        "    status: open\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", '[{"id":"real","status":"done"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 1
+    items = _load(target)["action_items"]
+    assert items[0] == "a bare string someone hand-edited in"
+    assert items[1]["status"] == "done"
+
+
+def test_non_mapping_action_item_stays_on_the_json_contract_when_unmatched(tmp_path):
+    # Same guard, reject path: the scalar must not be dereferenced while looking
+    # for a selector that is not there.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "action_items:\n"
+        "  - 42\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1",
+         "--set-action-status", '[{"epic":1,"action":"Nothing","status":"done"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)  # asserts stdout is JSON and stderr carries no traceback
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "no action item matches" in out["error"]
+    assert target.read_text(encoding="utf-8") == fixture
+
+
+def test_boolean_epic_in_the_file_does_not_match_epic_one(tmp_path):
+    # True == 1 in Python, so without the file-side bool guard a hand-edited
+    # "epic: true" row would be silently rewritten by a selector aimed at epic 1.
+    fixture = (
+        "development_status:\n"
+        "  1-1-a: done\n"
+        "action_items:\n"
+        "  - epic: true\n"
+        '    action: "Boolean epic"\n'
+        "    status: open\n"
+    )
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(fixture, encoding="utf-8")
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--set-action-status",
+         '[{"epic":1,"action":"Boolean epic","status":"done"}]']
+    )
+    assert proc.returncode == 1
+    out = _json(proc)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "no action item matches" in out["error"]
+    assert target.read_text(encoding="utf-8") == fixture
+
+
+def test_status_write_preserves_every_scalar_style(tmp_path):
+    # The status write must land on the line without re-styling it, whichever way
+    # the file spells the scalar.
+    target = tmp_path / "sprint-status.yaml"
+    target.write_text(STYLE_FIXTURE, encoding="utf-8")
+    payload = json.dumps(
+        [
+            {"id": "double", "status": "done"},
+            {"id": "single", "status": "done"},
+            {"id": "plain", "status": "done"},
+        ]
+    )
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--date",
+         "01-01-2026 09:00", "--set-action-status", payload]
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 3
+
+    before = STYLE_FIXTURE.splitlines()
+    after = target.read_text(encoding="utf-8").splitlines()
+    assert len(before) == len(after)
+    changed = [(b, a) for b, a in zip(before, after) if b != a]
+    assert changed == [
+        ('    status: "open"', '    status: "done"'),
+        ("    status: 'open'", "    status: 'done'"),
+        ("    status: open", "    status: done"),
+    ], changed
+
+
+def test_action_status_vocabulary_is_exactly_the_three():
+    # bmad-sprint-planning is the authority. Widening this tuple would let the
+    # script write a value sprint-planning's status view reports as illegal.
+    assert _module().ACTION_STATUSES == ("open", "in-progress", "done")
+
+
+def test_empty_status_array_is_a_no_op(tmp_path):
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "1", "--date",
+         "01-01-2026 09:00", "--set-action-status", "[]"]
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 0
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+def test_in_progress_item_transitions_to_done(tmp_path):
+    # Every other success case starts from "open"; the middle of the lifecycle
+    # has to work too.
+    target = _write_action_fixture(tmp_path)
+    proc = _run(
+        ["update", "--file", str(target), "--epic", "2", "--set-action-status",
+         '[{"id":"epic-2-retro-item-1-y","status":"done"}]']
+    )
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 1
+    assert _load(target)["action_items"][2]["status"] == "done"
+
+
+def test_action_items_updated_is_always_reported(tmp_path):
+    # Consumers read the counter unconditionally, so it must be present even when
+    # the flag was not passed.
+    target = _write_fixture(tmp_path)
+    proc = _run(["update", "--file", str(target), "--epic", "1", "--set-retro-done"])
+    assert proc.returncode == 0, proc.stderr
+    assert _json(proc)["action_items_updated"] == 0
+
+
+def test_post_write_status_mismatch_restores(tmp_path, monkeypatch, capsys):
+    # The last line of defence: the written file is re-parsed and every targeted
+    # item is checked. No CLI path can fake a mismatch, so the re-parse is
+    # doctored directly.
+    mod = _module()
+    target = _write_action_fixture(tmp_path)
+    real_load_yaml = mod._load_yaml
+    calls = {"n": 0}
+
+    def flaky(path):
+        yaml, data = real_load_yaml(path)
+        calls["n"] += 1
+        if calls["n"] == 2:  # the post-write re-parse
+            data["action_items"][0]["status"] = "open"
+        return yaml, data
+
+    monkeypatch.setattr(mod, "_load_yaml", flaky)
+    args = mod.build_parser().parse_args(
+        ["update", "--file", str(target), "--epic", "1", "--date", "01-01-2026 09:00",
+         "--set-action-status", '[{"id":"epic-1-retro-item-1-x","status":"done"}]']
+    )
+    with pytest.raises(SystemExit) as excinfo:
+        mod.cmd_update(args)
+    assert excinfo.value.code == 1
+    out = json.loads(capsys.readouterr().out)
+    assert out["ok"] is False
+    assert out["restored"] is True
+    assert "after write" in out["error"]
+    assert target.read_text(encoding="utf-8") == ACTION_FIXTURE
+
+
+if __name__ == "__main__":
+    sys.exit(pytest.main([__file__, "-q"]))
diff --git a/.claude/skills/bmad-review-adversarial-general/SKILL.md b/.claude/skills/bmad-review-adversarial-general/SKILL.md
new file mode 100644
index 0000000..ec9f025
--- /dev/null
+++ b/.claude/skills/bmad-review-adversarial-general/SKILL.md
@@ -0,0 +1,6 @@
+---
+name: bmad-review-adversarial-general
+description: 'Deprecated — forwards to bmad-review.'
+---
+
+Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `adversarial` lens, passing through any `also_consider` areas. Present the findings as a Markdown list — descriptions only, no severity, priority, or ranking; no JSON block.
diff --git a/.claude/skills/bmad-review-edge-case-hunter/SKILL.md b/.claude/skills/bmad-review-edge-case-hunter/SKILL.md
new file mode 100644
index 0000000..85bc024
--- /dev/null
+++ b/.claude/skills/bmad-review-edge-case-hunter/SKILL.md
@@ -0,0 +1,6 @@
+---
+name: bmad-review-edge-case-hunter
+description: 'Deprecated — forwards to bmad-review.'
+---
+
+Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `edge-case-hunter` lens, passing through any `also_consider` areas. Output ONLY the raw findings JSON array in the legacy shape: the four standard fields (plus `kind`/`confidence` on deletion findings), no `lens` field, no markdown wrapping, no extra text. `[]` is valid when nothing is found.
diff --git a/.claude/skills/bmad-review-verification-gap/SKILL.md b/.claude/skills/bmad-review-verification-gap/SKILL.md
new file mode 100644
index 0000000..9ada568
--- /dev/null
+++ b/.claude/skills/bmad-review-verification-gap/SKILL.md
@@ -0,0 +1,6 @@
+---
+name: bmad-review-verification-gap
+description: 'Deprecated — forwards to bmad-review.'
+---
+
+Merged into `bmad-review`. Invoke the `bmad-review` skill on the same content with only the `verification-gap` lens. Present the markdown rendering only (no JSON block), listing any `gap_shape: "other"` findings under an `## Other findings` heading. When there are no findings at all, output exactly this single line: `No verification gaps found.`
diff --git a/.claude/skills/bmad-review/SKILL.md b/.claude/skills/bmad-review/SKILL.md
new file mode 100644
index 0000000..0d168db
--- /dev/null
+++ b/.claude/skills/bmad-review/SKILL.md
@@ -0,0 +1,49 @@
+---
+name: bmad-review
+description: 'Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says "review this", "critical review", "editorial review", "hunt edge cases", "review the structure", or "review the prose".'
+---
+
+# BMad Review
+
+Review content through lenses — each a distinct method and stance — and report findings in one canonical shape. Report what is real — never pad to look thorough. Each lens sets its own stance toward the content and toward zero findings: for most an empty result is valid; the adversarial lens requires at least ten concrete findings and treats an empty list as a signal to re-check; the editorial lenses hold content sacrosanct and critique only how it is organized and expressed.
+
+The lens set is whatever `{workflow.lenses}` resolves to, not a fixed list — overrides add lenses and replace shipped ones. Never claim a capability from this file; read the resolved lenses and work from those.
+
+## Inputs
+
+- **content** — what to review: a diff, branch, uncommitted changes, file, spec, story, or any document. Args: `[path]`.
+- **lenses** (optional) — one or more lens codes or names, however the caller expresses them: a spoken request, or a directive of the form `skill:bmad-review lenses=<code>[,<code>...]` (the form bmm's `doc_standards` uses). Default: every applicable lens (a full review).
+- **also_consider** (optional) — areas to keep in mind alongside each lens's normal analysis.
+- **pre-resolved customization** (optional) — `[workflow]` field values supplied by a forwarding caller. See Execution step 1.
+
+## Conventions
+
+- Bare paths (e.g. `references/lens-edge-case-hunter.md`) resolve from `{skill-root}` — this skill's installed directory, where `customize.toml` lives. `{project-root}` resolves to the project working directory.
+- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).
+- In `style_guide`, `review_guidance`, and `persistent_facts`, a value prefixed `file:` is a path or glob — load that file's contents. If a `file:` value cannot be read, name the failed file in the output header and continue: the shipped baseline for `style_guide`, the remaining entries otherwise.
+
+## Execution
+
+1. **Resolve customization:** `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults. **Forwarded activation:** if a caller invoked you with pre-resolved customization fields (e.g. the `bmad-editorial-review` shim), honor them verbatim for those named fields — they already carry the user's overrides — and resolve only the remaining fields from your own `customize.toml`. Then execute each `{workflow.activation_steps_prepend}` entry in order, hold `{workflow.persistent_facts}` as standing context for the session, and treat `{workflow.review_guidance}` entries as standing review directives for every lens.
+2. **Load the content.** If it is empty or cannot be decoded as text: when the caller expects the raw findings JSON array (e.g. the legacy edge-case forwarder), return `[{"location":"N/A","trigger_condition":"Input empty or undecodable","guard_snippet":"Provide valid content to review","potential_consequence":"Review skipped — no analysis performed"}]` (no `lens` field) and stop; otherwise say what's wrong and ask for reviewable content. Classify the content — diff, source file, function, or document — and whether it is **code** or **docs**; scope rules and lens applicability both depend on it. A document that defines behavior (spec, requirements, plan, story) is `docs` that a behavioral lens may still apply to; judge by `when`.
+3. **Select lenses** from `{workflow.lenses}`. A lens with an empty `instruction` is disabled. If the user or caller named lenses, run exactly those only — `applies_to` and `when` do not filter an explicit request. Otherwise run every enabled lens whose `applies_to` covers the content class (`any` always covers) and whose `when` applies.
+4. **Announce the plan** in one line before running anything: the content class, the lenses about to run, and — when any lens has `after` set — that it runs on top of the named lens's findings. Skip the announcement entirely when the caller pinned an exact output contract (the legacy forwarders that demand raw JSON or one exact line) — their contract covers everything you emit, not just the findings block. Then execute each `{workflow.activation_steps_append}` entry in order.
+5. **Run the independent lenses** — every selected lens without `after`. Each sees the content and `also_consider`, never another lens's findings. Follow each lens's `instruction`; the shipped lenses load their reference file just-in-time, so load only what runs. When subagents are available, spawn one per lens in parallel: give it the lens `instruction` with `{skill-root}` and paths resolved absolute, the content or where to read it, any `also_consider` areas, the standing review directives, and the constraint "Return ONLY your findings — no other output." Otherwise run the lenses sequentially yourself, completing one before starting the next.
+6. **Run the dependent lenses** — every selected lens with `after`, once the lens it names has completed, passing that lens's findings in. A lens whose `after` target was not selected or produced nothing still runs, with no prior findings. Dependent lenses that name different targets are independent of each other and may run in parallel.
+7. **Assemble and present** per Output below. Keep every lens's findings — overlap between lenses is signal, not duplication; note it in the markdown report rather than deduping. Execute `{workflow.on_complete}` if set.
+
+## Output
+
+One JSON array holding every finding from every lens. Each finding carries:
+
+- `lens` — the code of the lens that produced it
+- `location` — where in the content (file:line-range for code, section for documents)
+- `trigger_condition` — the problem, or the condition that exposes it, in one line
+- `guard_snippet` — the concrete fix, guard, or missing check
+- `potential_consequence` — what goes wrong if it ships as-is
+
+Each lens file refines these semantics for its findings and may add lens-specific fields (e.g. `kind`/`confidence` on deletion findings, `gap_shape`/`consumer`/`evidence` on verification-gap findings). A lens file may instead declare its own findings shape and rendering — the editorial lenses render a findings table — and that shape wins for that lens's findings. `[]` is valid when nothing is found. No severity, priority, or ranking anywhere.
+
+Present per `{workflow.output_format}` — `"json"` (the raw array in a fenced json block), `"markdown"`, or `"both"` — unless the caller requested a specific shape; a legacy forwarder's output contract always wins, and governs everything you emit rather than the findings block alone. The markdown report groups findings by lens, each rendered in its declared shape: a short block per finding rendering the fields plus any extras worth surfacing, one line for a lens that found nothing, and a plain clean statement when the whole review is clean. Shape the report per `{workflow.output_preferences}`.
+
+When `{workflow.report_path}` is set, write the report there; otherwise present it in chat.
diff --git a/.claude/skills/bmad-review/customize.toml b/.claude/skills/bmad-review/customize.toml
new file mode 100644
index 0000000..e9f8e36
--- /dev/null
+++ b/.claude/skills/bmad-review/customize.toml
@@ -0,0 +1,141 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-review.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-review.toml         (team)
+#   {project-root}/_bmad/custom/bmad-review.user.toml    (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins
+#   arrays (persistent_facts, activation_steps_*, review_guidance): append
+#   arrays of tables keyed by `code`: matching key replaces, new keys append
+
+# Steps executed on activation: prepend runs before the skill's own
+# activation flow, append runs after the lens plan is settled and before the
+# lenses run. Each entry is a literal instruction.
+activation_steps_prepend = []
+activation_steps_append = []
+
+# Standing context held for every review, code and document alike. Entries
+# prefixed `file:` are paths or globs whose contents load as facts; all others
+# are literal facts. The shipped entry is a project-wide glob — set it to []
+# if you don't want every review scanning for it.
+persistent_facts = ["file:{project-root}/**/project-context.md"]
+
+# Standing review directives applied on every run alongside each lens's own
+# method. Each entry is a literal sentence or a `file:`-prefixed path/glob
+# whose contents load as directives.
+#
+# Examples:
+#   "Flag passive voice in headings."
+#   "Second-person imperative is the house voice; never suggest changing it."
+#   "file:{project-root}/docs/terminology.md"
+review_guidance = []
+
+# Executed after the findings are delivered. Freeform directive; empty = the
+# review ends with the findings.
+#
+# Example:
+#   on_complete = "Append a one-line review summary to {project-root}/docs/review-log.md"
+on_complete = ""
+
+# How findings are presented when the caller doesn't say: "json" (the raw
+# findings array only), "markdown" (the human report only), or "both". A lens
+# that declares its own rendering keeps it for its own findings.
+output_format = "both"
+
+# Where to write the review report. Empty = present in chat only. Accepts
+# {project-root}-prefixed paths.
+report_path = ""
+
+# How findings are presented — shaping, not destination. Freeform directive;
+# empty = each lens's default ordering and rollup.
+#
+# Example:
+#   output_preferences = "Cap output at the 20 highest-impact findings."
+output_preferences = ""
+
+# --- Editorial lens settings (used by the structure and prose lenses) ---
+
+# Default reader the editorial lenses calibrate for when the request doesn't
+# say:
+#   "humans"  clarity, flow, comprehension aids preserved
+#   "llm"     precision, consistent terminology, no hedging
+# A reader type stated in the request wins for that run.
+reader_type = "humans"
+
+# The baseline style guide for every editorial review: the name of a guide the
+# model knows well, a `file:`-prefixed path to a style guide document, or the
+# rules inline as text. A style guide stated in the request wins for that run.
+# Where the guide in effect conflicts with the lens's generic principles, the
+# guide wins — except content is sacrosanct.
+#
+# Examples (set in team/user override TOML):
+#   style_guide = "file:{project-root}/_bmad/style-guides/company-voice.md"
+#   style_guide = "Sentence-case headings. No Oxford comma. Address the reader as 'you'."
+style_guide = "Microsoft Writing Style Guide"
+
+# ---------------------------------------------------------------------------
+# Review lenses. Each lens is a pass over the content with its own method and
+# stance. `instruction` is the lens's whole execution recipe — the shipped
+# lenses load a reference file from the skill root, but an override may inline
+# any prompt.
+#
+# `applies_to` is the content this lens can review: "code", "docs", or "any".
+# It is the first filter — a lens never joins a default review for content it
+# does not apply to. `when` (optional) refines that judgement in prose. An
+# explicitly requested lens always runs, whatever both say.
+#
+# `after` (optional) names a lens this one builds on: it runs once that lens
+# has completed and receives its findings, instead of running independently.
+#
+# Empty `instruction` disables a lens. Keyed by `code`: an override with a
+# matching code replaces the shipped lens, a new code appends.
+#
+# Example (add an org-specific lens in team/user override TOML):
+#   [[workflow.lenses]]
+#   code = "accessibility"
+#   name = "Accessibility"
+#   applies_to = "any"
+#   when = "UI code or user-facing documents."
+#   instruction = "Review against WCAG 2.2 AA. Emit findings in the canonical fields."
+# ---------------------------------------------------------------------------
+
+[[workflow.lenses]]
+code = "adversarial"
+name = "Adversarial"
+applies_to = "any"
+when = "always"
+instruction = "Load `references/lens-adversarial.md` from the skill root and follow it."
+
+[[workflow.lenses]]
+code = "edge-case-hunter"
+name = "Edge-Case Hunter"
+applies_to = "any"
+when = "Content with behavior to trace: code, diffs, and the specs, requirements, plans, and stories that define behavior. Skip for prose documents with no behavioral surface."
+instruction = "Load `references/lens-edge-case-hunter.md` from the skill root and follow it."
+
+[[workflow.lenses]]
+code = "verification-gap"
+name = "Verification Gap"
+applies_to = "code"
+when = "Reviewed inside a repo where tests can be searched and read."
+instruction = "Load `references/lens-verification-gap.md` from the skill root and follow it."
+
+[[workflow.lenses]]
+code = "structure"
+name = "Editorial Structure"
+applies_to = "docs"
+when = "Documents whose shape is the author's to change."
+instruction = "Load `references/lens-structure.md` from the skill root and follow it."
+
+[[workflow.lenses]]
+code = "prose"
+name = "Editorial Prose"
+applies_to = "docs"
+after = "structure"
+when = "Documents being copy-edited."
+instruction = "Load `references/lens-prose.md` from the skill root and follow it."
diff --git a/.claude/skills/bmad-review/references/editorial-common.md b/.claude/skills/bmad-review/references/editorial-common.md
new file mode 100644
index 0000000..a5fb104
--- /dev/null
+++ b/.claude/skills/bmad-review/references/editorial-common.md
@@ -0,0 +1,56 @@
+# Editorial Lenses — Common Ground
+
+Shared by the `structure` and `prose` lenses. Load this once; when both lenses run, the setup below is done once and serves both.
+
+## Stance
+
+Review a document as a clinical editor and return suggested fixes the author can accept or reject row by row. Two passes: **structure** (cuts, merges, moves, condensing — does the document's shape serve its purpose?) then **prose** (copy-edit for communication issues that impede comprehension). Which of the two run, and in what order, is decided by lens selection — see the skill's Execution section.
+
+**Content is sacrosanct.** Never challenge ideas — only how they're organized and expressed. Propose, don't execute: the author decides what to accept.
+
+The baseline style guide is `{workflow.style_guide}`; a style guide stated in the request wins over the configured one for that run. Where the style guide in effect conflicts with a generic principle here — including the reader calibration — the style guide wins. Nothing overrides content being sacrosanct.
+
+## Setup
+
+1. Gather inputs: the content (required — a path or pasted text), plus whatever the request states: purpose, target audience, length target, reader type, style guide. If no reviewable content was provided, say so and stop. Request-level values win; `{workflow.reader_type}` and `{workflow.style_guide}` fill what the request leaves unstated. Treat `{workflow.review_guidance}` entries as standing review directives.
+2. When the content is a file, get exact word counts — document total and per heading section — via `uv run {skill-root}/scripts/word_metrics.py <path>` (`--help` documents the output), and ground every word-impact estimate and the reduction summary in those numbers. If the content was pasted or the script cannot run, estimate and mark the numbers as estimates.
+3. Infer purpose and audience from the content and standing context when not provided, and open the output with your one-sentence read — "this document exists to help [audience] accomplish [goal]" — so the author can correct a wrong premise before acting on the findings.
+
+## Reader calibration
+
+Calibrate every finding to the reader type — stated in the request, else `{workflow.reader_type}`.
+
+**humans** (default) — optimize for clarity, flow, and natural progression. These elements serve comprehension and engagement; preserve them unless clearly wasteful, and flag any recommendation that would cut one:
+
+- Visual aids: diagrams, images, and flowcharts anchor understanding
+- Expectation-setting: "What You'll Learn" helps readers confirm they're in the right place
+- Reader's journey: organize content as a linear progression, not a database
+- Mental models: overview before details prevents cognitive overload
+- Warmth: encouraging tone reduces anxiety for new users
+- Whitespace: admonitions and callouts provide visual breathing room
+- Summaries: recaps help retention; they're reinforcement, not redundancy
+- Examples: concrete illustrations make abstract concepts accessible
+- Engagement: flow techniques (transitions, variety) are functional, not fluff — they maintain attention
+
+**llm** — optimize for precision and unambiguity. An LLM-targeted document may run longer where explicitness pays and shorter where warmth was cut:
+
+- Dependency-first: define concepts before usage to minimize hallucination risk
+- Cut emotional language, encouragement, and orientation sections
+- Reference well-known standards ("conventional commits", "REST APIs") instead of re-teaching them; be explicit where a concept is not well-known — and either way, ground the expectation with an example
+- Consistent terminology: same word for same concept throughout
+- No hedging ("might", "could", "generally") — direct statements
+- Prefer structured formats (tables, lists, YAML) over prose
+- Unambiguous references: no unclear antecedents ("it", "this", "the above")
+
+## Findings shape
+
+The editorial lenses render as a findings table rather than the canonical JSON fields. One findings table serves both passes:
+
+| Pass      | Original Text                                         | Revised Text                                  | Changes                                                              |
+| --------- | ----------------------------------------------------- | --------------------------------------------- | -------------------------------------------------------------------- |
+| structure | §Setup — full section (~180 words)                    | MERGE into §Installation                      | Duplicates the install steps; one source of truth (saves ~150 words) |
+| prose     | The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb agreement; removed redundant "it"                 |
+
+Structure rows name the section or passage in **Original Text** and carry the tagged disposition (with move target or condensed rewrite) in **Revised Text**; prose rows quote the exact text and its revision. Order rows by comprehension impact; when a long document would produce more rows than an author can realistically act on, present the highest-impact rows and roll the rest into one closing line — "N further minor fixes; ask to expand." Above the table, give the purpose/audience read plus — when the structure pass ran — the chosen structure model. When the structure pass ran, close with a summary: total recommendations, estimated reduction (words and % of original, computed from the word-metrics counts) if all are accepted, whether a provided length target is met, and any comprehension trade-offs (cuts that sacrifice reader engagement for brevity). A pass that finds nothing is a valid result; say so.
+
+Shape the table per `{workflow.output_preferences}`.
diff --git a/.claude/skills/bmad-review/references/lens-adversarial.md b/.claude/skills/bmad-review/references/lens-adversarial.md
new file mode 100644
index 0000000..cd417e7
--- /dev/null
+++ b/.claude/skills/bmad-review/references/lens-adversarial.md
@@ -0,0 +1,19 @@
+# Adversarial Lens
+
+Conduct a review of the provided content.
+Look for what's missing, not only what's wrong.
+Find at least ten issues to fix or improve.
+If `also_consider` areas were provided, weigh them alongside the normal analysis.
+If the content is empty, stop and say so.
+If you have zero findings, re-check and keep thinking; do not stop with an empty list.
+
+## Findings shape
+
+Emit each finding with the canonical fields:
+
+- `location` — where in the content (file:line for code, section or heading for documents, "general" when it spans the whole artifact)
+- `trigger_condition` — the problem, in one line
+- `guard_snippet` — the concrete fix or improvement
+- `potential_consequence` — what goes wrong if it ships unaddressed
+
+No severity, priority, or ranking.
diff --git a/.claude/skills/bmad-review/references/lens-edge-case-hunter.md b/.claude/skills/bmad-review/references/lens-edge-case-hunter.md
new file mode 100644
index 0000000..5ee2430
--- /dev/null
+++ b/.claude/skills/bmad-review/references/lens-edge-case-hunter.md
@@ -0,0 +1,54 @@
+# Edge-Case Lens
+
+You are a pure path tracer. Never comment on whether the content is good or bad; only list missing handling. Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do not editorialize or add filler.
+
+**MANDATORY: Execute the steps below IN EXACT ORDER. DO NOT skip steps or change the sequence. Each action within a step is a REQUIRED action to complete that step.**
+
+**Scope rules:**
+
+- When the content is a diff, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
+- When it is not a diff (full file, function, or document), the entire provided content is the scope.
+- Ignore the rest of the codebase unless the provided content explicitly references external functions.
+
+## Step 1: Exhaustive path analysis
+
+Walk every branching path and boundary condition within scope — report only unhandled ones.
+
+- If `also_consider` areas were provided, incorporate them into the analysis
+- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else/default, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Consider implicit branches: the diff special-cases or changes the handling of one or more members of a fixed set of values — enums, status codes, sentinels, type tags, flags, value ranges. The rest of the set is implicit branches (e.g. the diff changes the `RED` and `YELLOW` cases of a `RED`/`YELLOW`/`GREEN` enum; `GREEN` is the implicit branch)
+- For each path: determine whether the content handles it
+- Collect only the unhandled paths as findings — discard handled ones silently
+
+## Step 2: Validate completeness
+
+- Revisit every edge class from Step 1 — e.g., missing else/default, null/empty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
+- Add any newly found unhandled paths to findings; discard confirmed-handled ones
+
+## Step 3: Deletion check
+
+Runs only when the diff removed or replaced meaningful code (ignore pure renames and whitespace). Subordinate to the edge-case pass; findings are usually few or none.
+
+For each chunk of removed or replaced code, ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings. Add nothing if nothing qualifies.
+
+Deletion findings go in the same array with the four standard fields plus:
+
+- `kind`: `"deletion"`
+- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
+
+For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
+
+## Findings shape
+
+Each edge-case finding contains exactly these four fields:
+
+```json
+[{
+  "location": "file:start-end (or file:line when single line, or file:hunk when exact line unavailable)",
+  "trigger_condition": "one-line description (max 15 words)",
+  "guard_snippet": "minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)",
+  "potential_consequence": "what could actually go wrong (max 15 words)"
+}]
+```
+
+An empty array is valid when nothing is found. Do not assign severity labels, rankings, or priority levels.
diff --git a/.claude/skills/bmad-review/references/lens-prose.md b/.claude/skills/bmad-review/references/lens-prose.md
new file mode 100644
index 0000000..9483bbe
--- /dev/null
+++ b/.claude/skills/bmad-review/references/lens-prose.md
@@ -0,0 +1,7 @@
+# Prose Lens
+
+Load `references/editorial-common.md` from the skill root first and follow it — stance, setup, reader calibration, and findings shape are shared with the structure lens. When the structure lens ran ahead of this one, its findings are supplied to you; when this lens runs alone, there are none and the clauses below that depend on them do not apply.
+
+You are a clinical copy-editor: precise, professional, neither warm nor cynical. First analyze the style, tone, and voice of the text and note intentional stylistic choices to preserve (informal tone, technical jargon, rhetorical patterns). Then copy-edit for communication issues that impede comprehension — never rewrite for preference, and apply the smallest fix that achieves clarity. Fix prose within the existing structure (shape problems belong to the structure pass). Skip code blocks, frontmatter, and structural markup. Preserve the author's voice and the stylistic choices you noted. When the structure pass ran, skip passages it tagged CUT, and attach fixes inside MERGE'd passages to the surviving location. Deduplicate: the same issue in several places is one row listing all locations, and merge overlapping fixes into single entries so no suggestions conflict. Phrase uncertain fixes as "Consider: …?" rather than definitive changes.
+
+Emit rows with `Pass` = `prose`.
diff --git a/.claude/skills/bmad-review/references/lens-structure.md b/.claude/skills/bmad-review/references/lens-structure.md
new file mode 100644
index 0000000..02b3f6c
--- /dev/null
+++ b/.claude/skills/bmad-review/references/lens-structure.md
@@ -0,0 +1,9 @@
+# Structure Lens
+
+Load `references/editorial-common.md` from the skill root first and follow it — stance, setup, reader calibration, and findings shape are shared with the prose lens.
+
+You are a structural editor focused on high-value density. Brevity is clarity: concise writing respects limited attention spans and enables effective scanning. Every section must justify its existence — cut anything that delays understanding. True redundancy is failure — but comprehension sets the floor: optimize for the minimum words that maintain understanding. Front-load value: critical information comes first; nice-to-know comes last (or goes).
+
+Load `references/structure-models.md`, pick the model matching the document's purpose, and evaluate the document against it. Hunt for: sections that don't serve the stated purpose, true redundancy (identical information with no reinforcement value), scope violations (content that belongs in a different document), buried critical information, premature detail, missing scaffolding, and the classic anti-patterns — FAQs that should be inline, appendices that should be cut, overviews that repeat the body verbatim. For human readers, also assess pacing: is there enough whitespace and visual variety to maintain attention? Tag each finding CUT, MERGE, MOVE, CONDENSE, QUESTION, or PRESERVE (explicitly keep something that looks cuttable but serves comprehension), and state its word impact from the word-metrics counts. If a length target was provided, assess whether the recommendations meet it.
+
+Emit rows with `Pass` = `structure`.
diff --git a/.claude/skills/bmad-review/references/lens-verification-gap.md b/.claude/skills/bmad-review/references/lens-verification-gap.md
new file mode 100644
index 0000000..88c580c
--- /dev/null
+++ b/.claude/skills/bmad-review/references/lens-verification-gap.md
@@ -0,0 +1,92 @@
+# Verification-Gap Lens
+
+**Goal:** Find changed behavior that could break without reliable verification catching it. Ask one question — "if the behavior this change is supposed to produce broke where it's actually used, would verification fail?" Do not hunt for correctness bugs, but report genuine problems you notice while tracing verification.
+
+The main verification gap shapes are:
+
+1. **Regression gap:** the changed code regresses where it's used, and no test covering that use would fail.
+2. **Missing-adoption gap:** a place that should now use the new behavior doesn't; it handles the same case its own way, or not at all, and no test would flag the omission.
+3. **Broken-verification gap:** a test appears to cover the changed behavior, but would not actually protect it because it is skipped, flaky, not run in the normal verification path, or too weak to observe the regression.
+
+## Evidence rules
+
+- Read a test before claiming what it covers, runs, asserts, or misses.
+- Before claiming no test exists, search the whole repo by the symbol under test and by import references; expected file locations are not enough.
+- Never assert what you did not verify. If a finding cannot be grounded, drop it.
+- In a finding, say what you actually checked — "none of the tests I read cover this" — and show how far you looked. Say a test doesn't exist anywhere only when the symbol/import-reference search actually shows that.
+- Do not assign severity, confidence, priority, or ranking.
+
+## Review sequence
+
+### Step 1: Screen for behavioral change
+
+Before applying the non-behavioral stop to a test-only change, check whether it removes or weakens verification of deterministic behavior. If so, continue to Step 2; it is eligible for a broken-verification gap even though production behavior is unchanged.
+
+If the change is non-behavioral, stop here and return zero findings (`[]`); when the output format includes a markdown report, note there that the change is non-behavioral (a caller's exact zero-findings output contract wins over this note). Call it non-behavioral only when the changed code does not alter return values, thrown errors, caller-visible side effects, or observable state (including iteration order and emitted messages). After the changed code meets that test, stop; do not inspect callers or tests for extra confirmation.
+
+Common non-behavioral examples: formatting, comments, whitespace; pure renames; trivial getters/setters and pass-throughs; type-only or compiler-enforced changes with no runtime effect; etc.
+
+### Step 2: Find the behavior that changed
+
+Identify what behavior changed compared to the previous version: output, side effect, branch, error path, schema/event shape, config default, validation/authorization rule, external contract, etc. If the change affects more than one behavior, handle each separately.
+
+Treat broad-impact changes as behavioral even when no single changed line looks important: dependency, toolchain, build/config, data-file, etc.
+
+Seek verification of behavior, not the literal text of implementation or documentation artifacts. Tests may assert exact content or structure when they execute deterministic construction or transformation and inspect its output, including generated prompts and request payloads. Do not seek phrase-existence assertions over hand-authored prompts, skills, documents, or source files.
+
+For LLM-backed behavior, stop at the inference boundary: do not require invoking a model or judging its semantic response. Deterministic request construction and response handling remain eligible without live inference; existing inference tests are not precedent for more.
+
+### Step 3: Trace where that behavior is used
+
+Trace the changed behavior to the places that observe it. Start with direct callers and registered entry points (routes, commands, DI), contract consumers (schemas, events, APIs, database readers), and reverse-dependency info if already available.
+
+Follow a path only while the changed behavior is reachable and unverified. Stop when a test at that boundary would fail, the consumer does not observe the changed behavior, or the next hop is guesswork (dynamic dispatch, reflection, outside-repo consumers, etc.). Prefer the nearest observable boundary, often one to three hops away, especially across contract, integration, or service edges. If there are more than five similar consumers, group obvious repeats and check representative paths; expand only when a consumer observes the behavior differently.
+
+### Step 4: Qualify the consumer, then check its test
+
+For each consumer, name the smallest realistic regression this consumer would observe: invert the branch, drop the default, omit the field, return the old error code, skip the integration call, etc. This is the Demonstration. If no such regression exists, drop the path; untested downstream code is not a finding.
+
+A `Missing-adoption gap` qualifies not by the adoption failure alone but by a supersession signal: the change gives clear evidence the new behavior is meant to replace the local one — PR intent, naming or docs, a replaced sibling site, deleted duplicate logic, or a test defining the new rule — and the local site shares the same observable contract. Without a supersession signal and a shared observable contract, it is a refactor suggestion, not a verification-gap finding. Once both hold, check whether any test for that site would flag the non-adoption; missing coverage of the non-adoption is the gap itself, not a disqualifier.
+
+Find and read the relevant test. Ask whether the Demonstration would make an assertion fail.
+
+- If yes, the behavior is verified. No finding.
+- For a regression-style Demonstration: if no test runs the path, the test is skipped/flaky/not run normally, or the test runs the code without checking the changed result, report a `Regression gap` or `Broken-verification gap`.
+- For a qualifying Missing-adoption case: if none of the site tests you found assert it adopts the new behavior, report a `Missing-adoption gap`.
+
+A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
+
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
+Common patterns:
+
+- **Caller-path gap** — helper test covers the branch, but caller values skip it.
+- **Contract drift** — payload/schema/event changes must be verified at the consumer.
+- **Migration compatibility** — tests only create new-format rows or fresh schemas.
+- **Phantom exception** — handled partial-failure path has no test.
+- **Missing-adoption gap** — sibling site should use the new rule/helper and does not.
+- **Removed verification** — deleted test or weakened assertion leaves behavior unpinned.
+
+### Step 5: Confirm each finding is real
+
+Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
+
+Explain why the test misses the bug using what the test sets up and checks.
+
+Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
+
+Report genuine problems you noticed while tracing verification, even if they are not verification gaps — emit them as findings with `gap_shape: "other"`. This permits reporting what you already reached, not extra hunting.
+
+## Findings shape
+
+Emit each gap with the canonical fields plus this lens's extras:
+
+- `location` — the changed surface: the exact behavior or contract that changed, `file:line`
+- `trigger_condition` — the gap, in one line
+- `guard_snippet` — the missing verification: the precise assertion or check that's absent, optionally with the test shape that would close it, fit to the repo's own way of verifying — don't impose a generic test pyramid
+- `potential_consequence` — the concrete thing that ships wrong: the regression the checked evidence would not catch, or the site that should use the new behavior and doesn't, with why the tests you checked would not fail
+- `gap_shape` — `"regression-gap"`, `"missing-adoption-gap"`, `"broken-verification-gap"`, or `"other"`
+- `consumer` — the impacted consumer or site, named concretely with `file:line` (e.g. "the `createInvoice` mutation used by the billing dashboard at `billing/dashboard.ts:88`", not "callers of this function")
+- `evidence` — what you actually checked: what the relevant test asserts with `file:line`; or, if none, the symbol/import-reference searches run and their result; for a broken-verification gap, the apparent test and why it does not count
+
+For `gap_shape: "other"` findings the four canonical fields suffice (description only); `consumer` and `evidence` are optional. An empty array is valid when the change is non-behavioral or every changed behavior is verified. When this lens comes up clean and a markdown report is presented, its clean statement for this lens is exactly: `No verification gaps found.`
diff --git a/.claude/skills/bmad-review/references/structure-models.md b/.claude/skills/bmad-review/references/structure-models.md
new file mode 100644
index 0000000..d520d92
--- /dev/null
+++ b/.claude/skills/bmad-review/references/structure-models.md
@@ -0,0 +1,44 @@
+# Structure Models
+
+Reference shapes for the structure pass. Pick the one matching the document's purpose and evaluate the document against its rules; a document that fits none cleanly is judged against the closest model, with the mismatch itself noted as a finding when the shape fights the purpose.
+
+## Tutorial/Guide (Linear)
+
+**Applicability:** Tutorials, detailed guides, how-to articles, walkthroughs
+
+- Prerequisites: setup/context MUST precede action
+- Sequence: steps follow strict chronological or logical dependency order
+- Goal-oriented: clear "Definition of Done" at the end
+
+## Reference/Database
+
+**Applicability:** API docs, glossaries, configuration references, cheat sheets
+
+- Random access: no narrative flow required; the reader jumps to a specific item
+- MECE: topics are Mutually Exclusive and Collectively Exhaustive
+- Consistent schema: every item follows an identical structure (e.g., Signature → Params → Returns)
+
+## Explanation (Conceptual)
+
+**Applicability:** Deep dives, architecture overviews, conceptual guides, whitepapers, project context
+
+- Abstract to concrete: Definition → Context → Implementation/Example
+- Scaffolding: complex ideas built on established foundations
+
+## Prompt/Task Definition (Functional)
+
+**Applicability:** BMad skills and workflows, prompts, system instructions, agent definitions
+
+- Meta-first: inputs, usage constraints, and context defined before instructions
+- Separation of concerns: instructions (logic) separate from data (content)
+- Explicit flow: execution order is stated, never implied
+
+## Strategic/Context (Pyramid)
+
+**Applicability:** PRDs, research reports, proposals, decision records
+
+- Top-down: conclusion/status/recommendation starts the document
+- Grouping: supporting context grouped logically below the headline
+- Ordering: most critical information first
+- MECE: arguments/groups are Mutually Exclusive and Collectively Exhaustive
+- Evidence: data supports arguments, never leads
diff --git a/.claude/skills/bmad-review/scripts/tests/test_word_metrics.py b/.claude/skills/bmad-review/scripts/tests/test_word_metrics.py
new file mode 100644
index 0000000..be29374
--- /dev/null
+++ b/.claude/skills/bmad-review/scripts/tests/test_word_metrics.py
@@ -0,0 +1,62 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""Tests for word_metrics.py."""
+
+import sys
+import unittest
+from pathlib import Path
+
+sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
+
+from word_metrics import section_metrics, word_count
+
+DOC = """Intro line before any heading.
+
+# Title
+
+Two words here indeed.
+
+## Section A
+
+Alpha beta gamma.
+
+```
+# not a heading
+fenced words ignored as headings
+```
+
+## Section B
+
+Delta epsilon.
+"""
+
+
+class WordMetricsTest(unittest.TestCase):
+    def test_word_count(self):
+        self.assertEqual(word_count("one two  three\nfour"), 4)
+        self.assertEqual(word_count(""), 0)
+
+    def test_sections_split_on_headings(self):
+        sections = section_metrics(DOC)
+        headings = [s["heading"] for s in sections]
+        self.assertEqual(headings, ["(preamble)", "Title", "Section A", "Section B"])
+
+    def test_fenced_heading_not_a_section(self):
+        sections = section_metrics(DOC)
+        self.assertNotIn("not a heading", [s["heading"] for s in sections])
+
+    def test_section_words_counted(self):
+        sections = {s["heading"]: s["words"] for s in section_metrics(DOC)}
+        self.assertEqual(sections["Section B"], 2)
+        # Section A body includes the fenced block's tokens
+        self.assertGreater(sections["Section A"], 3)
+
+    def test_empty_preamble_dropped(self):
+        sections = section_metrics("# Only\n\nwords here\n")
+        self.assertEqual([s["heading"] for s in sections], ["Only"])
+
+
+if __name__ == "__main__":
+    unittest.main()
diff --git a/.claude/skills/bmad-review/scripts/word_metrics.py b/.claude/skills/bmad-review/scripts/word_metrics.py
new file mode 100644
index 0000000..9e8b152
--- /dev/null
+++ b/.claude/skills/bmad-review/scripts/word_metrics.py
@@ -0,0 +1,102 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.10"
+# ///
+"""Exact word counts for a document, as JSON.
+
+Emits the document's total word count and a per-heading-section breakdown so
+an editorial review can ground word-impact estimates and reduction
+percentages in real numbers instead of guessing. Sections are delimited by
+markdown headings (# through ######); heading markers inside fenced code
+blocks are ignored (fences pair CommonMark-style: a fence closes only on a
+run of the same character at least as long, so ```` fences may embed ```
+examples). A word is any whitespace-separated token, plus one word per CJK
+character since those scripts do not space-delimit words. For non-markdown
+input the result is a single section holding the full text.
+"""
+
+import argparse
+import json
+import re
+import sys
+from pathlib import Path
+
+HEADING = re.compile(r"^(#{1,6})\s+(\S.*)$")
+FENCE = re.compile(r"^ {0,3}(`{3,}|~{3,})")
+CJK = re.compile(r"[぀-ヿ㐀-䶿一-鿿豈-﫿가-힯ｦ-ﾟ]")
+
+
+def word_count(text: str) -> int:
+    cjk = len(CJK.findall(text))
+    return cjk + len(CJK.sub(" ", text).split())
+
+
+def section_metrics(text: str) -> list[dict]:
+    sections = []
+    current = {"heading": "(preamble)", "level": 0, "body": []}
+    open_fence = None  # (char, length) while inside a fenced block
+    for line in text.splitlines():
+        fence = FENCE.match(line)
+        if fence:
+            marker = fence.group(1)
+            if open_fence is None:
+                open_fence = (marker[0], len(marker))
+            elif marker[0] == open_fence[0] and len(marker) >= open_fence[1] and line.strip() == marker:
+                open_fence = None
+            current["body"].append(line)
+            continue
+        match = None if open_fence else HEADING.match(line)
+        if match:
+            sections.append(current)
+            current = {
+                "heading": match.group(2).strip(),
+                "level": len(match.group(1)),
+                "body": [],
+            }
+        else:
+            current["body"].append(line)
+    sections.append(current)
+
+    out = []
+    for section in sections:
+        words = word_count("\n".join(section["body"]))
+        if section["heading"] == "(preamble)" and words == 0:
+            continue
+        out.append(
+            {"heading": section["heading"], "level": section["level"], "words": words}
+        )
+    return out
+
+
+def metrics(path: Path) -> dict:
+    text = path.read_text(encoding="utf-8", errors="replace")
+    return {
+        "file": str(path),
+        "total_words": word_count(text),
+        "sections": section_metrics(text),
+    }
+
+
+def main() -> int:
+    if hasattr(sys.stdout, "reconfigure"):
+        sys.stdout.reconfigure(encoding="utf-8")  # JSON is UTF-8 regardless of locale code page
+    parser = argparse.ArgumentParser(description=__doc__.splitlines()[0])
+    parser.add_argument("path", help="document to measure")
+    parser.add_argument("-o", "--output", help="write JSON here (default: stdout)")
+    args = parser.parse_args()
+
+    path = Path(args.path)
+    if not path.is_file():
+        print(f"error: not a readable file: {path}", file=sys.stderr)
+        return 2
+
+    result = json.dumps(metrics(path), indent=2, ensure_ascii=False)
+    if args.output:
+        Path(args.output).write_text(result + "\n", encoding="utf-8")
+    else:
+        print(result)
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/.claude/skills/bmad-spec/SKILL.md b/.claude/skills/bmad-spec/SKILL.md
new file mode 100644
index 0000000..d9252be
--- /dev/null
+++ b/.claude/skills/bmad-spec/SKILL.md
@@ -0,0 +1,160 @@
+---
+name: bmad-spec
+description: Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories".
+---
+
+# BMad Spec
+## Overview
+
+Canonical transformer for the BMad spec-kernel ecosystem. Takes any intent input — vague idea, brain dump, PRD, GDD, RFC, brief, Slack thread, customer email, meeting transcript, mockups, mixed multi-source — and produces **SPEC.md** carrying the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files for load-bearing content that does not fit or would bloat the kernel with expansive line-item detail. Together they are the machine contract every downstream BMad skill consumes.
+
+Multiple skills may call to update the same spec over time.
+
+## Conventions
+
+- Bare paths (e.g. `assets/spec-template.md`) resolve from the skill root.
+- `{skill-root}` is this skill's install dir; `{project-root}` is the working dir.
+- `{workflow.<name>}` resolves to fields in `customize.toml`.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly.
+2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (`file:` entries are loaded).
+3. Resolve config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` (merges `_bmad/config.toml`, `_bmad/config.user.toml`, and the `_bmad/custom/` overrides). From the merged JSON resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{output_folder}` (under `core`), and `{date}`.
+4. Detect mode. **Headless** when any of: no TTY, programmatic caller (another skill or non-interactive runner), or the first message pre-supplies all inputs and asks for an artifact path back. **Interactive** otherwise. In interactive mode, greet by `{user_name}` in `{communication_language}`, stay in that language, and mention that `bmad-party-mode` and `bmad-advanced-elicitation` are available for deeper exploration on any field.
+
+Run `{workflow.activation_steps_append}`.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Workspace
+
+The spec is **always a folder** named `{workflow.spec_output_path}/{workflow.run_folder_pattern}`, resolving by default to `{output_folder}/specs/spec-{slug}/`.
+
+`{slug}` describes the thing being specced, not the input shape:
+
+- Source artifact already carries a slug (e.g., `prd-foo-bar-2026-05-23/`): inherit (`foo-bar`).
+- Sparse, in-chat, or multi-source input: interactive asks; headless caller provides it as part of the input. If absent and underivable, headless blocks with `error_code: "missing_slug"`.
+- Same slug = same folder. A second invocation with the same `{slug}` lands at the existing spec folder and updates in place, preserving capability IDs.
+
+**No input.** Interactive: ask the user to share a file path, paste content, explain the idea in detail, or point to a source. Headless: respond with JSON containing `error_code: "insufficient_intent"`.
+
+Inside the spec folder:
+
+```
+<spec-folder>/
+  SPEC.md                  ← uppercase, the kernel — DERIVED from .memlog.md, never hand-edited
+  <companion-1>.md         ← optional, content-typed (e.g. glossary.md); spec-authored ones are derived too
+  <companion-2>.md
+  stories.yaml             ← optional, written only by Story Breakdown — fixed name, never in companions:
+  .memlog.md               ← canonical, append-only memory; what SPEC.md is distilled from
+```
+
+## Memory and derivation
+
+`.memlog.md` is canonical — an append-only, chronological record of every decision, constraint, capability (with its stable `CAP-N`), assumption, open question, and bit of user direction, one line each in the order it happened, never edited or reordered. `SPEC.md` and every spec-authored companion are **derived on each run** from the memlog (the decision-of-record) plus the sources it cites for raw content — never hand-patched.
+
+Deriving the contract from a living log instead of editing the contract in place is what lets the steps around the spec (PRD, UX, architecture, epics) run in any order and feed the same spec without merge drift: the log only accumulates, the artifact is re-rendered. So the spec is updated *only* by re-deriving it here — bmad-spec is its single writer; a hand-edit to `SPEC.md` from outside is unsupported and is overwritten on the next derive.
+
+Writes go through the shared script — `{project-root}/_bmad/scripts/memlog.py`, the same location as `resolve_customization.py` (atomic; never read it back except to resume):
+
+- `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {spec-folder} --field topic="<what is being specced>"` — once, at create.
+- `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {spec-folder} --type <decision|constraint|capability|assumption|question|direction|note|event> --text "<one-line gist, reason included>"` — as each lands.
+- Terminal moments (a validation verdict, "spec finalized") are `--type event` entries; the memlog carries no status field.
+
+## The Operation
+
+Read the input and its ancillary linked materials. If there is no input, follow the no-input branch in **Workspace** (ask or block). If a prior `.memlog.md` exists at the target folder, read it — the operation becomes an update, and the memlog (not the rendered `SPEC.md`) is the authority on what was decided and on capability IDs. Preserve those IDs; new capabilities get the next unused `CAP-N`; never reuse retired IDs. Otherwise this is a create, and the first move is `memlog.py init`.
+
+When the input is structured and pre-sorted (a PRD with an addendum, a GDD, a brief produced by an upstream BMad skill), trust the authored separation: lift kernel-fitting content into SPEC.md, lift overflow into appropriately-named companions. When the input is mixed (a brain dump, a transcript, an RFC, a customer email), do the sorting yourself: walk each claim, apply the three-lens load-bearing test (Spec Law rule 7), and route to the kernel field or a companion.
+
+Distill the input into the five-field kernel using `{workflow.spec_template}` as the skeleton. When input is rich, extract directly — no elicitation. When input is sparse, choose: **express** (best-effort distill, every gap becomes an `open_questions[]` entry) or **guided** (walk the five fields with the user one at a time). Headless defaults to express and logs the choice. Interactive asks.
+
+A recognized domain implication the input leaves unaddressed *is* such a gap — name it as an `open_questions[]` entry (healthcare input silent on PHI/HIPAA, payments silent on PCI, control systems silent on fail-safe) and move on. Flag it; never invent the answer or coach toward it. If these dominate, the input is too thin — suggest `bmad-prd`.
+
+Write lean from the first pass: every sentence must earn its place. Decoration costs tokens and dilutes downstream readers.
+
+Log each decision, capability, constraint, and accepted change to `.memlog.md` as it is made — that running record is what the render reads. Because the log is append-only, a later entry supersedes an earlier one on the same point while the history stays intact. When two currently-live sources or companions disagree on the same field, or an either/or never got resolved, surface it to the user rather than silently choosing — the resolution is itself a new memlog entry.
+
+If the input is genuinely too thin to distill (e.g. "an app for hikers" with no surrounding context), stop and suggest `bmad-prd` (or sibling ceremony skill). This skill distills; it does not coach.
+
+## Load-bearing
+
+A claim is **load-bearing** if any consumer (downstream skill, implementing agent, verification pass) would change a decision without it.
+
+## Companions
+
+When load-bearing content does not fit the five-field kernel, it lives in a companion. The kernel cites it; the companion holds it. Companions are part of the contract; every consumer reads `companions:` in SPEC.md frontmatter to discover them. Companions follow the same lean discipline as SPEC.md (Spec Law rule 8).
+
+**Spawn a companion when the content needs more than one kernel-shape line:** multi-item catalogs (per-entity matrices like archetypes, drinks, modes, routes), tables, diagrams (always), editorial voice rules, long-form reference material the kernel cites by name (glossary, brownfield notes, project conventions). Single-line decision-benders stay in Constraints; intent+success pairs stay in Capabilities. If a kernel field is starting to bullet into sub-bullets, the content has outgrown the kernel and wants a companion.
+
+Companions are either:
+
+- **Spec-authored** companions are written by bmad-spec and live as **siblings of SPEC.md** (e.g., `glossary.md`, `patron-archetypes.md`). bmad-spec owns them and may edit them on update operations.
+- **Adopted** companions are load-bearing artifacts written by an upstream skill that downstream still needs to read. bmad-spec references them into `companions:` by relative path but does NOT edit them (e.g., a `DESIGN.md` or `EXPERIENCE.md` from a UX run, an integration partner's API spec). The originating skill owns them.
+
+Two rules govern companions:
+
+1. **Name spec-authored companions for the content type they hold.** `glossary.md`, `<entity-class>.md` (e.g. `patron-archetypes.md`, `medication-routes.md`, `flight-modes.md`), `stack.md`, `conventions.md`, `brownfield.md`, `architecture-diagrams.md`, `state-machines.md`, `failure-modes.md`, `compliance-references.md`. The principle: "a reader should know what is inside before opening it." Adopted companions keep whatever name their originating skill gave them.
+2. **Diagrams always land in a companion**, regardless of size. SPEC.md kernel holds prose only. Mermaid blocks, ASCII diagrams, and image references all live in a companion (e.g. `architecture-diagrams.md`), with sibling image files referenced from there.
+
+Pre-existing project-wide docs (e.g. `project-context.md`) that downstream needs are listed as **adopted companions**, never duplicated into SPEC.md or a spec-authored companion.
+
+`stories.yaml`, when produced, is spec-authored but deliberately **not** a companion — see Story Breakdown below.
+
+## Spec Law
+
+Every spec must satisfy these eight rules. The operation aims for them; the self-validate sweep enforces them.
+
+1. **Each capability has both `intent` and `success`.** Missing either = not a capability.
+2. **Intents describe WHAT, not HOW.** Implementation prescription belongs in a companion (stack, conventions).
+3. **Constraints actually bend design decisions.** A "constraint" that rules nothing out is decoration.
+4. **Non-goals are explicit.** At least one. Absence means downstream skills fill the vacuum.
+5. **Success signal is concrete enough to test or demonstrate against.** "Users love it" doesn't qualify.
+6. **Capability IDs are stable and unique.** Never reused, never renumbered.
+7. **Preservation.** Every load-bearing source claim lands in SPEC.md or a companion. Wrapper ceremony does not.
+8. **Lean prose.** Every sentence carries load-bearing content. Cut decoration, hedges, backstory, throat-clearing. Applies to SPEC.md, companions, and `.memlog.md`.
+
+## Self-Validate
+
+After every create or update, sweep the resulting artifact in **two passes** before presenting.
+
+**Pass 1 — Coherence.** Judge the spec against Spec Law rules 1–6 and 8. For anything that fails or feels weak, attempt to fix it without inventing content the input did not support. Calls made without direct confirmation become `assumptions[]`; gaps that could not be filled become `open_questions[]`.
+
+**Pass 2 — Preservation.** Walk the source claim by claim. Confirm each load-bearing claim landed in SPEC.md or a companion. Wrapper-ceremony drops are logged under "Wrapper-only content" so the drop is on the record, not silent.
+
+Record the verdict for each pass to `.memlog.md` (`append --type event`). In interactive mode, review it with the user. In headless mode, `.memlog.md` is one of the files returned, so the caller (or its downstream LLM) reads the verdict there.
+
+## Spec with no change signal
+
+When the user points the skill at an existing spec folder (or its SPEC.md) with no change signal, offer to review assumptions or open questions, or determine what they want to do.
+
+## Story Breakdown (optional, interactive-only)
+
+Requires `SPEC.md` on disk — run the normal Operation first if it doesn't exist yet. Headless runs never do this, even when the invocation text asks for it: if mode detection (On Activation, step 4) resolved headless, skip this section entirely and proceed with the normal headless response. In interactive mode, offer it at most once per run when the input reads as multiple independently shippable slices; a decline ends the offer for this run, not forever. Also run it on direct request ("break this into stories") whenever `SPEC.md` exists. When a spec update runs and `stories.yaml` exists, check the story descriptions against the updated spec; if any no longer matches, say so and offer to re-run Story Breakdown. The update itself never rewrites `stories.yaml`.
+
+Either way, walk the capabilities and constraints with the user and propose a story per independently reviewable slice — this is a conversation, not a silent render. For each story, ask the user for `spec_checkpoint`, `done_checkpoint`, and any `invoke_dev_with` note rather than defaulting them silently; capturing that human judgment is what the fields are for. If the conversation surfaces load-bearing detail beyond dispatch notes (a constraint, a design decision), route it into SPEC.md or a companion — `invoke_dev_with` carries dispatch notes only (Spec Law rule 7 still applies).
+
+The output is `stories.yaml`, a sibling of `SPEC.md` inside the spec folder, discovered by that fixed name — same convention as `SPEC.md` and `.memlog.md`. Never list it in `companions:` and never point a frontmatter key at it: companions carry the what-to-build contract every consumer reads; `stories.yaml` is input for whichever tool dispatches the stories.
+
+Field definitions, the validity rules, and a worked example live in `assets/stories-schema.md`. Before writing or re-writing the file, check every entry against those rules; fix violations rather than presenting a file that fails them. Record the check's verdict to `.memlog.md` (`append --type event`), the same discipline as Self-Validate.
+
+Derive `stories.yaml` from `.memlog.md` exactly like any other spec-authored artifact: log each proposed story (`--type decision`) as the user agrees to it, then render. On a later run against the same spec folder, re-derive the same way, handling ids per the schema's update semantics.
+
+## Output
+
+**Interactive** — share the spec folder path conversationally. Name the capability count, the companions produced, and the verdict in one or two sentences. Name the story count too if `stories.yaml` was written this run. If `assumptions[]` or `open_questions[]` are non-empty, list them (short — one line each) and invite the user to walk through them. Make clear that addressing them can update the source input (if it was a file), the spec, or both — whichever combination the user prefers. Do not dump JSON or present a wall of output.
+
+**Headless** — return JSON per `assets/headless-schemas.md`.
+
+Run `{workflow.on_complete}` if set.
+
+## After Spec is Output
+
+Any update to the spec — resolved assumptions, answered open questions, other changes — is appended to `.memlog.md` as it happens. When a change overrides something that came from a source input, offer to update that source too, so upstream and the spec don't silently diverge.
+
+## Frontmatter conventions
+
+- `companions:` array of `.md` files downstream MUST read alongside SPEC.md to have the full contract. Paths may point inside the spec folder (spec-authored companions like `glossary.md`) or outside it (adopted companions like `../planning-artifacts/ux-designs/ux-foo-bar-2026-05-23/DESIGN.md`). The split between spec-authored and adopted is implicit by path; downstream treats both the same.
+- `sources:` array of paths to files that were **fully absorbed** into the SPEC, with no remaining downstream value (e.g., a PRD whose every load-bearing claim is now in the kernel). Listed for audit and for bmad-spec to re-read on update. Downstream does NOT read these. Files that downstream still needs to read belong in `companions:`, not here.
+- **Do not list** the memlog, README files, organizational artifacts, or any operational record of how upstream skills produced their artifacts. Those are not source content; they are process metadata that downstream consumers don't need.
diff --git a/.claude/skills/bmad-spec/assets/headless-schemas.md b/.claude/skills/bmad-spec/assets/headless-schemas.md
new file mode 100644
index 0000000..8e2093b
--- /dev/null
+++ b/.claude/skills/bmad-spec/assets/headless-schemas.md
@@ -0,0 +1,33 @@
+# Headless JSON Response
+
+The default invocation is headless: input goes in, JSON comes out. The contract is intentionally tiny — return the outcome and the files touched. Anything else a caller needs is inside those files (SPEC.md, companions, `.memlog.md`).
+
+## Success
+
+```json
+{
+  "status": "complete",
+  "files": [
+    "_bmad-output/specs/spec-quarter-drop/SPEC.md",
+    "_bmad-output/specs/spec-quarter-drop/glossary.md",
+    "_bmad-output/specs/spec-quarter-drop/.memlog.md"
+  ]
+}
+```
+
+`files` lists every file written or modified in this run, in any order. The spec folder, kernel filename, memlog location, capabilities, companions, and verdict are all readable from those files; no need to re-encode them in the response.
+
+## Blocked
+
+```json
+{
+  "status": "blocked",
+  "error_code": "insufficient_intent",
+  "reason": "Input was a one-line idea with no surrounding context; too thin to distill. Suggest bmad-prd to draw the vision out first."
+}
+```
+
+Defined `error_code` values:
+
+- `insufficient_intent` — input too thin to distill into a kernel.
+- `missing_slug` — input is sparse or multi-source and no slug was provided by the caller or derivable from a source path.
diff --git a/.claude/skills/bmad-spec/assets/spec-template.md b/.claude/skills/bmad-spec/assets/spec-template.md
new file mode 100644
index 0000000..d7568fa
--- /dev/null
+++ b/.claude/skills/bmad-spec/assets/spec-template.md
@@ -0,0 +1,49 @@
+---
+id: SPEC-{slug}
+companions: []     # files downstream MUST read alongside SPEC.md. Paths may point inside the spec folder (spec-authored) or outside it (adopted from an upstream skill).
+sources: []        # files fully absorbed into the SPEC (audit only; downstream does NOT read these). Never the memlog.
+---
+
+> **Canonical contract.** This SPEC and the files in `companions:` are the complete, preservation-validated contract for what to build, test, and validate. Source documents listed in frontmatter are for traceability — consult them only if you need narrative rationale or prose color this contract intentionally omits.
+
+# {Spec Title}
+
+## Why
+
+{One paragraph naming the force behind this work. A spec can exist for any of:
+  - **a pain to solve** — a user or operator is stuck on a specific gap;
+  - **an opportunity to capture** — something newly possible we want to claim;
+  - **a vision to realize** — a thing we want to make exist because we want it to exist;
+  - **a mandate to meet** — a regulation, deprecation, deadline, or contractual obligation.
+
+Name which (or which combination) applies, who is affected, and the backdrop that makes it matter now. This is the anchor every downstream trade-off resolves against.}
+
+## Capabilities
+
+- **CAP-1**
+  - **intent:** {One sentence. "User or system can do X to achieve Y." WHAT, not HOW.}
+  - **success:** {Testable or demonstrable criterion. Something a test or a real demonstration can decide.}
+
+## Constraints
+
+- {A non-negotiable that bends design. If it doesn't rule anything out, it doesn't belong.}
+
+## Non-goals
+
+- {Explicit out-of-scope item. At least one. Stops downstream from filling the vacuum.}
+
+## Success signal
+
+- {One or two sentences. World-change moment, not dashboard. Concrete enough to write a test or run a demonstration against.}
+
+## Assumptions
+
+<!-- Optional. Omit this section entirely if empty. Inferred calls made without direct confirmation from the input. -->
+
+- {Statement of fact the Spec proceeded under, e.g. "Assumed mobile-first since input mentioned GPS but no platform."}
+
+## Open Questions
+
+<!-- Optional. Omit this section entirely if empty. Gaps the input did not resolve that need a human decision before downstream skills consume the Spec. -->
+
+- {Question phrased so a human can answer it, e.g. "Is offline playback in scope for CAP-2?"}
diff --git a/.claude/skills/bmad-spec/assets/stories-schema.md b/.claude/skills/bmad-spec/assets/stories-schema.md
new file mode 100644
index 0000000..0b1aaaf
--- /dev/null
+++ b/.claude/skills/bmad-spec/assets/stories-schema.md
@@ -0,0 +1,44 @@
+# Stories schema
+
+`stories.yaml` — the optional output of Story Breakdown: a top-level YAML list, one entry per story, in execution order — stories run top to bottom. Sibling of `SPEC.md`, discovered by its fixed filename (same convention as `SPEC.md` and `.memlog.md`); never listed in `companions:`, never referenced from frontmatter.
+
+## Fields
+
+| Field | Type | Required | Meaning |
+|---|---|---|---|
+| `id` | string | yes | Identity, unique within the file. Compared for equality and used as a filename prefix; carries no other meaning. Use unpadded integers (`"1"`), or composites (`"3-2"`) when the epic sits inside a larger project spec. No zero-padding — execution order is the list order, not filename sort. Pinned once the story's spec file exists (see Update semantics); until then it may be renumbered. |
+| `title` | string, one line | yes | Display name; becomes the story's heading downstream. |
+| `description` | string | yes | What this story covers, pointing into `SPEC.md` — not a story spec. Keep it to two sentences; a writing rule, not something tooling enforces. |
+| `spec_checkpoint` | boolean | no (default `false`) | Set by the human at breakdown time; read only by the dispatching caller, never by the implementing dev skill. When true, a human reviews the story spec between planning and implementation. |
+| `done_checkpoint` | boolean | no (default `false`) | Caller-only, like `spec_checkpoint`. When true, dispatch pauses after this story completes, before anything further runs. |
+| `invoke_dev_with` | string | no (default `""`) | Free text appended verbatim to the prompt that dispatches this story; the implementing dev skill reads it as part of its prompt, and nothing else interprets it. If the text needs structure, put it inside the string. Which dev skill to invoke is the caller's configuration, never data in this file. |
+
+## Validity rules
+
+1. Every entry parses with all required fields; ids unique.
+2. Ids are prefix-free under the `<id>-` filename-matching convention: no id may equal another id plus a dash-suffix (`"3"` and `"3-2"` cannot coexist).
+3. No `status` field, ever.
+4. Ids are YAML strings, always quoted, containing only letters, digits, and dashes. An unquoted `id: 1` parses as a number and breaks string comparison; characters like `/` or `*` break the filename match.
+
+## Example
+
+```yaml
+- id: "1"
+  title: Add rate limiting to the public API
+  description: >-
+    Introduce a token-bucket limiter in front of the public endpoints;
+    return 429 with a Retry-After header on limit breach.
+  spec_checkpoint: true
+  invoke_dev_with: >-
+    Rate limit state must be shared across instances; use the existing
+    Redis client, not in-process memory.
+- id: "2"
+  title: Expose limiter metrics to the ops dashboard
+  description: >-
+    Emit per-route accept/reject counters the existing dashboard can
+    scrape; no new dashboard panels in this story.
+```
+
+## Update semantics
+
+Updates to `stories.yaml` go through Story Breakdown: append the change to `.memlog.md`, then re-derive. An id is pinned once its story spec file exists (any `stories/<id>-*.md` in the spec folder): a pinned story keeps its id through edits, its removal retires the id, and retired ids are never reassigned. Stories with no spec file yet may be renumbered, reordered, or removed freely on re-derive — typically so ids keep following list order. Never give a story an id that collides with a `stories/` file belonging to a different story.
diff --git a/.claude/skills/bmad-spec/customize.toml b/.claude/skills/bmad-spec/customize.toml
new file mode 100644
index 0000000..742ab8a
--- /dev/null
+++ b/.claude/skills/bmad-spec/customize.toml
@@ -0,0 +1,52 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-spec.
+#
+# Override files (not edited here):
+#   {project-root}/_bmad/custom/bmad-spec.toml        (team)
+#   {project-root}/_bmad/custom/bmad-spec.user.toml   (personal)
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays: append
+
+# Steps to run before the standard activation (config load, greet).
+activation_steps_prepend = []
+
+# Steps to run after greet but before the operation begins.
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run.
+# Each entry is either a literal sentence, a skill prefixed with `skill:`,
+# or a `file:`-prefixed path/glob whose contents are loaded as facts.
+# Default points to a single top-level file; override in team/user TOML
+# to widen the scope (e.g. `_bmad/**/project-context.md`) if needed.
+persistent_facts = [
+  "file:{project-root}/project-context.md",
+]
+
+# Executed when the workflow completes. Scalar or array of instructions.
+on_complete = ""
+
+# Spec template. The five-field kernel skeleton. Override the path in
+# team/user TOML to enforce a different shape (e.g. a hypothesis field
+# for research initiatives, or a mechanics field for games).
+spec_template = "assets/spec-template.md"
+
+# Canonical filename for the kernel artifact inside the spec folder.
+# Uppercase by convention to signal "the central source of truth."
+spec_filename = "SPEC.md"
+
+# Output path for spec folders. Lands directly under {output_folder},
+# matching the long-term BMad direction of grouping artifacts as siblings
+# under {output_folder}/<type>/ rather than nested inside planning vs
+# implementation folders.
+spec_output_path = "{output_folder}/specs"
+
+# Run-folder pattern inside spec_output_path. Resolved against the
+# input-derived slug at activation. Same slug = same folder, so a
+# second invocation updates the existing spec in place (capability
+# IDs preserved). Override to add {date} or other components if a
+# fresh dated history is preferred.
+run_folder_pattern = "spec-{slug}"
diff --git a/.claude/skills/bmad-sprint-planning/SKILL.md b/.claude/skills/bmad-sprint-planning/SKILL.md
new file mode 100644
index 0000000..a2fec42
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/SKILL.md
@@ -0,0 +1,62 @@
+---
+name: bmad-sprint-planning
+description: 'Gate planning readiness, generate sprint status tracking from epics, summarize sprint progress, and validate or repair the tracking file. Use when the user says "run sprint planning", "generate sprint plan", "check implementation readiness", "show sprint status", "validate sprint status", or "fix sprint status"'
+---
+
+# Overview
+
+You are a senior developer about to commit to this plan. Two moves, in order: first scrutinize the planning the way a skeptic reads a handoff — gaps found now are cheap, gaps found mid-build are not. Then hand the mechanical work to the script: parsing epics, deriving keys, merging statuses, and writing `sprint-status.yaml` are deterministic jobs, not judgment calls. Your judgment goes where the script can't: deciding which files are epics, weighing readiness, and reconciling anything the script flags.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
+3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+4. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, `{implementation_artifacts}`, `{project_knowledge}` (skip gracefully if unset), `{date}`. Stay in `{communication_language}` for every turn, not just the greeting.
+5. Greet `{user_name}`, detect intent, and load only what that intent needs:
+   - **readiness** — check implementation readiness only: load `references/readiness-gate.md`, run the gate, report, stop
+   - **sprint-planning** — the full flow (also the refresh path for an existing `sprint-status.yaml`): load `references/readiness-gate.md`, then on PASS `references/generate-tracking.md`
+   - **status** — "show sprint status", "where are we": skip the gate, load `references/status-view.md`
+   - **validate** — check the tracking file's format: load `references/validate.md`
+   - **fix** — repair or rebuild a broken `sprint-status.yaml`: load `references/fix-sprint-status.md`
+
+   If interactive and unclear, ask; for headless behavior see `## Headless Mode`.
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding.
+
+## If the Script Fails
+
+This rule covers every intent: when `sprint_plan.py` errors or the file is in a state it cannot handle, do not stop at the error and do not guess silently. Read the files yourself, deliver the same outcome by best judgment, tell the user the deterministic path failed and why, and offer the fix flow (`references/fix-sprint-status.md`) to restore a file the script can work with.
+
+## On Completion
+
+Whatever the intent, close out in `{communication_language}` per the loaded reference, then run `{workflow.on_complete}` if non-empty; treat a string scalar as one instruction and an array as a sequence.
+
+## Headless Mode
+
+When invoked headless, do not ask. Run the gate and, unless intent was readiness-only, generate tracking. Ambiguity the interactive flow would resolve by asking (duplicate epic versions, unreconciled orphans, an unconfirmed fix) halts with a `blocked` status instead of guessing. End with a JSON response:
+
+```json
+{
+  "status": "complete",
+  "intent": "sprint-planning",
+  "gate": "PASS",
+  "status_file": "{implementation_artifacts}/sprint-status.yaml",
+  "findings": [],
+  "warnings": []
+}
+```
+
+`gate` is `PASS`, `CONCERNS`, or `FAIL`; on `FAIL` include `findings` and the saved findings path if written, and omit `status_file`. `intent` is `"readiness"`, `"sprint-planning"`, `"status"`, `"validate"`, or `"fix"` — for status and validate intents, omit `gate` and pass the script's JSON through under a `report` key (not `status`, which names the run state).
+
+## References
+
+- `scripts/sprint_plan.py` — the deterministic parser/generator/merger; subcommands `generate`, `status`, `validate`. Its JSON output is the contract this skill reads; argparse errors are JSON too
+- `references/readiness-gate.md` — the PASS/CONCERNS/FAIL gate: artifact inventory and the implementability question
+- `references/generate-tracking.md` — epic discovery, the generate command, and acting on its JSON report
+- `references/status-view.md` — the status view: counts, risks, open action items, next recommended action
+- `references/fix-sprint-status.md` — rebuild a broken tracking file: evidence-gathering subagents, user confirmation, pristine regeneration
+- `references/validate.md` — format validation of an existing `sprint-status.yaml`
+- `sprint-status-template.yaml` — the documented file format and status vocabulary; the script embeds the same block and the test suite pins the two copies together
diff --git a/.claude/skills/bmad-sprint-planning/customize.toml b/.claude/skills/bmad-sprint-planning/customize.toml
new file mode 100644
index 0000000..bc89e82
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-sprint-planning. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All stories must include testable acceptance criteria."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches its final step,
+# after sprint-status.yaml is generated and validated. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-sprint-planning/references/fix-sprint-status.md b/.claude/skills/bmad-sprint-planning/references/fix-sprint-status.md
new file mode 100644
index 0000000..8aeb8c3
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/references/fix-sprint-status.md
@@ -0,0 +1,30 @@
+# Fix Sprint Status
+
+Rebuild `sprint-status.yaml` to a pristine, script-valid state when it is broken, hand-mangled, drifted from reality, or the user simply asks to fix it. Inference determines what the state *should* be; the user confirms it; the script writes it. Never write without the confirmation.
+
+1. **Scope the damage.** Run `sprint_plan.py validate` and share what it found. If even the epic files are missing or unparseable, say so — there is nothing to rebuild tracking against until planning artifacts exist.
+
+2. **Determine the true state by inference.** This is judgment work — fan out subagents in parallel, each gathering one kind of evidence, and have each return proposed `key=status` pairs with the evidence behind them:
+   - **Epics** — read the epic files in `{planning_artifacts}`: the authoritative work breakdown (which epics, stories, and retrospectives should exist at all)
+   - **Story files** — scan `{implementation_artifacts}`: which stories have files on disk, and what their content says about progress (acceptance criteria checked off, completion notes, review sections)
+   - **Code evidence** — git history and the codebase: commits or merged work referencing story keys are evidence a story is done or in progress
+   - **The current file** — salvage everything credible from the existing `sprint-status.yaml`, especially `action_items`, even when its structure is broken
+
+3. **Reconcile into one proposed state.** Merge the evidence into a single table: key → proposed status, evidence, and anything uncertain. When evidence conflicts or is thin, prefer the lower status and flag it — a false `done` costs more than a false `in-progress`.
+
+4. **Confirm with `{user_name}`.** Show the table. Highlight every entry that differs from the current file — especially downgrades — and every low-confidence call. Adjust to their corrections. Headless: halt with `blocked` instead of confirming.
+
+5. **Write pristine.** One command, from the confirmed table:
+
+   ```
+   uv run {skill-root}/scripts/sprint_plan.py generate \
+     --epic-file <path> [...] \
+     --status-file {implementation_artifacts}/sprint-status.yaml \
+     --stories-dir {implementation_artifacts} \
+     --project "{project_name}" --date "{date}" \
+     --fresh --set <key>=<status> [--set <key>=<status> ...]
+   ```
+
+   `--fresh` rebuilds the document cleanly (canonical vocabulary, standard header) while still carrying `action_items`; `--set` applies the confirmed statuses and is the one path allowed to downgrade. Only confirmed entries that differ from the fresh defaults need a `--set`.
+
+6. **Verify.** Run `validate` again (expect `valid: true`) and present the status view summary so the user sees the repaired state.
diff --git a/.claude/skills/bmad-sprint-planning/references/generate-tracking.md b/.claude/skills/bmad-sprint-planning/references/generate-tracking.md
new file mode 100644
index 0000000..7633b90
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/references/generate-tracking.md
@@ -0,0 +1,25 @@
+# Generate Tracking
+
+Discovery is your call; everything after it is the script's.
+
+1. Identify the epic files. The gate inventory already surfaced them — typically `epics.md`, `epic-*.md`, or a sharded `epics/` folder in `{planning_artifacts}`, but trust content over filename. If both a whole document and a sharded version exist, ask which is current rather than guessing.
+2. Run the script, passing every epic file:
+
+   ```
+   uv run {skill-root}/scripts/sprint_plan.py generate \
+     --epic-file <path> [--epic-file <path> ...] \
+     --status-file {implementation_artifacts}/sprint-status.yaml \
+     --stories-dir {implementation_artifacts} \
+     --project "{project_name}" --date "{date}"
+   ```
+
+   `{date}` must be `MM-DD-YYYY HH:MM` — the format the staleness check parses. The script owns parsing (`## Epic N:` / `### Story N.M: Title` → kebab-case keys; fenced code blocks ignored), ordering (epic, its stories, its retrospective), merging with any existing file (preserve advanced statuses, never downgrade; legacy v6 values like `drafted`/`contexted` are normalized to their modern meaning, never reset; `action_items`, custom keys, and user comments carried through; `project_key`/`tracking_system`/`story_location` kept from the existing file unless overridden by flag), story-file detection (a story file on disk floors its status at `ready-for-dev`), atomic writes, and post-write validation. It prints a JSON report. Add `--dry-run` to preview — the report's `in_sync`, `new_entries`, `dropped_orphans`, `illegal`, and `legacy_mapped` fields answer "is tracking in sync?" without writing.
+
+3. Read the JSON report and act on it — this is where judgment re-enters:
+   - `warnings` about unparsed Epic/Story-like headings mean the epic file deviates from the standard format. Show the user, fix the headings together (or accept the omission), and rerun.
+   - `dropped_orphans` are entries that existed in the old status file but match nothing in the epics — usually renames. Each carries its old status; reconcile with the user, then transplant by rerunning with `--set <new-key>=<old-status>`.
+   - If the epics defeat the parser entirely (a format the regexes can't see), fall back to building the file yourself against `sprint-status-template.yaml`, and tell the user the deterministic path didn't apply.
+
+## Report
+
+Present the result from the script's JSON in `{communication_language}`: file path, epic/story counts, status breakdown, anything upgraded from disk. Suggest next steps — review the file, `bmad-build` to start the first story, rerun this skill anytime to refresh after epics change.
diff --git a/.claude/skills/bmad-sprint-planning/references/readiness-gate.md b/.claude/skills/bmad-sprint-planning/references/readiness-gate.md
new file mode 100644
index 0000000..ce08a5a
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/references/readiness-gate.md
@@ -0,0 +1,20 @@
+# Readiness Gate
+
+Before generating any tracking, judge whether the plan can actually be built. If the user only asked to check readiness, this gate is the deliverable — report the verdict and stop.
+
+Inventory what planning actually exists: scan `{planning_artifacts}` and `{project_knowledge}` for intent and planning artifacts — briefs, PRFAQs, PRDs, specs, UX outputs, architecture, epics and stories. Identify documents by reading what they are, not by filename patterns; projects arrive with different artifact mixes and naming.
+
+Assess the plan as a whole against one question: **could a developer implement these epics without inventing decisions nothing records?**
+
+- Requirements and decisions in the intent artifacts trace forward into stories; stories trace back to recorded intent — flag orphans in both directions
+- Epics deliver user value and carry no forward dependencies; stories are independently completable
+- Architecture and UX decisions the stories rely on are recorded somewhere, not assumed
+- Conflicts between artifacts (a spec and an epic disagreeing) are surfaced, not silently resolved
+
+A missing document type is only a finding if stories depend on decisions nothing records — a project with no UX artifact and no UI stories is fine.
+
+Deliver a verdict:
+
+- **PASS** — state it in one line; for the full sprint-planning intent, continue with `generate-tracking.md`
+- **CONCERNS** — list them briefly with where each gap lives; ask `{user_name}` whether to proceed anyway or fix first
+- **FAIL** — the plan is not implementable as recorded. Present findings ordered by severity, name the skill that fixes each (the relevant plan skill, or `bmad-correct-course` for cross-cutting changes), offer to save the findings to `{planning_artifacts}/implementation-readiness.md`, and stop
diff --git a/.claude/skills/bmad-sprint-planning/references/status-view.md b/.claude/skills/bmad-sprint-planning/references/status-view.md
new file mode 100644
index 0000000..7ca84e7
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/references/status-view.md
@@ -0,0 +1,14 @@
+# Status View
+
+When the user wants to know where the sprint stands ("show sprint status", "where are we"), run:
+
+```
+uv run {skill-root}/scripts/sprint_plan.py status \
+  --status-file {implementation_artifacts}/sprint-status.yaml --date "{date}"
+```
+
+`{date}` is `MM-DD-YYYY HH:MM`. The script computes everything: counts by status (legacy values like `drafted` mapped transparently and reported in `legacy_mapped`), risk flags (stale file, orphaned stories, in-progress epics without stories, stories waiting in review, unrecognized keys), open action items from retrospectives, and the next recommended action by fixed priority — resume in-progress → review what's in review → start the next ready or backlog story → run an open retrospective → all done. If the file is missing, the script says so — offer to run sprint planning to create it.
+
+Render the JSON as a compact summary in `{communication_language}`: counts, risks, open action items, and the recommendation with its story key. Offer to run the recommended skill. Surface `illegal` and `unrecognized` entries and the script's `warnings` (malformed action items land there); if the user gives corrections, apply them via the fix flow rather than ad-hoc edits. No time estimates — status, risks, and next steps only.
+
+If the script errors — malformed YAML, a hand-edited structure it can't parse, anything — do not stop at the error. Read `sprint-status.yaml` yourself, apply best judgment to give the user the same summary (counts, risks, next recommended action), tell them the deterministic path failed and why, and offer the fix flow (`fix-sprint-status.md`) so the script works next time.
diff --git a/.claude/skills/bmad-sprint-planning/references/validate.md b/.claude/skills/bmad-sprint-planning/references/validate.md
new file mode 100644
index 0000000..c0cc7d4
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/references/validate.md
@@ -0,0 +1,10 @@
+# Validate
+
+When the user asks whether `sprint-status.yaml` is well-formed, run:
+
+```
+uv run {skill-root}/scripts/sprint_plan.py validate \
+  --status-file {implementation_artifacts}/sprint-status.yaml
+```
+
+Never writes; exits 0 whether valid or not. Report `valid` in one line. If `problems` is non-empty, list them plainly (each names the key or field at fault) and offer the fix flow (`fix-sprint-status.md`). If `legacy_mapped` is non-empty, note the file still uses v6 status names and that any regenerate will rewrite them to the modern vocabulary — progress is preserved either way.
diff --git a/.claude/skills/bmad-sprint-planning/scripts/__pycache__/sprint_plan.cpython-311.pyc b/.claude/skills/bmad-sprint-planning/scripts/__pycache__/sprint_plan.cpython-311.pyc
new file mode 100644
index 0000000..e0f7866
Binary files /dev/null and b/.claude/skills/bmad-sprint-planning/scripts/__pycache__/sprint_plan.cpython-311.pyc differ
diff --git a/.claude/skills/bmad-sprint-planning/scripts/sprint_plan.py b/.claude/skills/bmad-sprint-planning/scripts/sprint_plan.py
new file mode 100644
index 0000000..bc486ba
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/scripts/sprint_plan.py
@@ -0,0 +1,697 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["ruamel.yaml>=0.18"]
+# ///
+"""Parse epic files and deterministically generate or refresh sprint-status.yaml.
+
+Prints ONLY JSON to stdout — argparse failures included. Errors are emitted as
+JSON to stdout with a non-zero exit code. Writes are atomic (temp file, fsync,
+``os.replace``) and the original file bytes are restored atomically if
+post-write validation fails.
+
+Subcommands:
+  generate  Parse epics, merge with any existing status file, write the result.
+            --dry-run reports (including drift: in_sync, illegal, orphans)
+            without writing. --fresh ignores existing statuses for a pristine
+            rebuild; --set key=status applies explicit, user-confirmed statuses
+            on top — the repair path is allowed to downgrade.
+  status    Summarize an existing status file: counts, risks, open action
+            items, and the next recommended action. No writes.
+  validate  Report whether an existing status file is structurally valid:
+            parseable, recognized keys, legal statuses, well-formed
+            action_items. No writes; exit 0 whether valid or not.
+
+The LLM decides *which* files are epics (discovery is judgment); this script
+owns everything after that decision: parsing, key derivation, ordering, status
+preservation, story-file detection, action-item carry-over, and validation.
+Legacy v6 statuses (drafted, contexted) are normalized on read everywhere, so
+they merge and count by their modern meaning and are reported, never reset.
+"""
+
+import argparse
+import hashlib
+import io
+import json
+import os
+import re
+import sys
+import tempfile
+from pathlib import Path
+
+from ruamel.yaml import YAML
+from ruamel.yaml.comments import CommentedMap
+
+EPIC_RE = re.compile(r"^#{1,3}\s*Epic\s+(\d+)\s*:?\s*(.*?)\s*#*\s*$", re.IGNORECASE)
+STORY_RE = re.compile(
+    r"^#{2,4}\s*Story\s+(\d+)\.(\d+[a-z]?)\s*:?\s*(.*?)\s*#*\s*$", re.IGNORECASE
+)
+# Heading lines that mention Epic/Story but failed the strict patterns above.
+SUSPECT_RE = re.compile(r"^#{1,4}\s.*\b(?:epic|story)\b", re.IGNORECASE)
+FENCE_RE = re.compile(r"^\s{0,3}(?:```|~~~)")
+
+# The key grammar for sprint-status.yaml. The trailing [a-z]? matches
+# split-story keys like 2-6a-...; bmad-retrospective's sprint_status.py reads
+# the same file with the same grammar.
+EPIC_KEY_RE = re.compile(r"^epic-(\d+)$")
+RETRO_KEY_RE = re.compile(r"^epic-(\d+)-retrospective$")
+STORY_KEY_RE = re.compile(r"^(\d+)-(\d+)([a-z]?)-.+")
+
+STORY_RANK = {"backlog": 0, "ready-for-dev": 1, "in-progress": 2, "review": 3, "done": 4}
+EPIC_RANK = {"backlog": 0, "in-progress": 1, "done": 2}
+RETRO_RANK = {"optional": 0, "done": 1}
+RANKS = {"epic": EPIC_RANK, "story": STORY_RANK, "retro": RETRO_RANK}
+ACTION_STATUSES = ("open", "in-progress", "done")
+
+# v6 wrote these; they still exist in the wild (v6-shims/bmad-create-story
+# actively writes 'contexted'). Normalized on every read so no subcommand ever
+# treats a valid legacy file as illegal or resets its progress.
+LEGACY_STATUS = {"drafted": "ready-for-dev", "contexted": "in-progress"}
+
+STALE_DAYS_DEFAULT = 7
+DATE_FORMAT = "%m-%d-%Y %H:%M"
+# Hand-edited files drift toward ISO stamps; accept them rather than silently
+# disabling the staleness check.
+STAMP_FORMATS = (DATE_FORMAT, "%Y-%m-%d %H:%M", "%Y-%m-%d")
+
+# Kept byte-identical (modulo the leading "# ") with the STATUS DEFINITIONS
+# block in sprint-status-template.yaml; test_sprint_plan.py asserts the two
+# never drift.
+HEADER_COMMENT = """\
+STATUS DEFINITIONS:
+==================
+Epic Status:
+  - backlog: Epic not yet started
+  - in-progress: Epic actively being worked on
+  - done: All stories in epic completed
+
+Story Status:
+  - backlog: Story only exists in epic file
+  - ready-for-dev: Story file created, ready for development
+  - in-progress: Developer actively working on implementation
+  - review: Implementation complete, ready for review
+  - done: Story completed
+
+Retrospective Status:
+  - optional: Can be completed but not required
+  - done: Retrospective has been completed
+
+Action Item Status:
+  - open: Committed during a retrospective, not yet addressed
+  - in-progress: Actively being worked on
+  - done: Completed
+
+WORKFLOW NOTES:
+===============
+- Epic transitions to 'in-progress' automatically when its first story starts (via build's sprint sync)
+- Stories can be worked in parallel if team capacity allows
+- Developer typically creates the next story after the previous one is 'done' to incorporate learnings
+- Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)
+- Retrospective appends its action items to action_items; the status view surfaces open ones
+"""
+
+
+def _fail(message, **extra):
+    print(json.dumps({"ok": False, "error": message, **extra}, default=str))
+    sys.exit(1)
+
+
+class JsonArgumentParser(argparse.ArgumentParser):
+    """Emit argparse failures on the JSON-only stdout contract, not usage text.
+
+    Built with ``add_help=False`` everywhere: the built-in help action prints
+    plain usage to stdout with exit 0, which would break the machine consumer
+    this script serves. ``-h`` therefore routes through ``error()`` as an
+    ordinary unrecognized argument; the skill's SKILL.md carries the usage a
+    human needs.
+    """
+
+    def error(self, message):
+        print(json.dumps({"ok": False, "error": f"argument error: {message}"}))
+        sys.exit(2)
+
+
+def _slug(text, maxlen=60):
+    # Unicode-aware: a non-Latin title must keep its own characters in the key
+    # rather than every such story collapsing onto one shared placeholder.
+    slug = re.sub(r"[^\w]+", "-", str(text).lower(), flags=re.UNICODE).strip("-")
+    slug = slug[:maxlen].strip("-")
+    if not slug:
+        # Nothing sluggable (punctuation/emoji only): a short content hash keeps
+        # the key deterministic and distinct instead of a bare "untitled".
+        slug = hashlib.sha256(str(text).encode("utf-8")).hexdigest()[:8]
+    return slug
+
+
+def classify_key(key):
+    """Return (kind, epic_num) for a recognized key, else None."""
+    m = RETRO_KEY_RE.match(key)
+    if m:
+        return "retro", int(m.group(1))
+    m = EPIC_KEY_RE.match(key)
+    if m:
+        return "epic", int(m.group(1))
+    m = STORY_KEY_RE.match(key)
+    if m:
+        return "story", int(m.group(1))
+    return None
+
+
+def _story_sort_key(key):
+    m = STORY_KEY_RE.match(key)
+    if not m:
+        return (10**9, 10**9, "", key)
+    return (int(m.group(1)), int(m.group(2)), m.group(3), key)
+
+
+def _normalize(raw):
+    """Map a raw status through the legacy vocabulary. Returns (status, was_legacy)."""
+    status = LEGACY_STATUS.get(raw, raw)
+    return status, raw in LEGACY_STATUS
+
+
+def parse_epics(paths):
+    """Return (entries, warnings). Entries are (key, kind, epic_num) in file order."""
+    epics = {}  # epic_num -> [story keys in order]
+    warnings = []
+    for path in paths:
+        try:
+            lines = Path(path).read_text(encoding="utf-8").splitlines()
+        except OSError as exc:
+            _fail(f"cannot read epic file {path}: {exc}")
+        in_fence = False
+        for lineno, line in enumerate(lines, 1):
+            if FENCE_RE.match(line):
+                in_fence = not in_fence
+                continue
+            if in_fence:
+                continue
+            epic_m = EPIC_RE.match(line)
+            if epic_m:
+                epics.setdefault(int(epic_m.group(1)), [])
+                continue
+            story_m = STORY_RE.match(line)
+            if story_m:
+                epic_num = int(story_m.group(1))
+                story_num = story_m.group(2)
+                key = f"{epic_num}-{story_num}-{_slug(story_m.group(3))}"
+                stories = epics.setdefault(epic_num, [])
+                if key in stories:
+                    warnings.append(f"duplicate story heading '{key}' at {path}:{lineno}")
+                else:
+                    stories.append(key)
+                continue
+            if SUSPECT_RE.match(line):
+                warnings.append(f"unparsed Epic/Story-like heading at {path}:{lineno}: {line.strip()}")
+    entries = []
+    for epic_num in sorted(epics):
+        entries.append((f"epic-{epic_num}", "epic", epic_num))
+        for story_key in epics[epic_num]:
+            entries.append((story_key, "story", epic_num))
+        entries.append((f"epic-{epic_num}-retrospective", "retro", epic_num))
+    return entries, warnings
+
+
+def _make_yaml():
+    yaml = YAML(typ="rt")
+    yaml.preserve_quotes = True
+    # Pin the emitter to the indentation the sprint-status template ships with.
+    # Without this, ruamel re-dumps block sequences at its own default offset and
+    # every write silently de-indents pre-existing, untouched action_items.
+    yaml.indent(mapping=2, sequence=4, offset=2)
+    yaml.encoding = "utf-8"
+    return yaml
+
+
+def _load_existing(path):
+    yaml = _make_yaml()
+    if not Path(path).exists():
+        return yaml, None
+    try:
+        with io.open(path, "r", encoding="utf-8") as fh:
+            data = yaml.load(fh)
+    except Exception as exc:
+        _fail(f"existing status file is not valid YAML: {exc}", status_file=str(path))
+    if data is not None and not isinstance(data, dict):
+        _fail(
+            f"existing status file is valid YAML but not a mapping (got {type(data).__name__})",
+            status_file=str(path),
+        )
+    return yaml, data
+
+
+def _merge_status(kind, computed, existing_raw, key, warnings, report):
+    """Return the higher-ranked of computed/existing; never downgrade."""
+    rank = RANKS[kind]
+    if existing_raw is None:
+        return computed
+    existing, was_legacy = _normalize(existing_raw)
+    if was_legacy:
+        report["legacy_mapped"].append({"key": key, "from": existing_raw, "to": existing})
+    if existing not in rank:
+        warnings.append(f"illegal status '{existing_raw}' on '{key}' replaced with '{computed}'")
+        report["illegal"].append({"key": key, "status": existing_raw})
+        return computed
+    return existing if rank[existing] >= rank[computed] else computed
+
+
+def build_status(entries, existing_data, stories_dir, warnings):
+    """Return (development_status CommentedMap, merge report dict)."""
+    existing_status = {}
+    if existing_data is not None:
+        existing_status = dict(existing_data.get("development_status") or {})
+    report = {
+        "new_entries": [],
+        "preserved": 0,
+        "changed": 0,
+        "upgraded_from_disk": [],
+        "dropped_orphans": [],
+        "legacy_mapped": [],
+        "illegal": [],
+    }
+    # One directory scan instead of a stat() per story.
+    story_files = set()
+    if stories_dir and Path(stories_dir).is_dir():
+        story_files = {p.name for p in Path(stories_dir).glob("*.md")}
+    dev = CommentedMap()
+    first_epic = True
+    for key, kind, _epic_num in entries:
+        default = {"epic": "backlog", "story": "backlog", "retro": "optional"}[kind]
+        computed = default
+        if kind == "story" and f"{key}.md" in story_files:
+            computed = "ready-for-dev"
+        merged = _merge_status(kind, computed, existing_status.get(key), key, warnings, report)
+        if key not in existing_status:
+            report["new_entries"].append(key)
+        elif merged == _normalize(existing_status[key])[0]:
+            report["preserved"] += 1
+        else:
+            report["changed"] += 1
+        if kind == "story" and computed == "ready-for-dev" and existing_status.get(key) in (None, "backlog"):
+            report["upgraded_from_disk"].append(key)
+        dev[key] = merged
+        if kind == "epic" and not first_epic:
+            dev.yaml_set_comment_before_after_key(key, before="\n")
+        if kind == "epic":
+            first_epic = False
+    computed_keys = {key for key, _, _ in entries}
+    # Old statuses ride along so the LLM can transplant them after a rename —
+    # the values would otherwise be destroyed by the write.
+    report["dropped_orphans"] = [
+        {"key": k, "status": existing_status[k]}
+        for k in existing_status
+        if k not in computed_keys
+    ]
+    report["in_sync"] = (
+        not report["new_entries"]
+        and not report["dropped_orphans"]
+        and not report["illegal"]
+        and not report["legacy_mapped"]
+        and report["changed"] == 0
+    )
+    return dev, report
+
+
+def _counts(dev):
+    counts = {}
+    for value in dev.values():
+        counts[value] = counts.get(value, 0) + 1
+    return counts
+
+
+def _dump_bytes(yaml, doc):
+    """Serialize before any file is touched, so a dump failure cannot leave a
+    partial file anywhere."""
+    buf = io.BytesIO()
+    yaml.dump(doc, buf)
+    return buf.getvalue()
+
+
+def _atomic_write(path, payload, mode=None):
+    """Replace ``path``'s contents with ``payload`` atomically.
+
+    Temp file alongside the target, fsynced, taking the target's permission
+    bits (mkstemp creates 0600, which would silently narrow the file), then
+    renamed over it. ``path`` is resolved through symlinks first: renaming onto
+    a symlink would detach the link and leave the real file stale.
+    """
+    path = os.path.realpath(path)
+    directory = os.path.dirname(path) or "."
+    os.makedirs(directory, exist_ok=True)
+    fd, tmp = tempfile.mkstemp(prefix=".sprint-status-", suffix=".tmp", dir=directory)
+    try:
+        with os.fdopen(fd, "wb") as fh:
+            fh.write(payload)
+            fh.flush()
+            os.fsync(fh.fileno())
+        if mode is not None:
+            os.chmod(tmp, mode)
+        os.replace(tmp, path)
+    except BaseException:
+        try:
+            os.unlink(tmp)
+        except OSError:
+            pass
+        raise
+
+
+def _parse_sets(pairs, valid_keys):
+    """Validate --set key=status pairs against the generated plan and vocabulary."""
+    parsed = []
+    for pair in pairs:
+        key, sep, status = pair.partition("=")
+        if not sep or not key or not status:
+            _fail(f"--set expects key=status, got '{pair}'")
+        if key not in valid_keys:
+            _fail(f"--set key '{key}' is not in the generated plan", valid_keys=sorted(valid_keys))
+        kind, _ = classify_key(key)
+        if status not in RANKS[kind]:
+            _fail(
+                f"--set status '{status}' is not legal for {kind} '{key}'",
+                legal=sorted(RANKS[kind]),
+            )
+        parsed.append((key, status))
+    return parsed
+
+
+def cmd_generate(args):
+    entries, warnings = parse_epics(args.epic_file)
+    if not entries:
+        _fail("no epics or stories parsed from the given epic files", epic_files=args.epic_file)
+    yaml, existing = _load_existing(args.status_file)
+    status_path = Path(args.status_file)
+    original_bytes = status_path.read_bytes() if status_path.exists() else None
+    original_mode = (os.stat(status_path).st_mode & 0o777) if status_path.exists() else None
+
+    merge_source = None if args.fresh else existing
+    dev, report = build_status(entries, merge_source, args.stories_dir, warnings)
+
+    # Explicit, user-confirmed statuses (the fix flow). Applied last: repair is
+    # the one path allowed to downgrade.
+    explicit = _parse_sets(args.set or [], set(dev.keys()))
+    for key, status in explicit:
+        dev[key] = status
+    report["explicit_set"] = [f"{k}={s}" for k, s in explicit]
+
+    def _meta(field, arg_value, default):
+        if arg_value is not None:
+            return arg_value
+        if existing is not None and existing.get(field):
+            return str(existing[field])
+        return default
+
+    generated = args.date
+    if existing is not None and existing.get("generated"):
+        generated = str(existing["generated"])
+
+    if existing is not None and not args.fresh:
+        # Round-trip the existing document: unknown top-level keys and their
+        # comments survive; only the managed fields and development_status are
+        # replaced.
+        doc = existing
+    else:
+        doc = CommentedMap()
+        doc.yaml_set_start_comment(HEADER_COMMENT)
+    doc["generated"] = generated
+    doc["last_updated"] = args.date
+    doc["project"] = args.project
+    doc["project_key"] = _meta("project_key", args.project_key, "NOKEY")
+    doc["tracking_system"] = _meta("tracking_system", args.tracking_system, "file-system")
+    doc["story_location"] = _meta("story_location", args.story_location, args.stories_dir)
+    doc["development_status"] = dev
+    if "action_items" not in doc and existing is not None and existing.get("action_items") is not None:
+        doc["action_items"] = existing["action_items"]
+        doc.yaml_set_comment_before_after_key(
+            "action_items",
+            before="\nAction items committed during retrospectives (section created by the retrospective workflow)",
+        )
+
+    result = {
+        "ok": True,
+        "action": "generate",
+        "status_file": str(args.status_file),
+        "dry_run": bool(args.dry_run),
+        "fresh": bool(args.fresh),
+        "epics": sum(1 for _, kind, _ in entries if kind == "epic"),
+        "stories": sum(1 for _, kind, _ in entries if kind == "story"),
+        "counts": _counts(dev),
+        "generated": generated,
+        "last_updated": args.date,
+        "warnings": warnings,
+        **report,
+    }
+
+    if args.dry_run:
+        print(json.dumps(result, default=str))
+        return
+
+    try:
+        payload = _dump_bytes(yaml, doc)
+        _atomic_write(args.status_file, payload, original_mode)
+        verify_yaml = _make_yaml()
+        with io.open(args.status_file, "r", encoding="utf-8") as fh:
+            reread = verify_yaml.load(fh)
+        if dict(reread.get("development_status") or {}) != {k: v for k, v in dev.items()}:
+            raise ValueError("development_status mismatch after write")
+        for field in ("generated", "last_updated", "project"):
+            if str(reread.get(field)) != str(doc[field]):
+                raise ValueError(f"{field} mismatch after write")
+    except Exception as exc:
+        if original_bytes is not None:
+            try:
+                _atomic_write(args.status_file, original_bytes, original_mode)
+                restored = True
+            except Exception:
+                restored = False
+        else:
+            Path(args.status_file).unlink(missing_ok=True)
+            restored = True
+        _fail(f"write or validation failed, original {'restored' if restored else 'NOT restored'}: {exc}",
+              restored=restored)
+    print(json.dumps(result, default=str))
+
+
+def _parse_stamp(value):
+    from datetime import datetime
+
+    for fmt in STAMP_FORMATS:
+        try:
+            return datetime.strptime(str(value), fmt)
+        except ValueError:
+            continue
+    return None
+
+
+def cmd_status(args):
+    from datetime import timedelta
+
+    _, data = _load_existing(args.status_file)
+    if data is None:
+        _fail("status file does not exist — run sprint planning to generate it",
+              status_file=str(args.status_file))
+    dev = dict(data.get("development_status") or {})
+    if not dev:
+        _fail("development_status missing or empty — re-run sprint planning",
+              status_file=str(args.status_file))
+
+    warnings = []
+    counts = {"story": {}, "epic": {}, "retro": {}}
+    by_status = {}
+    legacy_mapped, illegal, unrecognized = [], [], []
+    epic_nums, story_epic_nums = set(), set()
+    epic_status, retro_status = {}, {}
+    for key, raw in dev.items():
+        key = str(key)
+        parsed = classify_key(key)
+        if parsed is None:
+            unrecognized.append({"key": key, "status": raw})
+            continue
+        kind, epic_num = parsed
+        status, was_legacy = _normalize(raw)
+        if was_legacy:
+            legacy_mapped.append({"key": key, "from": raw, "to": status})
+        if status not in RANKS[kind]:
+            illegal.append({"key": key, "status": raw})
+            continue
+        counts[kind][status] = counts[kind].get(status, 0) + 1
+        if kind == "story":
+            by_status.setdefault(status, []).append(key)
+            story_epic_nums.add(epic_num)
+        elif kind == "epic":
+            epic_nums.add(epic_num)
+            epic_status[epic_num] = status
+        else:
+            retro_status[epic_num] = status
+    for stories in by_status.values():
+        stories.sort(key=_story_sort_key)
+
+    action_items = data.get("action_items") or []
+    open_items = []
+    for i, item in enumerate(action_items):
+        if not isinstance(item, dict):
+            warnings.append(f"action_items[{i}] is not a mapping and was skipped: {item!r}")
+            continue
+        status = item.get("status")
+        if status not in ACTION_STATUSES:
+            warnings.append(f"action_items[{i}] has a missing or unknown status ({status!r})")
+            continue
+        if status in ("open", "in-progress"):
+            open_items.append({k: item.get(k) for k in ("epic", "action", "owner", "status")})
+
+    risks = []
+    stamp = data.get("last_updated") or data.get("generated")
+    if args.date and stamp:
+        now, then = _parse_stamp(args.date), _parse_stamp(stamp)
+        if now is None or then is None:
+            warnings.append(
+                f"timestamp format not recognized (--date {args.date!r}, file {stamp!r}); "
+                "staleness check skipped"
+            )
+        elif now - then > timedelta(days=args.stale_days):
+            risks.append(f"sprint-status.yaml may be stale (last updated {stamp})")
+    for stories in by_status.values():
+        for key in stories:
+            num = classify_key(key)[1]
+            if num not in epic_nums:
+                risks.append(f"orphaned story '{key}' has no epic-{num} entry")
+    for num, status in epic_status.items():
+        if status == "in-progress" and num not in story_epic_nums:
+            risks.append(f"in-progress epic 'epic-{num}' has no stories")
+    if by_status.get("review"):
+        risks.append(f"{len(by_status['review'])} story(ies) in review — run bmad-code-review")
+    if unrecognized:
+        risks.append(f"{len(unrecognized)} unrecognized key(s) in development_status — run validate")
+
+    recommendation = None
+    if by_status.get("in-progress"):
+        recommendation = {"skill": "bmad-build", "story_key": by_status["in-progress"][0],
+                          "reason": "resume the in-progress story"}
+    elif by_status.get("review"):
+        recommendation = {"skill": "bmad-code-review", "story_key": by_status["review"][0],
+                          "reason": "review the completed implementation"}
+    elif by_status.get("ready-for-dev"):
+        recommendation = {"skill": "bmad-build", "story_key": by_status["ready-for-dev"][0],
+                          "reason": "start the next ready story"}
+    elif by_status.get("backlog"):
+        recommendation = {"skill": "bmad-build", "story_key": by_status["backlog"][0],
+                          "reason": "start the first backlog story"}
+    else:
+        optional_retros = sorted(num for num, status in retro_status.items() if status == "optional")
+        if optional_retros:
+            recommendation = {"skill": "bmad-retrospective", "story_key": None,
+                              "reason": f"all stories done — epic-{optional_retros[0]}-retrospective is still open"}
+
+    print(json.dumps({
+        "ok": True, "action": "status", "status_file": str(args.status_file),
+        "project": data.get("project"), "project_key": data.get("project_key"),
+        "tracking_system": data.get("tracking_system"),
+        "generated": data.get("generated"), "last_updated": data.get("last_updated"),
+        "stories": counts["story"], "epics": counts["epic"], "retrospectives": counts["retro"],
+        "legacy_mapped": legacy_mapped, "illegal": illegal, "unrecognized": unrecognized,
+        "open_action_items": open_items, "risks": risks, "warnings": warnings,
+        "recommendation": recommendation,
+        "all_done": recommendation is None,
+    }, default=str))
+
+
+def cmd_validate(args):
+    problems = []
+    legacy_mapped = []
+    path = Path(args.status_file)
+    if not path.exists():
+        print(json.dumps({
+            "ok": True, "action": "validate", "status_file": str(args.status_file),
+            "valid": False, "problems": ["status file does not exist"], "legacy_mapped": [],
+        }))
+        return
+    yaml = _make_yaml()
+    try:
+        with io.open(args.status_file, "r", encoding="utf-8") as fh:
+            data = yaml.load(fh)
+    except Exception as exc:
+        print(json.dumps({
+            "ok": True, "action": "validate", "status_file": str(args.status_file),
+            "valid": False, "problems": [f"not valid YAML: {exc}"], "legacy_mapped": [],
+        }, default=str))
+        return
+    if not isinstance(data, dict):
+        problems.append(f"top level is not a mapping (got {type(data).__name__})")
+    else:
+        for field in ("generated", "last_updated", "project", "development_status"):
+            if data.get(field) is None:
+                problems.append(f"missing required key '{field}'")
+        for field in ("generated", "last_updated"):
+            value = data.get(field)
+            if value is not None and _parse_stamp(value) is None:
+                problems.append(f"'{field}' timestamp {str(value)!r} does not match '{DATE_FORMAT}'")
+        dev = data.get("development_status")
+        if dev is not None and not isinstance(dev, dict):
+            problems.append("development_status is not a mapping")
+        elif dev:
+            for key, raw in dev.items():
+                parsed = classify_key(str(key))
+                if parsed is None:
+                    problems.append(f"unrecognized key '{key}' (expected epic-N, N-M-slug, or epic-N-retrospective)")
+                    continue
+                kind, _ = parsed
+                status, was_legacy = _normalize(raw)
+                if was_legacy:
+                    legacy_mapped.append({"key": str(key), "from": raw, "to": status})
+                if status not in RANKS[kind]:
+                    problems.append(f"illegal {kind} status {str(raw)!r} on '{key}'")
+        elif isinstance(data.get("development_status"), dict):
+            problems.append("development_status is empty")
+        items = data.get("action_items")
+        if items is not None:
+            if not isinstance(items, list):
+                problems.append("action_items is not a list")
+            else:
+                for i, item in enumerate(items):
+                    if not isinstance(item, dict):
+                        problems.append(f"action_items[{i}] is not a mapping")
+                    elif item.get("status") not in ACTION_STATUSES:
+                        problems.append(
+                            f"action_items[{i}] has a missing or unknown status ({item.get('status')!r})"
+                        )
+    print(json.dumps({
+        "ok": True, "action": "validate", "status_file": str(args.status_file),
+        "valid": not problems, "problems": problems, "legacy_mapped": legacy_mapped,
+    }, default=str))
+
+
+def build_parser():
+    parser = JsonArgumentParser(prog="sprint_plan.py", add_help=False)
+    sub = parser.add_subparsers(dest="command", required=True, parser_class=JsonArgumentParser)
+
+    gen = sub.add_parser("generate", add_help=False)
+    gen.add_argument("--epic-file", action="append", required=True)
+    gen.add_argument("--status-file", required=True)
+    gen.add_argument("--stories-dir", required=True)
+    gen.add_argument("--project", required=True)
+    gen.add_argument("--date", required=True)
+    gen.add_argument("--project-key", default=None)
+    gen.add_argument("--tracking-system", default=None)
+    gen.add_argument("--story-location", default=None)
+    gen.add_argument("--dry-run", action="store_true")
+    gen.add_argument("--fresh", action="store_true")
+    gen.add_argument("--set", action="append", metavar="KEY=STATUS")
+    gen.set_defaults(func=cmd_generate)
+
+    st = sub.add_parser("status", add_help=False)
+    st.add_argument("--status-file", required=True)
+    st.add_argument("--date", default=None)
+    st.add_argument("--stale-days", type=int, default=STALE_DAYS_DEFAULT)
+    st.set_defaults(func=cmd_status)
+
+    val = sub.add_parser("validate", add_help=False)
+    val.add_argument("--status-file", required=True)
+    val.set_defaults(func=cmd_validate)
+    return parser
+
+
+def main(argv=None):
+    args = build_parser().parse_args(argv)
+    args.func(args)
+
+
+if __name__ == "__main__":
+    main()
diff --git a/.claude/skills/bmad-sprint-planning/scripts/tests/__pycache__/test_sprint_plan.cpython-311-pytest-9.1.1.pyc b/.claude/skills/bmad-sprint-planning/scripts/tests/__pycache__/test_sprint_plan.cpython-311-pytest-9.1.1.pyc
new file mode 100644
index 0000000..2ea71c5
Binary files /dev/null and b/.claude/skills/bmad-sprint-planning/scripts/tests/__pycache__/test_sprint_plan.cpython-311-pytest-9.1.1.pyc differ
diff --git a/.claude/skills/bmad-sprint-planning/scripts/tests/test_sprint_plan.py b/.claude/skills/bmad-sprint-planning/scripts/tests/test_sprint_plan.py
new file mode 100644
index 0000000..253b220
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/scripts/tests/test_sprint_plan.py
@@ -0,0 +1,524 @@
+# /// script
+# requires-python = ">=3.10"
+# dependencies = ["pytest>=8.0", "ruamel.yaml>=0.18"]
+# ///
+"""Tests for sprint_plan.py — deterministic sprint-status generation.
+
+Run: uv run scripts/tests/test_sprint_plan.py
+ or: uv run --with pytest --with ruamel.yaml -m pytest scripts/tests/test_sprint_plan.py
+"""
+
+import importlib.util
+import json
+import sys
+from pathlib import Path
+
+import pytest
+from ruamel.yaml import YAML
+
+SCRIPT = Path(__file__).resolve().parents[1] / "sprint_plan.py"
+TEMPLATE = Path(__file__).resolve().parents[2] / "sprint-status-template.yaml"
+
+spec = importlib.util.spec_from_file_location("sprint_plan", SCRIPT)
+mod = importlib.util.module_from_spec(spec)
+spec.loader.exec_module(mod)
+
+EPICS_FIXTURE = """\
+# Project Epics
+
+## Epic 1: Foundation
+Some prose.
+
+### Story 1.1: User Authentication
+Acceptance criteria...
+
+### Story 1.2: Account Management
+
+## Epic 2: Chat
+### Story 2.1: Personality System
+### Story 2.6a: Split Story, With Punctuation!
+"""
+
+DATE = "08-01-2026 14:30"
+
+
+def run_generate(tmp_path, epics_text=EPICS_FIXTURE, existing=None, stories=(), extra=()):
+    epic_file = tmp_path / "epics.md"
+    epic_file.write_text(epics_text, encoding="utf-8")
+    status_file = tmp_path / "impl" / "sprint-status.yaml"
+    if existing is not None:
+        status_file.parent.mkdir(parents=True, exist_ok=True)
+        status_file.write_text(existing, encoding="utf-8")
+    stories_dir = tmp_path / "impl"
+    stories_dir.mkdir(parents=True, exist_ok=True)
+    for name in stories:
+        (stories_dir / f"{name}.md").write_text("story", encoding="utf-8")
+    argv = [
+        "generate", "--epic-file", str(epic_file), "--status-file", str(status_file),
+        "--stories-dir", str(stories_dir), "--project", "My Project", "--date", DATE,
+        *extra,
+    ]
+    mod.main(argv)
+    return status_file
+
+
+def load(status_file):
+    yaml = YAML()
+    with open(status_file, encoding="utf-8") as fh:
+        return yaml.load(fh)
+
+
+def out_json(capsys):
+    return json.loads(capsys.readouterr().out)
+
+
+def test_fresh_generate_orders_and_defaults(tmp_path, capsys):
+    status_file = run_generate(tmp_path)
+    result = out_json(capsys)
+    data = load(status_file)
+    keys = list(data["development_status"].keys())
+    assert keys == [
+        "epic-1", "1-1-user-authentication", "1-2-account-management", "epic-1-retrospective",
+        "epic-2", "2-1-personality-system", "2-6a-split-story-with-punctuation", "epic-2-retrospective",
+    ]
+    assert data["development_status"]["epic-1"] == "backlog"
+    assert data["development_status"]["1-1-user-authentication"] == "backlog"
+    assert data["development_status"]["epic-1-retrospective"] == "optional"
+    assert data["project"] == "My Project"
+    assert data["generated"] == DATE and data["last_updated"] == DATE
+    assert result["ok"] and result["epics"] == 2 and result["stories"] == 4
+    text = status_file.read_text(encoding="utf-8")
+    assert "STATUS DEFINITIONS" in text
+    assert "\n\n  epic-2:" in text  # blank line between epic groups
+
+
+def test_header_comment_matches_template():
+    """The template's STATUS DEFINITIONS block and the script's HEADER_COMMENT
+    are two copies of one contract; this pins them together."""
+    lines = TEMPLATE.read_text(encoding="utf-8").splitlines()
+    start = lines.index("# STATUS DEFINITIONS:")
+    block = []
+    for line in lines[start:]:
+        if not line.startswith("#"):
+            break
+        block.append(line[2:] if line.startswith("# ") else line[1:])
+    assert "\n".join(block) + "\n" == mod.HEADER_COMMENT
+
+
+EXISTING = """\
+generated: 01-01-2026 09:00
+last_updated: 01-01-2026 09:00
+project: My Project
+project_key: NOKEY
+tracking_system: file-system
+story_location: impl
+
+development_status:
+  epic-1: in-progress
+  1-1-user-authentication: done
+  1-2-account-management: backlog
+  epic-1-retrospective: optional
+  9-9-ghost-story: done
+
+action_items:
+  - epic: 1
+    action: "Add error-handling review; watch: quotes, commas"
+    owner: "Charlie"
+    status: open
+"""
+
+
+def test_merge_preserves_and_never_downgrades(tmp_path, capsys):
+    status_file = run_generate(tmp_path, existing=EXISTING)
+    result = out_json(capsys)
+    data = load(status_file)
+    assert data["development_status"]["epic-1"] == "in-progress"
+    assert data["development_status"]["1-1-user-authentication"] == "done"
+    assert data["generated"] == "01-01-2026 09:00"
+    assert data["last_updated"] == DATE
+    assert result["dropped_orphans"] == [{"key": "9-9-ghost-story", "status": "done"}]
+    assert "9-9-ghost-story" not in data["development_status"]
+
+
+def test_legacy_statuses_merge_by_meaning_not_reset(tmp_path, capsys):
+    existing = (EXISTING
+                .replace("1-2-account-management: backlog", "1-2-account-management: drafted")
+                .replace("epic-1: in-progress", "epic-1: contexted"))
+    status_file = run_generate(tmp_path, existing=existing)
+    result = out_json(capsys)
+    data = load(status_file)
+    assert data["development_status"]["1-2-account-management"] == "ready-for-dev"
+    assert data["development_status"]["epic-1"] == "in-progress"
+    assert {"key": "1-2-account-management", "from": "drafted", "to": "ready-for-dev"} in result["legacy_mapped"]
+    assert not any("illegal" in w for w in result["warnings"])
+    assert result["illegal"] == []
+
+
+def test_metadata_preserved_when_flags_omitted(tmp_path, capsys):
+    existing = (EXISTING
+                .replace("project_key: NOKEY", "project_key: JIRA-PROJ")
+                .replace("tracking_system: file-system", "tracking_system: jira")
+                .replace("story_location: impl", "story_location: /custom/stories"))
+    status_file = run_generate(tmp_path, existing=existing)
+    out_json(capsys)
+    data = load(status_file)
+    assert data["project_key"] == "JIRA-PROJ"
+    assert data["tracking_system"] == "jira"
+    assert data["story_location"] == "/custom/stories"
+
+
+def test_unknown_keys_and_comments_survive_regenerate(tmp_path, capsys):
+    existing = EXISTING + "\n# my own note\nsprint_goal: Ship the beta\n"
+    status_file = run_generate(tmp_path, existing=existing)
+    out_json(capsys)
+    data = load(status_file)
+    assert data["sprint_goal"] == "Ship the beta"
+    assert "# my own note" in status_file.read_text(encoding="utf-8")
+
+
+def test_fresh_rebuild_ignores_existing_statuses(tmp_path, capsys):
+    status_file = run_generate(tmp_path, existing=EXISTING, extra=("--fresh",))
+    result = out_json(capsys)
+    data = load(status_file)
+    assert data["development_status"]["1-1-user-authentication"] == "backlog"
+    assert data["development_status"]["epic-1"] == "backlog"
+    assert result["fresh"] is True
+    # action_items are retro history, not tracking state — carried even on --fresh
+    assert data["action_items"][0]["status"] == "open"
+
+
+def test_set_applies_explicit_statuses_even_downgrades(tmp_path, capsys):
+    status_file = run_generate(
+        tmp_path, existing=EXISTING,
+        extra=("--fresh", "--set", "1-1-user-authentication=in-progress", "--set", "epic-1=in-progress"),
+    )
+    result = out_json(capsys)
+    data = load(status_file)
+    assert data["development_status"]["1-1-user-authentication"] == "in-progress"
+    assert data["development_status"]["epic-1"] == "in-progress"
+    assert "1-1-user-authentication=in-progress" in result["explicit_set"]
+
+
+def test_set_rejects_unknown_key_and_illegal_status(tmp_path, capsys):
+    with pytest.raises(SystemExit) as excinfo:
+        run_generate(tmp_path, extra=("--set", "9-9-nope=done"))
+    assert excinfo.value.code == 1
+    assert out_json(capsys)["ok"] is False
+    with pytest.raises(SystemExit):
+        run_generate(tmp_path, extra=("--set", "epic-1=review"))
+    assert out_json(capsys)["ok"] is False
+
+
+def test_action_items_carried_verbatim(tmp_path):
+    status_file = run_generate(tmp_path, existing=EXISTING)
+    data = load(status_file)
+    assert data["action_items"][0]["action"] == "Add error-handling review; watch: quotes, commas"
+    assert data["action_items"][0]["status"] == "open"
+
+
+def test_story_file_on_disk_floors_ready_for_dev(tmp_path, capsys):
+    status_file = run_generate(tmp_path, stories=["1-2-account-management"])
+    result = out_json(capsys)
+    data = load(status_file)
+    assert data["development_status"]["1-2-account-management"] == "ready-for-dev"
+    assert data["development_status"]["1-1-user-authentication"] == "backlog"
+    assert result["upgraded_from_disk"] == ["1-2-account-management"]
+
+
+def test_story_file_never_downgrades_done(tmp_path):
+    status_file = run_generate(tmp_path, existing=EXISTING, stories=["1-1-user-authentication"])
+    data = load(status_file)
+    assert data["development_status"]["1-1-user-authentication"] == "done"
+
+
+def test_illegal_existing_status_warns_and_resets(tmp_path, capsys):
+    existing = EXISTING.replace("1-2-account-management: backlog", "1-2-account-management: shipped")
+    status_file = run_generate(tmp_path, existing=existing)
+    result = out_json(capsys)
+    data = load(status_file)
+    assert data["development_status"]["1-2-account-management"] == "backlog"
+    assert any("illegal status 'shipped'" in w for w in result["warnings"])
+    assert {"key": "1-2-account-management", "status": "shipped"} in result["illegal"]
+
+
+def test_fenced_code_blocks_are_not_parsed(tmp_path, capsys):
+    text = EPICS_FIXTURE + "\n```\n## Epic 9: Example Format\n### Story 9.1: Sample\n```\n"
+    status_file = run_generate(tmp_path, epics_text=text)
+    result = out_json(capsys)
+    data = load(status_file)
+    assert "epic-9" not in data["development_status"]
+    assert result["epics"] == 2
+    assert not any("Epic 9" in w for w in result["warnings"])
+
+
+def test_non_ascii_titles_keep_distinct_keys(tmp_path, capsys):
+    text = "## Epic 1: 基础\n### Story 1.1: 用户认证\n### Story 1.2: 账户管理\n"
+    status_file = run_generate(tmp_path, epics_text=text)
+    out_json(capsys)
+    keys = list(load(status_file)["development_status"].keys())
+    assert "1-1-用户认证" in keys and "1-2-账户管理" in keys
+
+
+def test_suspect_heading_is_reported(tmp_path, capsys):
+    text = EPICS_FIXTURE + "\n### Story Two point one: Bad Format\n"
+    run_generate(tmp_path, epics_text=text)
+    result = out_json(capsys)
+    assert any("unparsed Epic/Story-like heading" in w for w in result["warnings"])
+
+
+def test_dry_run_writes_nothing_and_reports_drift(tmp_path, capsys):
+    epic_file = tmp_path / "epics.md"
+    epic_file.write_text(EPICS_FIXTURE, encoding="utf-8")
+    status_file = tmp_path / "sprint-status.yaml"
+    status_file.write_text(EXISTING, encoding="utf-8")
+    original = status_file.read_bytes()
+    mod.main([
+        "generate", "--epic-file", str(epic_file), "--status-file", str(status_file),
+        "--stories-dir", str(tmp_path), "--project", "P", "--date", DATE, "--dry-run",
+    ])
+    result = out_json(capsys)
+    assert result["dry_run"] is True and result["ok"] is True
+    assert result["in_sync"] is False
+    assert "epic-2" in result["new_entries"]
+    assert result["dropped_orphans"] == [{"key": "9-9-ghost-story", "status": "done"}]
+    assert status_file.read_bytes() == original
+
+
+def test_dry_run_in_sync_after_generate(tmp_path, capsys):
+    status_file = run_generate(tmp_path)
+    capsys.readouterr()
+    mod.main([
+        "generate", "--epic-file", str(tmp_path / "epics.md"), "--status-file", str(status_file),
+        "--stories-dir", str(tmp_path / "impl"), "--project", "My Project", "--date", DATE,
+        "--dry-run",
+    ])
+    result = out_json(capsys)
+    assert result["in_sync"] is True
+    assert result["new_entries"] == [] and result["dropped_orphans"] == [] and result["illegal"] == []
+
+
+def test_no_epics_fails_with_json(tmp_path, capsys):
+    epic_file = tmp_path / "notes.md"
+    epic_file.write_text("just prose, no epics", encoding="utf-8")
+    with pytest.raises(SystemExit) as excinfo:
+        mod.main([
+            "generate", "--epic-file", str(epic_file), "--status-file", str(tmp_path / "s.yaml"),
+            "--stories-dir", str(tmp_path), "--project", "P", "--date", DATE,
+        ])
+    assert excinfo.value.code == 1
+    assert out_json(capsys)["ok"] is False
+
+
+def test_non_mapping_yaml_fails_with_json(tmp_path, capsys):
+    epic_file = tmp_path / "epics.md"
+    epic_file.write_text(EPICS_FIXTURE, encoding="utf-8")
+    status_file = tmp_path / "sprint-status.yaml"
+    status_file.write_text("- just\n- a\n- list\n", encoding="utf-8")
+    with pytest.raises(SystemExit) as excinfo:
+        mod.main([
+            "generate", "--epic-file", str(epic_file), "--status-file", str(status_file),
+            "--stories-dir", str(tmp_path), "--project", "P", "--date", DATE,
+        ])
+    assert excinfo.value.code == 1
+    assert "not a mapping" in out_json(capsys)["error"]
+    with pytest.raises(SystemExit):
+        mod.main(["status", "--status-file", str(status_file)])
+    assert "not a mapping" in out_json(capsys)["error"]
+
+
+def test_argument_errors_emit_json(capsys):
+    with pytest.raises(SystemExit) as excinfo:
+        mod.main(["generate"])
+    assert excinfo.value.code == 2
+    assert out_json(capsys)["ok"] is False
+    with pytest.raises(SystemExit) as excinfo:
+        mod.main(["-h"])
+    assert excinfo.value.code == 2
+    assert out_json(capsys)["ok"] is False
+
+
+STATUS_FIXTURE = """\
+generated: 01-01-2026 09:00
+last_updated: 07-30-2026 09:00
+project: My Project
+project_key: NOKEY
+tracking_system: file-system
+story_location: impl
+
+development_status:
+  epic-1: in-progress
+  1-1-user-authentication: done
+  1-2-account-management: drafted
+  epic-1-retrospective: optional
+  epic-2: backlog
+  2-1-personality-system: backlog
+  epic-2-retrospective: optional
+
+action_items:
+  - epic: 1
+    action: "Tighten error handling"
+    owner: "Charlie"
+    status: open
+  - epic: 1
+    action: "Old item"
+    owner: "Charlie"
+    status: done
+"""
+
+
+def run_status(tmp_path, capsys, fixture=STATUS_FIXTURE, extra=()):
+    status_file = tmp_path / "sprint-status.yaml"
+    status_file.write_text(fixture, encoding="utf-8")
+    mod.main(["status", "--status-file", str(status_file), "--date", DATE, *extra])
+    return json.loads(capsys.readouterr().out)
+
+
+def test_status_counts_and_recommendation(tmp_path, capsys):
+    result = run_status(tmp_path, capsys)
+    assert result["stories"] == {"done": 1, "ready-for-dev": 1, "backlog": 1}
+    assert result["epics"] == {"in-progress": 1, "backlog": 1}
+    assert result["retrospectives"] == {"optional": 2}
+    assert result["recommendation"]["skill"] == "bmad-build"
+    assert result["recommendation"]["story_key"] == "1-2-account-management"
+    assert result["all_done"] is False
+
+
+def test_status_maps_legacy_values(tmp_path, capsys):
+    result = run_status(tmp_path, capsys)
+    assert {"key": "1-2-account-management", "from": "drafted", "to": "ready-for-dev"} in result["legacy_mapped"]
+
+
+def test_status_open_action_items(tmp_path, capsys):
+    result = run_status(tmp_path, capsys)
+    assert len(result["open_action_items"]) == 1
+    assert result["open_action_items"][0]["action"] == "Tighten error handling"
+
+
+def test_status_malformed_action_items_are_flagged_not_dropped(tmp_path, capsys):
+    fixture = STATUS_FIXTURE + "  - \"just a string\"\n  - epic: 2\n    action: \"No status\"\n"
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert any("not a mapping" in w for w in result["warnings"])
+    assert any("missing or unknown status" in w for w in result["warnings"])
+    assert len(result["open_action_items"]) == 1
+
+
+def test_status_review_beats_ready(tmp_path, capsys):
+    fixture = STATUS_FIXTURE.replace("2-1-personality-system: backlog", "2-1-personality-system: review")
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert result["recommendation"]["skill"] == "bmad-code-review"
+    assert result["recommendation"]["story_key"] == "2-1-personality-system"
+    assert any("review" in r for r in result["risks"])
+
+
+def test_status_in_progress_beats_all(tmp_path, capsys):
+    fixture = STATUS_FIXTURE.replace("2-1-personality-system: backlog", "2-1-personality-system: in-progress")
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert result["recommendation"]["skill"] == "bmad-build"
+    assert result["recommendation"]["story_key"] == "2-1-personality-system"
+    assert result["recommendation"]["reason"] == "resume the in-progress story"
+
+
+def test_status_staleness_and_orphan_risks(tmp_path, capsys):
+    fixture = (STATUS_FIXTURE
+               .replace("last_updated: 07-30-2026 09:00", "last_updated: 01-02-2026 09:00")
+               .replace("  epic-2-retrospective: optional",
+                        "  epic-2-retrospective: optional\n  5-1-ghost: backlog"))
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert any("stale" in r for r in result["risks"])
+    assert any("orphaned story '5-1-ghost'" in r for r in result["risks"])
+
+
+def test_status_unparseable_timestamp_warns_instead_of_silence(tmp_path, capsys):
+    fixture = STATUS_FIXTURE.replace("last_updated: 07-30-2026 09:00", "last_updated: whenever")
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert any("staleness check skipped" in w for w in result["warnings"])
+
+
+def test_status_iso_and_date_typed_stamps_do_not_crash(tmp_path, capsys):
+    fixture = (STATUS_FIXTURE
+               .replace("generated: 01-01-2026 09:00", "generated: 2026-01-01")
+               .replace("last_updated: 07-30-2026 09:00", "last_updated: 2026-01-02"))
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert result["ok"] is True
+    assert result["generated"] == "2026-01-01"
+    assert any("stale" in r for r in result["risks"])  # ISO stamp still parses
+
+
+def test_status_all_done_recommends_retro_then_nothing(tmp_path, capsys):
+    fixture = (STATUS_FIXTURE
+               .replace("1-2-account-management: drafted", "1-2-account-management: done")
+               .replace("2-1-personality-system: backlog", "2-1-personality-system: done"))
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert result["recommendation"]["skill"] == "bmad-retrospective"
+    assert "epic-1-retrospective" in result["recommendation"]["reason"]
+    fixture_done = fixture.replace("epic-1-retrospective: optional", "epic-1-retrospective: done") \
+                          .replace("epic-2-retrospective: optional", "epic-2-retrospective: done")
+    result = run_status(tmp_path, capsys, fixture=fixture_done)
+    assert result["all_done"] is True and result["recommendation"] is None
+
+
+def test_status_odd_retro_key_reports_instead_of_crashing(tmp_path, capsys):
+    fixture = (STATUS_FIXTURE
+               .replace("1-2-account-management: drafted", "1-2-account-management: done")
+               .replace("2-1-personality-system: backlog", "2-1-personality-system: done")
+               .replace("epic-1-retrospective: optional", "epic-1-retrospective: done")
+               .replace("epic-2-retrospective: optional",
+                        "epic-2-retrospective: done\n  epic-abc-retrospective: optional"))
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert result["ok"] is True
+    assert {"key": "epic-abc-retrospective", "status": "optional"} in result["unrecognized"]
+    assert any("unrecognized key" in r for r in result["risks"])
+
+
+def test_status_illegal_status_reported(tmp_path, capsys):
+    fixture = STATUS_FIXTURE.replace("2-1-personality-system: backlog", "2-1-personality-system: shipped")
+    result = run_status(tmp_path, capsys, fixture=fixture)
+    assert {"key": "2-1-personality-system", "status": "shipped"} in result["illegal"]
+
+
+def test_status_missing_file_fails_json(tmp_path, capsys):
+    with pytest.raises(SystemExit) as excinfo:
+        mod.main(["status", "--status-file", str(tmp_path / "nope.yaml")])
+    assert excinfo.value.code == 1
+    assert json.loads(capsys.readouterr().out)["ok"] is False
+
+
+def run_validate(tmp_path, capsys, content):
+    status_file = tmp_path / "sprint-status.yaml"
+    if content is not None:
+        status_file.write_text(content, encoding="utf-8")
+    mod.main(["validate", "--status-file", str(status_file)])
+    return json.loads(capsys.readouterr().out)
+
+
+def test_validate_clean_file(tmp_path, capsys):
+    clean = STATUS_FIXTURE.replace("1-2-account-management: drafted", "1-2-account-management: backlog")
+    result = run_validate(tmp_path, capsys, clean)
+    assert result["valid"] is True and result["problems"] == []
+
+
+def test_validate_reports_problems_without_crashing(tmp_path, capsys):
+    broken = (STATUS_FIXTURE
+              .replace("2-1-personality-system: backlog", "2-1-personality-system: shipped")
+              .replace("epic-2-retrospective: optional",
+                       "epic-2-retrospective: optional\n  weird-key: done")
+              .replace("last_updated: 07-30-2026 09:00", "last_updated: whenever"))
+    result = run_validate(tmp_path, capsys, broken)
+    assert result["valid"] is False
+    assert any("illegal story status 'shipped'" in p for p in result["problems"])
+    assert any("unrecognized key 'weird-key'" in p for p in result["problems"])
+    assert any("'last_updated' timestamp" in p for p in result["problems"])
+    assert {"key": "1-2-account-management", "from": "drafted", "to": "ready-for-dev"} in result["legacy_mapped"]
+
+
+def test_validate_missing_file_and_bad_yaml(tmp_path, capsys):
+    result = run_validate(tmp_path, capsys, None)
+    assert result["valid"] is False and "does not exist" in result["problems"][0]
+    result = run_validate(tmp_path, capsys, "development_status: [unclosed\n")
+    assert result["valid"] is False and "not valid YAML" in result["problems"][0]
+    result = run_validate(tmp_path, capsys, "- a\n- b\n")
+    assert result["valid"] is False and any("not a mapping" in p for p in result["problems"])
+
+
+if __name__ == "__main__":
+    sys.exit(pytest.main([__file__, "-q"]))
diff --git a/.claude/skills/bmad-sprint-planning/sprint-status-template.yaml b/.claude/skills/bmad-sprint-planning/sprint-status-template.yaml
new file mode 100644
index 0000000..cc4dd7c
--- /dev/null
+++ b/.claude/skills/bmad-sprint-planning/sprint-status-template.yaml
@@ -0,0 +1,71 @@
+# Sprint Status Template
+# This is an EXAMPLE showing the expected format
+# The actual file will be generated with all epics/stories from your epic files
+
+# generated: {date}
+# project: {project_name}
+# project_key: {project_key}
+# tracking_system: {tracking_system}
+# story_location: {story_location}
+
+# STATUS DEFINITIONS:
+# ==================
+# Epic Status:
+#   - backlog: Epic not yet started
+#   - in-progress: Epic actively being worked on
+#   - done: All stories in epic completed
+#
+# Story Status:
+#   - backlog: Story only exists in epic file
+#   - ready-for-dev: Story file created, ready for development
+#   - in-progress: Developer actively working on implementation
+#   - review: Implementation complete, ready for review
+#   - done: Story completed
+#
+# Retrospective Status:
+#   - optional: Can be completed but not required
+#   - done: Retrospective has been completed
+#
+# Action Item Status:
+#   - open: Committed during a retrospective, not yet addressed
+#   - in-progress: Actively being worked on
+#   - done: Completed
+#
+# WORKFLOW NOTES:
+# ===============
+# - Epic transitions to 'in-progress' automatically when its first story starts (via build's sprint sync)
+# - Stories can be worked in parallel if team capacity allows
+# - Developer typically creates the next story after the previous one is 'done' to incorporate learnings
+# - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)
+# - Retrospective appends its action items to action_items; the status view surfaces open ones
+
+# EXAMPLE STRUCTURE (your actual epics/stories will replace these):
+# Timestamps use MM-DD-YYYY HH:MM.
+
+generated: 05-06-2025 21:30
+last_updated: 05-06-2025 21:30
+project: My Awesome Project
+project_key: NOKEY
+tracking_system: file-system
+story_location: "docs/stories"
+
+development_status:
+  epic-1: backlog
+  1-1-user-authentication: done
+  1-2-account-management: ready-for-dev
+  1-3-plant-data-model: backlog
+  1-4-add-plant-manual: backlog
+  epic-1-retrospective: optional
+
+  epic-2: backlog
+  2-1-personality-system: backlog
+  2-2-chat-interface: backlog
+  2-3-llm-integration: backlog
+  epic-2-retrospective: optional
+
+# Action items committed during retrospectives (section created by the retrospective workflow)
+action_items:
+  - epic: 1
+    action: "Add error-handling review to the code review checklist"
+    owner: "Charlie"
+    status: open
diff --git a/.claude/skills/bmad-sprint-status/SKILL.md b/.claude/skills/bmad-sprint-status/SKILL.md
new file mode 100644
index 0000000..3c3cbec
--- /dev/null
+++ b/.claude/skills/bmad-sprint-status/SKILL.md
@@ -0,0 +1,26 @@
+---
+name: bmad-sprint-status
+description: 'Deprecated — forwards to bmad-sprint-planning (status view).'
+---
+
+# DEPRECATED — forwards to bmad-sprint-planning (status view)
+
+This skill was consolidated into `bmad-sprint-planning`, which now owns the whole sprint-status artifact: gate it, generate it, view it. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-sprint-status.toml` override files keep working. New work should invoke `bmad-sprint-planning` directly — "show sprint status" routes straight to the status view.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-sprint-status.toml` and `bmad-sprint-status.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+
+2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+
+3. Emit a deprecation notice to the user in `{communication_language}`:
+
+   > Notice: `bmad-sprint-status` is deprecated and will be removed in a future release. It now forwards to `bmad-sprint-planning`, whose status view covers everything this skill did. To silence this notice, invoke `bmad-sprint-planning` directly next time (e.g. "show sprint status") and migrate any `_bmad/custom/bmad-sprint-status.toml` overrides to `_bmad/custom/bmad-sprint-planning.toml`.
+
+4. Invoke `bmad-sprint-planning` with the following context. Pass these as the activating context so it honors them instead of resolving its own customization from scratch:
+
+   - **Intent:** `status view` — skip `bmad-sprint-planning`'s usual intent detection and its readiness gate.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-sprint-planning`'s own `customize.toml` for the four legacy fields: `activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, and `on_complete` = the resolved values from step 1.
+   - **Original user input:** forward whatever the user said when invoking this skill verbatim.
+
+   `bmad-sprint-planning` takes the workflow from here. Do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-sprint-status/customize.toml b/.claude/skills/bmad-sprint-status/customize.toml
new file mode 100644
index 0000000..c3c5600
--- /dev/null
+++ b/.claude/skills/bmad-sprint-status/customize.toml
@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-sprint-status. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All stories must include testable acceptance criteria."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches its final step,
+# after sprint status is summarized and risks are surfaced. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/.claude/skills/bmad-technical-research/SKILL.md b/.claude/skills/bmad-technical-research/SKILL.md
new file mode 100644
index 0000000..6fe3468
--- /dev/null
+++ b/.claude/skills/bmad-technical-research/SKILL.md
@@ -0,0 +1,14 @@
+---
+name: bmad-technical-research
+description: 'Deprecated — forwards to bmad-deep-recon (technical type).'
+---
+
+# DEPRECATED — forwards to bmad-deep-recon (technical type)
+
+This skill was consolidated into `bmad-deep-recon`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-technical-research.toml` override files keep working. New work should invoke `bmad-deep-recon` directly — it drafts deep-research prompts for outside tools, processes finished reports into downstream-ready summaries, and runs research directly, across market, domain, technical, competitive, user-voice, and academic-lit types (plus a select shape for choose-between decisions and custom types).
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-technical-research.toml` and `bmad-technical-research.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+2. Emit a deprecation notice to the user (in their configured communication language): `bmad-technical-research` is deprecated and forwards to `bmad-deep-recon` with the technical type. To silence this notice and access the full new surface (draft/process/run modes, research types, verification levels, HTML briefing, handoffs), migrate `_bmad/custom/bmad-technical-research.toml` to `_bmad/custom/bmad-deep-recon.toml` and invoke `bmad-deep-recon` directly.
+3. Invoke `bmad-deep-recon` with: **research type** `technical` (skip its type inference), the four legacy fields above as pre-resolved values, and the user's original input verbatim. `bmad-deep-recon` takes the workflow from here — do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-ux/SKILL.md b/.claude/skills/bmad-ux/SKILL.md
new file mode 100644
index 0000000..2450ec8
--- /dev/null
+++ b/.claude/skills/bmad-ux/SKILL.md
@@ -0,0 +1,90 @@
+---
+name: bmad-ux
+description: Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
+---
+# BMad UX
+
+## Overview
+
+You are a master UX facilitator. **Elicit and capture** the user's vision, never impose yours. Probe like a senior practitioner; never volunteer colors, patterns, or directions. Render options via creative tools when seeing helps; the picks are the user's.
+
+Produce two peer contracts: **`DESIGN.md`** (visual identity per the [Google Labs spec](https://github.com/google-labs-code/design.md) — owns *how it looks*) and **`EXPERIENCE.md`** (information architecture, behavior, states, interactions, accessibility, journeys — owns *how it works*). EXPERIENCE.md cross-references DESIGN.md tokens by name using `{path.to.token}` syntax. Both spines win on conflict with any mock, wireframe, or import.
+
+## The DESIGN.md spine
+
+Per the [Google Labs spec](https://github.com/google-labs-code/design.md). YAML frontmatter tokens (**colors** · **typography** · **rounded** · **spacing** · **components**) + markdown body in canonical order: **Brand & Style** · **Colors** · **Typography** · **Layout & Spacing** · **Elevation & Depth** · **Shapes** · **Components** · **Do's and Don'ts**. Sections omittable; order locked when present. Spec rules: `references/design-md-spec.md`. Shape: read every entry in `{workflow.design_md_examples}`.
+
+## The EXPERIENCE.md spine
+
+Always: **Foundation** (form-factor, UI system when present; DESIGN.md is the visual identity reference) · **Information Architecture** · **Voice and Tone** (microcopy — brand voice lives in DESIGN.md.Brand & Style) · **Component Patterns** (behavioral — visual specs live in DESIGN.md.Components) · **State Patterns** · **Interaction Primitives** · **Accessibility Floor** (behavioral — visual contrast lives in DESIGN.md) · **Key Flows** (named-protagonist journeys with a climax beat).
+
+When triggered: **Inspiration & Anti-patterns** · **Responsive & Platform**.
+
+Invent sections for product-specific concerns. Shape: read every entry in `{workflow.experience_md_examples}`.
+
+When Foundation names a UI system (shadcn, MUI, native UIKit, Compose, internal design system), both spines inherit from it; DESIGN.md tokens reference or extend the system's defaults, EXPERIENCE.md specifies only the behavioral delta.
+
+## Sources
+
+UX may lead, follow, or stand alone. Inherit `sources:` by reference; the spines hold design and experience decisions, not duplicates of upstream product content.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools; consult them alongside generic web research on the same triggers, org tools preferred when their directive matches.
+3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
+4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn. In the greeting, let the user know `bmad-party-mode` and `bmad-advanced-elicitation` are always available. Then scan for misroute on the first message: PRD → `bmad-prd`; architecture → `bmad-architecture`; game UX → BMad GDS; agent/skill → `bmad-workflow-builder`; brief → `bmad-product-brief`.
+5. Detect intent: **Create**, **Update**, **Validate**. For Create, before binding a fresh workspace, scan `{workflow.ux_output_path}` for prior in-progress runs (folders matching `{workflow.run_folder_pattern}` whose `DESIGN.md` frontmatter `status` is not `final`) and offer to resume rather than starting over.
+
+Run `{workflow.activation_steps_append}`.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
+## Modes
+
+**Create.** Bind `{doc_workspace}` to `{workflow.ux_output_path}/{workflow.run_folder_pattern}/`. Create `.working/` and `imports/`; seed the memlog with `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field topic="<product/UX>"`; create `DESIGN.md` (frontmatter only) and `EXPERIENCE.md` (frontmatter only). Run Discovery → Finalize.
+
+**Update.** Read spines + memlog + sources. If `.memlog.md` is missing, init it with `uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace}` — this update is entry one. Surface conflicts with prior decisions. Run Finalize.
+
+**Validate.** See `references/validate.md`.
+
+## Discovery
+
+**Capture; do not author.** The spines are distilled at Finalize toward the memlog. Decisions → `.memlog.md` (canonical), each appended via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <decision|change|override|assumption|event> --text "…"` — never hand-edited; a resume reloads it. Creative-tool artifacts → `.working/`. User-supplied visuals (Figma, sketches, brand decks, image folders) → `imports/`, one `memlog.py append` per item. Spines win on conflict.
+
+**Source scan.** Glob `{planning_artifacts}/` for candidate input paths; surface paths only — never read content in the parent. User confirms which apply or adds others; subagent-extracts on confirm.
+
+Brain dump first — even when the user opens with paragraphs (that's intake). Subagent-extract big docs. One "anything else?" probe. Stakes: hobby / internal / consumer / regulated.
+
+Working mode:
+
+- **Fast path** — batch gaps, draft both spines with `[ASSUMPTION]` tags, skip creative tools.
+- **Coaching path** — walk decisions; creative tools woven in.
+- **Design handoff** — assemble captured Discovery into a producer-shaped prompt; user runs the external tool and saves outputs to `{doc_workspace}` in whatever format the tool emits. Producer registry: `{workflow.design_handoffs}` (default: Google Stitch). EXPERIENCE.md can follow via Update mode when ready.
+
+Creative tools — scan `{workflow.creative_tools}`, invoke when seeing helps. Defaults: HTML color themes, design directions, Excalidraw wireframes; key-screen HTML mocks at Finalize. See `references/creative-tools.md`. Research subagents on demand; consult `{workflow.external_sources}` when entries match.
+
+Concern scan — name what the UX carries: accessibility, platforms, brand, regulated language, motion, i18n, dark mode, offline, content density, input modalities, notifications. Open list; drives invented sections.
+
+Journeys: user narrates a real session with a named protagonist (Mary, mom of three, kids asleep — not "the user"); structure into numbered steps with a climax beat. Mirror source-spec names verbatim when defined.
+
+Form-factor: mobile / web / desktop / multi-surface must resolve before IA closes. Named-protagonist journeys often derive it (Pary on iPad implies an iPad surface; Skeeter on Android adds a multi-surface need); when journeys don't disambiguate, probe.
+
+Surface closure: stated needs become screens through journeys. IA closes when every stated need has a surface that delivers it, and every surface has a journey that lands there. When closure fails, probe — never invent the missing piece.
+
+## Reviewer Gate
+
+Used by Validate and Finalize. **Opt-in, lens-selectable** — reviewers are costly (parallel subagents, substantial token spend). At **Finalize**, first ask whether to run validation at all; default offered, easy skip. At **Validate** intent the user already opted in — skip that question. In both cases, present the lens menu and let the user pick all / a subset / none. Menu: rubric walker (`references/validate.md`) + `{workflow.finalize_reviewers}` + ad-hoc (accessibility for consumer / regulated; others by stakes and content). Picked lenses dispatch as parallel subagents → each writes `review-{slug}.md`, returns a compact summary. If any lens ran, run the synthesis pipeline in `references/validate.md`.
+
+## Finalize
+
+Outcomes, in order:
+
+- **Spines distilled.** Subagent reads `.memlog.md`, `.working/`, `imports/`, sources; produces `DESIGN.md` against `## The DESIGN.md spine` + `{workflow.design_md_examples}` and `EXPERIENCE.md` against `## The EXPERIENCE.md spine` + `{workflow.experience_md_examples}`. Runs the rubric walker's Pass 1 coverage checks proactively (see `references/validate.md`). Surface gaps; never invent.
+- **Inputs reconciled.** Subagent per user-supplied input → `reconcile-{slug}.md`. Surface dropped qualitative ideas.
+- **Reviewer Gate offered.** Ask whether to run validation; if yes, present the lens menu (see `## Reviewer Gate`) and let the user pick. If any lens ran, resolve findings before polish; otherwise proceed.
+- **Open items triaged.** Open Questions, `[ASSUMPTION]`, `[NOTE FOR UX]`. Phase-blockers one at a time; non-blockers → `memlog.py append`.
+- **Key-screen mocks rendered.** Key-screens tool → `.working/` for surfaces where layout drives behavior or anchors visual language.
+- **Mock coverage confirmed.** Walk every IA surface; classify *mocked* vs *spine-only*. Ask: *"These will be built from spine tables alone — any need a visual reference?"* Render more if named; log spine-only choices.
+- **Layout extracted, artifacts promoted.** Distill subagent re-reads each `.working/` and `imports/` artifact; lifts visual decisions into DESIGN.md and behavioral decisions into EXPERIENCE.md. Promote `.working/` keepers to `mockups/` (HTML) or `wireframes/` (Excalidraw); imports stay. Inline relative links at relevant spine sections; state spines-win-on-conflict once.
+- **Polished, handed off, closed.** Apply `{workflow.doc_standards}` in order. Execute `{workflow.external_handoffs}`; surface URLs. Set both files' `status: final`, `updated: {date}`. Log finalization via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type event --text "spines finalized"`. Share paths. Common next: `bmad-architecture`, `bmad-create-epics-and-stories`, `bmad-build`. Run `{workflow.on_complete}`.
diff --git a/.claude/skills/bmad-ux/assets/color-themes.md b/.claude/skills/bmad-ux/assets/color-themes.md
new file mode 100644
index 0000000..2b23b46
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/color-themes.md
@@ -0,0 +1,9 @@
+# Color Themes Renderer
+
+Subagent prompt. Produce one self-contained HTML page at the supplied `.working/color-themes-{n}.html` path showing 4-6 distinct theme variations side by side so the user can pick.
+
+Each variation: header (name + one-line emotional register), token chips for every semantic role decided so far, and one realistic UI snippet using the palette (content drawn from the conversation, not lorem). Include light and dark side-by-side when both modes are in scope. Avoid near-identical pastels — variations must differ in register, not just hue.
+
+Inline CSS only, system font stack, no JS, no network. Document concrete hex values in `<style>` comments per variation so the user can lift them if they pick that theme. The spine itself stays semantic.
+
+Return to the parent: file path, one-line per variation, mode coverage. Do not dump HTML into the parent context. If interactive, open the file with the platform opener — `open "PATH"` on macOS, `xdg-open` on Linux, `start ""` on Windows, path always double-quoted. On failure, give the user the path instead.
diff --git a/.claude/skills/bmad-ux/assets/design-directions.md b/.claude/skills/bmad-ux/assets/design-directions.md
new file mode 100644
index 0000000..289b270
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/design-directions.md
@@ -0,0 +1,9 @@
+# Design Directions Renderer
+
+Subagent prompt. Produce 3-6 distinct visual directions for the product's hero screen, each a separate self-contained HTML file at `.working/direction-{slug}.html` (or one combined `directions-{n}.html` if the parent's intent says side-by-side).
+
+Each direction is a *complete visual personality* applied to the same key screen — not a palette swap. Differ on density, type weight, motion implication, brand register. Each file: 2-3 sentence rationale, near-1:1 hero screen mockup in a phone or browser frame, ideally a secondary screen, at least one state variant visible (aging row, empty state, etc).
+
+Use real product content from the conversation. Voice/tone from `.memlog.md` applied to every visible string — no lorem. Inline CSS, system fonts, no JS or network. Document hex values in `<style>` comments per direction.
+
+Return to the parent: file paths, one-line personality summary per direction, what hero screen was depicted. Do not dump HTML into parent context. If interactive, open each file in the browser.
diff --git a/.claude/skills/bmad-ux/assets/design-example-editorial.md b/.claude/skills/bmad-ux/assets/design-example-editorial.md
new file mode 100644
index 0000000..e72dc7d
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/design-example-editorial.md
@@ -0,0 +1,158 @@
+---
+name: Linen & Logic
+colors:
+  surface: '#fbf9f4'
+  surface-dim: '#dbdad5'
+  surface-bright: '#fbf9f4'
+  surface-container-lowest: '#ffffff'
+  surface-container-low: '#f5f3ee'
+  surface-container: '#f0eee9'
+  surface-container-high: '#eae8e3'
+  surface-container-highest: '#e4e2dd'
+  on-surface: '#1b1c19'
+  on-surface-variant: '#4e453d'
+  inverse-surface: '#30312e'
+  inverse-on-surface: '#f2f1ec'
+  outline: '#80756b'
+  outline-variant: '#d1c4b9'
+  surface-tint: '#715a3f'
+  primary: '#59452b'
+  on-primary: '#ffffff'
+  primary-container: '#735c41'
+  on-primary-container: '#f5d6b4'
+  inverse-primary: '#e0c1a1'
+  secondary: '#a43b2c'
+  on-secondary: '#ffffff'
+  secondary-container: '#fd7d69'
+  on-secondary-container: '#71160b'
+  tertiary: '#374a5f'
+  on-tertiary: '#ffffff'
+  tertiary-container: '#4f6278'
+  on-tertiary-container: '#caddf8'
+  error: '#ba1a1a'
+  on-error: '#ffffff'
+  error-container: '#ffdad6'
+  on-error-container: '#93000a'
+  primary-fixed: '#fdddbb'
+  primary-fixed-dim: '#e0c1a1'
+  on-primary-fixed: '#281804'
+  on-primary-fixed-variant: '#58432a'
+  secondary-fixed: '#ffdad4'
+  secondary-fixed-dim: '#ffb4a7'
+  on-secondary-fixed: '#400200'
+  on-secondary-fixed-variant: '#842417'
+  tertiary-fixed: '#d0e4ff'
+  tertiary-fixed-dim: '#b4c8e2'
+  on-tertiary-fixed: '#071d30'
+  on-tertiary-fixed-variant: '#35485d'
+  background: '#fbf9f4'
+  on-background: '#1b1c19'
+  surface-variant: '#e4e2dd'
+typography:
+  display-lg:
+    fontFamily: Libre Caslon Text
+    fontSize: 48px
+    fontWeight: '400'
+    lineHeight: '1.1'
+    letterSpacing: -0.02em
+  display-lg-mobile:
+    fontFamily: Libre Caslon Text
+    fontSize: 36px
+    fontWeight: '400'
+    lineHeight: '1.1'
+  headline-md:
+    fontFamily: Libre Caslon Text
+    fontSize: 32px
+    fontWeight: '400'
+    lineHeight: '1.2'
+  headline-sm:
+    fontFamily: Libre Caslon Text
+    fontSize: 24px
+    fontWeight: '400'
+    lineHeight: '1.3'
+  body-lg:
+    fontFamily: DM Sans
+    fontSize: 18px
+    fontWeight: '400'
+    lineHeight: '1.6'
+    letterSpacing: 0.01em
+  body-md:
+    fontFamily: DM Sans
+    fontSize: 16px
+    fontWeight: '400'
+    lineHeight: '1.6'
+  label-caps:
+    fontFamily: DM Sans
+    fontSize: 12px
+    fontWeight: '500'
+    lineHeight: '1.4'
+    letterSpacing: 0.1em
+  caption:
+    fontFamily: DM Sans
+    fontSize: 13px
+    fontWeight: '400'
+    lineHeight: '1.4'
+rounded:
+  sm: 0.125rem
+  DEFAULT: 0.25rem
+  md: 0.375rem
+  lg: 0.5rem
+  xl: 0.75rem
+  full: 9999px
+spacing:
+  unit: 8px
+  gutter: 24px
+  margin-mobile: 20px
+  margin-desktop: 64px
+  editorial-gap: 80px
+---
+
+## Brand & Style
+
+The design system is rooted in the philosophy of "Slow Design"—an intentional departure from the frantic pace of fast fashion. It evokes a tactile, "linen-weight" sensation through high-end editorial layouts and a restrained aesthetic. The target audience values provenance over presence, seeking a reflective and sophisticated discovery experience that feels as much like a boutique magazine as a digital marketplace.
+
+The style is **Editorial Minimalism** with **Tactile** accents. It prioritizes breathable white space, asymmetrical layouts that mimic printed lookbooks, and a soft, sun-faded palette. Every interaction is designed to be deliberate and "anti-hype," eschewing aggressive animations for subtle transitions and quiet confidence.
+
+## Colors
+
+The palette is inspired by natural fibers and weathered landscapes. 
+- **Warm White (#F9F7F2)** serves as the primary canvas, providing a soft, non-clinical background that reduces eye strain.
+- **Bone (#E3DED1)** and **Dust (#C2B9A7)** are used for structural depth, subtle dividers, and secondary surfaces.
+- **Tobacco (#735C41)** is the primary ink color, used for high-contrast typography and essential UI elements.
+- **Sun-faded Red (#B84A39)** and **Wool Blanket Blue (#4A5D73)** are used sparingly as "organic accents"—highlighting editorial picks or signifying subtle state changes without disrupting the tranquil atmosphere.
+
+## Typography
+
+Typography is the primary vehicle for the brand’s sophisticated voice. 
+- **Libre Caslon Text** is the voice of the curator. Its classic proportions and elegant serifs provide the editorial weight required for discovery and storytelling.
+- **DM Sans** provides a quiet, functional counterpoint. It is used for body copy and navigational elements, ensuring clarity without competing with the headlines. 
+
+Large display titles should often use "optical sizing" logic—tighter leading and slightly negative letter spacing to create a cohesive visual block. Labels are always tracked out (0.1em) to maintain a sense of airy premiumness.
+
+## Layout & Spacing
+
+This design system employs a **Fluid Editorial Grid**. While it follows a 12-column structure on desktop, it encourages "asymmetrical breathing room"—intentionally leaving columns empty to direct focus toward high-quality imagery.
+
+Spacing is generous. The `editorial-gap` (80px+) should be used between major content sections to allow the user to pause and reflect. Mobile layouts should maintain a minimum of 20px side margins to ensure the content feels framed like a page, rather than bleeding to the edges of the device. Elements should lean toward vertical stacks to mimic the scroll of a digital journal.
+
+## Elevation & Depth
+
+Depth is communicated through **Tonal Layering** and **Ambient Shadows** rather than sharp borders.
+- **Surfaces:** Use the "Bone" color to define containers against the "Warm White" base. 
+- **Shadows:** Shadows are highly diffused and tinted with the "Tobacco" hue (`rgba(115, 92, 65, 0.08)`). They should feel like a soft glow of light hitting fabric, with large blur radii (20px+) and very low opacity.
+- **Borders:** When borders are necessary, they are 1px thick and rendered in "Dust," creating a "ghost" outline that barely separates elements from the background.
+
+## Shapes
+
+The shape language is **Soft (0.25rem)**. While a sharp edge feels too aggressive and a pill-shape feels too digital/tech-heavy, a subtle rounding of corners mimics the natural softening of woven textiles over time. 
+
+Larger containers (Cards, Modals) may use `rounded-lg` (0.5rem) to emphasize their tactile, object-like quality. Imagery should always follow these corner radii to maintain a cohesive, "framed" appearance.
+
+## Components
+
+- **Buttons:** Primary buttons use a solid "Tobacco" fill with "Warm White" text. Secondary buttons are "Bone" with "Tobacco" text or simply "Tobacco" text with a 1px "Dust" border. Padding is generous horizontally to create an elegant, elongated silhouette.
+- **Cards:** Editorial cards feature large imagery, a "headline-sm" title, and a "caption" subline. Shadows are only applied on hover to simulate a gentle lift.
+- **Inputs:** Minimalist underlines in "Dust" that transition to "Tobacco" on focus. Label text remains in "label-caps" above the field.
+- **Chips/Tags:** Used for material types (e.g., "100% Linen"). These are rendered in "Bone" backgrounds with "Tobacco" text, using the "Soft" corner radius.
+- **Icons:** Must be "Hand-drawn" or "Fine-line" style. Lines should have slight imperfections and vary in weight to reinforce the tactile, artisanal nature of the fashion being discovered.
+- **Navigation:** A simple, centered bottom bar or a top-weighted "Ghost" header that disappears on scroll to maximize the editorial viewport.
\ No newline at end of file
diff --git a/.claude/skills/bmad-ux/assets/design-example-mobile.md b/.claude/skills/bmad-ux/assets/design-example-mobile.md
new file mode 100644
index 0000000..1c301c8
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/design-example-mobile.md
@@ -0,0 +1,93 @@
+---
+name: Quill
+description: Daily writing companion. Calm, intentional, dark-mode-by-default. No streaks, no gamification.
+colors:
+  surface-base: '#FAF9F7'
+  surface-raised: '#FFFFFF'
+  ink-primary: '#1A1B1F'
+  ink-secondary: '#6B655A'
+  ink-disabled: '#B5AFA5'
+  accent: '#A87434'
+  border-hairline: '#E8E4DD'
+  surface-base-dark: '#1A1B1F'
+  surface-raised-dark: '#23252B'
+  ink-primary-dark: '#F0EDE8'
+  ink-secondary-dark: '#A39E94'
+  ink-disabled-dark: '#5E5A53'
+  accent-dark: '#D4A574'
+  border-hairline-dark: '#2E3036'
+typography:
+  title:
+    note: 'Platform native — iOS Title 1 · Android Headline Small'
+  body:
+    note: 'Platform native — iOS Body · Android Body Large'
+  meta:
+    note: 'Platform native — iOS Footnote · Android Body Small'
+rounded:
+  sm: 6px
+  md: 12px
+spacing:
+  '1': 4px
+  '2': 8px
+  '3': 12px
+  '4': 16px
+  '5': 24px
+  '6': 32px
+---
+
+## Brand & Style
+
+Quill is designed against the grain of contemporary habit apps. Where most products weaponize the user's calendar with streak counters and re-engagement nudges, Quill insists on something quieter — a daily prompt, a place to write, and the unspoken assurance that today's entry is enough. Showing up is the point, not the streak.
+
+The visual language follows. Calm surfaces in warm off-white (light) or deep ink (dark, the default). Generous breathing room. No chromatic color competing for attention except a single warm tobacco that signals save-and-send. Text-first. Hand-on-paper, not buzz-on-screen.
+
+## Colors
+
+The palette is restrained on purpose — a writing surface should not compete with the writing.
+
+- **Warm White (`#FAF9F7`)** is the primary canvas in light mode. Slightly warm to reduce eye strain and keep the surface from feeling clinical.
+- **Deep Ink (`#1A1B1F`)** is the dark-mode canvas and the primary body text color in light mode. Quill defaults to dark because most writing happens at night.
+- **Tobacco (`#A87434` light / `#D4A574` dark)** is the only chromatic color. Used exclusively for the save indicator and primary action — never for decoration, never for state badges.
+- **Hairline (`#E8E4DD` light / `#2E3036` dark)** separates list items at the lowest possible contrast. Anything heavier feels like UI rather than paper.
+
+Avoid: red error fills (Quill is a journal, not a form), gradients (the surface is paper), and saturated accent variants — one accent, used sparingly.
+
+## Typography
+
+Platform conventions are the spec. iOS uses Title 1 / Body / Footnote; Android uses Headline Small / Body Large / Body Small. Dynamic type honored at every level — the largest accessibility setting must still render legibly without truncation.
+
+Headlines are rare. The Today prompt is set in `title`; everything else is `body` or `meta`. No display sizes, no all-caps labels.
+
+## Layout & Spacing
+
+Scale: 4 / 8 / 12 / 16 / 24 / 32 px. The largest gaps land between major surfaces; the smallest sit between tightly related elements. Vertical rhythm follows a hard rule: composer breathes, list items don't.
+
+Mobile margins follow platform conventions (iOS 16pt, Android 16dp). Single-column always; modal stacks one level deep, never two.
+
+## Elevation & Depth
+
+Quill avoids elevation as a visual device. Cards and composer surfaces sit on `surface-raised`, distinguished from `surface-base` only by tone. Shadows are reserved for the rare moment of literal physical metaphor — never for hierarchy. Hierarchy comes from layout and typography, not shadow.
+
+## Shapes
+
+`rounded/sm` (6px) for inputs, list rows, and small surfaces. `rounded/md` (12px) for cards and the composer. Nothing fully rounded; no pills, no perfect circles for surfaces. The aesthetic is paper-with-soft-corners, not iOS-button-pill.
+
+Imagery follows container corners exactly.
+
+## Components
+
+- **Prompt card** — `surface-raised`. One per day. Today's prompt in `title`. Tap to open composer. No icon, no decoration; the prompt itself is the affordance.
+- **Composer** — Full-screen text view. Clean text field, generous vertical padding, single-line save indicator in the header.
+- **Save indicator** — Text only. Uses `ink-secondary`, never a checkmark icon, never a colored badge.
+- **Entry row** (Library) — Date in `meta`, first line of body in `body` (truncated to one line). Hairline divider only, no fill.
+- **Settings row** — Label left, value or chevron right. Tobacco accent only on destructive confirmations.
+
+## Do's and Don'ts
+
+| Do | Don't |
+|---|---|
+| Single accent color, used sparingly on save & primary action | Color-code by sentiment, mood, or category |
+| Text-only state indicators (`Saved.`) | Iconography for state (✓, ⚠, ●) |
+| Hairline dividers at lowest legible contrast | Card shadows, gradient fills, accent fills behind text |
+| Generous vertical rhythm in composer | Compress to fit more on screen |
+| Honor platform conventions for navigation | Override platform nav with custom drawer or hamburger |
diff --git a/.claude/skills/bmad-ux/assets/design-example-shadcn.md b/.claude/skills/bmad-ux/assets/design-example-shadcn.md
new file mode 100644
index 0000000..a7147f8
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/design-example-shadcn.md
@@ -0,0 +1,109 @@
+---
+name: Drift
+description: Focused task tracker for solo founders and small async teams. shadcn/ui on Next.js + Tailwind; this DESIGN.md specifies the brand-layer delta only.
+colors:
+  # Brand overrides on top of shadcn defaults. All unlisted tokens inherit
+  # from shadcn (background, foreground, muted, muted-foreground, popover,
+  # popover-foreground, card, card-foreground, border, input, ring, destructive).
+  primary: '#0F4C81'
+  primary-foreground: '#FFFFFF'
+  accent: '#F59E0B'
+  accent-foreground: '#1A1208'
+  primary-dark: '#5C8AC2'
+  primary-foreground-dark: '#0A1A2A'
+  accent-dark: '#FBC470'
+  accent-foreground-dark: '#1A1208'
+typography:
+  # Body, label, and muted inherit from shadcn (Geist Sans). Only display is overridden.
+  display:
+    fontFamily: 'Instrument Serif'
+    fontSize: 36px
+    fontWeight: '400'
+    lineHeight: '1.15'
+    letterSpacing: -0.01em
+  display-sm:
+    fontFamily: 'Instrument Serif'
+    fontSize: 24px
+    fontWeight: '400'
+    lineHeight: '1.2'
+rounded:
+  # Tighter than shadcn defaults — Drift reads sharper.
+  sm: 4px
+  md: 6px
+  lg: 8px
+spacing:
+  # shadcn / Tailwind defaults inherited; no overrides.
+components:
+  button-primary:
+    background: '{colors.primary}'
+    foreground: '{colors.primary-foreground}'
+    radius: '{rounded.md}'
+  focus-card:
+    background: '{colors.accent}'
+    foreground: '{colors.accent-foreground}'
+    radius: '{rounded.md}'
+    border: 'none'
+  command-palette-result-active:
+    background: '{colors.accent}'
+    foreground: '{colors.accent-foreground}'
+---
+
+## Brand & Style
+
+Drift is a focused task tracker for solo founders and small async teams. The product premise is that *work is a moving thing* — momentum matters more than perfectly groomed backlogs, and the right tool surfaces what you're working on *now* without making you administer a system to find it. The brand expression follows: a serif display moment in an otherwise sober sans-serif surface, a single warm accent that means *this is what's live*, and visual restraint everywhere else.
+
+Drift inherits shadcn/ui defaults wholesale. This DESIGN.md specifies only the brand-layer deltas — primary color, accent color, display typography, slightly tighter corners, and a handful of brand-specific components. The 80% of components that ship from shadcn (Button, Card, Dialog, Sheet, Command, Popover, Toast) inherit shadcn's visual specs as-is. Customizing those is *explicitly* against the brand discipline — shadcn's defaults are the contract.
+
+## Colors
+
+The Drift palette is two colors of brand-layer plus shadcn defaults for everything else.
+
+- **Primary Navy (`#0F4C81` light / `#5C8AC2` dark)** is the brand color. Used on primary buttons, active nav items, link underlines, and the "current week" indicator. Replaces shadcn's default `primary`.
+- **Focus Amber (`#F59E0B` light / `#FBC470` dark)** is the accent. Used exclusively to indicate the task or project currently in focus — the one you're working on *right now*. Never used for chrome, never used decoratively, never used for state badges. Amber means "live."
+- **All other tokens** (`background`, `foreground`, `muted`, `muted-foreground`, `border`, `input`, `ring`, `card`, `popover`, `destructive`) inherit from shadcn defaults. If the brand can't justify overriding a token, it doesn't override it.
+
+Avoid: chromatic flourishes, gradient surfaces, custom destructive colors (use shadcn's), more than two brand colors. The discipline is two-colors-and-stop.
+
+## Typography
+
+Body / label / caption inherit shadcn's Geist Sans ramp. Only the `display` role is brand-overridden, set in **Instrument Serif** at 36px (24px small variant). The serif moment appears in:
+
+- Empty-state hero text on Today and project surfaces
+- Project titles in the project detail header
+- The "Welcome back, {name}" greeting at first session of the day
+
+Everything else stays in Geist Sans. The serif is a punctuation mark, not a default voice.
+
+## Layout & Spacing
+
+shadcn / Tailwind spacing scale inherited as-is (the 4-based scale: 4, 8, 12, 16, 20, 24, 32, 40, 48, 64). Maximum content width: `max-w-3xl` (768px) — Drift is not a wide-table product, and forcing one-column reading keeps the surface focused.
+
+Single-column layout. Sidebar nav on `lg` (1024px+); on smaller viewports, the sidebar becomes a sheet triggered from the top bar.
+
+## Elevation & Depth
+
+Inherited from shadcn — subtle shadow on hover/active states, no elevation as a visual hierarchy device. Drift adds nothing on top of this; brand discipline is "shadcn's shadows are correct."
+
+## Shapes
+
+Tighter than shadcn defaults: `rounded/sm` (4px) for inputs, `rounded/md` (6px) for cards and buttons, `rounded/lg` (8px) for dialogs and the command palette. The crispness reads "tool" rather than "consumer app." Pill shapes (`rounded/full`) appear only on status badges.
+
+## Components
+
+Drift uses the following shadcn components as-is, unchanged: `Button`, `Card`, `Dialog`, `Sheet`, `Popover`, `DropdownMenu`, `Toast`, `Tabs`, `Avatar`, `Separator`. The contract: don't customize these.
+
+Brand-layer-overridden components:
+
+- **Button (primary variant)** — `{colors.primary}` fill, `{colors.primary-foreground}` text, `{rounded.md}` corner. Other variants (secondary, outline, ghost, destructive) inherit shadcn defaults.
+- **Focus card** — Custom Drift component. The "this is what you're working on now" card on Today and project detail. `{colors.accent}` fill, no border, slightly elevated. Appears at most once per surface.
+- **Command palette result (active)** — Override on shadcn's `Command` component: the highlighted/keyboard-selected result row uses `{colors.accent}` instead of shadcn's default `accent` token. Reinforces "this is what will fire if you hit Enter."
+
+## Do's and Don'ts
+
+| Do | Don't |
+|---|---|
+| Inherit shadcn defaults for everything not in the brand layer | Override shadcn's color tokens beyond `primary` and `accent` |
+| Use `{colors.accent}` only for "live / now / in-focus" | Use accent for state, chrome, or hover affordances |
+| `display` typography sparingly — empty states, hero greetings | Set body text in `display` to "make it pretty" |
+| Tighter corners than shadcn (4 / 6 / 8) | Use shadcn's default 6/8/12 (Drift reads sharper) |
+| Single-column layouts inside `max-w-3xl` | Wide multi-column tables (Drift is not a spreadsheet) |
diff --git a/.claude/skills/bmad-ux/assets/excalidraw-wireframe.md b/.claude/skills/bmad-ux/assets/excalidraw-wireframe.md
new file mode 100644
index 0000000..7f04c95
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/excalidraw-wireframe.md
@@ -0,0 +1,19 @@
+# Excalidraw Wireframe Renderer
+
+Subagent prompt. Produce one `.excalidraw` file at `.working/ia-{date}.excalidraw` (IA diagram) or `.working/flow-{name}-{date}.excalidraw` (flow wireframe).
+
+## CRITICAL: two-character `index` fields only
+
+Every element's `index` field must be **exactly two characters** (`a0`, `aZ`, `b3`, ...). Three-character indices cause a silent *"Error: invalid file"* with no diagnostic output. Assign sequentially across all elements; advance the leading letter when the trailing alphanumeric exhausts (`a0..a9, aA..aZ`, then `b0..`). Verify before writing.
+
+## Shape
+
+Valid Excalidraw file: `{type: "excalidraw", version: 2, source: "https://excalidraw.com", elements: [...], appState: {gridSize: null, viewBackgroundColor: "#ffffff"}, files: {}}`. Each element needs the standard Excalidraw element fields (`id, type, x, y, width, height, angle, strokeColor, backgroundColor, fillStyle, strokeWidth, strokeStyle, roughness, opacity, groupIds, frameId, roundness, seed, version, versionNonce, isDeleted, boundElements, updated, link, locked, index`). Text elements add `text, fontSize, fontFamily, textAlign, verticalAlign, baseline, containerId, originalText, lineHeight`.
+
+## Content
+
+**IA diagram:** boxes-and-arrows of auth stack, main app surfaces, modal routes, settings stack, cross-cutting affordances. Color sparingly to distinguish category. Layout for human legibility, not graph correctness.
+
+**Flow wireframe:** screen-by-screen rectangles left-to-right, simple shapes inside (nav bar, CTA, content blocks) at low fidelity. Arrows labeled with the user action that causes transition. Annotations alongside for climax and edge-case beats.
+
+Return to the parent: file path, kind, one-line subject, element count, confirmation that all indices are two-character. Do not dump JSON into parent context. Tell the user to open in Excalidraw desktop or excalidraw.com.
diff --git a/.claude/skills/bmad-ux/assets/experience-example-mobile.md b/.claude/skills/bmad-ux/assets/experience-example-mobile.md
new file mode 100644
index 0000000..5bd05ee
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/experience-example-mobile.md
@@ -0,0 +1,112 @@
+---
+name: Quill
+status: final
+sources:
+  - {planning_artifacts}/prds/quill-2025-08-15/prd.md
+updated: 2025-09-02
+---
+
+# Quill — Experience Spine
+
+> Illustrative example. Single-surface mobile (iOS + Android parity). Consumer posture, calm by default. Paired with `design-example-mobile.md` (Quill DESIGN.md). Demonstrates: microcopy as gating discipline, Inspiration & Anti-patterns earning its place, Responsive & Platform omitted (single-surface).
+
+## Foundation
+
+Single-surface mobile, iOS + Android with parity. No UI system named — inherits platform conventions for navigation, system gestures, dynamic type. `DESIGN.md` is the visual identity reference; this spine is the experience. Dark mode is the default surface; light is a setting.
+
+## Information Architecture
+
+| Surface | Reached from | Purpose |
+|---|---|---|
+| Today | App open (cold) | Today's prompt + entry composer |
+| Library | Tab bar | Past entries, searchable |
+| Entry detail | Library row tap | Read / edit one entry |
+| Settings | Today header gear | Account, export, theme |
+
+Bottom tab bar (Today / Library / Settings). No drawer. Modal stacks one level deep, never two.
+
+→ Composition reference: `mockups/today-cold.html`, `mockups/composer.html`. Spine wins on conflict.
+
+## Voice and Tone
+
+Microcopy. Brand voice and aesthetic posture live in `DESIGN.md`.
+
+| Do | Don't |
+|---|---|
+| "Today's prompt." | "Time to write!" |
+| "Saved." | "✓ Auto-saved successfully" |
+| "We couldn't reach the cloud — your work is on this device." | "Network error" |
+| Short, complete sentences. | Streak counters, encouragement, exclamation marks. |
+
+## Component Patterns
+
+Behavioral. Visual specs live in `DESIGN.md.Components`.
+
+| Component | Use | Behavioral rules |
+|---|---|---|
+| Prompt card | Today | One per day. Tap opens composer. |
+| Composer | Today + entry detail | No formatting toolbar in v1. Autosave on pause ≥ 600ms. |
+| Entry row | Library list | Tap → entry detail. Long-press reserved for system text selection. |
+| Save indicator | Composer header | Cycles `Editing…` → `Saved.` (≥ 800ms visible). |
+| Settings row | Settings list | Tap → detail or toggle. |
+
+## State Patterns
+
+| State | Surface | Treatment |
+|---|---|---|
+| Cold open | Today | Show today's prompt (cached). If no cache, `Today's prompt is loading.` with skeleton. |
+| Empty library | Library | `No entries yet — Today's prompt is your first.` Link to Today. |
+| Search empty | Library search | `No matches.` No suggestions. |
+| Offline write | Composer | Save locally. No banner. Sync on next foreground. |
+| Sync error | Settings → Account | Surfaced here only. Never block writing. |
+| Focus | Composer | Native cursor + keyboard. No custom focus chrome. |
+
+## Interaction Primitives
+
+- Tap to act. Long-press reserved for system text selection.
+- Swipe-to-delete on entry rows (native pattern, confirm sheet).
+- Pull-to-refresh on Library only.
+- **Banned:** carousels, hero animations on open, badge counts, streaks, push-notification re-engagement.
+
+## Accessibility Floor
+
+Behavioral. Visual contrast lives in `DESIGN.md`.
+
+- VoiceOver / TalkBack: every interactive element labeled with role + state. Save indicator announces `Saved` on transition.
+- Dynamic type honored through `DESIGN.md` typography tokens. UI must remain legible at largest setting — no truncated controls.
+- Reduce Motion: skip the save-indicator fade; show `Saved.` immediately.
+- Tap targets ≥ 44pt (iOS) / 48dp (Android).
+- Focus traversal follows reading order on every surface.
+
+## Inspiration & Anti-patterns
+
+- **Lifted from Day One:** the single daily entry framing — one prompt, one composer, no inbox.
+- **Lifted from iA Writer:** the no-toolbar composer; formatting is a settings-level decision, not a per-entry one.
+- **Rejected — Streaks (Duolingo, most habit apps):** streaks weaponize the user's calendar. Quill's value is showing up *today*, not punishing missed days.
+- **Rejected — AI prompt suggestions inside the composer:** the composer is for writing, not negotiating with a model. AI lives only in the daily prompt generation.
+
+## Key Flows
+
+### Flow 1 — Daily write (Mira, late evening, after work)
+
+1. Mira opens app.
+2. Today surface shows today's prompt (cached if offline).
+3. She taps the composer entry point.
+4. Composer opens, keyboard active.
+5. She writes; autosave fires on pause.
+6. She taps Back.
+7. **Climax:** Today surface shows `Saved.` and the entry's first line below the prompt — proof the day is captured.
+
+Failure: cold prompt fetch fails → composer still opens with cached generic prompt; banner on Today only after Mira returns.
+
+### Flow 2 — Recall past entry (Mira, three weeks later, looking for what she wrote about her mother)
+
+1. Mira taps Library.
+2. Scrolls or searches.
+3. Taps entry row.
+4. Entry detail opens in read mode.
+5. She taps anywhere to enter edit mode (cursor at tap point).
+6. Edits autosave.
+7. **Climax:** `Saved.` visible in entry header — the older self and the present self are in continuous conversation.
+
+Empty state: no entries → message routes back to Today.
diff --git a/.claude/skills/bmad-ux/assets/experience-example-shadcn.md b/.claude/skills/bmad-ux/assets/experience-example-shadcn.md
new file mode 100644
index 0000000..d46083c
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/experience-example-shadcn.md
@@ -0,0 +1,133 @@
+---
+name: Drift
+status: final
+sources:
+  - {planning_artifacts}/prds/drift-2026-03-12/prd.md
+updated: 2026-04-02
+---
+
+# Drift — Experience Spine
+
+> Illustrative example. Single-surface responsive web. shadcn/ui on Next.js + Tailwind. Paired with `design-example-shadcn.md` (Drift DESIGN.md). Demonstrates: component-library inheritance, keyboard-first interaction primitives, the "shadcn + brand-layer" pattern that covers most modern web SaaS.
+
+## Foundation
+
+Single-surface responsive web. shadcn/ui on Next.js 15+ with Tailwind CSS. The component library does most of the work; brand discipline is "respect the defaults except where the brand layer overrides them." `DESIGN.md` is the visual identity reference and names the override surface; this spine is the experience. Single-tenant per project; users can belong to multiple projects but each project is a self-contained workspace.
+
+## Information Architecture
+
+| Surface | Reached from | Purpose |
+|---|---|---|
+| Today | App open / `g t` | Current focus, in-progress tasks pulled from all projects |
+| Projects | Sidebar / `g p` | List of active and archived projects |
+| Project detail | Projects row / `g 1`–`g 9` | Tasks in this project, organized by lane |
+| Search | `⌘K` / `Ctrl+K` | Command palette — surface, navigate, act |
+| Settings | Avatar menu | Account, theme, keyboard shortcuts, billing |
+
+Sidebar collapses to icons on `md`; becomes a `Sheet` on `sm`. Modal stacks one level deep (e.g., open `Dialog` on top of a surface, never on top of another dialog).
+
+→ Composition reference: `mockups/today.html`, `mockups/project-detail.html`, `mockups/command-palette.html`. Spine wins on conflict.
+
+## Voice and Tone
+
+Microcopy. Brand voice and aesthetic posture live in `DESIGN.md`.
+
+| Do | Don't |
+|---|---|
+| "What are you working on?" | "Let's get productive! 🚀" |
+| "3 tasks in motion" | "You have 3 active items." |
+| "Closed. Nice work." | "Task completed successfully ✓" |
+| "Nothing in motion. Pick something." | "No active tasks. Click below to get started!" |
+| Manager-facing: counts and verbs. Employee-facing: same. | Different tone per audience — Drift talks to everyone the same way. |
+
+## Component Patterns
+
+Behavioral. Visual specs live in `DESIGN.md.Components` (or in shadcn defaults, when inherited).
+
+| Component | Use | Behavioral rules |
+|---|---|---|
+| Task row | Projects, Today | Click anywhere on row opens edit dialog. Checkbox toggles done state with optimistic update. Hover reveals quick-actions (`focus`, `defer`, `archive`). |
+| Focus card | Today, Project detail | At most one focus card per surface — the task or project marked with `focus` state. `f` keyboard shortcut sets focus on the active row. |
+| Command palette | Global (⌘K) | Fuzzy search across all projects, tasks, and commands. `Enter` fires the highlighted result. `→` previews a result. Escape closes. |
+| Project header | Project detail | Inline-editable title (click to edit, blur to save). Status pill: active / archived / done. |
+| Empty state | Anywhere | shadcn's empty pattern + one Drift-specific sentence. `display-sm` for the headline, body text below, single primary action. |
+
+## State Patterns
+
+| State | Surface | Treatment |
+|---|---|---|
+| Cold app load | Today | shadcn `Skeleton` rows (4-6) match expected layout. Resolves on data. |
+| No focus | Today | `display-sm`: "Nothing in motion. Pick something." Below: list of in-progress tasks from all projects. |
+| Empty project | Project detail | `display-sm`: "{Project title} is empty." Body: "Add a first task to get going." Single primary button. |
+| Command palette no matches | ⌘K | "No matches. Start typing a task or project name, or pick an action below." Followed by 4-5 common commands. |
+| Offline | Global (status bar) | shadcn `Toast` once: "You're offline. Changes will sync when you reconnect." Local writes continue. |
+| Permission denied | Projects (others' private) | Surface hidden from sidebar. No "blocked" screen. |
+| Stale data | Project detail | If background refresh detects changes, shadcn `Toast`: "Updated by {user_name}. Refresh." Manual refresh, no auto. |
+
+## Interaction Primitives
+
+**Keyboard-first.** Drift's primary audience is developers and power users; the keyboard surface is the product, the mouse is fallback.
+
+- `⌘K` / `Ctrl+K` — Command palette (universal)
+- `g t` / `g p` — Go to Today / Projects (vim-style)
+- `g 1`–`g 9` — Go to project by sidebar position
+- `f` — Set focus on highlighted task/project
+- `c` — Create new task (context-aware: in the active project)
+- `Esc` — Close dialogs, exit edit mode, clear command palette
+- `/` — Focus search in current surface
+
+**Mouse:** click to act, drag deferred to v2. Hover reveals row actions on `md+` (touch users tap to reveal).
+
+**Banned everywhere:** infinite scroll (pagination only), drag-to-reorder in v1, hover-only affordances on `sm` viewports, modal stacks > 1 level deep.
+
+## Accessibility Floor
+
+Behavioral. Visual contrast lives in `DESIGN.md` (inherits shadcn's WCAG AA-compliant defaults; brand overrides verified to maintain ratios).
+
+- WCAG 2.2 AA across the responsive web surface.
+- Screen reader announces page surface on navigation: "Today, focus surface" / "Project: {name}, task list, {N} tasks."
+- Keyboard shortcuts available without modifier on most surfaces (vim-style `g t` etc.) — users with motor-control limitations get the same surface as power users.
+- `Tab` order matches reading order on every surface. `Esc` always closes the topmost modal/popover.
+- Command palette is fully keyboard-operable; results announce as they update via `aria-live`.
+- Focus rings inherit shadcn's `ring` token — visible at AA contrast against `background`.
+
+## Responsive & Platform
+
+| Breakpoint | Behavior |
+|---|---|
+| `≥ lg` (1024px+) | Sidebar visible. Today is a 2-column layout: focus + in-motion list. |
+| `md` (768–1023px) | Sidebar collapses to icons. Today stacks to single column. |
+| `< md` (`sm`) | Sidebar becomes a `Sheet` triggered from top bar. Command palette opens fullscreen. |
+
+Drift is responsive web, not a native mobile app. The product works on phones for read + simple-edit, but the primary surface is desktop / laptop.
+
+## Inspiration & Anti-patterns
+
+- **Lifted from Linear:** the keyboard-first discipline. `⌘K` is the command center; vim-style nav (`g t`); no drag for primary navigation; status pill vocabulary.
+- **Lifted from Notion:** inline-editable titles. Click-to-edit on project header, blur to save. No edit/view mode toggle.
+- **Lifted from shadcn:** the entire surface vocabulary. Drift's brand is *what we add to shadcn*, not a from-scratch design system. This is a deliberate posture, not a shortcut.
+- **Rejected — Streaks, badges, achievement notifications:** Drift is a tool, not a habit app. Task closure is its own reward; no celebratory animation, no "🎉 5-day streak!" toast.
+- **Rejected — AI-suggested next tasks:** Drift surfaces what's in motion, doesn't tell the user what to work on. The user picks focus; the tool surfaces consequences.
+- **Rejected — Multi-column kanban as default project view:** lists are linear; kanban hides progress behind columns. Optional v2; not the default.
+
+## Key Flows
+
+### Flow 1 — Morning focus (Sarah, solo founder, 8:45am Tuesday)
+
+1. Sarah opens Drift in a browser tab.
+2. App loads Today. `display-sm`: "Welcome back, Sarah." Focus card shows yesterday's marked task — "Finish landing page hero copy" — still in motion.
+3. She hits `⌘K`, types "ship hero", sees the matching task and presses Enter to open it.
+4. Inline edit: she updates the task description with two new bullets. Tab + Tab triggers save.
+5. **Climax:** Sarah closes the dialog. Today re-renders: focus card still shows the hero task, but now with the updated body text visible at a glance. She doesn't have to navigate anywhere — the surface that greeted her now reflects the work she just did. She picks up her coffee and starts writing.
+
+Failure: data save fails → shadcn `Toast` (destructive variant): "Couldn't save. Trying again." Inline edit retained; another `Enter` retries.
+
+### Flow 2 — Async handoff (Devon and Mara, small remote team, mid-afternoon)
+
+1. Devon finishes wiring up the auth flow and marks the task `done`.
+2. Mara, time-zoned three hours ahead and online during overlap, opens Drift.
+3. Today loads; her focus is on her own front-end work, but the in-motion list shows Devon's auth task now marked done and one task below it newly assigned to her — "Wire up post-auth redirect" — that Devon set during checkout.
+4. She hits `f` on the row to mark it as her focus, then `Enter` to open it.
+5. **Climax:** The focus card swaps. Her surface now shows the post-auth redirect task as the live thing she's working on; the projects sidebar shows the Auth project highlighted; the command palette `⌘K` defaults its first result to "Go to Auth project." The state of the team's progress is *embedded in her surface* — no Slack thread to scroll, no status doc to read.
+
+Failure: Devon hadn't actually assigned the follow-up — Mara mis-assigned to herself. She hits `Esc`, `f` again to unfocus, and reassigns to Devon. No "are you sure" dialog; Drift trusts the user.
diff --git a/.claude/skills/bmad-ux/assets/headless-schemas.md b/.claude/skills/bmad-ux/assets/headless-schemas.md
new file mode 100644
index 0000000..1211393
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/headless-schemas.md
@@ -0,0 +1,84 @@
+# Headless Mode JSON Schemas
+
+Every headless run ends with one of these payloads. Omit keys for artifacts not produced.
+
+## Common fields
+
+- `status` — `"complete"`, `"blocked"`, or `"partial"`
+- `intent` — `"create"`, `"update"`, or `"validate"` (matches the detected intent)
+- `reason` — required when `status` is `"blocked"`; one-sentence explanation
+- `assumptions` — array of inferred values that were not directly confirmed by inputs
+- `open_questions` — array of items that need a human decision before the artifact can be considered final
+
+## Create
+
+```json
+{
+  "status": "complete",
+  "intent": "create",
+  "design": "{doc_workspace}/DESIGN.md",
+  "experience": "{doc_workspace}/EXPERIENCE.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "working_artifacts": ["{doc_workspace}/.working/color-themes-1.html"],
+  "promoted_artifacts": {
+    "mockups": ["{doc_workspace}/mockups/direction-calm-sage.html"],
+    "wireframes": ["{doc_workspace}/wireframes/ia-2026-05-19.excalidraw"]
+  },
+  "open_questions": [],
+  "assumptions": [],
+  "external_handoffs": [
+    {"directive": "Confluence upload", "tool": "corp:confluence_upload", "url": "https://confluence.corp/DESIGN/123", "status": "ok"}
+  ]
+}
+```
+
+The `working_artifacts` and `promoted_artifacts` keys are optional and omitted entirely when empty. Headless Create runs default to not enabling creative tools — both keys are typically absent in headless output unless the caller enabled them.
+
+## Update
+
+```json
+{
+  "status": "complete",
+  "intent": "update",
+  "design": "{doc_workspace}/DESIGN.md",
+  "experience": "{doc_workspace}/EXPERIENCE.md",
+  "memlog": "{doc_workspace}/.memlog.md",
+  "changes_summary": "1-3 sentences describing what changed and why",
+  "conflicts_with_prior_decisions": [],
+  "open_questions": [],
+  "external_handoffs": [
+    {"directive": "Confluence upload", "tool": "corp:confluence_upload", "url": "https://confluence.corp/DESIGN/123", "status": "ok"}
+  ]
+}
+```
+
+## Validate
+
+```json
+{
+  "status": "complete",
+  "intent": "validate",
+  "validation_report": "{doc_workspace}/validation-report.md",
+  "findings_summary": {
+    "critical": 0,
+    "high": 0,
+    "medium": 0,
+    "low": 0
+  },
+  "offer_to_update": true
+}
+```
+
+`validation_report` is always written for Validate intent — the path here is required, not optional.
+
+## Blocked
+
+```json
+{
+  "status": "blocked",
+  "intent": "update",
+  "reason": "Change signal ambiguous — could be a brand refresh or an accessibility audit response; no inferred direction"
+}
+```
+
+Always include the intent (best-guess if not certain) and a one-sentence `reason`.
diff --git a/.claude/skills/bmad-ux/assets/key-screens.md b/.claude/skills/bmad-ux/assets/key-screens.md
new file mode 100644
index 0000000..62f057c
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/key-screens.md
@@ -0,0 +1,29 @@
+# Key Screens Renderer
+
+Subagent prompt. Fired at Finalize (or during late Discovery once layout decisions firm up). Produces 1:1 HTML mocks of the load-bearing surfaces so the spine can link to them as visual reference. Spine remains the contract; mocks illustrate.
+
+## Inputs
+
+`.memlog.md`, the current drafts `DESIGN.md` and `EXPERIENCE.md`, `.working/` (especially the chosen color-theme and direction mocks), source PRD. The user names which surfaces to render — typically 2-4: the canonical entry surface, the most complex flow's hero screen, any load-bearing overlay/modal, and (when present) the Week / list / dashboard view.
+
+## What to render
+
+One HTML file per screen, at `.working/key-{slug}.html`. Each file: realistic device frame (phone or browser), real product content from the conversation (no lorem), every visible string voice-checked against `.memlog.md`, all decided tokens applied. Show one canonical state per screen; if a surface has a load-bearing alternate state (focus, error, crisis-card-present), render it as a second column or section in the same file.
+
+Inline CSS, system fonts, no JS, no network. The mock must render fully offline. Comment block at the top of the `<style>` notes which spine sections govern this screen so a future reader knows what to check.
+
+## What to return
+
+A compact summary to the parent:
+- file path per screen
+- one-line caption per screen ("Today picker at rest; accent on Thought record")
+- which spine sections each mock illustrates (Component Patterns rows, State Patterns rows, Flow steps)
+
+The parent, at Finalize "Promote working artifacts," uses this summary to insert inline `mockups/...` links into the relevant spine sections.
+
+## Anti-patterns
+
+- Do not invent layout — every composition decision must trace to a `.working/` artifact or a confirmation in `.memlog.md`. If a layout question is open, the mock is premature.
+- Do not show every screen of every flow — 2-4 load-bearing surfaces, not 14.
+- Do not stage marketing copy. Strings come from `.memlog.md` and voice rules.
+- Do not introduce a new pattern not in the spine's Component Patterns table. If you need one, log it and ask before rendering.
diff --git a/.claude/skills/bmad-ux/assets/validation-report-template.html b/.claude/skills/bmad-ux/assets/validation-report-template.html
new file mode 100644
index 0000000..a5d39be
--- /dev/null
+++ b/.claude/skills/bmad-ux/assets/validation-report-template.html
@@ -0,0 +1,319 @@
+<!DOCTYPE html>
+<!--
+  UX Design Validation Report — skeleton template.
+
+  This file is a starter the synthesis pass fills in directly. There is no
+  substitution engine. The LLM:
+    1. Reads {doc_workspace}/review-rubric.md and every review-{slug}.md from
+       additional reviewers.
+    2. Copies this skeleton.
+    3. Replaces the placeholder content (everything between TEMPLATE markers)
+       with the consolidated review, preserving the structure and CSS.
+    4. Writes the result to {doc_workspace}/validation-report.html.
+    5. Writes a markdown twin to {doc_workspace}/validation-report.md.
+
+  Visual rules the LLM must preserve:
+    - The container width, the color tokens, the typography.
+    - One dimension = one collapsible <section class="dimension">.
+    - Verdict pill uses the verdict-* class matching its judgment.
+    - Severity badge uses the badge-sev-* class matching its level.
+    - Each extra reviewer (accessibility, adversarial, etc.) gets its own
+      collapsible section below the rubric dimensions.
+    - The footer always shows the artifact paths and timestamp.
+-->
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>UX Design Validation: TEMPLATE_UX_SPEC_NAME</title>
+<style>
+  :root {
+    --bg: #fafaf9;
+    --surface: #ffffff;
+    --border: #e7e5e4;
+    --text: #1c1917;
+    --muted: #78716c;
+
+    --verdict-strong: #16a34a;
+    --verdict-adequate: #65a30d;
+    --verdict-thin: #d97706;
+    --verdict-broken: #dc2626;
+
+    --sev-low: #64748b;
+    --sev-medium: #ca8a04;
+    --sev-high: #ea580c;
+    --sev-critical: #dc2626;
+  }
+  * { box-sizing: border-box; }
+  html, body { margin: 0; padding: 0; }
+  body {
+    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Inter, system-ui, sans-serif;
+    background: var(--bg);
+    color: var(--text);
+    line-height: 1.6;
+    font-size: 15px;
+  }
+  .container { max-width: 960px; margin: 0 auto; padding: 32px 24px 64px; }
+
+  header.report-header {
+    display: flex;
+    align-items: flex-start;
+    justify-content: space-between;
+    gap: 24px;
+    padding-bottom: 16px;
+    border-bottom: 1px solid var(--border);
+    margin-bottom: 24px;
+  }
+  .title h1 { margin: 0; font-size: 22px; font-weight: 600; letter-spacing: -0.01em; }
+  .title .subtitle { color: var(--muted); font-size: 13px; margin-top: 4px; font-family: ui-monospace, "SF Mono", Menlo, monospace; }
+
+  .synthesis {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-left: 3px solid var(--muted);
+    border-radius: 8px;
+    padding: 18px 22px;
+    margin-bottom: 24px;
+    font-size: 15.5px;
+  }
+  .synthesis p { margin: 0 0 10px; }
+  .synthesis p:last-child { margin-bottom: 0; }
+
+  .dimension-summary {
+    display: grid;
+    grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
+    gap: 10px;
+    margin-bottom: 24px;
+  }
+  .dim-card {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-radius: 8px;
+    padding: 12px 14px;
+  }
+  .dim-card .dim-name { font-size: 13px; color: var(--muted); margin-bottom: 6px; }
+  .dim-card .dim-verdict { font-size: 14px; font-weight: 600; }
+
+  section.dimension, section.reviewer-section { margin-bottom: 14px; }
+  section.dimension details, section.reviewer-section details {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-radius: 8px;
+    overflow: hidden;
+  }
+  section summary {
+    padding: 14px 20px;
+    cursor: pointer;
+    user-select: none;
+    list-style: none;
+    display: flex;
+    align-items: center;
+    gap: 12px;
+  }
+  section summary::-webkit-details-marker { display: none; }
+  section summary::before {
+    content: "▸";
+    display: inline-block;
+    color: var(--muted);
+    transition: transform 0.15s ease;
+  }
+  section details[open] summary::before { transform: rotate(90deg); }
+  section summary h2 {
+    display: inline;
+    margin: 0;
+    font-size: 16px;
+    font-weight: 600;
+    letter-spacing: -0.005em;
+    flex: 1;
+  }
+  .verdict-pill {
+    font-size: 11px;
+    padding: 3px 10px;
+    border-radius: 999px;
+    font-weight: 600;
+    text-transform: uppercase;
+    letter-spacing: 0.04em;
+    color: white;
+  }
+  .verdict-strong { background: var(--verdict-strong); }
+  .verdict-adequate { background: var(--verdict-adequate); }
+  .verdict-thin { background: var(--verdict-thin); }
+  .verdict-broken { background: var(--verdict-broken); }
+
+  .dim-body { padding: 4px 20px 18px; }
+  .dim-judgment { color: var(--text); font-size: 14.5px; }
+  .dim-judgment p { margin: 0 0 10px; }
+
+  .findings-list { padding: 0 20px 4px; }
+  article.finding {
+    padding: 14px 0;
+    border-top: 1px solid var(--border);
+  }
+  article.finding:first-child { border-top: none; }
+  article.finding header {
+    display: flex;
+    align-items: center;
+    gap: 10px;
+    flex-wrap: wrap;
+    margin-bottom: 6px;
+  }
+  .badge {
+    font-size: 10.5px;
+    padding: 3px 8px;
+    border-radius: 4px;
+    font-weight: 600;
+    text-transform: uppercase;
+    letter-spacing: 0.04em;
+    line-height: 1.4;
+  }
+  .badge-sev-low { background: rgba(100, 116, 139, 0.12); color: var(--sev-low); }
+  .badge-sev-medium { background: rgba(202, 138, 4, 0.14); color: var(--sev-medium); }
+  .badge-sev-high { background: rgba(234, 88, 12, 0.14); color: var(--sev-high); }
+  .badge-sev-critical { background: rgba(220, 38, 38, 0.14); color: var(--sev-critical); }
+  .finding-title { margin: 0; font-size: 15px; font-weight: 500; flex: 1; min-width: 200px; }
+  .finding-location { font-family: ui-monospace, "SF Mono", Menlo, monospace; font-size: 12.5px; color: var(--muted); }
+  .finding-note, .finding-fix { margin-top: 6px; font-size: 14px; }
+  .finding-fix strong { color: var(--muted); font-weight: 500; }
+
+  .reviewer-source {
+    font-size: 12px;
+    color: var(--muted);
+    font-family: ui-monospace, "SF Mono", Menlo, monospace;
+  }
+
+  .mechanical {
+    background: var(--surface);
+    border: 1px solid var(--border);
+    border-radius: 8px;
+    padding: 16px 20px;
+    margin-top: 24px;
+    font-size: 14px;
+  }
+  .mechanical h3 { margin: 0 0 10px; font-size: 14px; font-weight: 600; color: var(--muted); text-transform: uppercase; letter-spacing: 0.04em; }
+  .mechanical ul { margin: 0; padding-left: 20px; }
+  .mechanical li { margin-bottom: 4px; color: var(--text); }
+
+  footer.report-footer {
+    margin-top: 40px;
+    padding-top: 16px;
+    border-top: 1px solid var(--border);
+    font-size: 12px;
+    color: var(--muted);
+    font-family: ui-monospace, "SF Mono", Menlo, monospace;
+  }
+  footer .meta { display: flex; gap: 24px; flex-wrap: wrap; }
+</style>
+</head>
+<body>
+  <div class="container">
+
+    <!-- TEMPLATE: header. Fill ux spec name and ux spec path. No overall grade —
+         per-category verdicts and severity counts below carry the picture. -->
+    <header class="report-header">
+      <div class="title">
+        <h1>TEMPLATE_UX_SPEC_NAME — UX Design Validation Report</h1>
+        <div class="subtitle">TEMPLATE_UX_SPEC_PATH</div>
+      </div>
+    </header>
+
+    <!-- TEMPLATE: overall synthesis paragraphs. Lift directly from
+         review-rubric.md "Overall verdict" section; expand if extra reviewers
+         (accessibility, adversarial, etc.) materially shift the picture.
+         Wrap each paragraph in <p>. -->
+    <div class="synthesis">
+      <p>TEMPLATE_SYNTHESIS_PARAGRAPH</p>
+    </div>
+
+    <!-- TEMPLATE: dimension summary cards. One per rubric category, in this
+         canonical order (from references/validate.md):
+           1. Flow coverage
+           2. Token completeness
+           3. Component coverage
+           4. State coverage
+           5. Visual reference coverage
+           6. Bloat & overspecification
+           7. Inheritance discipline
+           8. Shape fit
+         The dim-verdict text uses one of: strong | adequate | thin | broken. -->
+    <div class="dimension-summary">
+      <div class="dim-card">
+        <div class="dim-name">TEMPLATE_CATEGORY_NAME</div>
+        <div class="dim-verdict" style="color: var(--verdict-TEMPLATE_VERDICT)">TEMPLATE_VERDICT_TEXT</div>
+      </div>
+      <!-- repeat for each of the eight rubric categories -->
+    </div>
+
+    <!-- TEMPLATE: one section per rubric category, same canonical order as the
+         summary cards above. Skip a category entirely if the rubric review
+         marked it n/a for this UX spec. Open the section by default if verdict
+         is thin or broken. -->
+    <section class="dimension">
+      <details open>
+        <summary>
+          <h2>TEMPLATE_CATEGORY_NAME</h2>
+          <span class="verdict-pill verdict-TEMPLATE_VERDICT">TEMPLATE_VERDICT_TEXT</span>
+        </summary>
+        <div class="dim-body">
+          <div class="dim-judgment">
+            <p>TEMPLATE_DIMENSION_JUDGMENT</p>
+          </div>
+        </div>
+        <div class="findings-list">
+          <!-- TEMPLATE: zero or more findings -->
+          <article class="finding">
+            <header>
+              <span class="badge badge-sev-TEMPLATE_SEVERITY">TEMPLATE_SEVERITY</span>
+              <h3 class="finding-title">TEMPLATE_FINDING_TITLE</h3>
+              <span class="finding-location">TEMPLATE_LOCATION</span>
+            </header>
+            <div class="finding-note">TEMPLATE_FINDING_NOTE</div>
+            <div class="finding-fix"><strong>Fix:</strong> TEMPLATE_SUGGESTED_FIX</div>
+          </article>
+        </div>
+      </details>
+    </section>
+
+    <!-- TEMPLATE: one section per extra reviewer that ran (accessibility,
+         adversarial, brand-conformance, etc.). Skip this block entirely if
+         only the rubric walker ran. -->
+    <section class="reviewer-section">
+      <details>
+        <summary>
+          <h2>Accessibility review</h2>
+          <span class="reviewer-source">TEMPLATE_REVIEWER_SOURCE_FILE</span>
+        </summary>
+        <div class="dim-body">
+          <div class="dim-judgment">
+            <p>TEMPLATE_REVIEWER_PREAMBLE</p>
+          </div>
+        </div>
+        <div class="findings-list">
+          <article class="finding">
+            <header>
+              <span class="badge badge-sev-TEMPLATE_SEVERITY">TEMPLATE_SEVERITY</span>
+              <h3 class="finding-title">TEMPLATE_FINDING_TITLE</h3>
+              <span class="finding-location">TEMPLATE_LOCATION</span>
+            </header>
+            <div class="finding-note">TEMPLATE_FINDING_NOTE</div>
+            <div class="finding-fix"><strong>Fix:</strong> TEMPLATE_SUGGESTED_FIX</div>
+          </article>
+        </div>
+      </details>
+    </section>
+
+    <!-- TEMPLATE: mechanical notes — short, bulleted. Skip if there are none. -->
+    <div class="mechanical">
+      <h3>Mechanical notes</h3>
+      <ul>
+        <li>TEMPLATE_MECHANICAL_NOTE</li>
+      </ul>
+    </div>
+
+    <footer class="report-footer">
+      <div class="meta">
+        <span>Rubric: TEMPLATE_RUBRIC_PATH</span>
+        <span>Generated: TEMPLATE_TIMESTAMP</span>
+      </div>
+    </footer>
+  </div>
+</body>
+</html>
diff --git a/.claude/skills/bmad-ux/customize.toml b/.claude/skills/bmad-ux/customize.toml
new file mode 100644
index 0000000..aad0829
--- /dev/null
+++ b/.claude/skills/bmad-ux/customize.toml
@@ -0,0 +1,102 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-ux.
+# Overrides:
+#   {project-root}/_bmad/custom/bmad-ux.toml         (team)
+#   {project-root}/_bmad/custom/bmad-ux.user.toml    (personal)
+# Merge rules: scalars override, arrays append.
+
+[workflow]
+
+# Steps to run before/after standard activation. Append-only.
+activation_steps_prepend = []
+activation_steps_append = []
+
+# Persistent facts loaded at activation and kept in mind for the run.
+# Entries: literal sentence, `skill:NAME`, or `file:PATH` (glob ok).
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Runs at workflow completion. String or array of instructions.
+on_complete = ""
+
+# Reference DESIGN.md spines the distillation subagent reads to anchor shape
+# and editorial richness. Convention-compliant with the Google Labs DESIGN.md
+# spec (https://github.com/google-labs-code/design.md). Append entries via
+# override TOML to seed an org-specific canonical aesthetic.
+# Each entry: `file:PATH` (or bare relative path, resolved skill-relative).
+design_md_examples = [
+  "assets/design-example-mobile.md",
+  "assets/design-example-shadcn.md",
+  "assets/design-example-editorial.md",
+]
+
+# Reference EXPERIENCE.md spines for the behavioral/flow/IA layer. Each entry:
+# `file:PATH` (or bare relative path, resolved skill-relative).
+experience_md_examples = [
+  "assets/experience-example-mobile.md",
+  "assets/experience-example-shadcn.md",
+]
+
+# Design handoff targets — external tools that can take over the design /
+# visual identity work. The user runs the tool externally and saves outputs
+# (whatever the tool produces — DESIGN.md, Figma files, React components,
+# HTML mocks) to {doc_workspace}.
+# Each entry: `tool:NAME: <directive>`, `skill:NAME`, or plain-text descriptor.
+# Default: Google Stitch (emits DESIGN.md + per-screen HTML). Other producers:
+# Vercel v0, Figma, Galileo, Anima, internal generators.
+design_handoffs = [
+  "Google Stitch (https://stitch.withgoogle.com) — emits DESIGN.md + per-screen HTML. Paste assembled prompt; save outputs to {doc_workspace}.",
+]
+
+# HTML skeleton filled in by the validation synthesis pass.
+validation_report_template = "assets/validation-report-template.html"
+
+# Run folder. DESIGN.md, EXPERIENCE.md, .memlog.md, .working/
+# (creative-tool artifacts), imports/ (user-supplied screens / brand decks /
+# Figma exports / sketches), optional mockups/ and wireframes/ (promoted
+# artifacts), optional validation-report.* all land inside
+# {ux_output_path}/{run_folder_pattern}/.
+ux_output_path = "{planning_artifacts}/ux-designs"
+run_folder_pattern = "ux-{project_name}-{date}"
+
+# Creative tools registry. Collaborative renderers invoked on demand during
+# Discovery and at Finalize. Entry forms: `file:PATH`, `skill:NAME`,
+# `tool:MCP_TOOL: <directive>`, or plain text. Defaults ship for HTML color
+# themes, HTML design directions, Excalidraw wireframes (Discovery), and
+# 1:1 HTML key-screen mockups (Finalize). Working artifacts land in
+# {doc_workspace}/.working/; finalize promotes those with lasting reference
+# value to mockups/ or wireframes/. See references/creative-tools.md.
+creative_tools = [
+  "file:assets/color-themes.md",
+  "file:assets/design-directions.md",
+  "file:assets/excalidraw-wireframe.md",
+  "file:assets/key-screens.md",
+]
+
+# Polish passes applied to DESIGN.md and EXPERIENCE.md at finalize.
+# Entries: `skill:NAME`, `file:PATH`, or plain text directive.
+# Suggested order: structural → content/voice → prose mechanics.
+# The default entry runs bmad-review's two editorial lenses in order:
+# structure, then prose on top of the structure findings. The `lenses=` suffix
+# names them; drop it to let bmad-review pick what fits the content.
+doc_standards = [
+  "skill:bmad-review lenses=structure,prose",
+]
+
+# Information retrieval registry. Consulted on demand when the conversation
+# surfaces a matching need. Distinct from creative_tools (artifact production).
+# Example: "When researching component patterns, consult corp:design_system_search."
+external_sources = []
+
+# Routes outputs beyond local files at Finalize. Returned URLs/IDs surfaced
+# to the user. Unavailable tools skipped and flagged.
+# Example: "Upload DESIGN.md to Confluence via corp:confluence_upload (space_key='DESIGN')."
+external_handoffs = []
+
+# Reviewers spawned at Finalize step 4 and at Validate intent, alongside
+# the rubric walker. Entries: `skill:NAME`, `file:PATH`, or plain text.
+# Common ad-hoc add (judged by the skill): accessibility-focused reviewer
+# for consumer / regulated work.
+finalize_reviewers = []
diff --git a/.claude/skills/bmad-ux/references/creative-tools.md b/.claude/skills/bmad-ux/references/creative-tools.md
new file mode 100644
index 0000000..f42a971
--- /dev/null
+++ b/.claude/skills/bmad-ux/references/creative-tools.md
@@ -0,0 +1,19 @@
+# Creative Tools
+
+`{workflow.creative_tools}` is a registry of collaborative renderers invoked on demand when seeing options helps the user decide. Entries follow the standard prefix convention: `skill:NAME`, `file:PATH`, `tool:MCP_TOOL_NAME: <directive>`, or plain-text directive.
+
+Defaults ship for HTML color themes, HTML design directions, Excalidraw wireframes (Discovery), and 1:1 HTML key-screen mocks (Finalize). Teams append more via override TOML — Figma MCP, custom skills, prompt-based mood boards.
+
+## When to invoke
+
+Decision moments where a visual beats more conversation: picking color tokens, picking a visual personality among directions, sketching IA, mocking a tricky flow. Fast-path users typically skip; coaching-path users typically lean in. Read the room.
+
+## Artifact handling
+
+Every renderer writes to `{doc_workspace}/.working/` with a descriptive filename. `.working/` is the audit trail and survives the run. At Finalize, the facilitator walks `.working/` with the user and promotes artifacts with lasting reference value to `{doc_workspace}/mockups/` (HTML anchoring a brand or layout decision) or `{doc_workspace}/wireframes/` (Excalidraw a dev would glance at). Bar for promotion: *would a future reader of `DESIGN.md` or `EXPERIENCE.md` open this?* Default is leave-in-`.working/`.
+
+## Renderer contract
+
+The parent passes the subagent: current `.memlog.md`, relevant prior `.working/` captures, the user's stated intent for this pass, the output path. The subagent writes its artifact under `.working/` and returns ONLY a compact summary (file path, one line per variant, mode coverage). Parent never holds the full payload.
+
+For HTML, open in the browser when interactive with the platform opener — `open "PATH"` on macOS, `xdg-open` on Linux, `start ""` on Windows, path always double-quoted. On failure, give the user the path instead. Skip in headless.
diff --git a/.claude/skills/bmad-ux/references/design-md-spec.md b/.claude/skills/bmad-ux/references/design-md-spec.md
new file mode 100644
index 0000000..f685b2b
--- /dev/null
+++ b/.claude/skills/bmad-ux/references/design-md-spec.md
@@ -0,0 +1,50 @@
+# DESIGN.md Spec — Working Reference
+
+Source of truth: [google-labs-code/design.md](https://github.com/google-labs-code/design.md) (Apache 2.0, Google Labs, April 2026). This file is a working summary; the URL wins on conflict.
+
+## Structure
+
+YAML frontmatter (machine-readable tokens) + markdown body (human-readable rationale, prose sections).
+
+## Frontmatter tokens
+
+| Key | Type | Notes |
+|---|---|---|
+| `name` | string | Required. Brand or system name. |
+| `description` | string | One-line statement of what this system is. |
+| `colors` | flat object | Kebab-case keys. Values are hex strings (`'#FBF9F4'`). |
+| `typography` | nested object | Each value: an object with any subset of `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`. |
+| `rounded` | object | Scale names (`sm`, `md`, `lg`, `xl`, `full`, `DEFAULT`) → CSS dimensions. `full` is conventionally `9999px`. |
+| `spacing` | object | Scale levels (`'1'`, `'2'`, ...) or named tokens (`gutter`, `margin-mobile`, `editorial-gap`) → dimensions. |
+| `components` | object | Component-name → object of component tokens mapped to values or `{path.to.token}` references. |
+
+## Body sections (omittable, order-locked when present)
+
+1. **Brand & Style** — Aesthetic posture in prose. The editorial voice — what *kind* of thing this is.
+2. **Colors** — Per-color story. Why each exists, where it's used, what it's *not* used for.
+3. **Typography** — Type roles, ramp, and rules. Platform conventions noted semantically when inherited.
+4. **Layout & Spacing** — Spacing scale narrative, grid behavior, margins, gutters, breakpoint rules.
+5. **Elevation & Depth** — Shadow language and tonal layering rules.
+6. **Shapes** — Corner radii rules and the aesthetic logic behind them.
+7. **Components** — Per-component visual specs: anatomy, color usage, sizing, state appearance.
+8. **Do's and Don'ts** — Hard visual rules — what to do, what to avoid.
+
+Sections may be omitted when not relevant; order is locked when present.
+
+## Cross-reference syntax
+
+`{path.to.token}` used in prose and inside component objects to reference frontmatter tokens. Examples:
+
+- `{colors.primary}`
+- `{typography.body.fontSize}`
+- `{rounded.md}`
+- `{spacing.4}`
+
+The path follows the YAML structure.
+
+## Common patterns
+
+- **Light/dark mode.** Either separate kebab-case tokens (`surface-base` / `surface-base-dark`) or separate DESIGN.md files per mode. The spec allows either; pick the form that reads cleanest for the product.
+- **Platform conventions.** When inheriting from native platforms (iOS UIKit, Android Compose, Apple Human Interface Guidelines), use a `note` field instead of literal values: `{ note: 'iOS Title 1 · Android Headline Small' }`. The spec is the spec; the platform owns the rendered values.
+- **UI-system inheritance.** When inheriting from shadcn / MUI / Tailwind / internal design system, reference the system's tokens by name rather than restating values. DESIGN.md specifies only the deltas (brand color overrides, typography swaps, component customizations).
+- **Component tokens.** The `components` frontmatter entry maps each named component (e.g., `button-primary`) to its specific token values. Use `{path.to.token}` references freely; the resolver flattens at consumption time.
diff --git a/.claude/skills/bmad-ux/references/headless.md b/.claude/skills/bmad-ux/references/headless.md
new file mode 100644
index 0000000..7f1f858
--- /dev/null
+++ b/.claude/skills/bmad-ux/references/headless.md
@@ -0,0 +1,37 @@
+# Headless Mode
+
+Load this file when invoked headless. Follow it for the whole run.
+
+## Detection
+
+Headless when any of: caller sets `headless: true` (or harness equivalent); invocation is from another skill or non-interactive runner; `{workflow.activation_steps_prepend}` declares it; first message is an automation context pre-supplying inputs. Ambiguous → default interactive.
+
+## Inputs
+
+Free-form structured payload in the first message:
+
+- `intent` — `"create"`, `"update"`, or `"validate"`. If absent, infer from the artifact set.
+- **Create**: any source spec (PRD, brief, requirements list, design-thinking output, prior UX — text, path, or URL) plus brand / platform / accessibility notes; `doc_workspace` if a specific run folder is required.
+- **Update**: existing workspace containing `DESIGN.md` + `EXPERIENCE.md` (or path to either) + change signal.
+- **Validate**: existing workspace containing `DESIGN.md` + `EXPERIENCE.md` (or path to either). Workspace defaults to the spines' containing directory.
+
+Inferences → `assumptions[]`. Gaps needing a human decision → `open_questions[]`. Do not invent persona, brand, accessibility, or scope detail.
+
+Creative tools default off in headless. Caller can override; artifacts land in `.working/` and are not promoted unless the caller signals.
+
+## Behavior
+
+Do not ask. Do not greet. Complete the intent from what's provided, what exists in `{doc_workspace}`, or what you can discover. If intent stays ambiguous after inference, halt with `status: "blocked"` and a one-sentence `reason`.
+
+`status`:
+- `"complete"` — stands on its own.
+- `"partial"` — artifact produced but `open_questions[]` non-empty or critical inputs inferred.
+- `"blocked"` — no artifact produced.
+
+End with JSON matching `assets/headless-schemas.md`. `intent` reflects detected intent. Omit keys for artifacts not produced.
+
+## Mode-specific overrides
+
+**Update.** Apply the change. Log it via `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type change --text "<change + rationale>"`. Surface conflicts in `conflicts_with_prior_decisions[]`.
+
+**Validate.** Always write both `validation-report.html` and `validation-report.md` regardless of finding count. Always include `"offer_to_update": true`. Skip the browser-open step.
diff --git a/.claude/skills/bmad-ux/references/validate.md b/.claude/skills/bmad-ux/references/validate.md
new file mode 100644
index 0000000..86516bc
--- /dev/null
+++ b/.claude/skills/bmad-ux/references/validate.md
@@ -0,0 +1,115 @@
+# Validate
+
+Critique an existing spine pair (`DESIGN.md` + `EXPERIENCE.md`) or any format of UX the user provides, without changing it. The synthesis pipeline below is also used at the Reviewer Gate during Create / Update Finalize.
+
+## Orient
+
+Subagent-extract from `.memlog.md`, sources in frontmatter, `imports/`, `mockups/`, `wireframes/`, `DESIGN.md`, `EXPERIENCE.md`. Parent assembles from extracts.
+
+## Reviewer Gate
+
+**Opt-in.** Reviewers are costly. At Finalize, ask first if the user wants to run UX validation with multiple subagent lenses. Default offered, easy skip. At Validate intent, skip that question, the user already invoked it.
+
+**Lens menu.** UNLESS HEADLESS MODE: Always present the lens picks before dispatching. Build the menu from: rubric walker (this file) + `{workflow.finalize_reviewers}` + ad-hoc reviewers the skill judges relevant. The user picks all, a subset, or none. Only picked lenses dispatch.
+
+Rubric walker prompt:
+
+> Validate the spine pair (`DESIGN.md` + `EXPERIENCE.md`) as the contract for downstream consumers (architecture, story-dev — human or AI). Can a consumer source-extract cleanly, with every reference resolving and every load-bearing decision committed? Read `{workflow.design_md_examples}` and `{workflow.experience_md_examples}` first.
+>
+> **Pass 1 — mechanical coverage.** Per category: extract, then list misses with location citations. No misses = **strong**.
+>
+> 1. **Flow coverage** (EXPERIENCE.md). Sources frontmatter → extract every UJ / requirement name. Verify each has a Key Flow with named protagonist, numbered steps, a climax beat, and a failure path where applicable.
+>
+> 2. **Token completeness** (DESIGN.md). Extract every token in the YAML frontmatter and every `{path.to.token}` reference in the prose. Verify each defined (see `references/design-md-spec.md` for type rules). **Color tokens missing hex (or light/dark pairs where applicable) are critical** — downstream code mirrors the spine. Platform conventions (native dynamic type, 8pt grid) may stay semantic. Contrast targets stated for load-bearing combinations.
+>
+> 3. **Component coverage** (both spines). Extract every component name used anywhere. Verify each has a row in DESIGN.md.Components (visual spec) *and* EXPERIENCE.md.Component Patterns (behavioral spec) — real rules, not one-word descriptions.
+>
+> 4. **State coverage** (EXPERIENCE.md). Walk every IA surface. List states it should have (empty, cold-load, focus, error, offline, permission-denied — whichever apply). Verify each covered.
+>
+> 5. **Visual reference coverage.** List every file in `mockups/`, `wireframes/`, `imports/`. Spines link to each inline at the relevant section and name what it illustrates; spines-win-on-conflict stated once. List orphans and unspecific references.
+>
+> **Pass 2 — judgment.** Verdict per category (*strong / adequate / thin / broken*); findings only where they add information.
+>
+> 6. **Bloat & overspecification.** Pixel specs where tokens cover it; source restatement (personas, FRs, scope); prose where a table works; sections no downstream consumer would read; decorative narrative untied to a decision. DESIGN.md prose may carry editorial voice; EXPERIENCE.md prose should not.
+>
+> 7. **Inheritance discipline.** `sources` frontmatter resolves. UJ / requirement names verbatim from sources. Glossary identical across spines and sources. Component names identical across all sections in both files. EXPERIENCE.md token references resolve to DESIGN.md tokens by name.
+>
+> 8. **Shape fit.** DESIGN.md sections in canonical order (Brand & Style → Colors → Typography → Layout & Spacing → Elevation & Depth → Shapes → Components → Do's and Don'ts; omittable but order-locked when present). EXPERIENCE.md required defaults present (Foundation, IA, Voice and Tone, Component Patterns, State Patterns, Interaction Primitives, Accessibility Floor, Key Flows). Dropped defaults defensible. Required-when-applicable present where triggered (Inspiration when sources / memlog show reference products or rejects; Responsive when multi-surface or breakpoints). Invented sections earn their place.
+>
+> Severity = downstream impact, not fix difficulty.
+>
+> Write to `{doc_workspace}/review-rubric.md`:
+>
+> ```markdown
+> # Spine Pair Review — {project_name}
+>
+> ## Overall verdict
+> [2–3 sentences]
+>
+> ## 1. Flow coverage — [verdict]
+> [What was checked.]
+> ### Findings
+> - **[critical|high|medium|low]** [finding] (location). *Fix:* [suggestion].
+>
+> (repeat 2–8)
+>
+> ## Mechanical notes
+> [Name inconsistencies, broken cross-refs, frontmatter completeness, Mermaid syntax.]
+> ```
+>
+> Return ONLY a compact summary: overall verdict, per-section verdicts, finding counts by severity, file path.
+
+The gate may dispatch `{workflow.finalize_reviewers}` and ad-hoc reviewers (accessibility for consumer / regulated). Each writes `review-{slug}.md` and returns a compact summary. Parallel.
+
+## Synthesis pipeline
+
+Under Validate intent, after every reviewer returns, render one consolidated report. Don't skip.
+
+1. Read every `{doc_workspace}/review-*.md`.
+2. Fill `{workflow.validation_report_template}`. No overall grade — the per-category verdicts and severity counts already say what's true. Synthesis paragraph lifts the rubric's overall verdict; add a second if extra reviewers shift the picture. One section per rubric category (open if thin / broken), one per extra reviewer (closed, adversarial voice preserved).
+3. Write `{doc_workspace}/validation-report.html`.
+4. Write the Markdown twin `{doc_workspace}/validation-report.md` — same content grouped by severity.
+5. Open HTML with the platform opener — `open "{doc_workspace}/validation-report.html"` on macOS, `xdg-open` on Linux, `start ""` on Windows, path always double-quoted. On failure, give the user the path instead. Skip headless.
+
+Re-running overwrites the consolidated report; individual `review-*.md` files persist.
+
+## Markdown twin shape
+
+```markdown
+# Validation Report — {project_name}
+
+- **DESIGN.md:** `{design_path}`
+- **EXPERIENCE.md:** `{experience_path}`
+- **Run at:** {ISO timestamp}
+
+## Overall verdict
+{synthesis paragraphs}
+
+## Category verdicts
+- Flow coverage — {verdict}
+- Token completeness — {verdict}
+- Component coverage — {verdict}
+- State coverage — {verdict}
+- Visual reference coverage — {verdict}
+- Bloat & overspecification — {verdict}
+- Inheritance discipline — {verdict}
+- Shape fit — {verdict}
+
+## Findings by severity
+
+### Critical (n)
+**[Category or Reviewer]** — Title (§ location)
+{Note}
+Fix: {suggested fix}
+
+### High (n) / Medium (n) / Low (n)
+...
+
+## Reviewer files
+- `review-rubric.md`
+- ...
+```
+
+## Close
+
+Surface artifact paths. Always offer to roll findings into an Update.
diff --git a/.claude/skills/bmad-validate-prd/SKILL.md b/.claude/skills/bmad-validate-prd/SKILL.md
new file mode 100644
index 0000000..3000d02
--- /dev/null
+++ b/.claude/skills/bmad-validate-prd/SKILL.md
@@ -0,0 +1,30 @@
+---
+name: bmad-validate-prd
+description: 'Deprecated — forwards to bmad-prd (validate intent).'
+---
+
+# DEPRECATED — forwards to bmad-prd (validate intent)
+
+This skill was consolidated into `bmad-prd`. It is retained as a thin compatibility shim so existing invocations by name and `_bmad/custom/bmad-validate-prd.toml` override files keep working. New work should invoke `bmad-prd` directly — it detects create / update / validate intent from the conversation.
+
+## On Activation
+
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-validate-prd.toml` and `bmad-validate-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
+
+2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+
+3. Emit a deprecation notice to the user in `{communication_language}`:
+
+   > Notice: `bmad-validate-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with validate intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`, `prd_output_path`, `run_folder_pattern`), migrate `_bmad/custom/bmad-validate-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+
+4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
+
+   - **Intent:** `validate` — skip `bmad-prd`'s usual intent detection step.
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `prd_output_path`, `run_folder_pattern`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+     - `activation_steps_prepend` = the resolved value from step 1
+     - `activation_steps_append` = the resolved value from step 1
+     - `persistent_facts` = the resolved value from step 1
+     - `on_complete` = the resolved value from step 1
+   - **Original user input:** forward whatever the user said when invoking this skill verbatim (the target PRD path, etc.).
+
+   `bmad-prd` takes the workflow from here. Do not execute any further steps in this shim.
diff --git a/.claude/skills/bmad-validate-prd/customize.toml b/.claude/skills/bmad-validate-prd/customize.toml
new file mode 100644
index 0000000..15ec851
--- /dev/null
+++ b/.claude/skills/bmad-validate-prd/customize.toml
@@ -0,0 +1,42 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-validate-prd. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All PRDs must include a regulatory-risk section."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 13 (Validation Report Complete) and
+# the user exits via [X] Exit — not on [E] Use Edit Workflow (which chains to
+# bmad-edit-prd), [R] Review (which loops within), or [F] Fix (which loops within).
+# Override wins. Leave empty for no custom post-completion behavior.
+
+on_complete = ""
diff --git a/_bmad/_config/bmad-help.csv b/_bmad/_config/bmad-help.csv
new file mode 100644
index 0000000..bd10d3d
--- /dev/null
+++ b/_bmad/_config/bmad-help.csv
@@ -0,0 +1,28 @@
+module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
+BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
+BMad Method,bmad-prd,Create Edit and Review PRD,PRD,"Facilitated PRD workflow — create a new PRD via coached discovery, update an existing one against a change signal, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,bmad-product-brief,,true,planning_artifacts,prd
+BMad Method,bmad-ux,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,,2-planning,bmad-prd,,false,planning_artifacts,ux design
+BMad Method,bmad-project-context,Project Context,PC,"Set up or refresh a repo's agent instructions so AI agents work well in it: verified commands, policy, conventions that differ from defaults, and known pitfalls. Setup, refresh, record, and audit — replaces document-project and generate-project-context.",,,anytime,,,false,repo root,AGENTS.md managed block
+BMad Method,bmad-spec,Spec,SPC,"Use to distill any intent input (brief, PRD, transcript, brain dump, design folder, mixed multi-source) into a succinct, no-fluff SPEC.md contract + companions that downstream work derives from. Locks the WHAT before the HOW. Works for software, game design, research, editorial, policy, business, anything intent-bearing. Validation mode also available.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files
+BMad Method,bmad-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal
+BMad Method,bmad-sprint-planning,Sprint Status,SS,Anytime: summarize sprint status with risks open action items and the next recommended action; can also validate or repair the tracking file.,status,,anytime,,,false,,status summary
+BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,plan,,,false,{output_folder}/brainstorming,brainstorming session
+BMad Method,bmad-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,plan,,,false,planning_artifacts,product brief
+BMad Method,bmad-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,plan,,,false,planning_artifacts,prfaq document
+BMad Method,bmad-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,plan,,,true,planning_artifacts,architecture
+BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,,plan,bmad-architecture,,true,planning_artifacts,epics and stories
+BMad Method,bmad-sprint-planning,Sprint Planning,SP,Readiness gate then tracking: verifies the planning is implementable (PASS/CONCERNS/FAIL) and produces the sprint status the implementation agents follow for every story.,,,plan,,,true,implementation_artifacts,sprint status
+BMad Method,bmad-build,Build,BD,Official Phase 4 implementation loop: clarify intent plan implement review and present.,,,ship,bmad-sprint-planning,bmad-code-review,true,implementation_artifacts,spec and project implementation
+BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. Optional extra layer after Build's built-in review.,,,ship,bmad-build,,false,,
+BMad Method,bmad-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,ship,,,false,,
+BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,ship,bmad-build,,false,implementation_artifacts,test suite
+BMad Method,bmad-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,ship,bmad-code-review,,false,implementation_artifacts,retrospective
+Core,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
+Core,bmad-brainstorming,Brainstorming,BSP,Use early in ideation or when stuck generating ideas.,,,anytime,,,false,{output_folder}/brainstorming,brainstorming session
+Core,bmad-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you need multiple perspectives or want agents to collaborate.,,,anytime,,,false,,
+Core,bmad-help,BMad Help,BH,,,,anytime,,,false,,
+Core,bmad-customize,BMad Customize,BC,"Use when you want to change how an agent or workflow behaves — add persistent facts, swap templates, insert activation hooks, or customize menus. Scans what's customizable, picks the right scope (agent vs workflow), writes the override to _bmad/custom/, and verifies the merge. No TOML hand-authoring required.",,,anytime,,,false,{project-root}/_bmad/custom,TOML override files
+Core,bmad-advanced-elicitation,Advanced Elicitation,AE,"Use at any checkpoint to push a just-produced draft, section, or plan past its first version — pick from a menu of elicitation methods (pre-mortem, first principles, red team, socratic) and apply the improvements.",,,anytime,,,false,,
+Core,bmad-review,Review,RV,"Use to review anything before it ships — a diff, branch, or uncommitted changes; a PRD, spec, story, or architecture doc; any prose document. Runs whichever installed lenses fit the content and reports findings in one shape: shipped lenses cover adversarial critique, edge cases, verification gaps, document structure (cuts, merges, moves), and prose copy-edit, and installs may add more. Reach for it to tighten a bloated or LLM-slop draft, pressure-test a plan before building, or check a change is adequately tested. Run every applicable lens or name the ones you want. Code Review in other modules calls it automatically.",,[path],anytime,,,false,,findings JSON array + markdown report
+Core,bmad-forge-idea,Forge Idea,FI,"Use to pressure-test and harden an idea — software, business, creative, research, or life — until it proves out, hardens into something buildable, or dies cheaply. Persona-driven interrogation; optional handoff to bmad-spec or bmad-build.",,,anytime,,,false,{output_folder}/forge,refined-idea brief (optional)
+Core,bmad-deep-recon,Deep Recon,RS,Decision-grade research three ways: draft a deep-research prompt for your own AI tool then process the returned report into a downstream-ready cited summary — or run the research directly via web fan-out. Types: market domain technical competitive user-voice academic-lit plus a select shape for choose-between decisions; claim verification and refresh lifecycle. Custom types via overrides.,,[type],anytime,,,false,{planning_artifacts}/research,research report/summary + optional html briefing
\ No newline at end of file
diff --git a/_bmad/_config/files-manifest.csv b/_bmad/_config/files-manifest.csv
new file mode 100644
index 0000000..59105a5
--- /dev/null
+++ b/_bmad/_config/files-manifest.csv
@@ -0,0 +1,265 @@
+type,name,module,path,hash
+"yaml","manifest","_config","_config/manifest.yaml","539f190c0099d21cffad41c6d5d3840155acea619c4acbe5eb4b4bf22d1c41bd"
+"csv","module-help","bmm","bmm/module-help.csv","fe1f3c778d5d909d5858e0d13f2a7d4d18f40180de05a3c4fa7a5470dabeb945"
+"html","validation-report-template","bmm","bmm/plan/bmad-prd/assets/validation-report-template.html","a80becdd8205d2d7c18738855830b096172a496b96b5ca8a0820ec55c9bb8bf9"
+"html","validation-report-template","bmm","bmm/plan/bmad-ux/assets/validation-report-template.html","8656945636fabe96624f8ef8fce931b073b5aecbe42d490584c1d5c7f31e1353"
+"json","bmad-manifest","bmm","bmm/plan/bmad-prfaq/bmad-manifest.json","9d91d2ae277b87bdfb8785df6a660788743c5cdf98cbd9fcf88c29f957324709"
+"md","acceptance-verdict","bmm","bmm/ship/bmad-retrospective/references/acceptance-verdict.md","09a65007c39af83e01e039331c252e6e670b134cd5e2a4b5e05ac9d9fb7e37f1"
+"md","aggregate-views","bmm","bmm/ship/bmad-retrospective/references/aggregate-views.md","5b278afce4a53692d8715b4af178e4233da0876921dc3154b5763d056cb5ff0b"
+"md","artifact-analyzer","bmm","bmm/plan/bmad-prfaq/agents/artifact-analyzer.md","7bdc44830f8d593346ec0ee15e36e1e431432fcc6c38b70bb861999315c9cfa4"
+"md","best-practices","bmm","bmm/plan/bmad-project-context/references/best-practices.md","ded4ad303ea7a62c2c55a8673085cb4deeaf8306a68ebcc09fa2c308589fbf9b"
+"md","brief-template","bmm","bmm/plan/bmad-product-brief/assets/brief-template.md","bb28edf75d023067551c8d417b19b8803324e7acfb2ad0c80f882e9134f4c1f1"
+"md","checklist","bmm","bmm/ship/bmad-correct-course/checklist.md","3e082b95def90ccb876e3101ce0bbaf797a0f03a9471e1347361897f27977327"
+"md","checklist","bmm","bmm/ship/bmad-qa-generate-e2e-tests/checklist.md","b58f810aeb1040c2f6758c88aa133afce72f8cc178d3d97ff0fbaa3d943057dc"
+"md","checklist","bmm","bmm/v6-shims/bmad-create-story/checklist.md","b94e28e774c3be0288f04ea163424bece4ddead5cd3f3680d1603ed07383323a"
+"md","checklist","bmm","bmm/v6-shims/bmad-dev-story/checklist.md","630b68c6824a8785003a65553c1f335222b17be93b1bd80524c23b38bde1d8af"
+"md","color-themes","bmm","bmm/plan/bmad-ux/assets/color-themes.md","ccb6e4ef47a196476cf9392d788938ad3ca8d07b9ce095b7c092dcb4e06735f0"
+"md","compile-epic-context","bmm","bmm/ship/bmad-build/compile-epic-context.md","6793b15ae85766cee529e6b349e45f2c6ec9e3212019611c29e8c77b4dc4b924"
+"md","compile-epic-context","bmm","bmm/ship/bmad-build-auto/compile-epic-context.md","64d13b41974cfa0dfc1de64b6fbd8365e9b99f91c7c98f0ee1a9fbd018f324ca"
+"md","creative-tools","bmm","bmm/plan/bmad-ux/references/creative-tools.md","e281292d7c0fdecdbb67ca9b7d95d4bed803626ba5edfd8dcc99146fcaa118e6"
+"md","customer-faq","bmm","bmm/plan/bmad-prfaq/references/customer-faq.md","96f8565197649c58908a1d61b6cd805fd01f57da7945ba889c18d087ad597aeb"
+"md","deletion-check","bmm","bmm/ship/bmad-build/references/deletion-check.md","0f1f124e4e957147e89164a272b10bedc694ad0d9ad2618c8610ac74ee9cb0da"
+"md","deletion-check","bmm","bmm/ship/bmad-build-auto/references/deletion-check.md","0f1f124e4e957147e89164a272b10bedc694ad0d9ad2618c8610ac74ee9cb0da"
+"md","deletion-check","bmm","bmm/ship/bmad-code-review/references/deletion-check.md","0f1f124e4e957147e89164a272b10bedc694ad0d9ad2618c8610ac74ee9cb0da"
+"md","design-directions","bmm","bmm/plan/bmad-ux/assets/design-directions.md","eab73b948da76a27abc908e1e7d6b124e8ff0362e6dd1990f7e60b9541cbcb98"
+"md","design-example-editorial","bmm","bmm/plan/bmad-ux/assets/design-example-editorial.md","a659166845b1a4ed3f9aef942c5935537a97382b10303684fbb78ed86265870e"
+"md","design-example-mobile","bmm","bmm/plan/bmad-ux/assets/design-example-mobile.md","a93fb9f114f2e83af0c961c0d7909b3859fc80bcd713715517cd639a53a0372a"
+"md","design-example-shadcn","bmm","bmm/plan/bmad-ux/assets/design-example-shadcn.md","25e0dfb2bb21483973a8f0a6ed650288b3dc2ae5ed02aa0f091bb9b6b0b39fc0"
+"md","design-md-spec","bmm","bmm/plan/bmad-ux/references/design-md-spec.md","d04d5f663607aba3f3181e818ae33856e6caf5e560dcb16fa64ed80b7cf3d590"
+"md","discover-inputs","bmm","bmm/v6-shims/bmad-create-story/discover-inputs.md","dfedba6a8ea05c9a91c6d202c4b29ee3ea793d8ef77575034787ae0fef280507"
+"md","edge-case-hunter","bmm","bmm/ship/bmad-build/review-prompts/edge-case-hunter.md","4ccb3599ed1b8cc54876b304dc567d1b4e3e0ec5c1add34df9a2445224ac77af"
+"md","edge-case-hunter","bmm","bmm/ship/bmad-build-auto/review-prompts/edge-case-hunter.md","4ccb3599ed1b8cc54876b304dc567d1b4e3e0ec5c1add34df9a2445224ac77af"
+"md","edge-case-hunter","bmm","bmm/ship/bmad-code-review/review-prompts/edge-case-hunter.md","4ccb3599ed1b8cc54876b304dc567d1b4e3e0ec5c1add34df9a2445224ac77af"
+"md","epics-template","bmm","bmm/plan/bmad-create-epics-and-stories/templates/epics-template.md","a804f740155156d89661fa04e7a4264a8f712c4dc227c44fd8ae804a9b0f6b72"
+"md","evidence-gathering","bmm","bmm/ship/bmad-retrospective/references/evidence-gathering.md","575bace78d7c03c48d86a209dd664f7dd22295a222b75e6d6298894cb7b7ce00"
+"md","excalidraw-wireframe","bmm","bmm/plan/bmad-ux/assets/excalidraw-wireframe.md","660bbcdebff50cd044a3752eda43f3cb303aca4b0f521b55a270da93b89ddb18"
+"md","experience-example-mobile","bmm","bmm/plan/bmad-ux/assets/experience-example-mobile.md","f8cd54c92193cd8c34a472df9c212ac7330976f6a115b729721dcb60034dc4f0"
+"md","experience-example-shadcn","bmm","bmm/plan/bmad-ux/assets/experience-example-shadcn.md","d6ca16e87b768e8b41f352c02ee08af21d7cdac04ca21e6ae1556864b4d27590"
+"md","fix-sprint-status","bmm","bmm/plan/bmad-sprint-planning/references/fix-sprint-status.md","0406c31b70da33e2a354d9785f43d8f9918f4b923d0aac2ebd1e3707ebad5806"
+"md","generate-tracking","bmm","bmm/plan/bmad-sprint-planning/references/generate-tracking.md","4dbf7aca26d0e6e893f288fc5e6158dbbcd65f77bbaf95e941ca705abceb1741"
+"md","generate-trail","bmm","bmm/ship/bmad-checkpoint-preview/generate-trail.md","4a5936d86fbe5a85285b4535097b1e2edda8849da35586f4b588a982d7224459"
+"md","headless","bmm","bmm/plan/bmad-architecture/references/headless.md","4db2708f335c94cb024b5eba022b1e3d88b1ec61c94c4716626d9b89684f5833"
+"md","headless","bmm","bmm/plan/bmad-prd/references/headless.md","4dad58ebee63933a53179016513ff94d143ce9f68e226489d390e2c36bf1d848"
+"md","headless","bmm","bmm/plan/bmad-ux/references/headless.md","8da7e23d269b1644f45b5104a243a6a27fd8d075aebb95d9b7752f0d143f0f5d"
+"md","headless-schemas","bmm","bmm/plan/bmad-prd/assets/headless-schemas.md","8d3621333a72400512bd62511bc4c73fc745711505e1f852c697ff8c5fa2de93"
+"md","headless-schemas","bmm","bmm/plan/bmad-spec/assets/headless-schemas.md","83afb3614716db2347d83586a67b9c524492dd50db5282436ccb35c99fb5f08a"
+"md","headless-schemas","bmm","bmm/plan/bmad-ux/assets/headless-schemas.md","e3a773dde85286f1a6f6dd8b26fc17e09ccea96f6257dfe7fb436353cd79242d"
+"md","internal-faq","bmm","bmm/plan/bmad-prfaq/references/internal-faq.md","26eb83f844cda1ed8efb50f4703d61713ada8a64bd27eb387f759f858b5748de"
+"md","key-screens","bmm","bmm/plan/bmad-ux/assets/key-screens.md","ff1c5060673dd595edd61e76806bae876264ec6895c2eaadf8a6190785bf5f7b"
+"md","prd-template","bmm","bmm/plan/bmad-prd/assets/prd-template.md","b6fe8fc1390b8e46961d5eb5e6f2fe6c65dca2f30623d492677672e02868f7ab"
+"md","prd-validation-checklist","bmm","bmm/plan/bmad-prd/assets/prd-validation-checklist.md","41d9f09064772a92ec908d970618e47ba63dc86b5c5a1a21d5a2c676d3ba8e3f"
+"md","press-release","bmm","bmm/plan/bmad-prfaq/references/press-release.md","c406adb0e2d2cc326cbc45d0174f89d014523448ad82bc272293999d22aec596"
+"md","prfaq-template","bmm","bmm/plan/bmad-prfaq/assets/prfaq-template.md","b27e6964f0437ab4e78c8c0ffbe5052c28e3b3ef2fc811726cbb394d5a5c7559"
+"md","readiness-gate","bmm","bmm/plan/bmad-sprint-planning/references/readiness-gate.md","7d58ea61fafe3c1d8218203abc7512e322ca384c78d9e71829df55dfabe1245b"
+"md","README","bmm","bmm/v6-shims/README.md","05315a8e369f5ebb9e615c1a33fd2b3f85eb92a9455c974cdc7ec7d3ea0d10bf"
+"md","retro-document","bmm","bmm/ship/bmad-retrospective/references/retro-document.md","de8164664cd2be7f73b8ba5552e9e0f58816d2a7c4be8efc7715461846bb7001"
+"md","reviewer-gate","bmm","bmm/plan/bmad-architecture/references/reviewer-gate.md","d32e32a3c1d59b5612b947004f3f6fef1117a13ce9f1ffa428d616e0b5d4db69"
+"md","SKILL","bmm","bmm/agents/bmad-agent-analyst/SKILL.md","99c72ea74b833743a71a8e3c54369348530525edcfae43da2d267ec27cefc8ff"
+"md","SKILL","bmm","bmm/agents/bmad-agent-architect/SKILL.md","72a542f7cd34ebf844c26431be564040824f0c16cf060b8795eff2c9e019f003"
+"md","SKILL","bmm","bmm/agents/bmad-agent-dev/SKILL.md","b980cf2c99976b5e1bd53128dc7b56bdd181ac39a57098d9b5a6bf0692db2675"
+"md","SKILL","bmm","bmm/agents/bmad-agent-pm/SKILL.md","7b84234262e749f22fe31032124024c8c4283ba55294916b2ec67917a3bb9fb5"
+"md","SKILL","bmm","bmm/agents/bmad-agent-ux-designer/SKILL.md","2ba39678706fd536a98f7afcbb3d85c3b74e24bdb86a191b330fcd7fd7e64c03"
+"md","SKILL","bmm","bmm/plan/bmad-architecture/SKILL.md","b3d8c6e5024cb9747ef1659cec8109f5bb797fd1760338e65237bb084b60fcdc"
+"md","SKILL","bmm","bmm/plan/bmad-create-epics-and-stories/SKILL.md","6b27b0730c61309190eb7c9c84ae98b11cbfe7187941ef88f45ddc8ded850c04"
+"md","SKILL","bmm","bmm/plan/bmad-generate-project-context/SKILL.md","8cc66337d465bb088831d8973a25cfb4374f1a3427638cc2fb553fad29d08f12"
+"md","SKILL","bmm","bmm/plan/bmad-prd/SKILL.md","5c220a51dc6f25499b7f18c7104a0a981dc3d721aa63d0fba88ec3de32c3fbde"
+"md","SKILL","bmm","bmm/plan/bmad-prfaq/SKILL.md","042611ccabfdab1254e6591f6b86f81f332acb874fc2d148af5ac6dcd5a1c726"
+"md","SKILL","bmm","bmm/plan/bmad-product-brief/SKILL.md","4c15a8ec688c998eeb71957f208b5953b1ac7a5641b008b3509f1f4fcdc8e6cd"
+"md","SKILL","bmm","bmm/plan/bmad-project-context/SKILL.md","1a276f306ed76f98ad2b04864cfe365426420d33438879ea4f0705c2a013324c"
+"md","SKILL","bmm","bmm/plan/bmad-spec/SKILL.md","5b5680dbf01dbfc5b4a5485e70f20ea48ac21a1d6137c4ea2ff704262dcc45d2"
+"md","SKILL","bmm","bmm/plan/bmad-sprint-planning/SKILL.md","6ed5dd51be5d6a807c7e6af0542bff609fe69e84b67025ed7aa3fd9ae1ccb36d"
+"md","SKILL","bmm","bmm/plan/bmad-ux/SKILL.md","6475c8171bf7346964234bd35994b9d5518102dc245768c660e4dacd1e6b50fd"
+"md","SKILL","bmm","bmm/ship/bmad-build/SKILL.md","bce4778d8d275095ca1836733337163c1bf11a5a62e6585b951de458a5ac2c8e"
+"md","SKILL","bmm","bmm/ship/bmad-build-auto/SKILL.md","ea6931f8210e92f7d9cfb845040d557d4d8c02eced3acc3d77bd2fcc4fffc235"
+"md","SKILL","bmm","bmm/ship/bmad-checkpoint-preview/SKILL.md","fbc932defc41c7d9ffd107dbbccc296854b2ece76d95e9712e19d24f0a4c3606"
+"md","SKILL","bmm","bmm/ship/bmad-code-review/SKILL.md","1ba6481b28c7e4b2ea0b1447e9011a9cac3ef51fdf957d09050606d2d16b196b"
+"md","SKILL","bmm","bmm/ship/bmad-correct-course/SKILL.md","507394a758e297152a806fe5529ecc54c6c2725c951bdcbbdb250622a83fa820"
+"md","SKILL","bmm","bmm/ship/bmad-qa-generate-e2e-tests/SKILL.md","4aad390d3f063efb8783637a0f72b993135ec2acb810693d3146a161172057c8"
+"md","SKILL","bmm","bmm/ship/bmad-retrospective/SKILL.md","8da5b53055afa76cf88135f186d35a6cb95bab1096ed96022354846dc788d26a"
+"md","SKILL","bmm","bmm/v6-shims/bmad-create-architecture/SKILL.md","2d199970238a7f415aa4b9224ec01f296b4b3ee7b399f75092ed8bdd3e414be1"
+"md","SKILL","bmm","bmm/v6-shims/bmad-create-prd/SKILL.md","fa8cc47fff80a19446057b0469e79ea65973ceccb71e96079bf734b34699eb69"
+"md","SKILL","bmm","bmm/v6-shims/bmad-create-story/SKILL.md","bea46d2823aded992d90a8d6d684f7c67c0865478b01c1443ba4c3eac04bbd28"
+"md","SKILL","bmm","bmm/v6-shims/bmad-dev-auto/SKILL.md","1c056c69a17043bfb4b80f9e42a8ec8338fc6fa47c6ae8d5cf53f8a326966b4a"
+"md","SKILL","bmm","bmm/v6-shims/bmad-dev-story/SKILL.md","8f9baf6a4643a3e9b307864eceed5aa9ddfe4e325226d70b78e0c85908ab7d5d"
+"md","SKILL","bmm","bmm/v6-shims/bmad-document-project/SKILL.md","c4a09a6dc3aaaf90e12e1467b48a37416820ff351316a4eda7cda826dbb7fbd7"
+"md","SKILL","bmm","bmm/v6-shims/bmad-domain-research/SKILL.md","6c873cdb44ed6444c2abfb335ad7af474fda56f4ba62c1c9c7cff42d9a243cd4"
+"md","SKILL","bmm","bmm/v6-shims/bmad-edit-prd/SKILL.md","26448c4017c09ad8defa8525d9517ce681bb50222320517eaa635fa0f31989f9"
+"md","SKILL","bmm","bmm/v6-shims/bmad-market-research/SKILL.md","b52667b85bee97ff23dd02532a2f286c72e63fd14b1afaedd6592de4d6112df6"
+"md","SKILL","bmm","bmm/v6-shims/bmad-quick-dev/SKILL.md","23bb1434e03693152311b8e79570bb8a042eb39f57615cc4d0df15b72f29b113"
+"md","SKILL","bmm","bmm/v6-shims/bmad-sprint-status/SKILL.md","95e695ce9665c6b3d617d41b0581bc30de6288263609a910559a97b26eb49e78"
+"md","SKILL","bmm","bmm/v6-shims/bmad-technical-research/SKILL.md","d8e6177fc03c3d815642bdf6b54b83ef37874e73118d89112f155dbda14afbfa"
+"md","SKILL","bmm","bmm/v6-shims/bmad-validate-prd/SKILL.md","16bff9ed7ec003add9c56818575f613380925782bd4ef0cc0804ed34a074eeaf"
+"md","spec-template","bmm","bmm/plan/bmad-spec/assets/spec-template.md","4b3a032c045fdd0903933446fc07f93e879997f28a0294ed4344da71192b20ee"
+"md","spec-template","bmm","bmm/ship/bmad-build/spec-template.md","68d0e3b9acaa0c22ab3b0dd1dbce9d8ef9b4d16637ed5e6fbd5244528732943e"
+"md","spec-template","bmm","bmm/ship/bmad-build-auto/spec-template.md","5fccfa92dd632d4be646ab40f2882452189aba49db57fe3fa00fcc1806666d74"
+"md","spine-template","bmm","bmm/plan/bmad-architecture/assets/spine-template.md","ef4ff795624eb5439fae54a06edb389feb5a0cf79cb01ae007af51109335d198"
+"md","status-view","bmm","bmm/plan/bmad-sprint-planning/references/status-view.md","c3547e221ebf6e55c874e2ada3e8c18198835213c76f0bb2e0e64150aac355ab"
+"md","step-01-clarify-and-route","bmm","bmm/ship/bmad-build/step-01-clarify-and-route.md","0a3afcde2b1d4475250896f132fd8839cf442b3364ebfbeeace5a489042c7c7f"
+"md","step-01-clarify-and-route","bmm","bmm/ship/bmad-build-auto/step-01-clarify-and-route.md","7480db7720720212bd045793fddcb91f06091fe512e53b38127f6440c3fd96e2"
+"md","step-01-gather-context","bmm","bmm/ship/bmad-code-review/steps/step-01-gather-context.md","3f5a74d63a91fb385d33786b78d09bb9bca483b1ac45933b9715c9fb79b79e9d"
+"md","step-01-orientation","bmm","bmm/ship/bmad-checkpoint-preview/step-01-orientation.md","d9e3b949c36d49a025f3535773af2b51888fe4ce616b6d6d69683a122716b1d2"
+"md","step-01-validate-prerequisites","bmm","bmm/plan/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md","7181608c1ee4e55c084c6627d68fc55a8a0b6917e489f8ac77531a0530428a30"
+"md","step-02-design-epics","bmm","bmm/plan/bmad-create-epics-and-stories/steps/step-02-design-epics.md","7c66987808c1f84e853fe54b7aff26d209196d450b5644704110f124a15179bc"
+"md","step-02-plan","bmm","bmm/ship/bmad-build/step-02-plan.md","d90db50ca7a679dd42f7d1587a909d0579f24480b116d6ed82b4c7d4fe9bea66"
+"md","step-02-plan","bmm","bmm/ship/bmad-build-auto/step-02-plan.md","a08e303c10f88dbfce88c55044757ec5059afe338793eb414e1ddb0b7c324625"
+"md","step-02-review","bmm","bmm/ship/bmad-code-review/steps/step-02-review.md","3d146c060e838413f1262211cc58b06eeee1a9a86b8997efd83d0dc8c03cfa60"
+"md","step-02-walkthrough","bmm","bmm/ship/bmad-checkpoint-preview/step-02-walkthrough.md","66cf893f8f968ee81034e9ccd8c20415692c3a8c23a9a143c2245fe6c800acdc"
+"md","step-03-create-stories","bmm","bmm/plan/bmad-create-epics-and-stories/steps/step-03-create-stories.md","c5b787a82e4e49ed9cd9c028321ee1689f32b8cd69d89eea609b37cd3d481afc"
+"md","step-03-detail-pass","bmm","bmm/ship/bmad-checkpoint-preview/step-03-detail-pass.md","d48163b9f305f15af57729a8443142e47beb6c3e977554afe12b39ee49cb9fc0"
+"md","step-03-implement","bmm","bmm/ship/bmad-build/step-03-implement.md","3b77ca64380b2989016191f488311ff392df0ebf4f641b9898d02b01767a646f"
+"md","step-03-implement","bmm","bmm/ship/bmad-build-auto/step-03-implement.md","f3e427c6033a26adcc327e4367db38c619527858a1175b148ec5a6f53d1bb408"
+"md","step-03-triage","bmm","bmm/ship/bmad-code-review/steps/step-03-triage.md","46a9e661e8aed6a7347cd7bc0b3f7edd8e4bffcfc96b2e15895f7a8ce2517d70"
+"md","step-04-final-validation","bmm","bmm/plan/bmad-create-epics-and-stories/steps/step-04-final-validation.md","5f6033e26ed06e070dcfcefb47d648b5a266012aaed7d53f028ab3f2c0542d20"
+"md","step-04-present","bmm","bmm/ship/bmad-code-review/steps/step-04-present.md","08baa98dae5e3bd70f211d1d3ce42f14e25030f4d6b17fc18e8635644847850c"
+"md","step-04-review","bmm","bmm/ship/bmad-build/step-04-review.md","bcf300e2faaf413afe1a25498284baabba09681bca089e615530d0b9dc5cee72"
+"md","step-04-review","bmm","bmm/ship/bmad-build-auto/step-04-review.md","8e9ff909192e1d5d50f9fc071c4b5eb8830cc921200d423904a30dadca58c3e9"
+"md","step-04-testing","bmm","bmm/ship/bmad-checkpoint-preview/step-04-testing.md","28a56e868968ea2d18add0df8c4bccced0f94b698e218df3d45ddac072ce369c"
+"md","step-05-present","bmm","bmm/ship/bmad-build/step-05-present.md","81e80f3fd38f8e3049afe9daf41783b86b00ac22544f7f36bd430496a12d8e46"
+"md","step-05-wrapup","bmm","bmm/ship/bmad-checkpoint-preview/step-05-wrapup.md","b1f04d64f0c9c9e4c051ebdd81eee1083d60c6aaca96bb5d3d85e0cbeca0143e"
+"md","step-oneshot","bmm","bmm/ship/bmad-build/step-oneshot.md","e75505130a2fcc49cd71dfb36c92e76255d39fdfe8d4f735c7c9276e2917cb8a"
+"md","stories-schema","bmm","bmm/plan/bmad-spec/assets/stories-schema.md","4f8137c00e2710288354a4466d1cfb90704f4b2a04bd3b63924218fd589cc6a9"
+"md","sync-sprint-status","bmm","bmm/ship/bmad-build/sync-sprint-status.md","6c9e2ec17245d2dcb796bd9a36997371a20db8e579a2f803d16064e3bc36c40b"
+"md","team-discussion","bmm","bmm/ship/bmad-retrospective/references/team-discussion.md","a9c504c436038c7e47d08322413aa3c213d2859b36ae30e873cb8c60fd9e008e"
+"md","template","bmm","bmm/plan/bmad-project-context/references/template.md","c8b9a1fc165996614504bb9c90c5b1c6c808a8d483e36a4d250d79f62fda6fa1"
+"md","template","bmm","bmm/v6-shims/bmad-create-story/template.md","29ba697368d77e88e88d0e7ac78caf7a78785a7dcfc291082aa96a62948afb67"
+"md","validate","bmm","bmm/plan/bmad-prd/references/validate.md","19b2fa66d58cb4fef3d920cd09c81f8add4ee44dd4191bec87eaba84c2093338"
+"md","validate","bmm","bmm/plan/bmad-sprint-planning/references/validate.md","ac680fa0a0f945a9bc0fc89ca709b2a8e6bc3b2617cd0d3d730378c4b5edd86d"
+"md","validate","bmm","bmm/plan/bmad-ux/references/validate.md","7c2189d9ac1585d9408b6ed0346ba564869e7db89dba8f81044db3431cfcee65"
+"md","verdict","bmm","bmm/plan/bmad-prfaq/references/verdict.md","81c06748ae2cb8e191cd282ecff83bea79532512c994fd4fffbf12c56be58a13"
+"md","verification-gap","bmm","bmm/ship/bmad-build/review-prompts/verification-gap.md","11b6bbbd4e3426a25cca81229c98971e5f20ce99638940c47c9c1484011b457a"
+"md","verification-gap","bmm","bmm/ship/bmad-build-auto/review-prompts/verification-gap.md","11b6bbbd4e3426a25cca81229c98971e5f20ce99638940c47c9c1484011b457a"
+"md","verification-gap","bmm","bmm/ship/bmad-code-review/review-prompts/verification-gap.md","11b6bbbd4e3426a25cca81229c98971e5f20ce99638940c47c9c1484011b457a"
+"md","web-researcher","bmm","bmm/plan/bmad-prfaq/agents/web-researcher.md","6e9127bb9bd3e4b15c701e4ced9eef328769262cd34eadc221bebe954c1f3aef"
+"md","workflow","bmm","bmm/ship/bmad-build/workflow.md","481ff00ef349a9c7845feca02bbfd5722b1e318ccabac858355da6c90c2d8a39"
+"md","workflow","bmm","bmm/ship/bmad-build-auto/workflow.md","f5f538a647b2a09406b11337244d1bd74fe97e7fa85b58a990184fcb480bfd90"
+"py","git_evidence","bmm","bmm/ship/bmad-retrospective/scripts/git_evidence.py","6e08688d2943217b61e784c7df3508aa1502d7cecf53ea7cd530944c431c91b6"
+"py","lint_spine","bmm","bmm/plan/bmad-architecture/scripts/lint_spine.py","040e0f1c13d31e6a21c518df943d1d7de7b75d8d98a07603b0983f3f3fb500db"
+"py","sprint_plan","bmm","bmm/plan/bmad-sprint-planning/scripts/sprint_plan.py","4c30f62c261599fc1da3fd319ea6ce5092aa0332221cedee1763a1040627e6bc"
+"py","sprint_status","bmm","bmm/ship/bmad-retrospective/scripts/sprint_status.py","a697eecd53cd9177657aee4cfdb2eab06d7d81f3e855b096cfe0482a74c50ebe"
+"py","test_git_evidence","bmm","bmm/ship/bmad-retrospective/scripts/tests/test_git_evidence.py","0abfc8fad338830fc2db656d3ccc500631b0ea7a2ab87d853c13a6bbd46ff13c"
+"py","test_lint_spine","bmm","bmm/plan/bmad-architecture/scripts/tests/test_lint_spine.py","e86bb9a62c5cca74ddc89c843386f2b992610fcc1792d40e03bc9cd445b77681"
+"py","test_sprint_plan","bmm","bmm/plan/bmad-sprint-planning/scripts/tests/test_sprint_plan.py","f1c3b640e156946b0a234e233807b2a3983cb0d3f2d13dbb9830fbe0c67e5238"
+"py","test_sprint_status","bmm","bmm/ship/bmad-retrospective/scripts/tests/test_sprint_status.py","23da16cca54904a256fcf88fd8f912c3f6091ea343768c241bbd2aeebbca2af3"
+"pyc","sprint_plan.cpython-311","bmm","bmm/plan/bmad-sprint-planning/scripts/__pycache__/sprint_plan.cpython-311.pyc","c92c8bd560b76b970c88ec2e3b18c6611f423ca91ffe6f741348ea94e04da61d"
+"pyc","sprint_status.cpython-311","bmm","bmm/ship/bmad-retrospective/scripts/__pycache__/sprint_status.cpython-311.pyc","a1f809abad01386d1342d3a70df401ced7c1de42c94133b65422ad3f2b2f382b"
+"pyc","test_git_evidence.cpython-311-pytest-9.1.1","bmm","bmm/ship/bmad-retrospective/scripts/tests/__pycache__/test_git_evidence.cpython-311-pytest-9.1.1.pyc","bd1ab9d967e7e77c9a734640a64e5c0282e6ce4a53a6b0956cc54f4cefd25770"
+"pyc","test_sprint_plan.cpython-311-pytest-9.1.1","bmm","bmm/plan/bmad-sprint-planning/scripts/tests/__pycache__/test_sprint_plan.cpython-311-pytest-9.1.1.pyc","640ded70adc12c995a3b92680a44ad9b679ca80bce6b0ae03f70e17a19aa5ae8"
+"pyc","test_sprint_status.cpython-311-pytest-9.1.1","bmm","bmm/ship/bmad-retrospective/scripts/tests/__pycache__/test_sprint_status.cpython-311-pytest-9.1.1.pyc","9f3cb3413808cd73dbdd619051b624482d7b5ce1359d2d549310e7b5434c0c55"
+"toml","customize","bmm","bmm/agents/bmad-agent-analyst/customize.toml","9b3e94d90784bbb24ab2c8f0563aaece48aa317554622750538e6c0e14478b37"
+"toml","customize","bmm","bmm/agents/bmad-agent-architect/customize.toml","82f0f082935f56e6fde41b007440edaa04984eb23abf26a3be7b1442baf0047a"
+"toml","customize","bmm","bmm/agents/bmad-agent-dev/customize.toml","f3f107f11f150f62091a792fcdf224dbf8d6c351d24e2b1d08aabb077e655feb"
+"toml","customize","bmm","bmm/agents/bmad-agent-pm/customize.toml","086d498b0e3d0c5dd193f8347ba30fdc93efcb57bbdfaff21fb0b418dba81ba8"
+"toml","customize","bmm","bmm/agents/bmad-agent-ux-designer/customize.toml","3df7da44945f9df34dbb3a64de086c756e6c298e73078e388e8f9a4f57cbf7ab"
+"toml","customize","bmm","bmm/plan/bmad-architecture/customize.toml","a6bb60a3adf976031f2870203285b1fc7a56e71e21232cd23bba544b178b5f15"
+"toml","customize","bmm","bmm/plan/bmad-create-epics-and-stories/customize.toml","da9e43605bc6aec83173050b5d37ede6aebfa9a17c5959a5029681d73e744ba3"
+"toml","customize","bmm","bmm/plan/bmad-prd/customize.toml","7f9a3a3503a3f758003ce2f1de59c31cc53658223e355fc76055f3140ef34e90"
+"toml","customize","bmm","bmm/plan/bmad-prfaq/customize.toml","8994f925bab65bd310e5ab38781286b6137f3e0c9e89f3ab8a2f480eb05e0de5"
+"toml","customize","bmm","bmm/plan/bmad-product-brief/customize.toml","50abc46f7c2e7cc7b02e2edc4aa6a237a46ea49dcc6781da5b42bd8968de39ab"
+"toml","customize","bmm","bmm/plan/bmad-project-context/customize.toml","9bf8a3aa919832cd8932853da550fcaebd06a9e13c0cde453f4379d8327f9c0f"
+"toml","customize","bmm","bmm/plan/bmad-spec/customize.toml","a89e0f53f9b6386c281dd0158a21801a6b16f122085fd68b0220cd403c18f830"
+"toml","customize","bmm","bmm/plan/bmad-sprint-planning/customize.toml","f7bde2f792e8604f26122ee792c5493e270710296044b07680db7d90e886caf3"
+"toml","customize","bmm","bmm/plan/bmad-ux/customize.toml","61f8bfbb020beb159b8da570ed416b02ec4a9ba3709aa0d08b417648d85328d8"
+"toml","customize","bmm","bmm/ship/bmad-build/customize.toml","68a0134f3f9e7f4a7b077aa2dcca1c68f208701d3487482e84afbee8717efec6"
+"toml","customize","bmm","bmm/ship/bmad-build-auto/customize.toml","eb0b39a3e24e86e9dbca98506c8384ec452c539acb690063cabab4385c82f09a"
+"toml","customize","bmm","bmm/ship/bmad-checkpoint-preview/customize.toml","1a1e0c3a8914adda3cec925eed51287e067c7f84120de64a8df53348e7b77de5"
+"toml","customize","bmm","bmm/ship/bmad-code-review/customize.toml","4f50371c61dea41c100b137e3d2ac750b4e55bb3be55e5a62c77f527dae22f94"
+"toml","customize","bmm","bmm/ship/bmad-correct-course/customize.toml","78095d25afb5b2d4844956f61e9ac640a62d0245174fab9406e9c289f33fd84b"
+"toml","customize","bmm","bmm/ship/bmad-qa-generate-e2e-tests/customize.toml","04a99926b2d79318b927434c7344dc666f143026ed99c7fcc0d6e3d68263ae66"
+"toml","customize","bmm","bmm/ship/bmad-retrospective/customize.toml","ff6fdda35fa4b7d9c2dcb4ffc3e06e56de9a588d4e4e6908379bc16a904d4225"
+"toml","customize","bmm","bmm/v6-shims/bmad-create-architecture/customize.toml","618be49b0286f18dfb4b6bac3d96bf1cf062994fa5278cd327be9898e651b43c"
+"toml","customize","bmm","bmm/v6-shims/bmad-create-prd/customize.toml","0c990af4c0a755402abbef893850bd542744a8b6f36c0587c9f3fb6dab6bf5e7"
+"toml","customize","bmm","bmm/v6-shims/bmad-create-story/customize.toml","1204f6de064436922f2813069778eb4eaa5f1f945aa8ea5a5ffb87897a2ba8fe"
+"toml","customize","bmm","bmm/v6-shims/bmad-dev-story/customize.toml","baba9f07f653063aa94981f1413d5dd4f604931077fbfb04d9c2e397f8d33237"
+"toml","customize","bmm","bmm/v6-shims/bmad-edit-prd/customize.toml","35cc2dfb3eda73a0ae4dc987cac58867b25c43ce5c5a1bf552e215826ede6c22"
+"toml","customize","bmm","bmm/v6-shims/bmad-sprint-status/customize.toml","96261fd227befaa4685b0a5091d3e85299d4ae8e4404176b42f5ef2e2fb501bd"
+"toml","customize","bmm","bmm/v6-shims/bmad-validate-prd/customize.toml","bfb3c8af5b81b2cdb9bb84f844f1b0dafc40d8c283effa6ad48db966b9446cef"
+"yaml","config","bmm","bmm/config.yaml","2f538aabeb6d78ea7dc0cc0d43f1aad5ece108b70e15465220a7c7de4007cf1a"
+"yaml","sprint-status-template","bmm","bmm/plan/bmad-sprint-planning/sprint-status-template.yaml","64b1a937e1fe03b8b8d158e3b1caeb89e7d51692a56c16038e2af091decc553a"
+"yaml","sprint-status-template","bmm","bmm/ship/bmad-retrospective/scripts/tests/fixtures/sprint-status-template.yaml","64b1a937e1fe03b8b8d158e3b1caeb89e7d51692a56c16038e2af091decc553a"
+"toml","config","config.toml","config.toml","75675094e803188d1a297580eb75a529cc3402f0b878d9b0260d398357e3c21f"
+"toml","config.user","config.user.toml","config.user.toml","e710ec2275165cd80616ff41899789eb6677223508d9acfadd89f305cdfda3e2"
+"csv","brain-methods","core","core/bmad-brainstorming/assets/brain-methods.csv","fff112eabca1a9cb8b190f8314bc47678becc5782a2372e11c83daa0e33b6dfd"
+"csv","methods","core","core/bmad-advanced-elicitation/assets/methods.csv","d110ff5f076fb9421552b83692fde2c2d367734049169c7a55f7267a3dc7ef89"
+"csv","module-help","core","core/module-help.csv","3d5feb19c1750d35676530c746a5c71e8959616f3c32fb161847971611d81b6b"
+"html","brain-selector","core","core/bmad-brainstorming/assets/brain-selector.html","c110919a3366bd96061f050f98503e3586185e3d1df5ff8b62a5a046c571a436"
+"json","brain-icons","core","core/bmad-brainstorming/assets/brain-icons.json","a101c56e89f1d0f9e4131dfdfc19e10c746e3a61c3f92537d04a6f4897b7d331"
+"md","academic-lit","core","core/bmad-deep-recon/types/academic-lit.md","514b0b7b1184cb95363dedeb0c2298a9bf5c430c74146fe2114f31780fadb325"
+"md","competitive","core","core/bmad-deep-recon/types/competitive.md","39b53df87d295fdc4388719fcdf31ad2221e64afc136e669207f46d2727a3aec"
+"md","converge","core","core/bmad-brainstorming/references/converge.md","1528c32ddc64f8061fec663306f7208d2fd4d4a90e660552b8138bda7e452dc0"
+"md","create-party","core","core/bmad-party-mode/references/create-party.md","2f810332c36c17d14eb55717aed48f3020acf0713bb9f932479be9fbc3856e9e"
+"md","domain","core","core/bmad-deep-recon/types/domain.md","3a34b2e62c3589f8c8d01158357ee9fba32648c9fdfe70035bb3ca971862896b"
+"md","draft","core","core/bmad-deep-recon/references/draft.md","ac19b33a00ca529c3281df6076f87a833a3b11fc30915ca2c6e7590f7986b90e"
+"md","editorial-common","core","core/bmad-review/references/editorial-common.md","f0cdc72ea345b2c5dc3001477b3dfcc909ca11b78f7db8865b6763d18ffc66c8"
+"md","finalize","core","core/bmad-brainstorming/references/finalize.md","b6074e7fb4d86ffcf899abc50b9049b4a1f6fe550917f4be7a1c7a888477e07e"
+"md","finalize","core","core/bmad-deep-recon/references/finalize.md","d2ba4bee615dfbca6e7725179fb5ebd856dd34a54ba3f306e25255dfd7b1d126"
+"md","headless","core","core/bmad-brainstorming/references/headless.md","b8ea5951199cff7e4813e06aef35683ca0658230fa015e358cacc466b1138a42"
+"md","html-briefing","core","core/bmad-deep-recon/references/html-briefing.md","cd3a88c1a5505fa7f1b715afc3adb34f3d64ade66f4c6b49a59f7e8cfcbe38d4"
+"md","in-chat-techniques","core","core/bmad-brainstorming/references/in-chat-techniques.md","18239464e3e4f00ea9063d015d26d6b0a696b72e7e3c5be92352da6db9a3f244"
+"md","lens-adversarial","core","core/bmad-review/references/lens-adversarial.md","7c5ce97ab2f3ecb96ceb6aa76417f68c1b7df535edd3cc51666d8e1216e6e557"
+"md","lens-edge-case-hunter","core","core/bmad-review/references/lens-edge-case-hunter.md","f2709e3adb40943ea0f19d0797be379caf0875eaef9a55081dc1e170e8288b68"
+"md","lens-prose","core","core/bmad-review/references/lens-prose.md","4cbcb1eaea8567d272f5db7c6cdfd74ed5a8aae6831053cb2f01cbfc2cb98b98"
+"md","lens-structure","core","core/bmad-review/references/lens-structure.md","98c08221f517133e57ef6325013935360c3365ebd7dcb8411b2050d7df507ee3"
+"md","lens-verification-gap","core","core/bmad-review/references/lens-verification-gap.md","e7123d81171eeeee1b3782d13d94c2988969fe357dd71949131a5eb97803e2c6"
+"md","lifecycle","core","core/bmad-deep-recon/references/lifecycle.md","2315fd9cb9223504639616b861ad593bfecb53d605efbd598ae2cf94fb6c4cdf"
+"md","market","core","core/bmad-deep-recon/types/market.md","81ac04499da441857672e29fcd7169436a7e239e67194288ac0d526ec514cb5e"
+"md","mode-agent-team","core","core/bmad-party-mode/references/mode-agent-team.md","def759a17f4bb45463b68fb74c2b828b0a4241720b2b6cc1c9c611a1016ae9d7"
+"md","mode-auto","core","core/bmad-party-mode/references/mode-auto.md","a37fd24f76dfcde385890d5c5947bb6f40ca44bea86c805d267b6ae3aab39f70"
+"md","mode-autonomous","core","core/bmad-brainstorming/references/mode-autonomous.md","d815d2c7f0f8cc0cdfa7c619eaf61f59fd78142f13c69365eda257da38b97bdf"
+"md","mode-facilitator","core","core/bmad-brainstorming/references/mode-facilitator.md","1b908498d285d190859aed00c3ba5b399d7f6aa8e94d54e95456d15cd6fe6073"
+"md","mode-partner","core","core/bmad-brainstorming/references/mode-partner.md","caa0ed378c116def4de382f4e5a95173c6ae6cc5464f1792e7d8196360f79c8a"
+"md","mode-subagent","core","core/bmad-party-mode/references/mode-subagent.md","86161b24a0b13b8f9cb9309042e4249d8caefff8cc33728b084cd2ec22f9d2e1"
+"md","party-memory","core","core/bmad-party-mode/references/party-memory.md","800b4b4b920bb881a7b32aaabca8559a98273799b2476d83a23e290e301fb315"
+"md","process","core","core/bmad-deep-recon/references/process.md","9017d04774807a29103ea97331e555e2793f90098af65752b72f3ee09df85906"
+"md","README","core","core/v6-shims/README.md","017900bb03baeddc0262041a6aa85bce744e8c45991dcde32ef042f9bc2a32b2"
+"md","research.template","core","core/bmad-deep-recon/assets/research.template.md","87d7cfa85fa5036b5a309b7bfb88f7934f50bb81f3cff02d2b49b4c7345cfc38"
+"md","resume","core","core/bmad-brainstorming/references/resume.md","0f79535d72eefe6c55bd5ae47fe4753de8d27235cf129f10b2c596a124c26526"
+"md","run","core","core/bmad-deep-recon/references/run.md","8e259dc88820ac989c79620af5c37e24f00df21ac4af308ce3563c0e66c9406c"
+"md","selection","core","core/bmad-deep-recon/references/selection.md","2b488c08f9550afe7fda32c2dc5d4591927afd7b9ad507fcce0ae8593c4b9d31"
+"md","SKILL","core","core/bmad-advanced-elicitation/SKILL.md","23a1f2903f6a19255e3ceae798afe48f6394694769b3b034502d174d683612b2"
+"md","SKILL","core","core/bmad-brainstorming/SKILL.md","e9cb07fe86aa254f9fb7217720d77fd693bf66a0c01af8114ecdf7148159fdd1"
+"md","SKILL","core","core/bmad-customize/SKILL.md","a42086f90024013e2611503eb0224ac0e90b2aecac44a886ae0e38cfdda69511"
+"md","SKILL","core","core/bmad-deep-recon/SKILL.md","dce5f7db03094a617cc3fcae1711b1dc7ccebe379376e67216544956d375f0d2"
+"md","SKILL","core","core/bmad-forge-idea/SKILL.md","a838096deb871b3482dffe6163be16104f7911698b25af5617751655fd3295c9"
+"md","SKILL","core","core/bmad-help/SKILL.md","68a19089a0073b299c705e9afaa8d18183e78f88a185a68e9efba2e14062effc"
+"md","SKILL","core","core/bmad-party-mode/SKILL.md","de035b4e081fdd626a20114178f706ac222f519171d82b02139a7cec561a3487"
+"md","SKILL","core","core/bmad-review/SKILL.md","144e6c46d9157f7a88722c56139cd78c12903b1283ed84dd9c2b1f5dfa7673c1"
+"md","SKILL","core","core/v6-shims/bmad-editorial-review/SKILL.md","3b939876b4977bec7f2d3ee33a8871b266f25efc72768d72868ac26ff9158cd2"
+"md","SKILL","core","core/v6-shims/bmad-editorial-review-prose/SKILL.md","153e7b0a240c3f5e49d6128ff1797aabc368618611d895f7f152e73fbcb12fab"
+"md","SKILL","core","core/v6-shims/bmad-editorial-review-structure/SKILL.md","5e45da216b00aad3955a7196df6cb8e52167f441d2dcd7c064983881691bf1e8"
+"md","SKILL","core","core/v6-shims/bmad-review-adversarial-general/SKILL.md","ca1d05a05eb41ec446abd862e9afe4a88b9188a3bb93bc3e70ca68ecb8740619"
+"md","SKILL","core","core/v6-shims/bmad-review-edge-case-hunter/SKILL.md","f9db1d7f58c5e3f7586c10c920d4dd9d6c6d6e2dff5cd49110ec1edb387937a1"
+"md","SKILL","core","core/v6-shims/bmad-review-verification-gap/SKILL.md","4ee67cc3d7355ba05d195797cb2d57d45f9046ee31781f2d133ff3484cfb53ae"
+"md","structure-models","core","core/bmad-review/references/structure-models.md","f84f85070e1af75f2482757aba9d37d69d805a20826d185527e598f2ba6b9292"
+"md","synthesis","core","core/bmad-deep-recon/references/synthesis.md","4d9ef1247ab45241f919010e94c99699abc0a6e18b5bd68fa93ae54afe59d172"
+"md","technical","core","core/bmad-deep-recon/types/technical.md","55f71428c70547b89d67ef0c6cdad59caeb0ee21082cd1230c05618ba8d04707"
+"md","user-voice","core","core/bmad-deep-recon/types/user-voice.md","1831ce46e53e8c68244d28e336c5ef9e53e64f21a00b74a817b9b2924c1e8e72"
+"md","verification","core","core/bmad-deep-recon/references/verification.md","0393ded4828fec69a4819d7236827910d641d09c3b61144c0211a9a78776fdd2"
+"py","brain","core","core/bmad-brainstorming/scripts/brain.py","1c75c667fc70a85055dd19d77fb21478e190874e4a61d070c3b0971dd1bd25cc"
+"py","list_customizable_skills","core","core/bmad-customize/scripts/list_customizable_skills.py","8787f542930b927789e7fdf12bc5a67ff08e19865903a5ad05ff2cc8fc426b66"
+"py","pick_methods","core","core/bmad-advanced-elicitation/scripts/pick_methods.py","60020ec4767894ea3d8707c4b61e78b679d434315be1dd29154bf64d88126fff"
+"py","recon_kit","core","core/bmad-deep-recon/scripts/recon_kit.py","8cb5187b5114b779532907383a013d40fdea1022bb9bed9a23bd8d0fdfa79e8c"
+"py","resolve_party","core","core/bmad-party-mode/scripts/resolve_party.py","0bed5ad2139f4412699c07d571c218470901b901ca4a72b441ec9308dbc8ce74"
+"py","resolve_personas","core","core/bmad-forge-idea/scripts/resolve_personas.py","b3e5f2f38de013ad878d8ac9c1d4e77d555c2d665dd6c0bc16f9f567d2bbd30c"
+"py","test_brain","core","core/bmad-brainstorming/scripts/tests/test_brain.py","021c0b9fae8db859725312d50d8b304fff00ee7acc310699c35523e86bffbdd8"
+"py","test_list_customizable_skills","core","core/bmad-customize/scripts/tests/test_list_customizable_skills.py","24c3d384b3b5d490b7335c17866bfe0425af253ce669c32382fa88feb705934d"
+"py","test_pick_methods","core","core/bmad-advanced-elicitation/scripts/tests/test_pick_methods.py","610099d8494529f9203d7262567810b500552bcef006b3b6388d58da3da71978"
+"py","test_recon_kit","core","core/bmad-deep-recon/scripts/tests/test_recon_kit.py","1b4ddf482dd2d11a214ee2f821c35d7a8c41905b5d8d9cc69a293304bb8a1665"
+"py","test_resolve_party","core","core/bmad-party-mode/scripts/tests/test_resolve_party.py","bb53fe03ec3013ed96c0fb399c1948f28bcf55cb2d7727fe0189343fcaa667d5"
+"py","test_resolve_personas","core","core/bmad-forge-idea/scripts/tests/test_resolve_personas.py","1c4fa4b1d68bfbd10e4b38cad3c8286dad62345cebd08fe94a6862351b02855e"
+"py","test_word_metrics","core","core/bmad-review/scripts/tests/test_word_metrics.py","3b5a285d3c9f611b3cda8c9c1d52d6b214c1f72e6e64a94ea5b0e220db5a8765"
+"py","word_metrics","core","core/bmad-review/scripts/word_metrics.py","fb45007a7f3cfc18d13ee8bd4787facdaae297570193bc769456297dd33da78b"
+"toml","customize","core","core/bmad-advanced-elicitation/customize.toml","735a276edd51786ccfd2c3417d9a2b9dee4244a6102698981b3888f68d979ed9"
+"toml","customize","core","core/bmad-brainstorming/customize.toml","21fcbc60c78db99ca0424da192ba0942dce2189f350f77838e4d3ecd501edd1c"
+"toml","customize","core","core/bmad-deep-recon/customize.toml","24d1383066034fd4fcf282279aaf0d29d21910fd1247dfe3dbad74a70e78814d"
+"toml","customize","core","core/bmad-forge-idea/customize.toml","ef5fadd1df3550cae00b1b442606bf84d187bfd55397563f143e1057430df45c"
+"toml","customize","core","core/bmad-party-mode/customize.toml","9c6ee33cd7fdd80e4adf514c3d54636d933d5250c2ddd78041c6cfe73b745bb0"
+"toml","customize","core","core/bmad-review/customize.toml","38470c888a809ee030dc11d38868bb1ac5c1d547f06d218b711be5df53385c00"
+"toml","customize","core","core/v6-shims/bmad-editorial-review/customize.toml","a5c5fed539e6543121e57cc29bb65559bb6391efc806bf8759c8e29697a94a34"
+"yaml","config","core","core/config.yaml","ebcfa97b8bf21a76d29993cc52c2f4f5508753b6119b873ce7a4bad1e9df2af5"
+"file",".gitignore","custom","custom/.gitignore","973b03a33f142c22cf9b65be285bebadd85790b6b55be04637d2f8c716f58fab"
+"file",".gitignore","render","render/.gitignore","240a3e0d37d2e86b614063f5347eb02d4f99ca6c254de6b82871ff8d95532a7d"
+"py","config_utils","scripts","scripts/config_utils.py","48afe2bc18a29201e343cce3703be1e70df9c83ee74eeb68e57ef8ef42e8c651"
+"py","memlog","scripts","scripts/memlog.py","3b00f82ca33dc4227f715123b939514ee35c4f9c71150c894c3d8185df1b48df"
+"py","render_skill","scripts","scripts/render_skill.py","8496d0d8b449d64c21b42a9aab3b13fc8a813a430c0695ffd84ad75bb1da7942"
+"py","resolve_config","scripts","scripts/resolve_config.py","fc78866fd42862d486d4346d2b35705f916a19e6c07bb474f8add25c71734a8e"
+"py","resolve_customization","scripts","scripts/resolve_customization.py","9b5124e0b781823a015a19d6cf5db52bbc34b6bab41c036fd1b3d464c2a137cd"
diff --git a/_bmad/_config/manifest.yaml b/_bmad/_config/manifest.yaml
new file mode 100644
index 0000000..5510015
--- /dev/null
+++ b/_bmad/_config/manifest.yaml
@@ -0,0 +1,21 @@
+installation:
+  version: 6.11.0
+  installDate: 2026-08-14T15:07:31.092Z
+  lastUpdated: 2026-08-14T15:07:31.092Z
+modules:
+  - name: core
+    version: 6.11.0
+    installDate: 2026-08-14T15:07:31.003Z
+    lastUpdated: 2026-08-14T15:07:31.092Z
+    source: built-in
+    npmPackage: null
+    repoUrl: null
+  - name: bmm
+    version: 6.11.0
+    installDate: 2026-08-14T15:07:31.069Z
+    lastUpdated: 2026-08-14T15:07:31.092Z
+    source: built-in
+    npmPackage: null
+    repoUrl: null
+ides:
+  - claude-code
diff --git a/_bmad/_config/skill-manifest.csv b/_bmad/_config/skill-manifest.csv
new file mode 100644
index 0000000..d708ea9
--- /dev/null
+++ b/_bmad/_config/skill-manifest.csv
@@ -0,0 +1,50 @@
+canonicalId,name,description,module,path
+"bmad-advanced-elicitation","bmad-advanced-elicitation","Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.","core","_bmad/core/bmad-advanced-elicitation/SKILL.md"
+"bmad-brainstorming","bmad-brainstorming","Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.","core","_bmad/core/bmad-brainstorming/SKILL.md"
+"bmad-customize","bmad-customize","Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'.","core","_bmad/core/bmad-customize/SKILL.md"
+"bmad-deep-recon","bmad-deep-recon","Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here through web fan-out. Shipped type packs: market, domain, technical, competitive, user-voice, academic-lit — plus a select shape for choose-between decisions and custom types via overrides. Use when the user says ""deep recon"", ""research this"", ""draft a research prompt"", ""process this research report"", ""market research"", ""domain research"", ""technical research"", ""competitor research"", ""literature review"", or ""help me choose between"".","core","_bmad/core/bmad-deep-recon/SKILL.md"
+"bmad-forge-idea","bmad-forge-idea","Pressure-test an idea through persona-driven interrogation until it hardens, proves out, or dies cheaply. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'.","core","_bmad/core/bmad-forge-idea/SKILL.md"
+"bmad-help","bmad-help","Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.","core","_bmad/core/bmad-help/SKILL.md"
+"bmad-party-mode","bmad-party-mode","Orchestrates lively group discussions between installed BMAD agents or custom personas, and helps author custom parties. Use when the user requests party mode, a roundtable, or multiple agent perspectives — or wants to create/configure a party, define personas, or build an AI focus-group panel.","core","_bmad/core/bmad-party-mode/SKILL.md"
+"bmad-review","bmad-review","Multi-lens review over any diff, doc, spec, or artifact — whichever installed lenses fit the content, run singly or together. Shipped lenses include adversarial, edge-case, verification-gap, structure, and prose. Use when the user says ""review this"", ""critical review"", ""editorial review"", ""hunt edge cases"", ""review the structure"", or ""review the prose"".","core","_bmad/core/bmad-review/SKILL.md"
+"bmad-editorial-review","bmad-editorial-review","Deprecated — forwards to bmad-review.","core","_bmad/core/v6-shims/bmad-editorial-review/SKILL.md"
+"bmad-editorial-review-prose","bmad-editorial-review-prose","Deprecated — forwards to bmad-review.","core","_bmad/core/v6-shims/bmad-editorial-review-prose/SKILL.md"
+"bmad-editorial-review-structure","bmad-editorial-review-structure","Deprecated — forwards to bmad-review.","core","_bmad/core/v6-shims/bmad-editorial-review-structure/SKILL.md"
+"bmad-review-adversarial-general","bmad-review-adversarial-general","Deprecated — forwards to bmad-review.","core","_bmad/core/v6-shims/bmad-review-adversarial-general/SKILL.md"
+"bmad-review-edge-case-hunter","bmad-review-edge-case-hunter","Deprecated — forwards to bmad-review.","core","_bmad/core/v6-shims/bmad-review-edge-case-hunter/SKILL.md"
+"bmad-review-verification-gap","bmad-review-verification-gap","Deprecated — forwards to bmad-review.","core","_bmad/core/v6-shims/bmad-review-verification-gap/SKILL.md"
+"bmad-agent-analyst","bmad-agent-analyst","Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.","bmm","_bmad/bmm/agents/bmad-agent-analyst/SKILL.md"
+"bmad-agent-architect","bmad-agent-architect","System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.","bmm","_bmad/bmm/agents/bmad-agent-architect/SKILL.md"
+"bmad-agent-dev","bmad-agent-dev","Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.","bmm","_bmad/bmm/agents/bmad-agent-dev/SKILL.md"
+"bmad-agent-pm","bmad-agent-pm","Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.","bmm","_bmad/bmm/agents/bmad-agent-pm/SKILL.md"
+"bmad-agent-ux-designer","bmad-agent-ux-designer","UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.","bmm","_bmad/bmm/agents/bmad-agent-ux-designer/SKILL.md"
+"bmad-architecture","bmad-architecture","Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says ""create the architecture"", ""create technical architecture"", ""architecture spine"", or ""create a solution design"".","bmm","_bmad/bmm/plan/bmad-architecture/SKILL.md"
+"bmad-create-epics-and-stories","bmad-create-epics-and-stories","Break requirements into epics and user stories. Use when the user says ""create the epics and stories list""","bmm","_bmad/bmm/plan/bmad-create-epics-and-stories/SKILL.md"
+"bmad-generate-project-context","bmad-generate-project-context","Deprecated — forwards to bmad-project-context. Use when the user says ""generate project context"" or ""create project context""","bmm","_bmad/bmm/plan/bmad-generate-project-context/SKILL.md"
+"bmad-prd","bmad-prd","Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.","bmm","_bmad/bmm/plan/bmad-prd/SKILL.md"
+"bmad-prfaq","bmad-prfaq","Working Backwards PRFAQ challenge that stress-tests a product concept customer-first. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.","bmm","_bmad/bmm/plan/bmad-prfaq/SKILL.md"
+"bmad-product-brief","bmad-product-brief","Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.","bmm","_bmad/bmm/plan/bmad-product-brief/SKILL.md"
+"bmad-project-context","bmad-project-context","Set up, refresh, or audit a repository's agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfall lines. Must be invoked by name.","bmm","_bmad/bmm/plan/bmad-project-context/SKILL.md"
+"bmad-spec","bmad-spec","Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says ""create a spec"", ""distill this into a spec"", ""validate this spec"", ""update the spec"", or ""break this into stories"".","bmm","_bmad/bmm/plan/bmad-spec/SKILL.md"
+"bmad-sprint-planning","bmad-sprint-planning","Gate planning readiness, generate sprint status tracking from epics, summarize sprint progress, and validate or repair the tracking file. Use when the user says ""run sprint planning"", ""generate sprint plan"", ""check implementation readiness"", ""show sprint status"", ""validate sprint status"", or ""fix sprint status""","bmm","_bmad/bmm/plan/bmad-sprint-planning/SKILL.md"
+"bmad-ux","bmad-ux","Plan UX patterns and design specifications. Use when the user says ""lets create UX design"" or ""create UX specifications"" or ""help me plan the UX""","bmm","_bmad/bmm/plan/bmad-ux/SKILL.md"
+"bmad-build","bmad-build","Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.","bmm","_bmad/bmm/ship/bmad-build/SKILL.md"
+"bmad-build-auto","bmad-build-auto","One iteration of an unattended development loop. Use when invoked by name.","bmm","_bmad/bmm/ship/bmad-build-auto/SKILL.md"
+"bmad-checkpoint-preview","bmad-checkpoint-preview","LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says ""checkpoint"", ""human review"", or ""walk me through this change"".","bmm","_bmad/bmm/ship/bmad-checkpoint-preview/SKILL.md"
+"bmad-code-review","bmad-code-review","Adversarial code review using parallel review layers and structured triage. Use when the user says ""run code review"" or ""review this code""","bmm","_bmad/bmm/ship/bmad-code-review/SKILL.md"
+"bmad-correct-course","bmad-correct-course","Manage significant changes during sprint execution. Use when the user says ""correct course"" or ""propose sprint change""","bmm","_bmad/bmm/ship/bmad-correct-course/SKILL.md"
+"bmad-qa-generate-e2e-tests","bmad-qa-generate-e2e-tests","Generate end to end automated tests for existing features. Use when the user says ""create qa automated tests for [feature]""","bmm","_bmad/bmm/ship/bmad-qa-generate-e2e-tests/SKILL.md"
+"bmad-retrospective","bmad-retrospective","Evidence-based epic retrospective — collect what the epic produced, verify findings against sources, render an acceptance verdict. Use when the user says ""run a retrospective"" or ""lets retro the epic [epic]"". Supports -H/--headless.","bmm","_bmad/bmm/ship/bmad-retrospective/SKILL.md"
+"bmad-create-architecture","bmad-create-architecture","Deprecated — forwards to bmad-architecture (create intent).","bmm","_bmad/bmm/v6-shims/bmad-create-architecture/SKILL.md"
+"bmad-create-prd","bmad-create-prd","Deprecated — forwards to bmad-prd (create intent).","bmm","_bmad/bmm/v6-shims/bmad-create-prd/SKILL.md"
+"bmad-create-story","bmad-create-story","Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name.","bmm","_bmad/bmm/v6-shims/bmad-create-story/SKILL.md"
+"bmad-dev-auto","bmad-dev-auto","Deprecated: forwards to bmad-build-auto. Do not use unless invoked by name.","bmm","_bmad/bmm/v6-shims/bmad-dev-auto/SKILL.md"
+"bmad-dev-story","bmad-dev-story","Deprecated: `bmad-build` is now the official implementation method. Only use this when explicitly invoked by name.","bmm","_bmad/bmm/v6-shims/bmad-dev-story/SKILL.md"
+"bmad-document-project","bmad-document-project","Deprecated — forwards to bmad-project-context. Use when the user says ""document this project"" or ""generate project docs""","bmm","_bmad/bmm/v6-shims/bmad-document-project/SKILL.md"
+"bmad-domain-research","bmad-domain-research","Deprecated — forwards to bmad-deep-recon (domain type).","bmm","_bmad/bmm/v6-shims/bmad-domain-research/SKILL.md"
+"bmad-edit-prd","bmad-edit-prd","Deprecated — forwards to bmad-prd (update intent).","bmm","_bmad/bmm/v6-shims/bmad-edit-prd/SKILL.md"
+"bmad-market-research","bmad-market-research","Deprecated — forwards to bmad-deep-recon (market type).","bmm","_bmad/bmm/v6-shims/bmad-market-research/SKILL.md"
+"bmad-quick-dev","bmad-quick-dev","Deprecated: forwards to bmad-build. Do not use unless invoked by name.","bmm","_bmad/bmm/v6-shims/bmad-quick-dev/SKILL.md"
+"bmad-sprint-status","bmad-sprint-status","Deprecated — forwards to bmad-sprint-planning (status view).","bmm","_bmad/bmm/v6-shims/bmad-sprint-status/SKILL.md"
+"bmad-technical-research","bmad-technical-research","Deprecated — forwards to bmad-deep-recon (technical type).","bmm","_bmad/bmm/v6-shims/bmad-technical-research/SKILL.md"
+"bmad-validate-prd","bmad-validate-prd","Deprecated — forwards to bmad-prd (validate intent).","bmm","_bmad/bmm/v6-shims/bmad-validate-prd/SKILL.md"
diff --git a/_bmad/bmm/config.yaml b/_bmad/bmm/config.yaml
new file mode 100644
index 0000000..22682ca
--- /dev/null
+++ b/_bmad/bmm/config.yaml
@@ -0,0 +1,16 @@
+# BMM Module Configuration
+# Generated by BMAD installer
+# Version: 6.11.0
+# Date: 2026-08-14T15:07:31.074Z
+
+user_skill_level: intermediate
+planning_artifacts: "{project-root}/_bmad-output/planning-artifacts"
+implementation_artifacts: "{project-root}/_bmad-output/implementation-artifacts"
+project_knowledge: "{project-root}/docs"
+
+# Core Configuration Values
+user_name: ProMods
+project_name: wow20
+communication_language: Deutsch
+document_output_language: Deutsch
+output_folder: "{project-root}/_bmad-output"
diff --git a/_bmad/bmm/module-help.csv b/_bmad/bmm/module-help.csv
new file mode 100644
index 0000000..f3abac0
--- /dev/null
+++ b/_bmad/bmm/module-help.csv
@@ -0,0 +1,19 @@
+module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
+BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
+BMad Method,bmad-project-context,Project Context,PC,"Set up or refresh a repo's agent instructions so AI agents work well in it: verified commands, policy, conventions that differ from defaults, and known pitfalls. Setup, refresh, record, and audit — replaces document-project and generate-project-context.",,,anytime,,,false,repo root,AGENTS.md managed block
+BMad Method,bmad-build,Build,BD,Official Phase 4 implementation loop: clarify intent plan implement review and present.,,,ship,bmad-sprint-planning,bmad-code-review,true,implementation_artifacts,spec and project implementation
+BMad Method,bmad-spec,Spec,SPC,"Use to distill any intent input (brief, PRD, transcript, brain dump, design folder, mixed multi-source) into a succinct, no-fluff SPEC.md contract + companions that downstream work derives from. Locks the WHAT before the HOW. Works for software, game design, research, editorial, policy, business, anything intent-bearing. Validation mode also available.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files
+BMad Method,bmad-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal
+BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,plan,,,false,{output_folder}/brainstorming,brainstorming session
+BMad Method,bmad-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,plan,,,false,planning_artifacts,product brief
+BMad Method,bmad-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,plan,,,false,planning_artifacts,prfaq document
+BMad Method,bmad-prd,Create Edit and Review PRD,PRD,"Facilitated PRD workflow — create a new PRD via coached discovery, update an existing one against a change signal, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,bmad-product-brief,,true,planning_artifacts,prd
+BMad Method,bmad-ux,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,,2-planning,bmad-prd,,false,planning_artifacts,ux design
+BMad Method,bmad-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,plan,,,true,planning_artifacts,architecture
+BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,,plan,bmad-architecture,,true,planning_artifacts,epics and stories
+BMad Method,bmad-sprint-planning,Sprint Planning,SP,Readiness gate then tracking: verifies the planning is implementable (PASS/CONCERNS/FAIL) and produces the sprint status the implementation agents follow for every story.,,,plan,,,true,implementation_artifacts,sprint status
+BMad Method,bmad-sprint-planning,Sprint Status,SS,Anytime: summarize sprint status with risks open action items and the next recommended action; can also validate or repair the tracking file.,status,,anytime,,,false,,status summary
+BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. Optional extra layer after Build's built-in review.,,,ship,bmad-build,,false,,
+BMad Method,bmad-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,ship,,,false,,
+BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,ship,bmad-build,,false,implementation_artifacts,test suite
+BMad Method,bmad-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,ship,bmad-code-review,,false,implementation_artifacts,retrospective
diff --git a/_bmad/bmm/v6-shims/README.md b/_bmad/bmm/v6-shims/README.md
new file mode 100644
index 0000000..781d86e
--- /dev/null
+++ b/_bmad/bmm/v6-shims/README.md
@@ -0,0 +1,28 @@
+# v6 Deprecation Shims
+
+Skills in this folder are deprecated skills kept for backward compatibility with v6 skill IDs.
+Some retain their full workflow, while others forward to the skill that replaced them, passing a
+stated intent and pre-resolved customization fields so the target skips its own intent inference.
+
+| Shim                       | Forwards to                          |
+| -------------------------- | ------------------------------------ |
+| `bmad-quick-dev`           | `bmad-build`                         |
+| `bmad-dev-auto`            | `bmad-build-auto`                    |
+| `bmad-create-story`        | Retained in full                     |
+| `bmad-dev-story`           | Retained in full                     |
+| `bmad-create-prd`          | `bmad-prd` (create intent)           |
+| `bmad-edit-prd`            | `bmad-prd` (update intent)           |
+| `bmad-validate-prd`        | `bmad-prd` (validate intent)         |
+| `bmad-create-architecture` | `bmad-architecture` (create intent)  |
+| `bmad-market-research`     | `bmad-deep-recon` (market type)      |
+| `bmad-domain-research`     | `bmad-deep-recon` (domain type)      |
+| `bmad-technical-research`  | `bmad-deep-recon` (technical type)   |
+| `bmad-sprint-status`       | `bmad-sprint-planning` (status view) |
+
+Enterprise users may still depend on these IDs, so they ship by default. Removal rides the
+v7 cut — never a 6.x minor.
+
+The folder is grouping only: the installer discovers skills recursively and installs each
+one under its own `name`, so nesting here does not change any installed path or skill ID.
+A future install option will let users include or exclude this folder before it is removed
+outright.
diff --git a/_bmad/config.toml b/_bmad/config.toml
new file mode 100644
index 0000000..53f7468
--- /dev/null
+++ b/_bmad/config.toml
@@ -0,0 +1,61 @@
+# ─────────────────────────────────────────────────────────────────
+# Installer-managed. Regenerated on every install — treat as read-only.
+#
+# Direct edits to this file will be overwritten on the next install.
+# To change an install answer durably, re-run the installer (your prior
+# answers are remembered as defaults). To pin a value regardless of
+# install answers, or to add custom agents / override descriptors, use:
+#   _bmad/custom/config.toml       (team, committed)
+#   _bmad/custom/config.user.toml  (personal, gitignored)
+# Those files are never touched by the installer.
+# ─────────────────────────────────────────────────────────────────
+
+[core]
+project_name = "wow20"
+document_output_language = "Deutsch"
+output_folder = "{project-root}/_bmad-output"
+
+[modules.bmm]
+planning_artifacts = "{project-root}/_bmad-output/planning-artifacts"
+implementation_artifacts = "{project-root}/_bmad-output/implementation-artifacts"
+project_knowledge = "{project-root}/docs"
+
+[agents.bmad-agent-analyst]
+module = "bmm"
+team = "software-development"
+name = "Mary"
+title = "Business Analyst"
+icon = "📊"
+description = "Channels Porter's strategic rigor and Minto's Pyramid Principle, grounds every finding in verifiable evidence, represents every stakeholder voice. Speaks like a treasure hunter narrating the find: thrilled by every clue, precise once the pattern emerges."
+
+[agents.bmad-agent-pm]
+module = "bmm"
+team = "software-development"
+name = "John"
+title = "Product Manager"
+icon = "📋"
+description = "Drives Jobs-to-be-Done over template filling, user value first, technical feasibility is a constraint not the driver. Speaks like a detective interrogating a cold case: short questions, sharper follow-ups, every 'why?' tightening the net."
+
+[agents.bmad-agent-ux-designer]
+module = "bmm"
+team = "software-development"
+name = "Sally"
+title = "UX Designer"
+icon = "🎨"
+description = "Balances empathy with edge-case rigor, starts simple and evolves through feedback, every decision serves a genuine user need. Speaks like a filmmaker pitching the scene before the code exists, painting user stories that make you feel the problem."
+
+[agents.bmad-agent-architect]
+module = "bmm"
+team = "software-development"
+name = "Winston"
+title = "System Architect"
+icon = "🏗️"
+description = "Favors boring technology for stability, developer productivity as architecture, ties every decision to business value. Speaks like a seasoned engineer at the whiteboard: measured, always laying out trade-offs rather than verdicts."
+
+[agents.bmad-agent-dev]
+module = "bmm"
+team = "software-development"
+name = "Amelia"
+title = "Senior Software Engineer"
+icon = "💻"
+description = "Test-first discipline (red, green, refactor), 100% pass before review, no fluff all precision. Speaks like a terminal prompt: exact file paths, AC IDs, and commit-message brevity — every statement citable."
diff --git a/_bmad/config.user.toml b/_bmad/config.user.toml
new file mode 100644
index 0000000..ab0e195
--- /dev/null
+++ b/_bmad/config.user.toml
@@ -0,0 +1,17 @@
+# ─────────────────────────────────────────────────────────────────
+# Installer-managed. Regenerated on every install — treat as read-only.
+# Holds install answers scoped to YOU personally.
+#
+# Direct edits to this file will be overwritten on the next install.
+# To change an answer durably, re-run the installer (your prior answers
+# are remembered as defaults). For pinned overrides or custom sections
+# the installer does not know about, use _bmad/custom/config.user.toml
+# — it is never touched by the installer.
+# ─────────────────────────────────────────────────────────────────
+
+[core]
+user_name = "ProMods"
+communication_language = "Deutsch"
+
+[modules.bmm]
+user_skill_level = "intermediate"
diff --git a/_bmad/core/config.yaml b/_bmad/core/config.yaml
new file mode 100644
index 0000000..3bfc808
--- /dev/null
+++ b/_bmad/core/config.yaml
@@ -0,0 +1,10 @@
+# CORE Module Configuration
+# Generated by BMAD installer
+# Version: 6.11.0
+# Date: 2026-08-14T15:07:31.074Z
+
+user_name: ProMods
+project_name: wow20
+communication_language: Deutsch
+document_output_language: Deutsch
+output_folder: "{project-root}/_bmad-output"
diff --git a/_bmad/core/module-help.csv b/_bmad/core/module-help.csv
new file mode 100644
index 0000000..25b47fc
--- /dev/null
+++ b/_bmad/core/module-help.csv
@@ -0,0 +1,10 @@
+module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
+Core,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
+Core,bmad-brainstorming,Brainstorming,BSP,Use early in ideation or when stuck generating ideas.,,,anytime,,,false,{output_folder}/brainstorming,brainstorming session
+Core,bmad-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you need multiple perspectives or want agents to collaborate.,,,anytime,,,false,,
+Core,bmad-help,BMad Help,BH,,,,anytime,,,false,,
+Core,bmad-customize,BMad Customize,BC,"Use when you want to change how an agent or workflow behaves — add persistent facts, swap templates, insert activation hooks, or customize menus. Scans what's customizable, picks the right scope (agent vs workflow), writes the override to _bmad/custom/, and verifies the merge. No TOML hand-authoring required.",,,anytime,,,false,{project-root}/_bmad/custom,TOML override files
+Core,bmad-advanced-elicitation,Advanced Elicitation,AE,"Use at any checkpoint to push a just-produced draft, section, or plan past its first version — pick from a menu of elicitation methods (pre-mortem, first principles, red team, socratic) and apply the improvements.",,,anytime,,,false,,
+Core,bmad-review,Review,RV,"Use to review anything before it ships — a diff, branch, or uncommitted changes; a PRD, spec, story, or architecture doc; any prose document. Runs whichever installed lenses fit the content and reports findings in one shape: shipped lenses cover adversarial critique, edge cases, verification gaps, document structure (cuts, merges, moves), and prose copy-edit, and installs may add more. Reach for it to tighten a bloated or LLM-slop draft, pressure-test a plan before building, or check a change is adequately tested. Run every applicable lens or name the ones you want. Code Review in other modules calls it automatically.",,[path],anytime,,,false,,findings JSON array + markdown report
+Core,bmad-forge-idea,Forge Idea,FI,"Use to pressure-test and harden an idea — software, business, creative, research, or life — until it proves out, hardens into something buildable, or dies cheaply. Persona-driven interrogation; optional handoff to bmad-spec or bmad-build.",,,anytime,,,false,{output_folder}/forge,refined-idea brief (optional)
+Core,bmad-deep-recon,Deep Recon,RS,Decision-grade research three ways: draft a deep-research prompt for your own AI tool then process the returned report into a downstream-ready cited summary — or run the research directly via web fan-out. Types: market domain technical competitive user-voice academic-lit plus a select shape for choose-between decisions; claim verification and refresh lifecycle. Custom types via overrides.,,[type],anytime,,,false,{planning_artifacts}/research,research report/summary + optional html briefing
diff --git a/_bmad/core/v6-shims/README.md b/_bmad/core/v6-shims/README.md
new file mode 100644
index 0000000..865f8e5
--- /dev/null
+++ b/_bmad/core/v6-shims/README.md
@@ -0,0 +1,25 @@
+# v6 Deprecation Shims
+
+Skills in this folder are forwarders kept for backward compatibility with v6 skill IDs.
+Each one holds no logic of its own — it forwards to the skill that replaced it, pinning
+the legacy output contract so existing callers keep working.
+
+| Shim                              | Forwards to                              |
+| --------------------------------- | ---------------------------------------- |
+| `bmad-editorial-review`           | `bmad-review` (structure + prose lenses) |
+| `bmad-editorial-review-prose`     | `bmad-review` (prose lens)               |
+| `bmad-editorial-review-structure` | `bmad-review` (structure lens)           |
+| `bmad-review-adversarial-general` | `bmad-review` (adversarial lens)         |
+| `bmad-review-edge-case-hunter`    | `bmad-review` (edge-case lens)           |
+| `bmad-review-verification-gap`    | `bmad-review` (verification-gap lens)    |
+
+`bmad-editorial-review` keeps its `customize.toml` so existing team and user
+overrides still resolve; the shim forwards those resolved values to `bmad-review`.
+
+External module repos (gds, loop, tea, bmb, os-utils) still invoke these IDs, so they
+ship by default. Removal rides the v7 cut — never a 6.x minor.
+
+The folder is grouping only: the installer discovers skills recursively and installs each
+one under its own `name`, so nesting here does not change any installed path or skill ID.
+A future install option will let users include or exclude this folder before it is removed
+outright.
diff --git a/_bmad/custom/.gitignore b/_bmad/custom/.gitignore
new file mode 100644
index 0000000..42d7bc6
--- /dev/null
+++ b/_bmad/custom/.gitignore
@@ -0,0 +1 @@
+*.user.toml
diff --git a/_bmad/custom/config.toml b/_bmad/custom/config.toml
new file mode 100644
index 0000000..4c3a857
--- /dev/null
+++ b/_bmad/custom/config.toml
@@ -0,0 +1,7 @@
+# Team / enterprise overrides for _bmad/config.toml.
+# Committed to the repo — applies to every developer on the project.
+# Tables deep-merge over base config; keyed entries merge by key.
+# Example: override an agent descriptor, or add a new agent.
+#
+# [agents.bmad-agent-pm]
+# description = "Prefers short, bulleted PRDs over narrative drafts."
diff --git a/_bmad/render/.gitignore b/_bmad/render/.gitignore
new file mode 100644
index 0000000..d6b7ef3
--- /dev/null
+++ b/_bmad/render/.gitignore
@@ -0,0 +1,2 @@
+*
+!.gitignore
diff --git a/_bmad/scripts/config_utils.py b/_bmad/scripts/config_utils.py
new file mode 100644
index 0000000..df6bb07
--- /dev/null
+++ b/_bmad/scripts/config_utils.py
@@ -0,0 +1,119 @@
+"""Shared strict TOML loading and structural merge support."""
+
+from __future__ import annotations
+
+import tomllib
+from pathlib import Path
+from typing import Any, Iterable
+
+
+class ConfigError(ValueError):
+    """Raised when a present configuration layer cannot be used safely."""
+
+
+_KEYED_MERGE_FIELDS = ("code", "id")
+
+
+def load_toml(path: Path, *, required: bool = False) -> dict[str, Any]:
+    """Load a TOML table, allowing absence only for optional layers."""
+    if not path.exists():
+        if required:
+            raise ConfigError(f"required TOML file not found: {path}")
+        return {}
+    if not path.is_file():
+        raise ConfigError(f"TOML layer is not a file: {path}")
+    try:
+        with path.open("rb") as stream:
+            parsed = tomllib.load(stream)
+    except tomllib.TOMLDecodeError as error:
+        raise ConfigError(f"failed to parse {path}: {error}") from error
+    except OSError as error:
+        raise ConfigError(f"failed to read {path}: {error}") from error
+    if not isinstance(parsed, dict):
+        raise ConfigError(f"TOML layer did not parse to a table: {path}")
+    return parsed
+
+
+def _detect_keyed_merge_field(items: list[Any]) -> str | None:
+    if not items or not all(isinstance(item, dict) for item in items):
+        return None
+    for candidate in _KEYED_MERGE_FIELDS:
+        if all(candidate in item for item in items):
+            for item in items:
+                value = item[candidate]
+                if not isinstance(value, str):
+                    raise ConfigError(
+                        f"keyed array identifier `{candidate}` must be a string, "
+                        f"got {type(value).__name__}"
+                    )
+                if not value:
+                    raise ConfigError(
+                        f"keyed array identifier `{candidate}` must not be empty"
+                    )
+            return candidate
+    return None
+
+
+def _merge_arrays(base: list[Any], override: list[Any]) -> list[Any]:
+    keyed_field = _detect_keyed_merge_field(base + override)
+    if keyed_field is None:
+        return list(base) + list(override)
+
+    result: list[Any] = []
+    index_by_key: dict[str, int] = {}
+    for item in base:
+        copied = dict(item)
+        index_by_key[copied[keyed_field]] = len(result)
+        result.append(copied)
+    for item in override:
+        copied = dict(item)
+        key = copied[keyed_field]
+        if key in index_by_key:
+            result[index_by_key[key]] = copied
+        else:
+            index_by_key[key] = len(result)
+            result.append(copied)
+    return result
+
+
+def structural_merge(base: Any, override: Any) -> Any:
+    """Merge tables recursively, keyed table arrays by identity, and append other arrays."""
+    if isinstance(base, dict) and isinstance(override, dict):
+        result = dict(base)
+        for key, value in override.items():
+            result[key] = structural_merge(result[key], value) if key in result else value
+        return result
+    if isinstance(base, list) and isinstance(override, list):
+        return _merge_arrays(base, override)
+    return override
+
+
+def merge_layers(layers: Iterable[dict[str, Any]]) -> dict[str, Any]:
+    merged: dict[str, Any] = {}
+    for layer in layers:
+        merged = structural_merge(merged, layer)
+    return merged
+
+
+def load_central_config(project_root: Path) -> dict[str, Any]:
+    bmad_dir = project_root / "_bmad"
+    return merge_layers(
+        (
+            load_toml(bmad_dir / "config.toml", required=True),
+            load_toml(bmad_dir / "config.user.toml"),
+            load_toml(bmad_dir / "custom" / "config.toml"),
+            load_toml(bmad_dir / "custom" / "config.user.toml"),
+        )
+    )
+
+
+def load_customization(project_root: Path | None, skill_dir: Path) -> dict[str, Any]:
+    skill_name = skill_dir.name
+    custom_dir = project_root / "_bmad" / "custom" if project_root else None
+    return merge_layers(
+        (
+            load_toml(skill_dir / "customize.toml", required=True),
+            load_toml(custom_dir / f"{skill_name}.toml") if custom_dir else {},
+            load_toml(custom_dir / f"{skill_name}.user.toml") if custom_dir else {},
+        )
+    )
diff --git a/_bmad/scripts/memlog.py b/_bmad/scripts/memlog.py
new file mode 100644
index 0000000..e7f1f24
--- /dev/null
+++ b/_bmad/scripts/memlog.py
@@ -0,0 +1,224 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.8"
+# ///
+"""memlog — an append-only memory log: LLM-optimal working memory for a skill.
+
+A memlog is the dense, chronological record of everything that mattered in a piece of
+work — every item the user generated or accepted — kept minimal like human memory: only
+what's important, never bloated. It persists ACROSS sessions, so a fresh session can
+load it and continue. It is NOT a deliverable; downstream artifacts (a brief, a PRD, a
+deck, a report) are *derived* from it on demand. The host skill supplies the vocabulary
+by how it calls `append` — the tool stays neutral.
+
+It is a FLAT log: there are no sections or grouping. Every entry is one line, recorded
+at the END in the order it happened. The chronology itself is the structure — an event
+like "started technique X" is just another entry, same as an idea or an insight.
+
+Three invariants make it trustworthy:
+
+  1. Append-only, chronological. Entries land at the end, in the order they happen.
+     Nothing is ever inserted backward, reordered, edited, or removed. There is no
+     edit or delete subcommand by design; history is never rewritten.
+  2. Write-only / blind. Every command is an atomic, context-free write and echoes the
+     new state as one line of JSON, so the caller never re-reads the file mid-session.
+     The one time the file is read is on resume — and the caller reads it itself, not
+     via this script.
+  3. No lifecycle status. A memory log has no "complete" flag. Whether the work is done,
+     blocked, or paused is itself a fact that happened, so it is recorded as an entry
+     (e.g. `append --type event --text "session complete"`), never as frontmatter the
+     log would have to mutate. The chronology stays the single source of truth, and a
+     resume learns the state by reading the last entries — the same way it learns
+     everything else.
+
+Atomicity: every write goes to a temp file, is flushed and fsync'd, then atomically
+renamed over the target, so a crash never leaves a half-written entry.
+
+The file shape (.memlog.md):
+
+    ---
+    topic: Onboarding flow for a budgeting app
+    goal: lift week-1 retention
+    updated: 2026-06-07T14:22
+    ---
+
+    - (note) user picked techniques: SCAMPER, then Six Thinking Hats
+    - (technique) started SCAMPER
+    - (idea) skip the signup wall: let people try with sample data first
+    - (idea) auto-import one bank account so the first screen shows real numbers
+    - (question) is open-banking consent too heavy for step one?
+    - (insight) the "scary numbers" risk and the "real numbers" idea are one lever: show real data, pre-categorized
+    - (direction) optimize for the anxious first-timer, not the power user
+    - (decision) lead with one pre-categorized account; defer multi-account import
+    - (event) session complete
+
+Each entry may carry an optional `--type` — what KIND it is (idea, insight, question,
+decision, direction, assumption, gap, note, event, …) — and an optional `--by` naming
+who it came from (e.g. `user`, `coach`), for sessions where authorship matters. Both
+render into one short inline tag: `(idea)`, `(idea by user)`, `(by coach)`. Omit them
+for a plain note. The host skill names the vocabulary; the script does not enforce one.
+
+Commands:
+  init   (--workspace DIR | --path FILE) [--field k=v ...]    create the memlog (errors if it exists)
+  append (--workspace DIR | --path FILE) --text STR [--type T] [--by W]  append one entry at the end
+  set    (--workspace DIR | --path FILE) --key K --value V    set/replace a descriptive frontmatter field
+
+Addressing: `--workspace` is the run folder, and the memlog is always {workspace}/.memlog.md.
+`--path` points straight at the memlog file instead, for callers that already hold the path.
+"""
+from __future__ import annotations  # keep type-hint syntax lazy so the script runs on 3.8+
+
+import argparse
+import json
+import os
+import sys
+from datetime import datetime
+from pathlib import Path
+
+MEMLOG = ".memlog.md"
+
+
+def now() -> str:
+    return datetime.now().strftime("%Y-%m-%dT%H:%M")
+
+
+def resolve(args) -> Path:
+    """The memlog file, from either addressing mode: {workspace}/.memlog.md or an explicit --path."""
+    return Path(args.path) if args.path else Path(args.workspace) / MEMLOG
+
+
+def split(text: str) -> tuple[dict, str]:
+    """Return (frontmatter dict in source order, body str). Frontmatter is plain key: value.
+
+    The closing fence is the first line that is *exactly* `---`, so a `---` inside a
+    field value (topic/goal are free user text) never truncates the frontmatter.
+    """
+    lines = text.splitlines()
+    if not lines or lines[0] != "---":
+        raise ValueError(".memlog.md has no frontmatter")
+    end = next((i for i in range(1, len(lines)) if lines[i] == "---"), None)
+    if end is None:
+        raise ValueError(".memlog.md frontmatter is not terminated")
+    meta: dict[str, str] = {}
+    for line in lines[1:end]:
+        if ":" in line:
+            k, v = line.split(":", 1)
+            meta[k.strip()] = v.strip()
+    return meta, "\n".join(lines[end + 1:]).lstrip("\n")
+
+
+def render(meta: dict, body: str) -> str:
+    # Neutralize newlines in values so a multi-line field can't break the fence on re-read.
+    fm = "\n".join(f"{k}: {' '.join(str(v).splitlines())}" for k, v in meta.items())
+    return "---\n" + fm + "\n---\n\n" + body.rstrip("\n") + "\n"
+
+
+def touch(meta: dict) -> None:
+    """Stamp `updated` and keep it last so the field order stays predictable."""
+    meta.pop("updated", None)
+    meta["updated"] = now()
+
+
+def write_atomic(path: Path, text: str) -> None:
+    """Temp + flush + fsync + atomic rename, so a crash never half-writes an entry."""
+    tmp = path.with_suffix(path.suffix + ".tmp")
+    with open(tmp, "w", encoding="utf-8") as f:
+        f.write(text)
+        f.flush()
+        os.fsync(f.fileno())
+    os.replace(tmp, path)
+
+
+def entry_count(body: str) -> int:
+    return sum(1 for ln in body.splitlines() if ln.startswith("- "))
+
+
+def ack(path: Path, body: str) -> None:
+    """Echo new state so the caller never re-reads the file to know where it stands."""
+    print(json.dumps({
+        "ok": True,
+        "memlog": str(path),
+        "entries": entry_count(body),
+    }))
+
+
+def cmd_init(args) -> int:
+    path = resolve(args)
+    if path.exists():
+        print(f"error: {path} already exists; use append/set to update it", file=sys.stderr)
+        return 2
+    path.parent.mkdir(parents=True, exist_ok=True)
+    meta: dict[str, str] = {}
+    for pair in args.field or []:
+        if "=" not in pair:
+            print(f"error: --field expects key=value, got {pair!r}", file=sys.stderr)
+            return 2
+        k, v = pair.split("=", 1)
+        meta[k.strip()] = v.strip()
+    touch(meta)
+    write_atomic(path, render(meta, ""))
+    ack(path, "")
+    return 0
+
+
+def cmd_append(args) -> int:
+    path = resolve(args)
+    meta, body = split(path.read_text(encoding="utf-8"))
+    text = " ".join(args.text.split())  # collapse newlines/runs → one-line entry, no prose bloat
+    label = args.type or ""
+    if args.by:
+        label = f"{label} by {args.by}".strip()  # attribution: "(idea by user)" / "(by coach)"
+    tag = f"({label}) " if label else ""
+    entry = f"- {tag}{text}"
+    body = (body.rstrip("\n") + "\n" + entry) if body.strip() else entry  # always at the end
+    touch(meta)
+    write_atomic(path, render(meta, body))
+    ack(path, body)
+    return 0
+
+
+def cmd_set(args) -> int:
+    path = resolve(args)
+    meta, body = split(path.read_text(encoding="utf-8"))
+    meta[args.key] = args.value
+    touch(meta)
+    write_atomic(path, render(meta, body))
+    ack(path, body)
+    return 0
+
+
+def add_target(sp) -> None:
+    """Every command addresses the memlog the same way: a run folder or an explicit path."""
+    g = sp.add_mutually_exclusive_group(required=True)
+    g.add_argument("--workspace", help="run folder; the memlog is {workspace}/.memlog.md")
+    g.add_argument("--path", help="explicit memlog file path (alternative to --workspace)")
+
+
+def main(argv: list[str] | None = None) -> int:
+    p = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
+    sub = p.add_subparsers(dest="cmd", required=True)
+
+    pi = sub.add_parser("init", help="create the memlog")
+    add_target(pi)
+    pi.add_argument("--field", action="append", metavar="KEY=VALUE", help="frontmatter field (repeatable)")
+    pi.set_defaults(func=cmd_init)
+
+    pa = sub.add_parser("append", help="append one entry at the end")
+    add_target(pa)
+    pa.add_argument("--text", required=True)
+    pa.add_argument("--type", help="entry kind, rendered as an inline tag")
+    pa.add_argument("--by", help="who the entry came from (e.g. user, coach); rendered into the tag")
+    pa.set_defaults(func=cmd_append)
+
+    pset = sub.add_parser("set", help="set a descriptive frontmatter field")
+    add_target(pset)
+    pset.add_argument("--key", required=True)
+    pset.add_argument("--value", required=True)
+    pset.set_defaults(func=cmd_set)
+
+    args = p.parse_args(argv)
+    return args.func(args)
+
+
+if __name__ == "__main__":
+    sys.exit(main())
diff --git a/_bmad/scripts/render_skill.py b/_bmad/scripts/render_skill.py
new file mode 100644
index 0000000..e0667e8
--- /dev/null
+++ b/_bmad/scripts/render_skill.py
@@ -0,0 +1,401 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Render a skill's Markdown sources into an immutable project snapshot."""
+
+from __future__ import annotations
+
+import argparse
+import hashlib
+import json
+import os
+import re
+import shutil
+import sys
+import tempfile
+from pathlib import Path
+from typing import Any
+
+# Installed scripts are consumer files, not a location for interpreter caches.
+sys.dont_write_bytecode = True
+
+from config_utils import ConfigError, load_central_config, load_customization, load_toml
+
+
+class RenderError(ValueError):
+    """Raised when rendering cannot safely publish a snapshot."""
+
+
+_CONFIG_TOKEN = re.compile(r"\{\{config\.([A-Za-z0-9_.-]+)\}\}")
+_SHORT_CONFIG_TOKEN = re.compile(r"\{\{\.([A-Za-z0-9_]+)\}\}")
+_CUSTOM_TOKEN = re.compile(r"\{workflow\.([A-Za-z0-9_.-]+)\}")
+_SNAPSHOT_TOKEN = re.compile(r"\[\[bmad-snapshot:([A-Za-z0-9_./-]+\.md)\]\]")
+
+
+def _hash_bytes(content: bytes) -> str:
+    return hashlib.sha256(content).hexdigest()
+
+
+def _canonical_json(value: Any) -> bytes:
+    return json.dumps(
+        value, ensure_ascii=False, sort_keys=True, separators=(",", ":")
+    ).encode("utf-8")
+
+
+def _lookup(data: dict[str, Any], dotted_path: str, label: str) -> Any:
+    current: Any = data
+    for part in dotted_path.split("."):
+        if not isinstance(current, dict) or part not in current:
+            raise RenderError(f"missing {label} `{dotted_path}`")
+        current = current[part]
+    return current
+
+
+def _require_string(value: Any, label: str, *, allow_empty: bool = False) -> str:
+    if not isinstance(value, str):
+        raise RenderError(f"{label} must be a string, got {type(value).__name__}")
+    if not allow_empty and not value.strip():
+        raise RenderError(f"{label} must not be empty")
+    return value
+
+
+def _require_string_list(value: Any, label: str) -> list[str]:
+    if not isinstance(value, list):
+        raise RenderError(f"{label} must be a list, got {type(value).__name__}")
+    result = []
+    for index, item in enumerate(value):
+        result.append(_require_string(item, f"{label}[{index}]"))
+    return result
+
+
+def _require_review_layers(value: Any, label: str) -> list[dict[str, str]]:
+    if not isinstance(value, list):
+        raise RenderError(f"{label} must be a list of tables")
+    result: list[dict[str, str]] = []
+    seen: set[str] = set()
+    for index, item in enumerate(value):
+        item_label = f"{label}[{index}]"
+        if not isinstance(item, dict):
+            raise RenderError(f"{item_label} must be a table")
+        identifier = _require_string(item.get("id"), f"{item_label}.id")
+        if identifier in seen:
+            raise RenderError(f"duplicate review layer id `{identifier}`")
+        seen.add(identifier)
+        layer = {
+            "id": identifier,
+            "name": _require_string(item.get("name", identifier), f"{item_label}.name"),
+            "instruction": _require_string(
+                item.get("instruction"), f"{item_label}.instruction", allow_empty=True
+            ),
+        }
+        if "when" in item:
+            layer["when"] = _require_string(item["when"], f"{item_label}.when")
+        result.append(layer)
+    return result
+
+
+def _load_sources(skill_dir: Path) -> dict[str, str]:
+    sources: dict[str, str] = {}
+    for candidate in sorted(skill_dir.rglob("*.md")):
+        if candidate.name == "SKILL.md":
+            continue
+        name = candidate.relative_to(skill_dir).as_posix()
+        path = candidate.resolve(strict=True)
+        if not path.is_relative_to(skill_dir):
+            raise RenderError(f"render source escapes skill directory: {name}")
+        if not path.is_file():
+            raise RenderError(f"render source is missing or not a file: {path}")
+        try:
+            sources[name] = path.read_text(encoding="utf-8")
+        except (OSError, UnicodeError) as error:
+            raise RenderError(f"failed to read render source {path}: {error}") from error
+    if "workflow.md" not in sources:
+        raise RenderError(f"render entry is missing: {skill_dir / 'workflow.md'}")
+    return sources
+
+
+def _resolve_config_value(value: Any, label: str, project_root: Path) -> str:
+    text = _require_string(value, label)
+    if "{project-root}" not in text:
+        return text
+    resolved = text.replace("{project-root}", str(project_root))
+    if not Path(resolved).is_absolute():
+        raise RenderError(f"{label} must resolve to an absolute path: {resolved}")
+    return resolved
+
+
+def _find_config_values(data: Any, key: str, prefix: str = "") -> list[tuple[str, Any]]:
+    matches: list[tuple[str, Any]] = []
+    if not isinstance(data, dict):
+        return matches
+    for name, value in data.items():
+        path = f"{prefix}.{name}" if prefix else name
+        if name == key and not isinstance(value, (dict, list)):
+            matches.append((path, value))
+        matches.extend(_find_config_values(value, key, path))
+    return matches
+
+
+def _resolve_short_config(
+    central: dict[str, Any], key: str, project_root: Path
+) -> tuple[str, str]:
+    matches = _find_config_values(central, key)
+    if not matches:
+        raise RenderError(f"missing config value `{key}`")
+    if len(matches) > 1:
+        paths = ", ".join(path for path, _ in matches)
+        raise RenderError(f"ambiguous config value `{key}` found at: {paths}")
+    path, value = matches[0]
+    return path, _resolve_config_value(value, f"config.{path}", project_root)
+
+
+def _format_markdown_list(items: list[str]) -> str:
+    if not items:
+        return "_None._"
+    rendered = []
+    for item in items:
+        lines = item.splitlines() or [""]
+        rendered.append("- " + lines[0])
+        rendered.extend("  " + line for line in lines[1:])
+    return "\n".join(rendered)
+
+
+def _format_review_layers(layers: list[dict[str, str]]) -> str:
+    active = [layer for layer in layers if layer["instruction"].strip()]
+    if not active:
+        return "No active review layers. HALT with blocking condition `no active review layers`."
+    sections = []
+    for layer in active:
+        section = [f"#### {layer['name']} (`{layer['id']}`)"]
+        if layer.get("when"):
+            section.extend(["", f"Run only when: {layer['when']}"])
+        section.extend(["", layer["instruction"].strip()])
+        sections.append("\n".join(section))
+    return "\n\n".join(sections)
+
+
+def _resolve_customization_value(value: Any, default: Any, label: str) -> tuple[Any, str]:
+    if isinstance(default, str):
+        allow_empty = not default.strip() or label == "customization.workflow.open_spec"
+        resolved = _require_string(value, label, allow_empty=allow_empty)
+        return resolved, resolved
+    if isinstance(default, list):
+        if default and all(isinstance(item, dict) for item in default):
+            resolved = _require_review_layers(value, label)
+            return resolved, _format_review_layers(resolved)
+        resolved = _require_string_list(value, label)
+        return resolved, _format_markdown_list(resolved)
+    raise RenderError(f"{label} has unsupported default type {type(default).__name__}")
+
+
+def _resolve_replacements(
+    sources: dict[str, str],
+    central: dict[str, Any],
+    customization: dict[str, Any],
+    defaults: dict[str, Any] | None,
+    project_root: Path,
+) -> tuple[dict[str, str], dict[str, Any]]:
+    replacements: dict[str, str] = {}
+    input_values: dict[str, Any] = {}
+    for content in sources.values():
+        for match in _SHORT_CONFIG_TOKEN.finditer(content):
+            token, key = match.group(0), match.group(1)
+            path, resolved = _resolve_short_config(central, key, project_root)
+            source = f"config.{path}"
+            replacements[token] = resolved
+            input_values[source] = resolved
+        for match in _CONFIG_TOKEN.finditer(content):
+            token, path = match.group(0), match.group(1)
+            source = f"config.{path}"
+            resolved = _resolve_config_value(
+                _lookup(central, path, "config value"), source, project_root
+            )
+            replacements[token] = resolved
+            input_values[source] = resolved
+        for match in _CUSTOM_TOKEN.finditer(content):
+            if defaults is None:
+                raise RenderError("customization tokens require customize.toml")
+            token, relative_path = match.group(0), match.group(1)
+            path = f"workflow.{relative_path}"
+            source = f"customization.{path}"
+            resolved, rendered = _resolve_customization_value(
+                _lookup(customization, path, "customization value"),
+                _lookup(defaults, path, "customization default"),
+                source,
+            )
+            replacements[token] = rendered
+            input_values[source] = resolved
+    return replacements, input_values
+
+
+def _render_sources(
+    sources: dict[str, str], replacements: dict[str, str], destination: Path
+) -> dict[str, str]:
+    """Resolve only tokens authored in installed sources in one opaque pass."""
+    # Workflow customization may reference installed skill files; bind those
+    # references to the immutable generation before inserting the prose.
+    replacements = {
+        token: value.replace("{skill-root}", str(destination))
+        if token.startswith("{workflow.")
+        else value
+        for token, value in replacements.items()
+    }
+    source_names = set(sources)
+    patterns = [
+        *(re.escape(token) for token in sorted(replacements, key=len, reverse=True)),
+        _SNAPSHOT_TOKEN.pattern,
+    ]
+    token_pattern = re.compile("|".join(patterns))
+
+    def replace(match: re.Match[str]) -> str:
+        token = match.group(0)
+        if token in replacements:
+            return replacements[token]
+        snapshot = _SNAPSHOT_TOKEN.fullmatch(token)
+        if snapshot is None:
+            raise RenderError(f"unsupported render token: {token}")
+        target = snapshot.group(1)
+        if target not in source_names:
+            raise RenderError(f"snapshot reference targets undeclared source: {target}")
+        return str(destination / target)
+
+    rendered: dict[str, str] = {}
+    for name, content in sources.items():
+        # Inserted paths and customization prose are never scanned as source tokens.
+        rendered[name] = token_pattern.sub(replace, content)
+    return rendered
+
+
+def _verify_existing(destination: Path, manifest: dict[str, Any]) -> None:
+    manifest_path = destination / "manifest.json"
+    try:
+        existing = json.loads(manifest_path.read_text(encoding="utf-8"))
+    except (OSError, UnicodeError, json.JSONDecodeError) as error:
+        raise RenderError(f"corrupt existing generation {destination}: {error}") from error
+    if existing != manifest:
+        raise RenderError(f"generation collision or corruption at {destination}")
+    expected_files = set(manifest["outputs"]) | {"manifest.json"}
+    actual_files = {
+        path.relative_to(destination).as_posix()
+        for path in destination.rglob("*")
+        if path.is_file()
+    }
+    if actual_files != expected_files:
+        raise RenderError(f"generation contains unexpected or missing files: {destination}")
+    for name, expected_hash in manifest["outputs"].items():
+        try:
+            actual_hash = _hash_bytes((destination / name).read_bytes())
+        except OSError as error:
+            raise RenderError(f"failed to verify {destination / name}: {error}") from error
+        if actual_hash != expected_hash:
+            raise RenderError(f"generation output hash mismatch: {destination / name}")
+
+
+def _publish(destination: Path, outputs: dict[str, bytes], manifest: dict[str, Any]) -> None:
+    destination.parent.mkdir(parents=True, exist_ok=True)
+    if destination.exists():
+        _verify_existing(destination, manifest)
+        return
+    staging = Path(tempfile.mkdtemp(prefix=".staging-", dir=destination.parent))
+    try:
+        for name, content in outputs.items():
+            path = staging / name
+            path.parent.mkdir(parents=True, exist_ok=True)
+            path.write_bytes(content)
+        (staging / "manifest.json").write_bytes(
+            json.dumps(manifest, ensure_ascii=False, indent=2, sort_keys=True).encode("utf-8")
+            + b"\n"
+        )
+        try:
+            os.rename(staging, destination)
+        except OSError:
+            if destination.exists():
+                _verify_existing(destination, manifest)
+            else:
+                raise
+    finally:
+        if staging.exists():
+            shutil.rmtree(staging, ignore_errors=True)
+
+
+def render(project_root: Path, skill_dir: Path) -> Path:
+    project_root = project_root.resolve(strict=True)
+    skill_dir = skill_dir.resolve(strict=True)
+    if not (project_root / "_bmad").is_dir():
+        raise RenderError(f"project root does not contain _bmad/: {project_root}")
+
+    sources = _load_sources(skill_dir)
+    central = load_central_config(project_root)
+    has_customization = any(
+        _CUSTOM_TOKEN.search(content) for content in sources.values()
+    )
+    defaults = (
+        load_toml(skill_dir / "customize.toml", required=True)
+        if has_customization
+        else None
+    )
+    customization = (
+        load_customization(project_root, skill_dir) if has_customization else {}
+    )
+    replacements, input_values = _resolve_replacements(
+        sources, central, customization, defaults, project_root
+    )
+    source_hashes = {
+        name: _hash_bytes(content.encode("utf-8")) for name, content in sources.items()
+    }
+    root_hash = _hash_bytes(str(project_root).encode("utf-8"))[:12]
+    slug = re.sub(r"[^a-z0-9]+", "-", project_root.name.lower()).strip("-") or "project"
+    slug = slug[:80].rstrip("-") or "project"
+    renderer_hash = _hash_bytes(Path(__file__).read_bytes())
+    identity = {
+        "project_root": str(project_root),
+        "renderer_sha256": renderer_hash,
+        "resolved_values": input_values,
+        "source_sha256": source_hashes,
+    }
+    generation_hash = _hash_bytes(_canonical_json(identity))[:20]
+    destination = (
+        project_root
+        / "_bmad"
+        / "render"
+        / skill_dir.name
+        / f"{slug}-{root_hash}"
+        / generation_hash
+    )
+    rendered = _render_sources(sources, replacements, destination)
+    outputs = {name: content.encode("utf-8") for name, content in rendered.items()}
+    output_hashes = {name: _hash_bytes(content) for name, content in outputs.items()}
+    manifest = {
+        "schema_version": 1,
+        "skill": skill_dir.name,
+        "project_root": str(project_root),
+        "project_slug": slug,
+        "root_hash": root_hash,
+        "generation_hash": generation_hash,
+        "inputs": identity,
+        "outputs": output_hashes,
+    }
+    _publish(destination, outputs, manifest)
+    return destination / "workflow.md"
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser(description=__doc__)
+    parser.add_argument("--project-root", required=True)
+    parser.add_argument("--skill", required=True)
+    args = parser.parse_args()
+    reconfigure = getattr(sys.stdout, "reconfigure", None)
+    if reconfigure is not None:
+        reconfigure(encoding="utf-8")
+    try:
+        entry = render(Path(args.project_root), Path(args.skill))
+    except (ConfigError, RenderError, OSError, UnicodeError, ValueError) as error:
+        sys.stdout.write(f"HALT: {error}\n")
+        return 1
+    sys.stdout.write(f"read and follow {entry}\n")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())
diff --git a/_bmad/scripts/resolve_config.py b/_bmad/scripts/resolve_config.py
new file mode 100644
index 0000000..630d6e5
--- /dev/null
+++ b/_bmad/scripts/resolve_config.py
@@ -0,0 +1,74 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Resolve BMad's four central TOML layers to JSON."""
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+# Installed scripts are consumer files, not a location for interpreter caches.
+sys.dont_write_bytecode = True
+
+try:
+    from config_utils import ConfigError, load_central_config
+except ModuleNotFoundError as error:
+    if error.name != "tomllib":
+        raise
+    sys.stderr.write("error: Python 3.11+ is required (stdlib `tomllib` not found).\n")
+    raise SystemExit(3) from None
+
+
+_MISSING = object()
+
+
+def extract_key(data, dotted_key: str):
+    current = data
+    for part in dotted_key.split("."):
+        if isinstance(current, dict) and part in current:
+            current = current[part]
+        else:
+            return _MISSING
+    return current
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser(
+        description="Resolve BMad central config using four-layer TOML merge."
+    )
+    parser.add_argument(
+        "--project-root",
+        "-p",
+        required=True,
+        help="Absolute project root containing _bmad/",
+    )
+    parser.add_argument(
+        "--key",
+        "-k",
+        action="append",
+        default=[],
+        help="Dotted field path to resolve (repeatable). Omit for full dump.",
+    )
+    args = parser.parse_args()
+
+    try:
+        merged = load_central_config(Path(args.project_root).resolve())
+    except ConfigError as error:
+        sys.stderr.write(f"error: {error}\n")
+        return 1
+
+    output = merged
+    if args.key:
+        output = {}
+        for key in args.key:
+            value = extract_key(merged, key)
+            if value is not _MISSING:
+                output[key] = value
+    sys.stdout.write(json.dumps(output, indent=2, ensure_ascii=False) + "\n")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())
diff --git a/_bmad/scripts/resolve_customization.py b/_bmad/scripts/resolve_customization.py
new file mode 100755
index 0000000..d110c2a
--- /dev/null
+++ b/_bmad/scripts/resolve_customization.py
@@ -0,0 +1,99 @@
+#!/usr/bin/env python3
+# /// script
+# requires-python = ">=3.11"
+# ///
+"""Resolve a skill's default, team, and user TOML customization layers."""
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+# Installed scripts are consumer files, not a location for interpreter caches.
+sys.dont_write_bytecode = True
+
+try:
+    from config_utils import ConfigError, load_customization
+except ModuleNotFoundError as error:
+    if error.name != "tomllib":
+        raise
+    sys.stderr.write("error: Python 3.11+ is required (stdlib `tomllib` not found).\n")
+    raise SystemExit(3) from None
+
+
+_MISSING = object()
+
+
+def find_project_root(start: Path) -> Path | None:
+    current = start.resolve()
+    while True:
+        if (current / "_bmad").exists() or (current / ".git").exists():
+            return current
+        if current.parent == current:
+            return None
+        current = current.parent
+
+
+def extract_key(data, dotted_key: str):
+    current = data
+    for part in dotted_key.split("."):
+        if isinstance(current, dict) and part in current:
+            current = current[part]
+        else:
+            return _MISSING
+    return current
+
+
+def write_json_stdout(output) -> None:
+    reconfigure = getattr(sys.stdout, "reconfigure", None)
+    if reconfigure is not None:
+        reconfigure(encoding="utf-8")
+    sys.stdout.write(json.dumps(output, indent=2, ensure_ascii=False) + "\n")
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser(
+        description="Resolve skill customization using three-layer TOML merge."
+    )
+    parser.add_argument(
+        "--skill", "-s", required=True, help="Absolute path to the skill directory"
+    )
+    parser.add_argument(
+        "--project-root",
+        "-p",
+        help="Explicit project root containing _bmad/ (recommended)",
+    )
+    parser.add_argument(
+        "--key",
+        "-k",
+        action="append",
+        default=[],
+        help="Dotted field path to resolve (repeatable). Omit for full dump.",
+    )
+    args = parser.parse_args()
+
+    skill_dir = Path(args.skill).resolve()
+    project_root = (
+        Path(args.project_root).resolve()
+        if args.project_root
+        else find_project_root(skill_dir) or find_project_root(Path.cwd())
+    )
+    try:
+        merged = load_customization(project_root, skill_dir)
+    except ConfigError as error:
+        sys.stderr.write(f"error: {error}\n")
+        return 1
+
+    output = merged
+    if args.key:
+        output = {}
+        for key in args.key:
+            value = extract_key(merged, key)
+            if value is not _MISSING:
+                output[key] = value
+    write_json_stdout(output)
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())