skills.rest
MaksymilianCzadowski
MaksymilianCzadowskiCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Jul 16, 2026
Search Tags:#requirements#issue tracker#user stories#spec#prd#triage#product spec
One-click install
npx skills add https://github.com/MaksymilianCzadowski/skills --skill to-spec-maksymilianczadowski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/MaksymilianCzadowski/skills/tree/main/skills/engineering/to-spec
Command: npx skills add https://github.com/MaksymilianCzadowski/skills --skill to-spec-maksymilianczadowski

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 discussion you have already had into a complete, structured spec and publishes it directly to your project issue tracker. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a full spec from existing conversation context and codebase exploration, with no additional interviews. - Test Seam Planning: Identifies the highest-level testing seams in the codebase 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. - Use Case: After discussing a new feature with your AI assistant, 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 assistant 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 a feature with your AI assistant. It synthesizes the existing conversation and codebase context into a structured spec with problem statement, user stories, and implementation decisions, then publishes it to your issue tracker.

What sections does the generated spec template include?▼

The spec template includes Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. User stories follow the standard actor-feature-benefit format and are expected to be extensive.

Does the spec include specific file paths or code snippets?▼

No, the spec deliberately excludes file paths and code snippets because they become outdated quickly. The only exception is prototype snippets that encode a decision more precisely than prose, such as a state machine or schema.

What setup is required before publishing specs to the issue tracker?▼

The issue tracker and triage label vocabulary must be configured first by running /setup-matt-pocock-skills. Once configured, the Skill publishes the spec and applies the ready-for-agent triage label automatically.

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

Avoid it when the conversation lacks enough context about the problem or solution, since the Skill does not interview the user. It also requires user confirmation of proposed testing seams before the spec is written.

Related Skills

Explore More Product & Management Skills→
mst-software-vnmst-software-vn
1

to-prd

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

Official
Intermediate
J0JngJ0Jng
7

to-spec

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

Community
Intermediate
haryelramalhoharyelramalho

domain-modeling

Creates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.

Community
Advanced
petrkohutpetrkohut

bmad-agent-pm

Guide user interviews and stakeholder alignment to create Product Requirements Documents.

Community
Advanced