sanurb/prd-discover
prd-discover/SKILL.md
Extract a validated problem brief through user interview and codebase exploration. Activate ONLY when the user says "new PRD", "plan a feature", or "write a PRD". Not for implementation specs, bug triage, or general feature discussion.
development
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add sanurb/skills prd-discoverInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 9:11 AM15.0s2 files scanned
SKILL.md
- name:
- prd-discover
- description:
- Extract a validated problem brief through user interview and codebase exploration. Activate ONLY when the user says "new PRD", "plan a feature", or "write a PRD". Not for implementation specs, bug triage, or general feature discussion.
PRD Discover
Extract the real problem before anyone talks about solutions. This skill produces one artifact: a problem brief that grounds every downstream decision.
Activation guard: Only run this skill when the user explicitly requests a PRD. Do not activate on general feature discussions, bug reports, or implementation questions.
Step 1: Interview the User About the Problem
Ask these five questions. Do NOT proceed until all five have answers.
- Who is struggling? — Name the specific user or persona.
- What is the pain? — Describe from the user's perspective, not the team's.
- What happens today? — Current workaround, manual process, or nothing.
- Why now? — What changed that makes this urgent.
- Any solution ideas? — Capture verbatim, but tag as
[SOLUTION IDEA].
If the user leads with a solution ("build feature X"), redirect:
"Before we go there — what user problem does X solve? Who experiences it? What do they do today without it?"
Do not accept "users want X" as a problem statement. Probe: "What evidence do we have that this solves a real problem?"
Step 2: Explore the Codebase
Scan the repository for context relevant to the problem:
- Architecture: modules, data models, API surface affected
- Existing patterns: how similar features are built today
- Constraints: technical debt, dependencies, or limitations
- Prior art: has something like this been attempted before?
Report findings to the user. If greenfield with no codebase, skip to Step 3.
Step 3: Produce the Problem Brief
Create the output directory and write the artifact:
mkdir -p /tmp/prd-{name}
Copy the template from assets/problem-brief-template.md and fill every section from the interview and codebase exploration.
Non-Negotiable Acceptance Criteria
The problem brief is NOT complete unless ALL of these are true:
- [ ] Problem stated from the user's perspective — not the team's or a stakeholder's
- [ ] No solution presented as a requirement — all tagged
[SOLUTION IDEA] - [ ] "Who" names a specific user or persona — not "users" generically
- [ ] "Why Now" has a concrete trigger — not "it would be nice"
- [ ] Codebase context section exists (or explicitly marked "greenfield")
- [ ] The brief fits on one page — if it doesn't, the problem is not focused enough
Output
- Artifact:
/tmp/prd-{name}/problem-brief.md - Next skill:
prd-interview
Related Skills
sanurb/setup-sanurb-skills
development
VerifiedTrustedCommunity
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub, GitLab, fp, or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `fp-plan`, `fp-implement`, `fp-review`, `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
SKILL.mdUpdated Jun 4, 2026
sanurb/prototype
development
VerifiedTrustedCommunity
Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
SKILL.mdUpdated Jun 4, 2026
sanurb/herdr
tools
VerifiedTrustedCommunity
Control herdr (a terminal-native agent multiplexer) from inside it. Manage workspaces and tabs, split panes, spawn sibling agents, read pane output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1). Do not use outside herdr.
SKILL.mdUpdated Jun 4, 2026
sanurb/handoff
documentation
VerifiedTrustedCommunity
Compact the current conversation into a handoff document for another agent to pick up.
SKILL.mdUpdated Jun 4, 2026