skills.rest
IsKenKenYa
IsKenKenYaCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

2|Updated Jun 21, 2026
Search Tags:#planning#specification#requirements#issue tracker#user stories#spec#triage
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill to-spec-iskenkenya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/to-spec
Command: npx skills add https://github.com/IsKenKenYa/skills --skill to-spec-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long design discussion, turning everything that was agreed into a formal specification is tedious and error-prone. This Skill synthesizes the current conversation and codebase understanding into a complete spec and publishes it to the project issue tracker without re-interviewing the user. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Distills the existing discussion into a structured spec covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Seam Planning: Identifies the highest-level test seams in the codebase, preferring existing 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 grilling a feature design in chat, invoke the Skill to produce a ready-for-implementation issue with extensive user stories and documented architectural decisions. ## Quick Start Ask the agent to turn the current conversation into a spec and publish it to the 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 design conversation into a spec?▼

Invoke the to-spec skill after the discussion. 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.

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

No. The skill explicitly does not interview the user; it only synthesizes what has already been discussed. The single checkpoint is confirming that the proposed test seams match your expectations.

What issue tracker setup does to-spec require?▼

The issue tracker and triage label vocabulary must already be configured in the environment. If they are missing, the skill instructs you to run /setup-matt-pocock-skills before proceeding.

What label does to-spec apply when publishing a spec?▼

It applies the ready-for-agent triage label to the published issue, marking the spec as ready for implementation without any additional triage step.

When should I not use to-spec for writing a specification?▼

Avoid it when requirements are still unclear or undecided, since the skill only synthesizes existing discussion. Use an interview-style skill such as grill-with-docs first to flesh out the design.

Related Skills

Explore More Product & Management Skills→
khapn-2933khapn-2933

tkm:brainstorm

Analyzes feasibility and trade-offs for CTO-level technical decisions and architecture planning.

Community
Advanced
SevWrenSevWren
1

to-spec

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

Community
Intermediate
haryelramalhoharyelramalho

domain-modeling

Creates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.

Community
Advanced
AvistianAvistian

to-prd

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

Community
Intermediate