@event4u/agent-config 1.33.0 → 1.35.0

package/.agent-src/skills/copilot-agents-optimization/SKILL.md

@@ -2,6 +2,7 @@
 name: copilot-agents-optimization
 description: "Use when optimizing AGENTS.md or copilot-instructions.md — deduplicates against .augment/ content, enforces line budgets, and focuses each file on its audience."
 source: package
+domain: process
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/copilot-config/SKILL.md

@@ -2,6 +2,7 @@
 name: copilot-config
 description: "Use when configuring GitHub Copilot — copilot-instructions.md, PR review patterns, output optimization — even when the user just says 'tune Copilot' or 'why is Copilot commenting on X'."
 source: package
+domain: process
 ---
 
 # Copilot Skill

package/.agent-src/skills/customer-research/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: customer-research
+description: "Use when shaping a discovery slice — JTBD-framed interview guide, switch-event focus, verbatim quotes not summaries. Triggers on 'talk to users', 'why did they cancel', 'before we build X'."
+status: active
+tier: senior
+source: package
+domain: product
+context_spine: [product]
+---
+
+# customer-research
+
+## When to use
+
+- A backlog item is fuzzy because no one has talked to a current user about the underlying job in the last quarter.
+- A churn or refund spike needs a switch-event explanation, not a feature gap list.
+- A product owner is about to write AC for a feature that has not been validated against a real user job.
+
+Do NOT use for quantitative funnel diagnosis (see `funnel-analysis`),
+RICE-style ranking (see `rice-prioritization`), or surveying at scale —
+this skill is about depth-5-to-10 interviews, not statistics.
+
+## Cognition cluster
+
+- **Mental model 2 — Jobs-to-be-Done.** Frames every question against
+  the **switch event**: what caused the user to fire the previous
+  solution? See [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 2.
+- **Mental model 3 — Pareto principle.** A research week that
+  produces 12 distinct insights is usually re-discovering the same
+  three. See `mental-models.md` § 3.
+
+## Procedure
+
+### Step 0: Frame the job
+
+1. Write one sentence: *"Users hire \<thing\> to make progress in \<situation\>, when motivated by \<pressure\>, expecting \<outcome\>."* If you cannot finish the sentence, the discovery slice is not yet shaped — stop and route to `po-discovery`.
+2. Read the **product** slot of the [context-spine](../../../docs/contracts/context-spine.md) (if the consumer project has filled it) for bounded scope, and the **team** slot for the senior PO / researcher handoff target. Skip if absent — note in the brief.
+3. Identify **one** competing solution the user might fire. Multiple competitors per session blurs the switch event.
+
+### Step 1: Recruit the right 5–8
+
+1. Recruit **switchers** (joined in last 60 days) and **leavers**
+   (cancelled in last 60 days). Long-tenure power-users go in a
+   separate bucket — they explain habits, not jobs.
+2. 5 minimum, 8 maximum. Saturation hits around 6 in a tightly
+   scoped job — the Pareto cut. Beyond 8 is research theatre.
+3. Avoid friends, employees, beta-program over-talkers — selection bias is the failure mode that survives the AC.
+
+### Step 2: Run the interview
+
+1. Open with the **switch event**: *"Walk me through the day you decided to start using \<product\>."* Time, place, trigger, alternative considered.
+2. Past behaviour, not hypothetical. Replace *"would you use"* with *"the last time you needed X, what did you do?"*.
+3. Capture **quotes**, not summaries. Verbatim quotes survive the AC; paraphrases get re-interpreted into pre-existing beliefs.
+4. Listen for the **anxiety / habit** pair — what they feared in switching, what habit died.
+
+### Step 3: Code the evidence
+
+1. One quote per insight. Tag each with: switch-event, anxiety, habit, expected-outcome, unexpected-outcome.
+2. An insight without a quote is a hypothesis, not a finding — mark it.
+3. Frequency-rank by how many distinct interviewees touched the insight (≥ 3 is signal; 1 is anecdote).
+
+### Step 4: Hand back
+
+1. Produce the three artifacts (see `## Output`).
+2. Hand the brief to the senior PO. Do **not** translate findings into AC inside this skill — that is `refine-ticket`'s job.
+
+## Related Skills
+
+**WHEN to use this**
+
+- The unit of analysis is **a real user's switch event**.
+- Discovery is fuzzy and the team is about to ship without validation.
+- A retention or churn spike needs a narrative, not a metric.
+
+**WHEN NOT to use this**
+
+- Quantitative drop-off across stages — route to [`funnel-analysis`](../funnel-analysis/SKILL.md).
+- Ranking competing initiatives — route to [`rice-prioritization`](../rice-prioritization/SKILL.md).
+- Reframing a fuzzy product ask before any user contact — route to [`po-discovery`](../po-discovery/SKILL.md).
+- AC sharpening on an already-validated ticket — route to [`refine-ticket`](../refine-ticket/SKILL.md).
+
+## When the agent should load this
+
+- "We need to talk to users before we build X."
+- "Why are people churning at month 2?"
+- "Run customer research on the new pricing tier."
+- "I keep guessing what the user wants — let's actually ask."
+- "Before refining this ticket, do we know the real job?"
+
+## Output
+
+1. **`research-brief.md`** — frame sentence, recruit criteria, target sample, JTBD focal job, list of competing solutions in scope. Pre-interview artifact.
+2. **`evidence-log.md`** — one row per insight: quote · interviewee ID · tag (switch / anxiety / habit / outcome) · frequency. Sorted by frequency descending. Verbatim only.
+3. **`switch-event-summary.md`** — narrative of the dominant switch event(s) the research surfaced, with ≥ 3 supporting quotes per claim. Hand-off artifact for [`refine-ticket`](../refine-ticket/SKILL.md) and the senior product owner persona (currently [`product-owner`](../../personas/product-owner.md); senior persona shipping in next plate).
+
+## Gotcha
+
+- Asking *"would you use"* contaminates the answer with politeness; ground every question in past behaviour.
+- One articulate interviewee can swamp evidence-log. Frequency-rank by distinct people, not distinct quotes.
+- Tagging too aggressively pre-interview hides surprise findings — leave room for `unexpected-outcome`.
+- A research week without ≥ 3 disqualified hypotheses is suspect — research that confirms everything is research that asked nothing.
+
+## Do NOT
+
+- Do NOT translate findings into acceptance criteria inside this skill — hand off to `refine-ticket`.
+- Do NOT recruit only happy users; switchers and leavers carry the switch-event signal, satisfied users do not.
+- Do NOT skip the frame sentence. An unframed interview produces 50 quotes about 8 different jobs.
+
+## Runnable example
+
+Pricing-tier churn at month 2:
+
+- Frame: *"Customers hire \<product\> to make progress in \<weekly reporting\>, motivated by \<board cadence\>, expecting \<one-click roll-up\>."*
+- Recruit: 6 leavers (cancelled within 30 days of month 2), 2 switchers from competitor C.
+- Interview: open with *"Walk me through the day you decided to cancel."* Capture verbatim.
+- Output: `evidence-log.md` shows 5 of 8 cite the *manual export step* as the cancellation trigger — switch-event signal, ≥ 3 frequency. `switch-event-summary.md` recommends the senior PO scope a discovery slice on the export step, not the report itself.

package/.agent-src/skills/dashboard-design/SKILL.md

@@ -2,6 +2,7 @@
 name: dashboard-design
 description: "Use when designing monitoring dashboards — visualization selection, layout principles, observability strategies (RED/USE/Golden Signals), and data storytelling."
 source: package
+domain: devops
 ---
 
 # dashboard-design

package/.agent-src/skills/data-flow-mapper/SKILL.md

@@ -2,6 +2,7 @@
 name: data-flow-mapper
 description: "Use BEFORE editing code that touches user data — traces the value from entry → validation → transformation → storage → egress, every hop cited with file:line."
 source: package
+domain: discovery
 ---
 
 # data-flow-mapper

package/.agent-src/skills/database/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: database
 description: "Use when working with database architecture, MariaDB/MySQL tuning, indexing strategies, slow queries, or multi-connection patterns — even when the user just says 'this query is slow'."
+personas:
+  - eloquent-tamer
 source: package
+domain: engineering
 ---
 
 # database

package/.agent-src/skills/dcf-modeling/SKILL.md

@@ -4,6 +4,7 @@ description: "Wing-4 valuation cognition for a CFO / finance-partner. Use when a
 status: active
 tier: senior
 source: package
+domain: product
 ---
 
 # dcf-modeling

package/.agent-src/skills/decision-record/SKILL.md

@@ -0,0 +1,218 @@
+---
+name: decision-record
+description: "Use when locking a trade-off, structuring an ADR draft, or wiring supersession chains — frames options · trade-offs · consequences before the file is written by `adr-create`."
+status: active
+tier: senior
+source: package
+domain: process
+context_spine: [team]
+personas:
+  - senior-engineer
+  - critical-challenger
+  - product-owner
+---
+
+# decision-record
+
+> Shape the **thinking** behind an architectural decision: list the
+> options, expose trade-offs, lock the chosen variant, and wire the
+> supersession chain. Hands off to [`adr-create`](../adr-create/SKILL.md)
+> for file mechanics (numbering, index, frontmatter). This skill does
+> not write the ADR file itself.
+
+## When to use
+
+- A team is about to commit to a non-trivial architectural choice and
+  wants the trade-offs on paper first.
+- Two engineers disagree on an approach — surface the options and
+  consequences before one wins by attrition.
+- A previous decision needs revisiting; the result must `supersede:`
+  the older ADR with explicit rationale.
+- German triggers: "lass uns das festzurren", "Trade-off-Matrix",
+  "welche Option ziehen wir?".
+
+Do NOT use when:
+
+- The file mechanics are the entire ask (numbering, regenerating the
+  index) — route directly to [`adr-create`](../adr-create/SKILL.md).
+- The decision is reversible and small (e.g. variable rename) — ADRs
+  are for choices that constrain future work.
+- The user wants a feature plan, not a decision — route to the
+  planning command instead.
+
+## Cognition cluster
+
+- **Mental model 4 — Second-order thinking.** Every decision unlocks
+  some futures and locks out others; the consequences block names
+  what becomes harder, not just what becomes easier. See
+  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 4.
+- **Mental model 6 — Theory of constraints.** A decision that does
+  not move the binding constraint is theatre; if the trade-off matrix
+  scores every option the same on the constraint that matters, the
+  options are fungible — surface and stop. See `mental-models.md` § 6.
+- **Mental model 10 — Reversible vs irreversible.** Two-way doors
+  get a one-page record; one-way doors get the full options +
+  consequences + supersession chain. The reversibility row of the
+  matrix decides which template fires. See `mental-models.md` § 10.
+- **Team context-spine slot.** Read the **team** slot of the
+  [context-spine](../../../docs/contracts/context-spine.md) to
+  capture who is bound by the decision (review groups, on-call
+  rotation). Skip if the consumer project has not filled it; note in
+  the record.
+
+## Procedure
+
+### 1. State the decision in one sentence
+
+*"We need to decide `X` because `Y`."* If you cannot, the decision
+is not ripe — surface that and stop.
+
+### 2. Identify and enumerate options (≥ 2, usually ≤ 4)
+
+Each option gets:
+
+- **Name** — short, descriptive, never "option A / B / C".
+- **Sketch** — what it actually does in one paragraph.
+- **Cost / benefit** — three to five bullets per side, concrete.
+- **Reversibility** — easy / costly / one-way (Bezos two-way / one-way
+  door framing).
+
+Add an **explicit "do nothing"** option whenever it is plausible —
+forces the user to compare the change against the status quo.
+
+### 3. Build the trade-off matrix
+
+| Criterion | Option 1 | Option 2 | ... |
+|---|---|---|---|
+| Implementation cost | | | |
+| Operational cost | | | |
+| Reversibility | | | |
+| Blast radius | | | |
+| Time-to-value | | | |
+
+Pick criteria that *separate* the options. Criteria where every
+option scores the same are noise — drop them.
+
+### 4. Lock the choice + consequences
+
+Write:
+
+- **Decision:** *"We pick `<Option name>`."*
+- **Consequences:** what becomes true, what becomes harder, what
+  becomes impossible. At least one of each, or admit that nothing
+  becomes harder (rare; verify).
+
+### 5. Wire the supersession chain (if any)
+
+If this decision overrides a prior ADR:
+
+- Cite the prior ADR id and one-line summary.
+- State **what changed in the world** that justifies overriding —
+  not "we now think differently".
+- Hand off the `supersedes:` linkage to `adr-create`.
+
+### 6. Hand off to file mechanics
+
+Output the structured payload (below). The user — or
+`adr-create` — turns it into the file.
+
+## Related Skills
+
+**WHEN to use this**
+
+- The team is about to lock a non-trivial choice and the trade-offs
+  need to survive the conversation that produced them.
+- A prior ADR is being overridden and the supersession chain needs
+  explicit "what changed in the world" rationale.
+- A planning thread has surfaced ≥ 2 viable options and silence is
+  about to pick one by attrition.
+
+**WHEN NOT to use this**
+
+- The choice splits stakeholders along role lines (PO vs ops, eng vs
+  support) — start with [`stakeholder-tradeoff`](../stakeholder-tradeoff/SKILL.md);
+  this skill locks the choice **after** the human cost is mapped.
+- The output is the ADR file itself (numbering, index regen) — route
+  to [`adr-create`](../adr-create/SKILL.md); this skill produces the
+  payload, not the file.
+- The risk shape is the dominant question — route to
+  [`risk-officer`](../risk-officer/SKILL.md) first, then return.
+- The decision is reversible and cheap — write a one-line note and
+  move on; ADRs are for irreversible or expensive constraints.
+
+## When the agent should load this
+
+- "Lass uns das festzurren."
+- "Welche Option ziehen wir und warum?"
+- "Wir müssen ein ADR draus machen."
+- "Trade-off-Matrix für X vs Y."
+- "Diese Entscheidung überschreibt das alte ADR-NN."
+
+## Output
+
+```
+Decision: <one sentence>
+
+Options:
+  1. <name> — <sketch>
+       Pros: ...
+       Cons: ...
+       Reversibility: easy | costly | one-way
+  2. ...
+  N. Do nothing — <sketch>
+
+Trade-off matrix:
+  | Criterion | <opt 1> | <opt 2> | ... |
+  | ...
+
+Locked: <chosen option name>
+
+Consequences:
+  + <becomes true>
+  - <becomes harder>
+  ✗ <becomes impossible>
+
+Supersedes: <ADR-XYZ "title">  (if any)
+Trigger:    <what changed>     (if superseding)
+
+Next: /adr-create  with the payload above
+```
+
+## Gotcha
+
+- "We compared the options" is not a comparison. The matrix must
+  separate them on at least two criteria.
+- Pros without cons is advocacy, not analysis. If you cannot find
+  cons for the chosen option, you have not understood it yet.
+- A supersession with no "what changed in the world" is a vibe
+  pivot. Reject and ask.
+
+## Do NOT
+
+- Do NOT pick the option before listing them — the matrix is the
+  point, not the conclusion.
+- Do NOT write the ADR file from this skill — `adr-create` owns
+  filenames, numbering, and index regeneration.
+- Do NOT pad option counts to look thorough; two real options beat
+  four straw men.
+- Do NOT silently update an old ADR; supersession is explicit.
+
+## Runnable example
+
+Replacing the in-house cron runner with a managed scheduler:
+
+- Decision: *"We need to decide between keeping the in-house cron
+  runner and migrating to the managed scheduler because the on-call
+  rotation has paged on missed-run incidents three times in 60 days."*
+- Options: (1) keep in-house + add monitoring; (2) migrate to
+  managed scheduler; (3) do nothing.
+- Matrix rows that **separate** options: implementation cost,
+  operational load, blast radius on outage, reversibility.
+- Locked: *"We pick the managed scheduler."*
+- Consequences: `+` on-call gets paged on scheduler infra, not
+  application code. `–` job definitions move to a vendor format,
+  raising migration cost if we leave. `✗` we cannot run jobs in the
+  app process anymore — assumes vendor uptime.
+- Supersedes: ADR-014 *"in-house cron runner"*; trigger = three
+  missed-run pages in 60 days now exceed the SLO budget.
+- Next: `/adr-create` with the payload, append `supersedes: ADR-014`.

package/.agent-src/skills/deep-reading-analyst/SKILL.md

@@ -3,6 +3,7 @@ name: deep-reading-analyst
 description: "Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary."
 status: active
 source: package
+domain: discovery
 external_source: "https://github.com/ginobefun/deep-reading-analyst-skill/tree/26cd7dc9920e025d39751e396e707399022e49ef/src/deep-reading-analyst"
 refresh_trigger: "Upstream `ginobefun/deep-reading-analyst-skill` major rewrite (new framework added, dispatch table reshaped, or SHA pin invalidated by reference rename)."
 sunset_criterion: "Replace with a 50-line pointer skill if (a) all referenced modules are adopted as project-local guidelines (`docs/guidelines/agent-infra/{framework}.md`) AND (b) the dispatch logic moves into a project-native router."

package/.agent-src/skills/defense-in-depth/SKILL.md

@@ -2,6 +2,7 @@
 name: defense-in-depth
 description: "Use when validation needs entry, business-logic, environment, and instrumentation guards so a bad value cannot reach the failure point — turns a local bug fix into a structural one."
 source: package
+domain: quality
 ---
 
 # defense-in-depth

package/.agent-src/skills/dependency-upgrade/SKILL.md

@@ -2,6 +2,7 @@
 name: dependency-upgrade
 description: "Use when upgrading dependencies — "update Laravel", "bump PHP version", or "upgrade packages". Covers changelog review, breaking change detection, and verification."
 source: package
+domain: engineering
 ---
 
 # dependency-upgrade

package/.agent-src/skills/description-assist/SKILL.md

@@ -2,6 +2,7 @@
 name: description-assist
 description: "Use when polishing a skill/rule/command/guideline frontmatter description — pushier phrasing, trigger coverage, undertrigger audit — even if the user just says 'make this pushier'."
 source: package
+domain: process
 ---
 
 <!-- cloud_safe: degrade -->

package/.agent-src/skills/design-review/SKILL.md

@@ -2,6 +2,7 @@
 name: design-review
 description: "Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more."
 source: package
+domain: quality
 ---
 
 # design-review

package/.agent-src/skills/devcontainer/SKILL.md

@@ -2,6 +2,7 @@
 name: devcontainer
 description: "Use when configuring DevContainers or GitHub Codespaces — devcontainer.json, custom images, secrets, VS Code features — even when the user just says 'why does my Codespace not start'."
 source: package
+domain: devops
 ---
 
 # devcontainer

package/.agent-src/skills/developer-like-execution/SKILL.md

@@ -2,6 +2,7 @@
 name: developer-like-execution
 description: "Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without naming it."
 source: package
+domain: process
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/discovery-interview/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: discovery-interview
+description: "Use when running discovery interviews — question-bank build, bias audit, insight extraction. Triggers on 'audit my guide', 'extract insights from transcript', 'is my hypothesis falsifiable'."
+status: active
+tier: senior
+source: package
+domain: product
+context_spine: [product]
+---
+
+# discovery-interview
+
+## When to use
+
+- A discovery slice has been framed (`customer-research` ran), but the interview guide is still rough or untested.
+- A transcript exists and the team needs structured insight extraction, not narrative summary.
+- An interview round produced surprising findings; a bias audit is needed before the team acts on them.
+
+Do NOT use for the upstream framing of the discovery slice (frame
+sentence, recruit criteria, JTBD focal job) — that is
+[`customer-research`](../customer-research/SKILL.md). Do NOT use for
+quantitative survey design or scale-bound research.
+
+## Cognition cluster
+
+- **Mental model 22 — Data-informed, not data-driven.** Interview
+  data is signal at low N; treat it as evidence to reason with, not
+  a vote count. See
+  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 22.
+- **Mental model 15 — Signal vs noise.** A vivid quote from one
+  articulate user can swamp three muted but consistent signals;
+  frequency-rank by distinct people, never by quote count. See
+  `mental-models.md` § 15.
+- **Mental model 28 — Eisenhower matrix.** Sort post-interview
+  insights into urgent / important quadrants so the team acts on
+  high-importance signals, not the loudest ones. See
+  `mental-models.md` § 28.
+- **Product context-spine slot.** Read **product** for the focal job
+  + competitor names; do **not** re-derive these inside this skill.
+  See [`context-spine`](../../../docs/contracts/context-spine.md).
+
+## Procedure
+
+### 1. Build the question bank
+
+1. Anchor on the **switch event** from `customer-research`. The
+   first question is always *"Walk me through the day you decided
+   to ..."* — never *"would you ..."*.
+2. Three layers:
+   - **Past behaviour** (what did you do? when? alternative considered?)
+   - **Anxiety / habit** (what feared in switching? what habit died?)
+   - **Outcome** (what changed for you? expected? unexpected?)
+3. Cap at 8 open questions per 45-min slot. Beyond that, the
+   interview becomes a survey delivered in person.
+
+### 2. Audit the bank for bias
+
+Before running, inspect each question and review the bank against the
+four common biases:
+
+- **Leading** — *"Don't you think X is annoying?"* → rewrite as past
+  behaviour.
+- **Hypothetical** — *"Would you use Y?"* → replace with *"Last
+  time you needed Y, what did you do?"*.
+- **Confirmation** — every question presupposes the team's hypothesis
+  is correct. At least two questions must be able to **disconfirm** it.
+- **Recall ceiling** — questions that ask for events ≥ 90 days back
+  produce confabulation; bound the timeframe.
+
+A bank that survives the audit unchanged is suspect — re-read.
+
+### 3. Run-time discipline
+
+1. Open with the switch event. Stay silent for 8 seconds after the
+   user finishes; the second answer is usually the truer one.
+2. Capture verbatim, not paraphrase. *"It made me anxious"* is data;
+   *"the user expressed concern"* is interpretation.
+3. Probe with *"tell me more about X"* on any anxiety / habit
+   mention; do not switch topics until the thread is exhausted.
+
+### 4. Extract insights
+
+For each transcript:
+
+1. One quote per insight. Tag: switch / anxiety / habit /
+   expected-outcome / unexpected-outcome / disconfirmation.
+2. Frequency-rank by distinct interviewees (≥ 3 = signal; 1 = anecdote).
+3. Mark **disconfirmations** explicitly — these are the most
+   valuable rows, because they are the cheapest to ignore.
+
+### 5. Hand back
+
+Produce the three artifacts (see `## Output`); hand the disconfirmation
+log to whoever owns the original hypothesis.
+
+## Related Skills
+
+**WHEN to use this**
+
+- The discovery slice is framed and the interview guide / transcript
+  is the unit of work.
+- A round of interviews ran and the insights need structured extraction
+  (frequency-ranked, bias-audited, disconfirmations highlighted).
+
+**WHEN NOT to use this**
+
+- The slice itself is unframed — start with
+  [`customer-research`](../customer-research/SKILL.md); this skill
+  inherits its frame, never re-derives it.
+- The signal needs to come from existing artefacts (issues, PRs, errors)
+  rather than a live interview — route to [`voc-extract`](../voc-extract/SKILL.md).
+- Insights translate into AC for a ticket — hand off to
+  [`refine-ticket`](../refine-ticket/SKILL.md).
+- The output is a quantitative funnel — route to
+  [`funnel-analysis`](../funnel-analysis/SKILL.md).
+
+## When the agent should load this
+
+- "Hilf mir den Interview-Leitfaden auditieren."
+- "Welche Fragen sind biased?"
+- "Extract die Insights aus diesem Transkript."
+- "Wir haben 6 Interviews geführt — was ist Signal, was ist Anekdote?"
+- "Ist meine Hypothese widerlegbar mit dem aktuellen Frageset?"
+
+## Output
+
+1. **`question-bank.md`** — 8 open questions, each tagged
+   past-behaviour / anxiety-habit / outcome; bias-audit notes per
+   rewritten question.
+2. **`insight-log.md`** — one row per insight: quote · interviewee
+   ID · tag · distinct-people frequency. Sorted descending. Verbatim.
+3. **`disconfirmation-log.md`** — each row names the original
+   hypothesis, the interview-derived disconfirmation, and the named
+   owner who must respond before the team acts on the round.
+
+## Gotcha
+
+- A bank that survived the audit unchanged is rare; usually means
+  the audit was rushed, not that the bank was perfect.
+- One articulate interviewee biases insight-extraction toward their
+  vocabulary — frequency-rank by people, not quotes.
+- Disconfirmations are the cheapest insight to ignore and the most
+  valuable to act on; the log exists so they survive the round.
+
+## Do NOT
+
+- Do NOT re-derive the frame inside this skill — read the **product**
+  spine slot or hand back to `customer-research`.
+- Do NOT translate insights into AC inside this skill — that is
+  `refine-ticket`.
+- Do NOT collapse disconfirmations into "we also heard X" prose;
+  they earn their own log.

package/.agent-src/skills/docker/SKILL.md

@@ -2,6 +2,7 @@
 name: docker
 description: "Use when working with Docker — Dockerfile edits, docker-compose services, containers, or the dual-container (fast + Xdebug) setup — even when the user just says 'my container won't start'."
 source: package
+domain: devops
 ---
 
 # docker

package/.agent-src/skills/dto-creator/SKILL.md

@@ -2,6 +2,7 @@
 name: dto-creator
 description: "Use when the user says "create a DTO", "new data transfer object", or needs to convert request/response data into a typed PHP class. Creates DTOs with SimpleDto base class and attribute mapping."
 source: package
+domain: engineering
 ---
 
 # dto-creator

package/.agent-src/skills/eloquent/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: eloquent
 description: "Use when writing Eloquent models, relationships, scopes, or queries via Model:: — 'fetch users with their orders'. NOT for PHPStan output, non-Eloquent services, or raw SQL questions."
+personas:
+  - eloquent-tamer
 source: package
+domain: engineering
 ---
 
 # eloquent

package/.agent-src/skills/error-handling-patterns/SKILL.md

@@ -2,6 +2,7 @@
 name: error-handling-patterns
 description: "Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized."
 source: package
+domain: engineering
 status: active
 refresh_trigger: "≥30% of cited upstream pattern catalogues become deprecated, OR a new top-2 ecosystem (Python/JS/PHP/Go/Rust) ships a paradigm-shifting standard error model"
 sunset_criterion: "When the upstream framework docs (Laravel, FastAPI, Express, Axum, Effect-TS) all carry an equivalent in-tree decision framework AND consumer projects no longer cite this skill in PR reviews for two consecutive review cycles."

package/.agent-src/skills/estimate-ticket/SKILL.md

@@ -9,6 +9,7 @@ personas:
   - critical-challenger
   - ai-agent
 source: package
+domain: product
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/existing-ui-audit/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: existing-ui-audit
 description: "Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set."
+personas:
+  - frontend-engineer
 source: package
+domain: discovery
 ---
 
 # existing-ui-audit