to-prd
Use only when explicitly invoked to synthesize the current conversation or supplied notes into a concise product requirements document without inventing…
Skill by JobsHwang
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/jobshwang-to-prd
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, design, productivity
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/to-prd
What's inside
- Skill name
to-prd- Description
- Use only when explicitly invoked to synthesize the current conversation or supplied notes into a concise product requirements document without inventing technical design.
- License
- MIT
- Instructions
- 16 lines in SKILL.md · view on GitHub
Files (2)
- SKILL.md
- prd-template.md · references/
SKILL.md (first lines)
# To PRD Convert already-established product context into a durable, reviewable brief. 1. Use the current conversation, a supplied artifact, or both as the source. Do not restart the interview. 2. Inspect the repository only for relevant product facts, terminology, and existing document conventions. 3. Preserve the user's language. Keep the document proportional to the change and use [references/prd-template.md](references/prd-template.md) selectively. 4. Capture why and what: outcome, users, scenarios, scope, non-goals, requirements, acceptance, constraints, assumptions, risks, and open questions. 5. Do not prescribe modules, APIs, schemas, libraries, or implementation steps. 6. If a material answer is still unknown, record it under Open Questions instead of automatically launching clarification. Use an explicitly requested path or an established local convention. Otherwise write `.scratch/<feature>/prd.md`, choosing a short semantic feature slug. Never overwrite a conflicting artifact silently. Report the written path, the key scope boundary, and any open questions. Suggest the next explicit action, usually `to-spec`, but do not invoke it.
From JobsHwang/skills, MIT.
More from JobsHwang/skills
- 0.563score
obsidian-doc-organizer
JobsHwang
Organize an Obsidian vault inbox or a user-selected set of notes by inspecting the vault's existing conventions, proposing safe destinations, normalizing…
SkillBFreshness: B★ 2Claude Code +9 - 0.559score
to-spec
JobsHwang
Use only when explicitly invoked to turn agreed requirements or a PRD into an actionable technical delivery contract grounded in the current repository.
SkillBFreshness: B★ 2Claude Code +9 - 0.557score
handoff
JobsHwang
Compact the current work into a concise handoff for another agent or session.
SkillBFreshness: B★ 2Claude Code +9 - 0.554score
arch-scan
JobsHwang
Use only when explicitly invoked to survey a repository for architectural deepening opportunities and report ranked, evidenced candidates without changing code.
SkillBFreshness: B★ 2Claude Code +9 - 0.554score
slice-spec
JobsHwang
Use only when explicitly invoked to split a large delivery spec into independently verifiable vertical slices with explicit dependency edges.
SkillBFreshness: B★ 2Claude Code +9 - 0.549score
grill-me
JobsHwang
Use only when explicitly invoked to deeply interview the user about a plan, product idea, or design until every material decision branch is resolved.
SkillBFreshness: B★ 2Claude Code +9 - 0.549score
clarify
JobsHwang
Use only when explicitly invoked to resolve the minimum set of requirement questions that materially affect safe delivery.
SkillBFreshness: B★ 2Claude Code +9
Signals
- Stars
- 2
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Aug 3, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/JobsHwang/skills
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from JobsHwang
- 0.563score
obsidian-doc-organizer
JobsHwang
Organize an Obsidian vault inbox or a user-selected set of notes by inspecting the vault's existing conventions, proposing safe destinations, normalizing…
SkillBFreshness: B★ 2Claude Code +9 - 0.559score
to-spec
JobsHwang
Use only when explicitly invoked to turn agreed requirements or a PRD into an actionable technical delivery contract grounded in the current repository.
SkillBFreshness: B★ 2Claude Code +9 - 0.557score
handoff
JobsHwang
Compact the current work into a concise handoff for another agent or session.
SkillBFreshness: B★ 2Claude Code +9 - 0.554score
arch-scan
JobsHwang
Use only when explicitly invoked to survey a repository for architectural deepening opportunities and report ranked, evidenced candidates without changing code.
SkillBFreshness: B★ 2Claude Code +9 - 0.554score
slice-spec
JobsHwang
Use only when explicitly invoked to split a large delivery spec into independently verifiable vertical slices with explicit dependency edges.
SkillBFreshness: B★ 2Claude Code +9 - 0.549score
grill-me
JobsHwang
Use only when explicitly invoked to deeply interview the user about a plan, product idea, or design until every material decision branch is resolved.
SkillBFreshness: B★ 2Claude Code +9
Cite this page
to-prd skill. Agent Mart. https://agentmart.dev/skills/jobshwang-to-prd (last updated 2026-10-24)