skills.rest
inkfin
inkfinCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

Synthesizes conversation context into a structured spec saved under plans/<feature>/spec.md.

Updated Jan 19, 2023
Search Tags:#planning#markdown#specification#requirements#feature design#user stories#spec
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill to-spec-inkfin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_to-spec
Command: npx skills add https://github.com/inkfin/dotfiles --skill to-spec-inkfin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long design discussion, decisions and requirements live only in chat history and are easily lost. This Skill converts the current conversation and codebase understanding into a durable, structured specification document without re-interviewing the user. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Produces a spec from existing discussion context with no interview, using the project's domain glossary and respecting existing ADRs. - Test Seam Planning: Identifies the highest-level existing seams for testing the feature and checks them with the user before writing. - Structured Spec Template: Writes problem statement, solution, extensive user stories, implementation decisions, testing decisions, out-of-scope items, and notes to plans/<feature-slug>/spec.md. - Use Case: After discussing a new billing feature with the AI, invoke the Skill to capture all agreed decisions as a spec file under plans/billing/spec.md for later implementation. ## Quick Start Ask the AI to turn the current conversation into a spec and save it under plans/<feature>/spec.md.

Frequently Asked Questions about to-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a design conversation into a written spec?▼

Invoke the to-spec skill after your discussion. It synthesizes the existing conversation context and codebase understanding into a structured spec saved at plans/<feature-slug>/spec.md, without asking new interview questions.

What sections does the generated spec template include?▼

The spec includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. Code snippets are only included when they encode a decision more precisely than prose.

Does the spec include specific file paths or code?▼

No. Implementation decisions avoid specific file paths and code snippets because they become outdated quickly. The exception is prototype snippets that capture decisions like state machines, schemas, or type shapes more precisely than prose.

How are test seams chosen for the spec?▼

The skill prefers existing seams over new ones and selects the highest seam possible, aiming for as few seams as possible across the codebase. It checks with the user that the proposed seams match their expectations before writing the spec.

Where is the spec file saved and what if work tracking is missing?▼

Specs are saved as local markdown under plans/<feature-slug>/spec.md, creating the directory if needed. If docs/agents/work-tracking.md is missing, run /agent-repo-setup once or follow the default conventions.

Related Skills

Explore More Software Engineering Skills→
jwh3timesjwh3times
1

to-spec

Synthesizes conversation context into a structured spec published to the project issue tracker.

Community
Intermediate
davepoondavepoon
3.4k

implement-feature

Implements features from specifications with architecture design, code, and tests.

Community
Intermediate
haryelramalhoharyelramalho

domain-modeling

Creates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.

Community
Advanced
MichaelSolatiMichaelSolati

to-prd

Synthesize conversation and codebase context into structured PRDs and publish them to the issue tracker.

Community
Intermediate