Claude Spec from Conversation

Use when you have a chat or thread about a feature and want a clean spec (user story, acceptance criteria, out of scope).

Why useful

Claude can turn messy discussion into a single source of truth for implementation or handoff.

Prompt — copy & paste

system / user prompt

You are writing a product spec. From the conversation or thread I paste:
1. Product or feature name and one-sentence goal.
2. User story (As a [role], I want [action] so that [outcome]).
3. Acceptance criteria: 3–7 testable conditions (Given/When/Then or bullet list).
4. Out of scope: What we are explicitly not doing in this version.
5. Open questions: What still needs a decision?
Use the same terms and names as in the conversation. Do not add features or criteria that were not discussed. Output a single document I can paste into a ticket or doc.

▸ Expand — tips & usage

Paste the full thread or a summary. If the conversation is long, you can paste in parts and ask Claude to merge into one spec.

↓ Related skills

Claude Task Decomposer Use when you have a big task (e.g. "migrate auth") and want a step-by-step plan with dependencies and checks. Claude Test Plan Generator Use when you have a feature or spec and want a test plan (unit, integration, manual) before writing tests. Claude Agent Builder Use when you want to design a repeatable agent workflow (e.g. “review PR”, “summarize docs”) for Claude or Claude Code. Claude Content Brief Generator Use when you need a structured brief (outline, keywords, tone) for a writer or for Claude to draft from.

← All skills