skills.rest
Fatih0234
Fatih0234COMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-spec

Generates a structured feature spec from conversation context and publishes it to the project issue tracker.

Updated Aug 27, 2026
Search Tags:#requirements#issue tracker#feature specification#user stories#spec#triage#test seams
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill to-spec-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/engineering/to-spec
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill to-spec-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a design discussion into a written spec usually means re-interviewing stakeholders and re-deriving decisions already made in conversation. This Skill synthesizes the current conversation and codebase understanding directly into a structured spec and publishes it to the project issue tracker, with no repeated questioning. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Converts the existing discussion context into a full spec covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Test Seam Planning: Identifies the highest-level existing seams in the codebase for testing 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 billing feature with your AI pair programmer, invoke the Skill to produce a complete spec with extensive user stories and post it as a triaged issue ready for implementation. ## Quick Start Ask the agent 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 software spec?▼

Invoke the Skill after discussing the feature with your agent. It synthesizes the existing conversation and codebase context into a spec with problem statement, user stories, implementation and testing decisions, then publishes it to your issue tracker.

How do I 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>'. The stories cover all aspects of the feature discussed in the conversation.

Does this Skill ask interview questions before writing the spec?▼

No, it explicitly does not interview the user. It synthesizes what has already been discussed, only checking with the user that the proposed test seams match their expectations.

What issue tracker setup does the spec publishing require?▼

The issue tracker and triage label vocabulary must be configured beforehand, typically via the setup-matt-pocock-skills Skill. Without it, the Skill instructs the user to run that setup first.

Should a spec include file paths and code snippets?▼

Generally no, since they become outdated quickly. The exception is prototype snippets that encode a decision more precisely than prose, such as state machines, schemas, or type shapes, trimmed to decision-rich parts.

Related Skills

Explore More Software Engineering Skills→
rohitg00rohitg00
2.8k

domain-modeling

Build a shared-language glossary and bounded contexts before writing code.

Community
Intermediate
FradSerFradSer
588

to-spec

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

Community
Intermediate
anionzoanionzo

brainstorming

Convert vague requests into concrete directions with locked decisions.

Community
Intermediate
dhruvbaldawadhruvbaldawa
31

interviewing

Clarify ambiguous requirements through structured questioning and documentation.

Community
Basic