skills.rest
yersonargotev
yersonargotevCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

1|Updated Jul 5, 2026
Search Tags:#requirements#issue tracker#spec generation#feature specification#user stories#testing seams#triage label
One-click install
npx skills add https://github.com/yersonargotev/packy --skill to-spec-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/engineering/to-spec
Command: npx skills add https://github.com/yersonargotev/packy --skill to-spec-yersonargotev

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 with the ready-for-agent label.

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 with the AI. 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 user stories for a software specification?▼

The spec template 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, without requiring a new interview.

Does to-spec require any setup before use?▼

Yes, the issue tracker and triage label vocabulary must be configured beforehand. If they are missing, the skill instructs you to run /setup-matt-pocock-skills before it can publish specs.

What are testing seams in a spec?▼

Testing seams are the boundaries at which a feature will be tested. The skill prefers existing seams over new ones, chooses the highest seam possible, and asks you to confirm the proposed seams before writing the spec.

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

Avoid it when the feature has not been discussed yet, since the skill explicitly does not interview the user. It only synthesizes what is already known from the conversation and codebase exploration.

Related Skills

Explore More Software Engineering 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
mst-software-vnmst-software-vn
1

improve-codebase-architecture

Scan a codebase for module deepening opportunities and render findings as a visual HTML report.

Official
Advanced
jwh3timesjwh3times
1

to-questionnaire

Generates a structured Markdown questionnaire for a recipient who holds knowledge the user lacks.

Community
Basic