Plaid
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption.
Install Prd V10 Case Study Builder
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-case-study-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-v10-case-study-builder .claude/skills/prd-v10-case-study-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prd-v10-case-study-builder" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builder into .claude/skills/prd-v10-case-study-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v10-case-study-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-case-study-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prd-v10-case-study-builder .agents/skills/prd-v10-case-study-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prd-v10-case-study-builder" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builder into .agents/skills/prd-v10-case-study-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v10-case-study-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-case-study-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prd-v10-case-study-builder .cursor/skills/prd-v10-case-study-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prd-v10-case-study-builder" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builder into .cursor/skills/prd-v10-case-study-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v10-case-study-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mattgierhart/PRD-driven-context-engineering.git --path .claude/skills/prd-v10-case-study-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-case-study-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prd-v10-case-study-builder .gemini/skills/prd-v10-case-study-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prd-v10-case-study-builder" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builder into .gemini/skills/prd-v10-case-study-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v10-case-study-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-case-study-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prd-v10-case-study-builder .github/skills/prd-v10-case-study-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prd-v10-case-study-builder" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builder into .github/skills/prd-v10-case-study-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v10-case-study-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-case-study-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prd-v10-case-study-builder .opencode/skills/prd-v10-case-study-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prd-v10-case-study-builder" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v10-case-study-builder into .opencode/skills/prd-v10-case-study-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v10-case-study-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
prd-v10-case-study-builder- GitHub stars
- 180
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,112 words
- Files
- 1
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption.
- Works in 6 steps: Identify candidate customers — Pull from… → Run the case-study interview — Extended… → Structure the story — Situation →… → …
- Requests to build case studies
- SKILL.md covers Execution Mode, What This Does, How It Works and Example, plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prd V10 Case Study Builder is an agent skill from mattgierhart/PRD-driven-context-engineering. Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Triggers on requests to build case studies, produce customer stories, create reference content, or when user asks "build a case study", "customer story", "reference account", "case study interview", "before/after story", "social proof page", "logo wall". Outputs CFD-CASE- evidence entries, GTM-CASE- marketing assets, and updates ADO-REF- with story status.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Storytelling, PRD writing and Physical and earth sciences. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.
When your agent uses it
- Requests to build case studies
- Produce customer stories
- Create reference content
- User asks build a case study
Example prompts
- “build a case study”
- “customer story”
- “reference account”
- “/prd-v10-case-study-builder”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify candidate customers — Pull from ADO-REF-* candidates and CFD-* entries with strong outcome quantification. Must satisfy
- Run the case-study interview — Extended Mom Test interview (45–60 min), focused on
- Structure the story — Situation → Complication → Question → Resolution (the McKinsey SCQR pattern)
- Quantify outcome — Specific numbers beat vague claims
- Get customer review — Send draft to customer for accuracy + tone + legal. Iterate until approved.
- Produce in 3 formats
What it can do on your machine
Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Prd V10 Case Study Builder loads about 2.9k tokens when it runs. Until then it costs about 125 tokens; SKILL.md has 1,112 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 1,112 words, ~2,863 tokens.
Download SKILL.mdSave it as
.claude/skills/prd-v10-case-study-builder/SKILL.md (or your agent's skills folder).- name
- prd-v10-case-study-builder
- description
- Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Triggers on requests to build case studies, produce customer stories, create reference content, or when user asks "build a case study", "customer story", "reference account", "case study interview", "before/after story", "social proof page", "logo wall". Outputs CFD-CASE-* evidence entries, GTM-CASE-* marketing assets, and updates ADO-REF-* with story status.
- allowed-tools
- Read, Write, Edit, Glob, Grep
- context
- fork
- execution_modes.default
- standard
- execution_modes.supports
- quick, standard, deep
Case Study Builder
Position in workflow: v1.0 Mom Test Interview → v1.0 Case Study Builder → v1.0 Testimonial Collector, GTM channels
Execution Mode
Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.
| Mode | What this skill produces |
|---|---|
| quick | Short-format case (testimonial + 1-paragraph story + logo); single placement |
| standard | Full case study (1,500 words) + short and medium derivatives + customer-approved + 3 channel placements |
| deep | Long-form case (2,500–4,000 words) + multi-format derivatives (PDF, blog, video, conference talk) + measurable outcome quantified + outcome-attribution interview |
What This Does
Turns customer success — already documented as CFD-* evidence and ADO-REF-* candidates — into structured case studies. Case studies are the pragmatist buyer's #1 reference signal: they need to see a customer in their segment achieving the outcome they want, with enough detail to make it credible.
This is an operational "doing" skill, not a strategy skill. The strategic question (which segment, what story angle, what outcome to highlight) was answered by prd-v10-chasm-adoption-moore. This skill produces the artifact.
How It Works
- Identify candidate customers — Pull from ADO-REF-* candidates and CFD-* entries with strong outcome quantification. Must satisfy:
- In-beachhead (or in an adjacent segment where the story would still resonate)
- Has a quantifiable outcome to talk about
- Willing to be public (consent path is clear)
- Run the case-study interview — Extended Mom Test interview (45–60 min), focused on:
- Before-state (specific past: what life was like, what tools, what cost)
- Trigger (what changed; why they evaluated alternatives)
- Evaluation (who they considered; how they chose)
- Implementation (what happened in onboarding; what was hard)
- After-state (specific present: quantified outcome, time/money saved, what they can do now they couldn't)
- Structure the story — Situation → Complication → Question → Resolution (the McKinsey SCQR pattern):
- Situation: where they were before
- Complication: what broke / changed / hit a wall
- Question: what they needed to figure out
- Resolution: how they solved it (your product as one part of the answer, ideally credibly)
- Quantify outcome — Specific numbers beat vague claims:
- "Cut tier-selection time from 3 days to 30 minutes" beats "much faster"
- "Saved $12k/year on tool consolidation" beats "saves money"
- "85% activation rate (industry average 35%)" beats "great activation"
- Get customer review — Send draft to customer for accuracy + tone + legal. Iterate until approved.
- Produce in 3 formats:
- Short (testimonial — 1–2 sentences + name + role + logo): for landing pages, pricing page, ad creative
- Medium (1-paragraph + 3 bullet outcomes + logo + linked deeper): for "Customers" page, social, email
- Long (1,500–2,500 word case study): for blog, sales enablement, sales call followup
Example
Customer: Acme Logistics (beachhead segment: freight forwarders, 50-200 employees, US PNW). ADO-REF-002.
Interview: 50 minutes with Acme's VP Operations.
Quantified outcome:
- Tier-selection time: 3 days → 30 min (90% reduction)
- Annual savings from tool consolidation: $14k
- Onboarding time per new hire: 2 weeks → 3 days (after migrating to product)
SCQR:
- Situation: Acme used 4 disjointed tools to track shipments, with manual export every Friday for ops reporting
- Complication: Two new hires + a Q3 customer surge meant the manual export bottlenecked the team; ops director was working Saturdays to keep the dashboards current
- Question: How could Acme consolidate tooling without disrupting an in-flight Q4 customer onboarding?
- Resolution: Acme migrated to [product] over 3 weeks; consolidated 4 tools to 1; automated the Friday export. VP Operations reclaimed 6 hours/week. New hires onboard in 3 days instead of 2 weeks.
Three formats produced:
- Short: "We replaced 4 tools with [product] and cut new-hire onboarding from 2 weeks to 3 days." — [Name], VP Ops, Acme Logistics
- Medium: 1-paragraph + 3 bullet outcomes + Acme logo + "Read the full story →"
- Long: 1,800-word blog case study with screenshots, quotes, before/after metrics, and an embedded testimonial video.
What You Get Back
- CFD-CASE-* entries — One per case-study interview; the durable evidence record
- GTM-CASE-* entries (one per produced format) — Marketing assets with placement plan
- Updates to ADO-REF-* entries — Reference status: "draft pending" → "approved" → "published"
- Customer approval record — Signed approval + version-controlled draft history
Show full SKILL.md (479 more words)Show less
When to Use It
| Trigger | Mode |
|---|---|
| First reference customer in beachhead is ready to talk | standard |
| Chasm-crossing push needs 3+ in-segment case studies | deep |
| Pricing-page logo wall expansion | quick (short format only) |
| Sales enablement asset for new segment | standard |
| Investor / partner update | standard |
| Customer success milestone (e.g., 1-year anniversary) | quick |
Do not use for: customers outside beachhead during chasm crossing (their story doesn't resonate with pragmatists); customers without consent (legal risk); customers without quantifiable outcomes (story will feel vague).
Consumes
- CFD-* customer evidence (Mom Test discipline) — Source for candidate selection
- ADO-REF-* candidates (from prd-v10-chasm-adoption-moore) — Cultivated reference targets
- ADO-BEACHHEAD-* — Defines "in-segment" for case priority
- KPI-* outcomes — Defines what "outcome" means; case quantification must speak to these
- GTM-* positioning + offer — Tone, voice, and value claims must match positioning
- BR-POS-* — Constraints (e.g., "no enterprise procurement language")
Produces
- CFD-CASE-* entries in
SoT/SoT.customer_feedback.md - GTM-CASE-* entries (with Type=Case-Asset) for each produced format
- ADO-REF-* updates — Status, placement, consent tracking
- CFD-* gaps surfaced — If outcome can't be quantified, log as research gap
Output Template
CFD-CASE-XXX: Case Study — [Customer Name]
Type: Case-Study
Date: YYYY-MM-DD
Customer: [Logo / company name]
Customer fit: [In-beachhead | Adjacent segment]
Interview length: [minutes]
Interviewer: [Name]
Quantified outcome (the proof):
Before: [Specific number / state]
After: [Specific number / state]
Delta: [%change or $ value]
Time horizon: [over what period]
Story (SCQR):
Situation: [Where they were before]
Complication: [What changed / broke / hit a wall]
Question: [What they needed to figure out]
Resolution: [How it got solved — your product as part of the answer]
Quotes (verbatim, approved):
- "[Quote]" — [Name, Role]
- "[Quote]" — [Name, Role]
Customer approval:
Approved by: [Name, Role]
Approved version: vX
Date: YYYY-MM-DD
Scope: [logo only | quote | full case study | on-stage]
Linked formats:
Short: GTM-CASE-AAA
Medium: GTM-CASE-BBB
Long: GTM-CASE-CCC
Linked IDs: ADO-REF-XXX (cultivation), PER-YYY (segment fit), KPI-ZZZ (outcome), CFD-AAA (interview source)GTM-CASE-XXX: Case-Study Asset — [Format]
Type: Case-Asset
Format: [Short | Medium | Long]
Channel: [Landing page | Pricing page | Blog | Sales deck | Email | Ad creative]
Owner: [Person / role]
Status: [Draft | In review | Approved | Live]
Content: [The actual asset content — quote, paragraph, full case]
Placement plan:
- [URL or section, e.g., "/pricing — Acme logo wall, position 3"]
Attribution: utm_campaign=case-<customer>
Linked IDs: CFD-CASE-AAA (parent case), ADO-REF-BBB (reference account), GTM-YYY (positioning)Anti-Patterns
| Pattern | Signal | Fix |
|---|---|---|
| No quantified outcome | "Customer loves us!" | Specific numbers or skip; vague cases don't move pragmatists |
| Wrong segment | Featuring a startup case to a pragmatist enterprise audience | In-segment cases only during chasm crossing |
| No customer approval on record | Published with assumed approval | Always get signed approval; preserve version history |
| Marketing voice override | Customer's actual words rewritten into your marketing tone | Their voice; light edits for clarity only |
| Single-format publish | Long-form blog only | Three formats: short for placement, medium for browsing, long for depth |
| One-and-done | Case study published, never updated | Refresh quarterly with new outcome data; cases stale fast |
| Featuring failures-rebranded-as-wins | "We rebuilt their entire infrastructure" hides "we replaced a failed implementation" | Don't dress up bad stories; pragmatists smell it |
Quality Gates
Before publishing:
- Customer in-beachhead or rationale for cross-segment placement
- Outcome quantified with specific numbers
- SCQR structure complete (Situation, Complication, Question, Resolution)
- Verbatim quotes with name + role
- Customer approval on record (scope explicit)
- Three formats produced (short, medium, long) — or rationale for fewer
- Placement plan per format
- Voice matches GTM- positioning (and customer's actual words)
- BR-POS-* constraints honored
Downstream Connections
| Consumer | What it uses | Example |
|---|---|---|
| Launch Channels (ORB) | Cases become Owned and Borrowed channel content | Blog case = Owned; co-marketing case = Borrowed |
| Alternatives Pages | Cases anchor "when to pick us" sections with real proof | Page references Acme case for migration-from-X story |
| Cold Outreach (Tiered) | Cases referenced in Touch 3 of sequences | Tier 1 outreach mentions in-segment case study |
| Testimonial Collector | Short-format derivatives are testimonial-shaped | Auto-eligible for testimonial walls |
| AEO Audit | Cases become AI-citation sources | High-traffic case pages cited by AI search |
| Sales / Investor | Direct asset for sales calls and investor updates | "Here's how Acme uses [product]" |
Detailed References
- BrianRWagner's
case-study-builderskill (ai-marketing-claude-code-skills) - Joe Pulizzi, Epic Content Marketing (case study as content)
- Annette Franz, Customer Understanding (interview discipline)
- McKinsey's SCQR (Situation/Complication/Question/Resolution) framework
- (No bundled
references/— the case study itself is the artifact)
© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/prd-v10-case-study-builder of mattgierhart/PRD-driven-context-engineering.
Open the folder on GitHubat commit 30ed1b0
Compare with similar skills
Prd V10 Case Study Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prd V10 Case Study Builder this skillmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.9k | Automated safety check: Pass | MIT | |
| PlaidBuildGreatProducts/plaid | 218 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Product Manager SkillsDigidai/product-manager-skills | 185 | — | ~6.1k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| PmLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Pass | MIT | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 357 | — | ~1.9k | Automated safety check: Pass | None | |
| Feature Launch Playbookgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Product Manager Skills
Digidai/product-manager-skills
PM skill for Claude Code, Codex, Cursor, and Windsurf. An agent skill from Digidai/product-manager-skills.
Pm
LeoYeAI/openclaw-master-skills
You are the Product Manager. An agent skill from LeoYeAI/openclaw-master-skills.
Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
Feature Launch Playbook
gooseworks-ai/goose-skills
Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…
Exec Dashboard Blueprint
gtmagents/gtm-agents
Layout and storytelling guide for marketing analytics executive dashboards.
More from mattgierhart/PRD-driven-context-engineering
All 45 skills in this repoGhm Gate Check
mattgierhart/PRD-driven-context-engineering
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).
Ghm Harvest
mattgierhart/PRD-driven-context-engineering
Extracts durable insights from temp/ files to SoT during EPIC Phase E.
Ghm Id Register
mattgierhart/PRD-driven-context-engineering
Validates and registers new SoT IDs with cross-reference integrity.
Ghm Sot Builder
mattgierhart/PRD-driven-context-engineering
Creates new Source of Truth (SoT) files when existing templates don't fit your needs.
Prd V01 Problem Framing
mattgierhart/PRD-driven-context-engineering
Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.
Prd V01 User Value Articulation
mattgierhart/PRD-driven-context-engineering
Transform validated pain points into articulated user value statements for PRD v0.1 Spark.
Related
Questions about Prd V10 Case Study Builder
What does Prd V10 Case Study Builder do?
Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Prd V10 Case Study Builder is an agent skill from mattgierhart/PRD-driven-context-engineering.0 Market Adoption.
When should I use Prd V10 Case Study Builder?
Prd V10 Case Study Builder fits situations like: requests to build case studies; produce customer stories; create reference content; user asks build a case study.
How do I install Prd V10 Case Study Builder in Claude Code?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a claude-code`. Or copy the skill folder (.claude/skills/prd-v10-case-study-builder in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v10-case-study-builder in your project. Claude Code loads it when a task matches its description.
How do I install Prd V10 Case Study Builder in Codex?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a codex`. Or copy the skill folder (.claude/skills/prd-v10-case-study-builder in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v10-case-study-builder in your project. Codex loads it when a task matches its description.
Can I use Prd V10 Case Study Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-case-study-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-v10-case-study-builder, .gemini/skills/prd-v10-case-study-builder, .github/skills/prd-v10-case-study-builder and .opencode/skills/prd-v10-case-study-builder in your project.
What does Prd V10 Case Study Builder need to run?
SKILL.md names no scripts, command-line tools or credentials: Prd V10 Case Study Builder is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep.
Does Prd V10 Case Study Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Prd V10 Case Study Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Prd V10 Case Study Builder use?
Prd V10 Case Study Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prd V10 Case Study Builder use?
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Prd V10 Case Study Builder?
Skills that share tags, products or a category with Prd V10 Case Study Builder: Plaid (BuildGreatProducts/plaid, 218 stars), Product Manager Skills (Digidai/product-manager-skills, 185 stars), Pm (LeoYeAI/openclaw-master-skills, 2.2k stars) and Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 357 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prd V10 Case Study Builder?
mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.
Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.