skills.rest
damoke012
damoke012COMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Apr 16, 2025
Search Tags:#requirements#issue tracker#spec generation#user stories#triage#conversation synthesis#testing seams
One-click install
npx skills add https://github.com/damoke012/eks_code --skill to-spec-damoke012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/damoke012/eks_code/tree/main/.claude-env/skills/to-spec
Command: npx skills add https://github.com/damoke012/eks_code --skill to-spec-damoke012

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, scope) from existing discussion context. - Test Seam Planning: Identifies and proposes testing seams in the codebase, preferring existing high-level seams, and confirms them with the user before writing. - 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, invoke this Skill to produce a ready-for-implementation spec issue with extensive user stories and architectural decisions, respecting the project's glossary and ADRs. ## Quick Start Ask the AI to turn the current conversation into a spec and publish it to the 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, without asking new interview questions.

How do I publish a spec to a project issue tracker?▼

The skill writes the spec using its built-in template and publishes it directly to the configured project issue tracker, applying the ready-for-agent triage label so no additional triage is needed.

What sections does the generated spec template include?▼

The template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. File paths and code snippets are excluded except for decision-rich prototype excerpts.

What are testing seams in spec planning?▼

Testing 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 necessary, and confirms them with the user before writing the spec.

Why does the skill say to run setup-matt-pocock-skills?▼

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

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
J0JngJ0Jng
7

to-spec

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

Community
Intermediate
ishandutta2007ishandutta2007
13

Prototyping

Build disposable prototypes that surface state after each interaction.

Community
Intermediate
mattpocockmattpocock
242.8k

to-questionnaire

Generates a structured Markdown questionnaire to extract knowledge from a specific recipient.

Community
Basic