{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "cbrock84-headcount--review-design-before-build",
 "repo": "cbrock84/headcount",
 "repo_url": "https://github.com/cbrock84/headcount",
 "repo_slug": "cbrock84-headcount",
 "title": "Review a design for threats before building it",
 "page_title": "How to review a design for threats before building it with Headcount",
 "summary": "Load the security threat-modeling skill to find assets, entry points, and trust boundaries in a planned design.",
 "who": "An engineer or tech lead with a design doc for a new feature who wants security issues found before code is written.",
 "problem": "Security gaps in a design are cheaper to fix before build, but reviewing them needs a specialist lens that is easy to skip.",
 "outcome": "A threat model for the design that names the assets worth attacking, the entry points, the trust boundaries, and the controls that address them.",
 "steps": [
  "In Claude Code, run `/plugin marketplace add cbrock84/headcount`.",
  "Run `/plugin install security@headcount`.",
  "Ask in plain words, for example \"review this design before we build it\", and attach or paste the design doc.",
  "To call the skill directly, run `/security:threat-modeling`. (inferred, check the README)"
 ],
 "agent_prompt": "Using the cbrock84/headcount repo, load the security:threat-modeling skill and run it against the design in <design-doc-path>. Expected output: a list of assets, entry points, trust boundaries, and controls for that design. Verify that every trust boundary named in the output appears in the design doc.",
 "agents": [
  "claude-code"
 ],
 "difficulty": "Beginner",
 "time": "15 minutes",
 "basis": "readme",
 "caveat": "The README describes the security department as reviewer-class, so expect it to flag stop conditions rather than only offer opinions.",
 "category": "Work and operations",
 "tags": [
  "Work and operations"
 ],
 "lang": "markdown",
 "requirements": [
  "Claude Code, or ChatGPT or Codex with the repository added as a plugin marketplace",
  "A project or document that the skills can read, such as a design doc, a page, or a figures summary",
  "Permission to add a plugin marketplace to your coding tool"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": true,
 "score": 1.0,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/cbrock84-headcount/review-design-before-build/",
 "md": "https://dedupedai.com/use-cases/cbrock84-headcount/review-design-before-build/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/cbrock84-headcount--review-design-before-build.json",
 "api_version": "v1"
}