to-spec

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

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/regisleandro/clara-financas --skill to-spec-regisleandro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/regisleandro/clara-financas/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/regisleandro/clara-financas --skill to-spec-regisleandro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal spec (PRD) usually means re-interviewing stakeholders and rewriting everything from scratch. This Skill eliminates that duplication by synthesizing the existing conversation and codebase understanding directly into a publishable spec. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Converts the current discussion into a structured spec with problem statement, solution, user stories, implementation decisions, testing decisions, and scope boundaries — no re-interview required. - Test Seam Planning: Identifies the highest-level existing seams in the codebase for testing, proposing new ones only when necessary and confirming 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 your AI pair programmer, invoke this Skill to produce a complete spec aligned with the project's domain glossary and ADRs, ready for an agent to implement. ## Quick Start Ask the assistant 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 product spec or PRD?

Invoke this Skill after discussing a feature with the AI. It synthesizes the existing conversation and codebase understanding into a structured spec covering problem statement, solution, user stories, implementation and testing decisions, then publishes it to the issue tracker.

Does the spec skill interview the user for requirements?

No. The Skill explicitly avoids interviewing and instead synthesizes what has already been discussed in the conversation. It only checks with the user to confirm that proposed test seams match expectations.

What sections does the generated spec template include?

The template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. File paths and code snippets are excluded except for decision-rich prototype fragments.

What setup is required before using the spec publishing workflow?

The issue tracker and triage label vocabulary must be provided beforehand, via the /setup-matt-pocock-skills command. Without that configuration, the Skill cannot publish the spec or apply the ready-for-agent label.

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

Avoid it when the conversation lacks enough decisions to fill the template, or when requirements need structured stakeholder interviews rather than synthesis. The Skill assumes prior discussion already covered the problem, solution, and technical direction.