skills.rest
CYRUS-pinto
CYRUS-pintoCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Sep 11, 2026
Search Tags:#requirements#issue tracker#spec generation#feature specification#user stories#conversation synthesis#triage label
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill to-spec-cyrus-pinto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill to-spec-cyrus-pinto

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 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 any of it manually. ## 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 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, then publishes it to the project issue tracker.

How to write user stories for a feature specification?▼

The skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. It derives them automatically from the conversation rather than asking interview questions.

Does the spec include file paths or code snippets?▼

No, implementation decisions avoid specific file paths and code snippets since they become outdated quickly. The exception is prototype snippets that encode decisions more precisely than prose, such as state machines, schemas, or type shapes.

What happens if the issue tracker is not configured?▼

The skill expects the issue tracker and triage label vocabulary to have been provided beforehand. If they are missing, it instructs the user to run /setup-matt-pocock-skills before proceeding.

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

Avoid it when requirements have not yet been discussed, since the skill does not interview the user. It only synthesizes what is already known, so an empty or shallow conversation produces an incomplete spec.

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
ninthdayninthday

prototype

Build throwaway prototypes that answer design questions about logic or UI.

Community
Intermediate
CommunitMeCommunitMe

task-creator

Convert vague project requests into structured Jira tickets via interviews and impact analysis.

Official
Advanced