to-prd

Generated source view for the actual executable engineering/to-prd skill. The durable routing article is Agent Engineering Skills. Source: skills/engineering/to-prd/SKILL.md

Runtime Source

Field Value
Category engineering
Origin personal
Slug to-prd
Source slug to-prd
Family Agent Engineering Skills
Source skills/engineering/to-prd/SKILL.md

Bundled Resources

No bundled resource files.

Description

Turn the current conversation, notes, or prototype findings into a PRD/spec without re-interviewing. Use when the user says "/to-spec", "write a PRD", "turn this into a spec", "make this a product brief", "capture the plan", or when a planning session needs a durable product spec. Adapted from mattpocock/skills.

Skill Source

---
name: to-prd
description: Turn the current conversation, notes, or prototype findings into a PRD/spec without re-interviewing. Use when the user says "/to-spec", "write a PRD", "turn this into a spec", "make this a product brief", "capture the plan", or when a planning session needs a durable product spec. Adapted from mattpocock/skills.
origin: personal
source_slug: to-prd
---

# To PRD

Synthesize what has already been discussed. Do not restart the interview unless a
load-bearing requirement is missing.

## First Move

1. Read the current conversation context, linked docs, and any prototype findings.
2. Search for an existing PRD/spec/plan to update.
3. Choose an output location:
   - app repo: `docs/prd/<slug>.md`, `docs/specs/<slug>.md`, or the repo's existing convention
   - `kevin-wiki`: `plans/<slug>.md` or `wiki/inbox/prds/<slug>.md`
   - issue tracker: only if Kevin explicitly wants GitHub/Linear writes

## PRD Shape

```markdown
# <Feature / Product>

## Problem

## Solution

## User Stories

## Implementation Decisions

## Testing Decisions

## Out Of Scope

## Open Questions

## Timeline
```

Use product language, not stale file-path predictions. Include code snippets only when a
prototype produced a precise decision that prose would blur.

## Testing Decision

Name the highest honest seam for proof: API route, CLI, UI flow, public function,
integration test, or browser check.

## Related Skills

- `grill-with-docs` before PRD when alignment is still fuzzy.
- `prototype` when a PRD question needs evidence.
- `to-issues` after PRD when it is ready to execute.

Upstream: `github.com/mattpocock/skills/skills/engineering/to-prd/SKILL.md`
at `5d78bd0903420f97c791f834201e550c765699f8`.

Timeline

1 page links here