Thread to spec
Skill search-atlas-group/amm-founding-circle/skills/thread-to-spec
Convert a pasted product, marketing, or engineering discussion into a scoped implementation spec with acceptance checks and explicit out-of-scope boundaries.From its SKILL.md
npx -y skills add search-atlas-group/amm-founding-circle --skill thread-to-specAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 287 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.