skills.rest
rockcookies
rockcookiesCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

1|Updated Feb 2, 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/rockcookies/skills --skill to-spec-rockcookies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/rockcookies/skills/tree/main/skills/mattpocock/to-spec
Command: npx skills add https://github.com/rockcookies/skills --skill to-spec-rockcookies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal specification usually requires tedious re-interviewing and manual write-up. This Skill converts the existing conversation and codebase understanding directly into a structured spec and publishes it to the project issue tracker without asking redundant questions. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a complete spec from the current conversation context without interviewing the user again. - 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: Writes the spec using a fixed template (problem statement, user stories, implementation and testing decisions, out of scope) and publishes it with the ready-for-agent triage label. - Use Case: After discussing a new feature with the AI, invoke this Skill to produce a ready-for-development spec issue that respects the project's domain glossary and ADRs. ## 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 project issue tracker.

How to write a spec without re-interviewing stakeholders?▼

This skill explicitly avoids interviewing the user and instead synthesizes what has already been discussed. It explores the repository for context, confirms testing seams with the user, and writes the spec from a fixed template.

What sections does the generated spec template include?▼

The template includes Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. It avoids specific file paths or code snippets except for decision-rich prototype excerpts.

Does to-spec require any setup before use?▼

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

When should I not use conversation-to-spec synthesis?▼

Avoid it when requirements have not been discussed yet, since the skill does not interview the user. It works best after a substantive design conversation where seams, scope, and decisions are already established.

Related Skills

Explore More Product & Management Skills→
Kushal9889Kushal9889

setup-matt-pocock-skills

Configure issue tracker, triage labels, and domain documentation for engineering skills.

Community
Intermediate
ArtemioPadillaArtemioPadilla
3

implement-feature

Implement approved feature specs through architecture design, coding, testing, and documentation.

Community
Advanced
kk20300113-pngkk20300113-png

grill-with-docs

Stress-test feature plans against project domain models and documented architecture decisions.

Community
Intermediate
JohannesKoningsJohannesKonings
9

to-spec

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

Community
Intermediate