Synthesizes conversation context into a Spec published as a labeled GitHub issue.
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill to-spec-benjr70
Please help me install this Agent Skill. Skill: to-spec Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/to-spec Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill to-spec-benjr70
spec, creating a durable contract that implementation Slices are cut from and reviewed against. ## Core Features & Use Cases - Synthesis without re-interview: Builds the Spec from the current conversation and codebase exploration, with only two short confirmations (seams and modules) to catch mis-synthesis. - Structured Spec template: Produces Problem Statement, Solution, numbered User Stories, Implementation Decisions, Module design, Testing Decisions, Out of Scope, and Further Notes sections. - GitHub publishing workflow: Creates the spec label if missing, publishes via gh issue create, and links the Spec as a sub-issue of a parent Map when one exists. - Autonomous (AFK) mode: When no human is present, skips confirmations, records seams and modules as stated assumptions, and flags them as unconfirmed in Further Notes. - Use Case: After discussing a new notification feature for the Smart Smoker app, run the Skill to produce a Spec issue with numbered user stories and module design, then hand it to /to-tickets to cut implementable Slices. ## Quick Start Ask the assistant to turn the current conversation into a Spec and publish it as a GitHub issue labeled spec.High-intent search queries and answers about installing and using this skill.
Run the to-spec Skill after the discussion; it synthesizes the conversation into a Spec template covering problem, solution, user stories, and module design, then publishes it with gh issue create under the spec label.
No. It explicitly avoids discovery interviews and synthesizes decisions already made in the conversation. The only round-trips are two short confirmations about test seams and modules, which are skipped entirely in autonomous AFK mode.
The Skill checks for the label with gh label list and creates it with an explicit color if missing. It never uses gh label create --force, which would rewrite the color and description of an existing label.
Yes. When the Spec originates from a wayfinder Map, the Skill adds 'Part of #<map>' as the first body line and attaches the Spec as a sub-issue of the Map using the GitHub sub_issues API.
Avoid it when requirements are not yet decided, since the Skill assumes decisions were already made upstream. A Spec is also never labeled AFK or added to Project #1 because it is not directly implementable work.
govoelValidate plans against repository documentation and update CONTEXT.md and ADRs.
mmartinsolivBreak plans, specs, or PRDs into dependency-ordered tracer-bullet issues.
sebafermanelliGenerate JSDoc/TSDoc, READMEs, API docs, and specs as in-repo Markdown.
posit-devDrafts complete GitHub issue drafts for the Positron repository with duplicate checking.