thread-to-spec
Use this when a conversation needs to become executable work.
Input
Accept any of:
- pasted chat thread;
- meeting transcript;
- notes from a client call;
- product brief;
- GitHub issue;
- docs excerpt.
Do not require access to private tools. Pasted text is enough.
Process
- Identify the desired outcome.
- List decisions already made.
- List open questions.
- Define what is explicitly out of scope.
- Break the work into small vertical slices.
- Add verification for each slice.
Spec Template
# <Title>
## Outcome
<One paragraph.>
## Source
<Where the request came from.>
## Decisions
- <Locked decision.>
## Open Questions
- <Question, owner, default assumption.>
## In Scope
- <Work item.>
## Out of Scope
- <Thing not to touch and why.>
## Slices
1. <Slice name>
- Current:
- Target:
- Files or surfaces:
- Acceptance check:
## Verification
- <Command, browser check, review step, or manual proof.>
## Handoff Prompt
<A concise prompt another agent could execute.>
Quality Bar
The spec is ready only when a different person or agent can start without asking what "done" means.