skills.rest
MSC72m
MSC72mCOMMUNITY
Explore all skills by this author →
𝕏@MSC72mGitHub

to-spec

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

Updated Aug 22, 2026
Search Tags:#specification#requirements#issue tracker#feature planning#user stories#spec#triage
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill to-spec-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/MSC72m/DevForge/tree/main/skills/to-spec
Command: npx skills add https://github.com/MSC72m/DevForge --skill to-spec-msc72m

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 proposes testing seams in the codebase, preferring existing high-level seams, and confirms them with the user before writing. - 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, invoke this Skill to produce a ready-for-implementation spec issue that respects the project's domain glossary and ADRs. ## 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, then publishes it to the project issue tracker.

How to write a spec without re-answering requirements questions?▼

This skill does not interview the user; it only synthesizes what was already discussed in the conversation. It explores the repository for context, confirms proposed testing seams with you, and writes the spec from a fixed template.

Does to-spec work without an issue tracker configured?▼

No. The issue tracker and triage label vocabulary must be provided beforehand. If they are missing, the skill instructs you to run /setup-matt-pocock-skills to configure the environment first.

What are testing seams in spec writing?▼

Testing seams are the boundaries at which a feature will be tested. The skill prefers existing seams over new ones, chooses the highest seam possible, and checks with the user that the proposed seams match expectations before writing the spec.

When should I not include code snippets in a spec?▼

Avoid file paths and code snippets because 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 decision-rich parts.

Related Skills

Explore More Software Engineering Skills→
OatseOatse

to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

Community
Intermediate
volter-aivolter-ai

approver

Defines the human approval task spec that parks requests until a person marks them done.

Official
Basic
arthur-debertarthur-debert

grill-me-with-docs

Challenge plans against CONTEXT.md, ADRs, and spec documents.

Community
Advanced
The-Focus-AIThe-Focus-AI

to-spec

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

Official
Intermediate