to-spec

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

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/1arley/volibear --skill to-spec-1arley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/1arley/volibear/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/1arley/volibear --skill to-spec-1arley

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 validates testing seams against the codebase, preferring existing high-level seams before proposing new ones. - 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 authentication feature with the AI, invoke this Skill to produce a full spec with user stories and testing decisions, then file it as a ready-for-agent issue. ## 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, without asking new interview questions.

What does the generated spec template include?▼

The spec includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. It avoids specific file paths or code snippets except decision-rich prototype excerpts.

Does to-spec publish the spec to an issue tracker?▼

Yes, it publishes the finished spec to the project issue tracker and applies the ready-for-agent triage label. The tracker and label vocabulary must be configured beforehand via the setup-matt-pocock-skills step.

What are testing seams in a spec?▼

Testing seams are the boundaries where the feature will be tested. The skill prefers existing high-level seams over new ones, checks them with the user, and aims to minimize the number of seams across the codebase.

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

Avoid it when requirements are not yet discussed, since the skill does not interview the user. It only synthesizes what has already been explored in the conversation and codebase.