skills.rest
sndrgrdn
sndrgrdnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-spec

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

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

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 feature spec?▼

Invoke the to-spec skill after discussing the feature. It synthesizes the existing conversation and codebase context 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 software specification?▼

The skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. The stories cover all aspects of the feature based on the prior conversation.

Does to-spec interview the user before writing the spec?▼

No, the skill explicitly does not interview the user. It synthesizes only what has already been discussed, though it does ask the user to confirm the proposed testing seams before writing the spec.

What happens if the issue tracker is not configured?▼

The skill expects the issue tracker and triage label vocabulary to be provided beforehand. If they are missing, it instructs the user to run /setup-matt-pocock-skills to configure the environment.

Can the spec include code snippets or file paths?▼

The spec avoids 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.

Related Skills

Explore More Product & Management Skills→
mst-software-vnmst-software-vn
1

to-prd

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

Official
Intermediate
J0JngJ0Jng
7

to-spec

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

Community
Intermediate
tokisakiyuutokisakiyuu

improve-codebase-architecture

Identifies shallow modules and proposes deepening refactors to improve codebase testability and navigability.

Community
Advanced
tomholfordtomholford
6

write-a-prd

Create a PRD from interviews, codebase exploration, and module design.

Community
Advanced