skills.rest
falentio
falentioCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Aug 22, 2026
Search Tags:#planning#requirements#issue tracker#user stories#spec#product specification#triage label
One-click install
npx skills add https://github.com/falentio/cimi --skill to-spec-falentio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/to-spec
Command: npx skills add https://github.com/falentio/cimi --skill to-spec-falentio

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 the highest-level testing seams in the codebase before writing the spec, confirming them with the user. - 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 analytics feature with the AI, invoke this Skill to produce a ready-for-implementation spec issue without repeating any requirements. ## 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 product spec?▼

Invoke the to-spec skill after discussing the feature with the AI. It synthesizes the existing conversation into a spec with problem statement, user stories, implementation decisions, and testing decisions, then publishes it to the project issue tracker.

Does the to-spec skill ask interview questions before writing the spec?▼

No. The skill explicitly does not interview the user; it synthesizes only what has already been discussed. It does check with the user that proposed test seams match expectations before writing the spec.

What issue tracker setup does the spec publishing require?▼

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

What label is applied when a spec is published to the issue tracker?▼

The skill applies the ready-for-agent triage label to the published spec issue. No additional triage step is needed after publishing.

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

Avoid it when requirements have not yet been discussed, since the skill only synthesizes existing context and will not elicit new information. It is also unsuitable when no issue tracker or triage labels have been configured.

Related Skills

Explore More Product & Management Skills→
darkmatterdarkmatter
1

improve-codebase-architecture

Detect shallow modules and propose deepening refactors using project glossary and ADRs.

Official
Advanced
J0JngJ0Jng
7

to-spec

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

Community
Intermediate
automatedigitalautomatedigital
1

grill-with-docs

Align software plans with domain glossaries and architectural decision records.

Official
Intermediate
The-Focus-AIThe-Focus-AI

to-spec

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

Official
Intermediate