to-spec

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc --skill to-spec-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/Ab0umar/selrs.cc/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/Ab0umar/selrs.cc --skill to-spec-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into an actionable 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 full spec (problem statement, solution, user stories, implementation and testing decisions, scope) from existing discussion context. - Test Seam Planning: Identifies the highest-level existing seams in the codebase for testing 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 discussing a new feature with your AI pair programmer, invoke this Skill to produce a complete, tracker-ready spec with extensive user stories and explicit out-of-scope boundaries. ## 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 conversation into a feature spec?▼

Invoke the to-spec skill after discussing the feature with your AI agent. 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.

How to write user stories for a software specification?▼

This skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. The stories are derived from the conversation context and cover all aspects of the feature being specified.

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

No, the skill explicitly does not interview the user. It synthesizes only what has already been discussed in the conversation, though it does ask the user to confirm the proposed test seams before writing the spec.

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 to configure the environment first.

What are test seams in spec writing?▼

Test seams are the boundaries in the codebase where a feature will be tested. The skill prefers existing seams over new ones, chooses the highest-level seam possible, and aims to minimize the total number of seams across the codebase.