to-spec

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

1|Updated May 25, 2020
One-click install
npx skills add https://github.com/titaneric/dotfiles --skill to-spec-titaneric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/to-spec
Command: npx skills add https://github.com/titaneric/dotfiles --skill to-spec-titaneric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal spec (PRD) is tedious and often requires re-interviewing stakeholders. This Skill converts the current conversation and codebase understanding directly into a structured spec and publishes it to the project issue tracker without asking redundant questions. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a complete spec from existing discussion context, with no interview phase. - Test Seam Planning: Identifies and proposes testing seams in the codebase, preferring existing high-level seams, and confirms them with the user. - 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 spec covering problem statement, user stories, implementation decisions, testing decisions, and out-of-scope items, then file it as a triaged 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 product spec?

Invoke this Skill after discussing the feature with the AI. It synthesizes the existing conversation and codebase exploration into a structured spec covering problem statement, solution, user stories, implementation decisions, and testing decisions, with no additional interview.

How do I publish a spec to a project issue tracker?

The Skill writes the spec using its built-in template and publishes it directly to the configured project issue tracker, applying the ready-for-agent triage label so no further triage is needed.

What is a testing seam in spec planning?

A testing seam is a boundary in the codebase where behavior can be tested externally. The Skill prefers existing seams at the highest possible level, proposes new ones only when necessary, and confirms the choices with the user before writing the spec.

What setup is required before using this spec workflow?

The issue tracker and triage label vocabulary must be configured first by running /setup-matt-pocock-skills. Without that setup, the Skill cannot publish specs or apply the ready-for-agent label.

When should I not include code snippets in a spec?

Avoid file paths and code snippets in implementation decisions since they become outdated quickly. The exception is prototype snippets that encode a decision more precisely than prose, such as state machines, schemas, or type shapes, trimmed to the decision-rich parts.