skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/core/pack.json

@@ -0,0 +1,50 @@
+{
+  "description": "The cross-role toolkit every pack builds on: structured intake, document critique, the review council, and output hygiene, plus the ship-a-draft wrapper. Installed automatically with every role pack.",
+  "display_name": "Core",
+  "keywords": ["intake", "critique", "review", "hygiene"],
+  "links": {
+    "documentation": "https://sananthanarayan.github.io/skilldrop/packs/core/"
+  },
+  "maintainers": [
+    {
+      "name": "sananthanarayan"
+    }
+  ],
+  "first-value": {
+    "audience-posture": "non-technical",
+    "prerequisites": [],
+    "starter-task": "Turn rough notes into a structured brief, then get a verdict on the draft",
+    "starter-prompt": "Here are my notes from today's planning call: <paste them>. Turn them into a brief, then critique the draft you write from it.",
+    "verification": "brief-intake returns a structured brief with gaps tagged, and doc-critique ends with a verdict: SHIP IT, SHIP WITH CHANGES, MAJOR REWRITE or WRONG ARTIFACT.",
+    "recovery": "If neither skill activates, check that `brief-intake/SKILL.md` and `doc-critique/SKILL.md` exist in your skills folder (`~/.claude/skills/` by default). In Claude Code, start a new session after installing."
+  },
+  "journey": {
+    "when": "You have rough notes, a transcript or a ticket and want a finished document, not a first draft.",
+    "you_bring": [
+      "the raw material: notes, a Slack thread, a transcript or a ticket",
+      "the kind of document you want at the end, such as an ADR, a runbook or an exec summary",
+      "answers to the gaps the brief flags as missing"
+    ],
+    "time": "20–45 minutes",
+    "steps": [
+      {
+        "skill": "brief-intake",
+        "you_do": "Paste the raw material and name the document you want it to become.",
+        "you_get": "A structured brief with every field tagged explicit, implied, inferred or missing, plus a list of what the next step will refuse to start without.",
+        "decide": "Answer or explicitly accept each missing field before drafting; the brief never fills them in for you."
+      },
+      {
+        "skill": "doc-critique",
+        "you_do": "Hand over the draft you wrote from the brief, by hand or with any generator skill.",
+        "you_get": "A critique that opens with a verdict and lists findings as blocker, major, minor or nit, each pointing to the section and suggesting a fix.",
+        "decide": "Gate G4: SHIP IT or SHIP WITH CHANGES moves on; MAJOR REWRITE sends you back to the brief; WRONG ARTIFACT means you need a different kind of document."
+      },
+      {
+        "skill": "output-hygiene",
+        "you_do": "Run it on the settled draft and say where it is going (markdown, commit message, plain text).",
+        "you_get": "The draft with invisible Unicode, provenance trailers and chat closers stripped, prose tells quoted with rewrites, and a 'Not touched' list."
+      }
+    ],
+    "you_end_with": "A reviewed, cleaned document with its verdict, the changes it carried, and a note of what the scrub did not touch."
+  }
+}

skilldrop_cli/data/packs/core/skills/brief-intake/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: brief-intake
+description: Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, deck-builder, tech-comparison-matrix) can consume without further intake. Use whenever the user has unstructured source material and is about to invoke another skilldrop skill, or when a draft is missing the load-bearing context the next step will need.
+---
+
+# brief-intake
+
+You help the user (or the next skill in the chain) absorb raw unstructured input and emit a clean, structured brief shaped for whatever artifact comes next. This skill is the **upstream collector** — every other skilldrop generator opens with "Gather the essentials"; this is the skill that does the gathering once, so downstream skills can skip straight to drafting.
+
+## How to respond
+
+1. **Identify the downstream target.** Ask if the user hasn't said: *"What are you going to do with this brief?"* Map the answer to one of:
+
+   | Downstream skill | Trigger phrases |
+   |---|---|
+   | `adr-generator` | "ADR", "decision record", "capture a decision", "we decided X" |
+   | `design-doc` | "design doc", "tech proposal", "one-pager for review", "RFC" |
+   | `runbook-generator` | "runbook", "on-call doc", "operational doc", "prod-readiness" |
+   | `tech-comparison-matrix` | "compare X vs Y", "vendor selection", "tech selection" |
+   | `exec-summary` | "exec summary", "1-pager for the VP", "board update" |
+   | `deck-builder` / `slide-outliner` | "deck", "slides", "presentation", "pitch", "review meeting" |
+   | `decision-log` | "decisions and action items", "follow-ups from the meeting" |
+   | _(generic)_ | None of the above — emit the generic brief and let the user pick later |
+
+2. **Ingest the source.** The user will paste text, give a file path, or describe verbally. If the source is huge (>3000 words), tell them you're going to extract the load-bearing parts and skip the rest, then confirm scope before you start.
+
+3. **Extract once, into the target's shape.** Each downstream skill needs a specific set of fields. Use the matching template:
+
+   - `templates/brief-adr.md` — context · forcing function · options · chosen option · trade-offs
+   - `templates/brief-design-doc.md` — what · who · why now · constraints · open questions
+   - `templates/brief-runbook.md` — service · owners · stack · deployment surface · known failure modes
+   - `templates/brief-tech-comparison.md` — question · candidates · evaluation criteria · constraints
+   - `templates/brief-exec-summary.md` — ask · audience · business impact · what you need
+   - `templates/brief-deck.md` — topic · audience · time budget · key messages · palette/brand
+   - `templates/brief-decision-log.md` — source · scope · today's date
+   - `templates/brief-generic.md` — fallback when target is unknown
+
+4. **Mark every field with a confidence tag.** Each extracted field is tagged inline:
+
+   - `[explicit]` — stated outright in the source
+   - `[implied]` — clearly inferable from the source (quote the snippet)
+   - `[inferred]` — your judgement, not in the source — the user should verify
+   - `[missing]` — not in the source; the downstream skill will need to ask
+
+   This is the audit trail. The downstream skill (or the user) can then trust `[explicit]` fields and challenge the `[inferred]` ones.
+
+5. **Surface the gaps explicitly.** End with a "🚩 Missing for downstream" section listing fields that came back `[missing]` and which ones are load-bearing enough that the downstream skill will refuse to start without them. For example: "`adr-generator` will refuse to draft without at least 2 considered options — only 1 found in the source."
+
+6. **Don't draft the artifact yourself.** This skill stops at the structured brief. Hand off explicitly: *"Brief ready. Run `/adr-generator` with this brief as input."*
+
+## Quality bar
+
+- **Quote, don't paraphrase, when extracting.** When a field is `[explicit]` or `[implied]`, include a 5–15 word verbatim snippet from the source so the downstream skill (and the user) can verify nothing was hallucinated.
+- **Convert relative dates to absolute dates.** "Next Friday", "EOQ", "the sprint after this one" all become `YYYY-MM-DD` with `(implied)` if you had to compute it. Today's date is in the system context — use it.
+- **Don't invent people.** If the source says "someone from platform should…", the owner is `unowned`, not a guess.
+- **Don't merge across sources unless the user asked.** If the user pastes a Slack thread *and* a doc, ask whether you should treat them as one brief or extract separately.
+- **Strip noise aggressively.** Greetings, off-topic banter, "lol", and emoji reactions get dropped. The brief is the signal, not the conversation.
+
+## When to use this skill
+
+- ✅ Before invoking any other skilldrop generator when the input is messy.
+- ✅ When a user pastes a 90-minute transcript and says "I need an ADR from this".
+- ✅ When the next step's `SKILL.md` says "Gather the essentials" and the user has unstructured source material.
+- ✅ As a checkpoint after `decision-log` — to turn a single extracted decision into an `adr-generator` brief.
+
+## When NOT to use this skill
+
+- ❌ When the user has already given a clean, structured brief — go straight to the downstream skill.
+- ❌ For pure summarization — that's not what this is. The output is shaped for a *specific next step*, not a generic summary.
+- ❌ For raw transcript cleanup. If the user wants meeting notes cleaned up, use `decision-log`.
+
+## Anti-patterns to avoid
+
+- ❌ Padding `[inferred]` fields to make the brief look complete. Empty `[missing]` is more honest and more useful.
+- ❌ Restating the source verbatim. The brief is *shaped*, not a copy.
+- ❌ Skipping the gaps section because the brief looks fine — the gaps are the *most useful output* for the user about to invoke the downstream skill.
+- ❌ Asking 4+ clarifying questions. If the source is too thin, say so once and let the user decide whether to add material or proceed with gaps flagged.
+- ❌ Emitting the brief in prose. Downstream skills want structured fields, not paragraphs.
+- ❌ **Showing the machinery.** The reply and the artifact are for the person who asked. Don't mention this skill, its files, templates, caps or internal terms, or that the run is non-interactive. Name another skill once, at the end, as a suggested next step, never inside the artifact.

skilldrop_cli/data/packs/core/skills/brief-intake/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Turn this Slack thread into a structured brief",
+    "should_trigger": true
+  },
+  {
+    "query": "I have a messy transcript — get it into shape for the design-doc skill",
+    "should_trigger": true
+  },
+  {
+    "query": "Structure this raw context into a brief before I run the next skill",
+    "should_trigger": true
+  },
+  {
+    "query": "Take this half-written Notion page and extract a clean brief",
+    "should_trigger": true
+  },
+  {
+    "query": "Extract the decisions, owners, and due dates from this discussion",
+    "should_trigger": false
+  },
+  {
+    "query": "Write the ADR itself from this context",
+    "should_trigger": false
+  },
+  {
+    "query": "Critique this brief's quality",
+    "should_trigger": false
+  },
+  {
+    "query": "Summarize this thread for the executive team",
+    "should_trigger": false
+  }
+]

skilldrop_cli/data/packs/core/skills/brief-intake/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill_name": "brief-intake",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Here's a messy Slack thread about our caching problem — turn it into a brief I can hand to design-doc.",
+      "assertions": [
+        "Extracted fields marked [explicit] or [implied] carry a short verbatim snippet from the source so nothing is hallucinated",
+        "Relative dates are converted to absolute YYYY-MM-DD, marked implied where computed",
+        "Gaps are named as missing rather than filled in with plausible invention",
+        "The output names the downstream skill the brief is shaped for",
+        "The brief is structured into the fields that downstream skill needs, not a summary"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/core/skills/brief-intake/manifest.json

@@ -0,0 +1,11 @@
+{
+  "name": "brief-intake",
+  "version": "0.1.1",
+  "description": "Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, deck-builder, tech-comparison-matrix) can consume without further intake. Use whenever the user has unstructured source material and is about to invoke another skilldrop skill, or when a draft is missing the load-bearing context the next step will need.",
+  "entrypoint": "SKILL.md",
+  "deps": { "npm": [], "pip": [] },
+  "env": { "required": [], "optional": [] },
+  "related": ["adr-generator", "decision-log", "deck-builder", "design-doc", "exec-summary", "runbook-generator", "slide-outliner", "tech-comparison-matrix"],
+  "tags": ["intake", "brief", "extraction", "preprocessing", "pipeline"],
+  "model": { "tier": "standard", "rationale": "Extraction + [explicit]/[implied]/[inferred] tagging. The tagging needs care — above haiku, below opus." }
+}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-adr.md

@@ -0,0 +1,41 @@
+# Brief: ADR
+
+> Target downstream skill: `adr-generator`
+
+## Decision
+{One-sentence noun phrase — the decision, not the question} [explicit|implied|inferred|missing]
+> "{verbatim snippet from source}"
+
+## Context / forcing function
+{Why is a decision needed *now*? What changed?} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Decision drivers
+- {Driver 1 — constraint, requirement, or non-negotiable} [explicit|implied|inferred|missing]
+- {Driver 2}
+- {Driver 3}
+
+## Options considered
+- **Option A** — {one-line description} [explicit|implied|inferred|missing]
+- **Option B** — {one-line description}
+- **Option C** — {one-line description, or omit if only two were considered}
+
+## Chosen option
+**{Option name}** — because {one-sentence rationale tied to a driver above} [explicit|implied|inferred|missing]
+
+## Consequences / trade-offs
+- ✅ {what becomes easier} [explicit|implied|inferred|missing]
+- ⚠️ {acceptable trade-off}
+- ❌ {what becomes harder or constrains future choices}
+
+## Format hint
+{`MADR` (default) | `Nygard` (if source frames it as a simple decision)}
+
+## Numbering hint
+{ADR directory mentioned in source, e.g. `docs/adr/` — or `unknown` so adr-generator asks}
+
+---
+
+## 🚩 Missing for downstream
+- {field: why it matters to adr-generator}
+- {e.g. "Only 1 option captured — adr-generator requires ≥2 considered options"}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-decision-log.md

@@ -0,0 +1,35 @@
+# Brief: Decision Log
+
+> Target downstream skill: `decision-log`
+
+This brief is lightweight — most of `decision-log`'s work is *its own* extraction. `brief-intake` mostly normalizes the source before handing it over.
+
+## Source
+- **Type:** {Slack thread | meeting transcript | email chain | Notion page | mixed} [explicit|implied|inferred|missing]
+- **Date of meeting / thread:** {YYYY-MM-DD} [explicit|implied|inferred|missing]
+- **Attendees / participants:** {names if stated, "unknown" otherwise} [explicit|implied|inferred|missing]
+- **Length:** {word count or minutes if known} [inferred]
+
+## Scope the user wants extracted
+- [ ] Decisions
+- [ ] Action items
+- [ ] Open questions
+- [ ] Risks raised
+
+(Default: all four if user didn't specify.)
+
+## Today's date
+{YYYY-MM-DD} — needed for converting relative dates ("next Friday", "EOQ") to absolute. [explicit]
+
+## Sprint / fiscal context
+- **Current sprint ends:** {YYYY-MM-DD} [explicit|implied|inferred|missing]
+- **Quarter ends:** {YYYY-MM-DD} [explicit|implied|inferred|missing]
+
+## Cleaned source
+{Paste the source with the obvious noise stripped — greetings, off-topic banter, emoji-only messages. Keep ambiguous parts; decision-log decides what's load-bearing.}
+
+---
+
+## 🚩 Missing for downstream
+- {e.g. "No date — decision-log can't convert 'Friday' to an absolute date"}
+- {e.g. "Attendees unknown — owners can't be attributed to names"}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-deck.md

@@ -0,0 +1,43 @@
+# Brief: Deck
+
+> Target downstream skills: `slide-outliner` → `deck-builder` (and `audience-profile` for the structural rules)
+
+## Topic / working title
+{One line} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Audience
+- **Free-form description from source:** {as quoted} [explicit|implied|inferred|missing]
+- **Mapped archetype:** {exec | board | technical | sales | investor | internal | partner | customer} [inferred]
+- **If mixed audience:** least-technical archetype above + appendix for the rest
+
+## Time budget
+- **Speaking time:** {minutes} [explicit|implied|inferred|missing]
+- **Reading time (if pre-read):** {minutes} [explicit|implied|inferred|missing]
+- **Implied slide count:** {derived from time × audience archetype}
+
+## The one thing the audience should leave with
+{Single sentence — the headline message} [explicit|implied|inferred|missing]
+
+## Key messages (3–5)
+1. {Message} [explicit|implied|inferred|missing]
+2. {Message}
+3. {Message}
+
+## Evidence available
+- **Quantified data:** {numbers the source provides — for `big_number` slides} [explicit|implied|inferred|missing]
+- **Quotes:** {customer / exec / analyst quotes for `quote` slides} [explicit|implied|inferred|missing]
+- **Diagrams:** {existing diagrams that should be embedded} [explicit|implied|inferred|missing]
+
+## Brand / palette
+- **Palette source:** {named preset | hex values | "use our brand colors"} [explicit|implied|inferred|missing]
+- **Specific colors mentioned:** {hex / role} [explicit|implied|inferred|missing]
+
+## Constraints
+- {e.g. "no logos other than ours", "must include compliance disclaimer", "30s pre-roll for the cover"} [explicit|implied|inferred|missing]
+
+---
+
+## 🚩 Missing for downstream
+- {e.g. "Audience not specified — deck-builder will refuse to start"}
+- {e.g. "No palette — deck-builder will ask before building"}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-design-doc.md

@@ -0,0 +1,48 @@
+# Brief: Design Doc
+
+> Target downstream skill: `design-doc`
+
+## What we're building
+{One sentence} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Who's affected
+- **Users / callers:** {who consumes this} [explicit|implied|inferred|missing]
+- **Teams:** {who owns or depends on it}
+- **Systems:** {upstream/downstream services}
+
+## Why now (forcing function)
+{What changed? Outage, regulatory, scaling cliff, competitor, deadline} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Goals
+- {Goal 1} [explicit|implied|inferred|missing]
+- {Goal 2}
+- {Goal 3}
+
+## Non-goals
+- {Real non-goal — something a reasonable reader might assume you *are* doing} [explicit|implied|inferred|missing]
+- {Another non-goal}
+
+## Constraints
+- {Hard constraint — tech, regulatory, budget, timeline} [explicit|implied|inferred|missing]
+- {Soft constraint}
+
+## Alternatives the source mentions
+- {Alternative 1 — and why-not if stated} [explicit|implied|inferred|missing]
+- {Alternative 2}
+
+## Risks raised in the source
+- {Risk — and any proposed mitigation} [explicit|implied|inferred|missing]
+
+## Open questions
+- {Question — and who should answer if stated} [explicit|implied|inferred|missing]
+
+## Target length
+{1-pager | 2–5 pages (default) | longer with explicit reason}
+
+---
+
+## 🚩 Missing for downstream
+- {field: why it matters}
+- {e.g. "No 'why now' captured — design-doc refuses to draft without a forcing function"}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-exec-summary.md

@@ -0,0 +1,47 @@
+# Brief: Exec Summary
+
+> Target downstream skill: `exec-summary`
+
+## The Ask
+{One line — what decision / approval / resource are we requesting?} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Audience
+- **Role:** {VP / C-suite / board / partner CTO / steering committee} [explicit|implied|inferred|missing]
+- **Technical depth:** {none / light / fluent} [explicit|implied|inferred|missing]
+- **Reading time:** {30s / 1 min / 3 min — default 60s for a 1-pager} [explicit|implied|inferred|missing]
+- **What they already know:** {context to skip} [explicit|implied|inferred|missing]
+
+## The project, in one sentence
+{What it is — plain language, no jargon} [explicit|implied|inferred|missing]
+
+## Why now
+{Forcing function — competitor, regulation, outage, market window} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Recommendation
+{What you want them to agree to} [explicit|implied|inferred|missing]
+
+## Business impact (quantified where possible)
+- **Revenue:** {$X ARR / $Y new revenue / 0 if n/a} [explicit|implied|inferred|missing]
+- **Cost:** {savings or spend} [explicit|implied|inferred|missing]
+- **Risk:** {what's at stake if we *don't* do this} [explicit|implied|inferred|missing]
+- **Time:** {when does the impact land} [explicit|implied|inferred|missing]
+
+## Cost & timeline
+- **Investment:** {$ / FTEs / months} [explicit|implied|inferred|missing]
+- **Timeline:** {phases + dates} [explicit|implied|inferred|missing]
+
+## Top 3 risks (project-specific, not generic)
+1. {Risk} — mitigation: {mitigation} [explicit|implied|inferred|missing]
+2. {Risk} — mitigation: {mitigation}
+3. {Risk} — mitigation: {mitigation}
+
+## What we need from the audience
+- {Concrete ask — money / headcount / decision / introduction} [explicit|implied|inferred|missing]
+
+---
+
+## 🚩 Missing for downstream
+- {field: why it matters}
+- {e.g. "No quantified business impact — exec-summary will have to use 'directional' language"}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-generic.md

@@ -0,0 +1,45 @@
+# Brief: Generic
+
+> Target downstream skill: _unknown_ — emit this when the user hasn't picked a next step yet.
+
+This is the fallback shape. It's a superset of the most useful fields across all targets — the user (or you, next turn) picks the downstream skill and the relevant fields move into its specific brief.
+
+## One-line summary
+{What is this about?} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Type of artifact the user might want next
+{Best guess based on the source — and why}
+- {e.g. "Looks like a decision being captured → adr-generator"}
+- {e.g. "Looks like a runbook brief — service name + on-call mentioned"}
+
+## Subject
+- **What it's about (object):** {service / decision / project / vendor selection} [explicit|implied|inferred|missing]
+- **Who's involved:** {teams, people, customers} [explicit|implied|inferred|missing]
+- **Why now:** {forcing function if any} [explicit|implied|inferred|missing]
+
+## Key facts (load-bearing)
+- {Fact 1 — quote} [explicit|implied|inferred|missing]
+- {Fact 2}
+- {Fact 3}
+
+## Decisions / asks present in the source
+- {Anything that looks like a decision or an ask} [explicit|implied|inferred|missing]
+
+## Open questions / unknowns
+- {Things explicitly unresolved in the source} [explicit|implied|inferred|missing]
+
+## Dates / deadlines
+- {Date → what it's tied to (absolute, with `(implied)` if computed)} [explicit|implied|inferred|missing]
+
+## Names / owners
+- {Name → role / responsibility} [explicit|implied|inferred|missing]
+
+## Numbers / metrics
+- {Number → what it measures} [explicit|implied|inferred|missing]
+
+---
+
+## 🚩 Next step
+Pick a downstream skill, then run `brief-intake` again with that target to get the precisely-shaped brief. Suggested:
+- {Skill name} — because {reason from this source}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-runbook.md

@@ -0,0 +1,44 @@
+# Brief: Runbook
+
+> Target downstream skill: `runbook-generator`
+
+## Service
+- **Name:** {service-name} [explicit|implied|inferred|missing]
+- **One-line purpose:** {what it does} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Owners
+- **Team:** {team name — role-based, not individual} [explicit|implied|inferred|missing]
+- **Primary on-call rotation:** {rotation name / PagerDuty schedule} [explicit|implied|inferred|missing]
+- **Escalation chain:** {who's next if primary is unavailable} [explicit|implied|inferred|missing]
+
+## Tech stack
+- **Language / runtime:** {e.g. Go 1.22, Python 3.12} [explicit|implied|inferred|missing]
+- **Storage:** {e.g. Postgres 15, Redis, S3} [explicit|implied|inferred|missing]
+- **Message brokers / queues:** {e.g. Kafka, SQS — or `n/a`} [explicit|implied|inferred|missing]
+- **External dependencies:** {APIs, vendor services} [explicit|implied|inferred|missing]
+
+## Deployment surface
+- **Platform:** {Kubernetes / ECS / Lambda / VMs} [explicit|implied|inferred|missing]
+- **Namespace / cluster / region:** {coordinates} [explicit|implied|inferred|missing]
+- **Deploy mechanism:** {GitHub Actions / ArgoCD / manual / …} [explicit|implied|inferred|missing]
+
+## Known failure modes (the "common 5")
+- {Failure 1 — symptom + suspected cause if known} [explicit|implied|inferred|missing]
+- {Failure 2}
+- {Failure 3}
+- {Failure 4}
+- {Failure 5}
+
+## Existing dashboards / alerts referenced in source
+- {Dashboard URL or name} [explicit|implied|inferred|missing]
+- {Alert name → page severity}
+
+## SLOs (if any)
+- {Metric → target, e.g. "p99 latency < 200ms"} [explicit|implied|inferred|missing]
+
+---
+
+## 🚩 Missing for downstream
+- {field: why it matters}
+- {e.g. "No owner team — runbook-generator refuses to draft without current ownership"}

skilldrop_cli/data/packs/core/skills/brief-intake/templates/brief-tech-comparison.md

@@ -0,0 +1,38 @@
+# Brief: Tech Comparison
+
+> Target downstream skill: `tech-comparison-matrix`
+
+## The question
+{One sentence — what's being chosen and what for. e.g. "Pick a primary OLTP datastore for the new checkout service."} [explicit|implied|inferred|missing]
+> "{verbatim snippet}"
+
+## Candidates
+- **{Candidate A}** — {one-line positioning if source has it} [explicit|implied|inferred|missing]
+- **{Candidate B}**
+- **{Candidate C}**
+
+## Evaluation criteria (with weights if source implies them)
+- **{Criterion 1}** ({weight if known}) — {what "good" looks like} [explicit|implied|inferred|missing]
+- **{Criterion 2}**
+- **{Criterion 3}**
+- **{Criterion 4}**
+- **{Criterion 5}**
+
+## Constraints / non-negotiables
+- {Existing estate, e.g. "must run on AWS"} [explicit|implied|inferred|missing]
+- {Team skills, e.g. "team has 5 years of Postgres"}
+- {Compliance, e.g. "data must stay in eu-west-1"}
+
+## Workload profile
+- **Read/write ratio:** {ratio} [explicit|implied|inferred|missing]
+- **Scale targets:** {QPS, data volume, growth} [explicit|implied|inferred|missing]
+- **Consistency needs:** {strong / eventual / tunable} [explicit|implied|inferred|missing]
+
+## Tentative leaning (if stated)
+{"Source seems to favour X because Y" — flag so matrix can be honest about bias} [explicit|implied|inferred|missing]
+
+---
+
+## 🚩 Missing for downstream
+- {e.g. "Only 1 candidate captured — comparison needs ≥2"}
+- {e.g. "No evaluation criteria — matrix will default to a generic set"}