skills.rest
ninthday
ninthdayCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-spec

Synthesizes the current conversation into a specification and publishes it to the project issue tracker.

Updated Mar 30, 2026
Search Tags:#specification#issue tracker#user stories#software planning#feature spec#conversation synthesis#triage label
One-click install
npx skills add https://github.com/ninthday/skills-base --skill to-spec-ninthday
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/ninthday/skills-base/tree/main/skills/to-spec
Command: npx skills add https://github.com/ninthday/skills-base --skill to-spec-ninthday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long design discussion, teams often lose decisions and context when moving from conversation to implementation. This Skill converts the current conversation and codebase understanding into a structured specification and publishes it directly to the project issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Conversation Synthesis: Generates a spec purely from the existing conversation context, with no additional user interviews. - Structured Spec Template: Produces problem statement, solution, extensive user stories, implementation decisions, testing decisions, and out-of-scope sections. - 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 an AI agent and exploring the codebase, invoke this Skill to capture all agreed decisions as a spec issue ready for an implementation agent to pick up. ## Quick Start Ask the agent 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 software specification?▼

Invoke the to-spec skill after your design 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 your issue tracker.

How to publish a spec to a project issue tracker automatically?▼

The skill writes the spec using a fixed template and publishes it to the configured project issue tracker, applying the ready-for-agent triage label so no further triage is needed.

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 in the current conversation, though it does ask you to confirm the proposed test seams.

What happens if the issue tracker is not configured?▼

The skill expects the issue tracker and triage label vocabulary to be provided beforehand. If they are missing, it instructs the user to run /setup-matt-pocock-skills to configure the environment first.

What are the limitations of the generated specification?▼

The spec deliberately excludes specific file paths and code snippets because they become outdated quickly. Only prototype-derived snippets that encode decisions more precisely than prose may be inlined.

Related Skills

Explore More Software Engineering Skills→
mst-software-vnmst-software-vn
1

to-prd

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

Official
Intermediate
AO-HySAO-HyS

to-spec

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

Official
Intermediate
truffle-aitruffle-ai
648

grill-me

Interviews the user about a plan or design to resolve every decision branch.

Official
Basic
laozhong86laozhong86
1

gxpm-setup

Scaffold per-repo gxpm configuration with issue tracker, triage labels, and domain docs.

Community
Intermediate