skills.rest
dulltackle
dulltackleCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Jun 26, 2026
Search Tags:#requirements#issue tracker#spec generation#feature specification#user stories#conversation synthesis#triage label
One-click install
npx skills add https://github.com/dulltackle/kangkang-skills --skill to-spec-dulltackle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/dulltackle/kangkang-skills/tree/main/to-spec
Command: npx skills add https://github.com/dulltackle/kangkang-skills --skill to-spec-dulltackle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal specification is tedious and error-prone. This Skill converts the current conversation and codebase understanding directly into a structured spec and publishes it to the project issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a complete spec (problem statement, solution, user stories, implementation and testing decisions) from what has already been discussed. - Test Seam Planning: Identifies existing or proposed testing seams in the codebase and confirms them with the user before writing the spec. - Issue Tracker Publishing: Publishes the finished spec to the project issue tracker and applies the ready-for-agent triage label. - Use Case: After discussing a new feature with the AI and exploring the codebase, invoke this Skill to produce a ready-for-implementation spec issue without writing it manually. ## Quick Start Ask the AI to turn the current conversation into a spec and publish it to the project issue tracker.

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 conversation into a spec automatically?▼

Invoke the to-spec skill after discussing the feature with the AI. It synthesizes the existing conversation and codebase understanding into a structured spec with problem statement, user stories, and implementation decisions, then publishes it to the issue tracker.

How to write user stories for a feature spec?▼

The skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. It derives them from the conversation context rather than interviewing the user again.

Does to-spec require any setup before use?▼

Yes, the issue tracker and triage label vocabulary must be configured beforehand by running /setup-matt-pocock-skills. Without that setup, the skill cannot publish the spec or apply the ready-for-agent label.

Can the spec include code snippets or file paths?▼

The spec template excludes specific file paths and code snippets because they become outdated quickly. An exception is made for prototype snippets that encode decisions more precisely than prose, such as state machines, schemas, or type shapes.

What are test seams in spec writing?▼

Test seams are the boundaries at which a feature will be tested. The skill prefers existing seams at the highest possible level, proposes new ones only when needed, and confirms them with the user before writing the spec.

Related Skills

Explore More Product & Management Skills→
jwh3timesjwh3times
1

to-spec

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

Community
Intermediate
SevWrenSevWren
1

to-spec

Synthesizes conversation context into a spec and publishes it to the project issue tracker.

Community
Intermediate
ninthdayninthday

prototype

Build throwaway prototypes that answer design questions about logic or UI.

Community
Intermediate
JohannesKoningsJohannesKonings
9

to-spec

Synthesize active conversation context into structured technical specifications and project requirements.

Community
Intermediate