To Spec
Gjør samtalen du allerede har hatt om til en repo-bevisst spesifikasjon i .plan/
Krever oppsett
Hva den gjør
Syntetiserer den nåværende samtalen og kodebasen til en spesifikasjon (PRD) skrevet til .plan/<slug>/spec.md, uten intervjutrinn. Den tvinger frem en test-seam sketch før skriving og et fixed section set: problem, solution, an exhaustive user-story list, implementation decisions, testing decisions and out-of-scope. Kalles frem ved å skrive /to-spec after you have finished discussing a feature.
Testrapport
Kjørte den mot en real 25-line Python CLI pluss a feature conversation, og diffed the result with a no-skill spec: 21 user stories against zero, and 0 file-path or code references against 4 that would rot on the first refactor. The seam step is where it earns its keep – it drove the test plan onto the existing main(argv) entry point and flagged that the note file has to be redirectable per test, a gap the baseline spec missed and that we confirmed by execution (a test-style call wrote straight into $HOME/.notes.json). It also caught four behaviours the baseline dropped, including what a rename of a non-existent label should do. The catch is the frontmatter carries disable-model-invocation, so it never activates from a phrasing like 'write this up as a spec' – you have to type /to-spec, which the repo's own skills/README documents honestly. It lives under skills/.optional/, a hidden directory you will not spot browsing the repo on GitHub.
Testet på: 2026-07-28 · Claude Code 2.x (agent harness)
Installer
git clone https://github.com/rengwu/wayfinder-maps.git mkdir -p ~/.claude/skills cd wayfinder-maps && cp -r skills/.optional/to-spec ~/.claude/skills/to-spec
Kommandoer og eksempelprompter
/to-specGjør samtalen du allerede har hatt om til en repo-bevisst spesifikasjon i .plan/
Skills utløses av vanlige forespørsler — ingen kommandoer å huske. Etter installasjonen aktiverer prompter som disse skillen (på engelsk):
/to-spec turn what we just discussed about tagging into a written PRDSave a spec to .plan for the notes feature we just finished designingWrite a PRD from this conversation with an exhaustive user story list