to-spec

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

Updated Nov 10, 2013
One-click install
npx skills add https://github.com/bnferguson/dotfiles --skill to-spec-bnferguson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/bnferguson/dotfiles --skill to-spec-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long design discussion, turning scattered conversation context into a formal, actionable specification is tedious and error-prone. This Skill converts what has already been discussed 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) purely from existing conversation context and codebase exploration. - Test Seam Planning: Identifies the highest-level existing seams in the codebase for testing 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 automatically. - Use Case: After discussing a new billing feature with the AI, invoke this Skill to produce a full spec with extensive user stories and post it as a triaged issue ready for an implementation agent. ## 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 an AI conversation into a feature spec?▼

Invoke the to-spec skill after your design discussion. It synthesizes the existing conversation context and codebase exploration into a structured spec covering problem statement, solution, user stories, and implementation decisions, then publishes it to your issue tracker.

How do I publish a spec to a project issue tracker from a conversation?▼

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

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

No. The skill explicitly does not interview the user; it only synthesizes what has already been discussed. The single checkpoint is confirming that the proposed test seams match your expectations.

What happens if the issue tracker and triage labels are not configured?▼

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

What are test seams in a feature specification?▼

Test seams are the boundaries at which a feature will be tested. The skill prefers existing seams at the highest possible level in the codebase, proposes new ones only when necessary, and aims for as few seams as possible.