to-prd

Files (3)

• SKILL.md
• openai.yaml · agents/
• 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