skills.rest
SevWren
SevWrenCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

1|Updated Jun 2, 2026
Search Tags:#planning#requirements#issue tracker#user stories#spec#prd#triage
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill to-spec-sevwren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/CLAUDE/skills/engineering/to-spec
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill to-spec-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design discussion into a structured spec (PRD) is tedious and often requires re-interviewing stakeholders. This Skill converts the current conversation and codebase understanding directly into a published spec 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 validates testing seams in the codebase before writing the spec, preferring existing high-level seams. - 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 repo, invoke this Skill to produce a structured spec with problem statement, user stories, implementation decisions, testing decisions, and out-of-scope notes, then file it as an issue ready for an agent to implement. ## Quick Start Ask the AI to turn the current conversation into a spec and publish it to the issue tracker using the to-spec skill.

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 spec or PRD?▼

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, without asking new questions.

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 additional triage step is needed.

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.

Does the spec skill interview the user before writing?▼

No. The skill explicitly avoids interviewing and only synthesizes what has already been discussed. It does check with the user that proposed testing seams match expectations before writing the spec.

What setup is required before using the to-spec skill?▼

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

Related Skills

Explore More Product & Management Skills→
ArcReelArcReel
4.3k

to-spec

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

Official
Intermediate
FradSerFradSer
588

to-spec

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

Community
Intermediate
automatedigitalautomatedigital
1

grill-with-docs

Align software plans with domain glossaries and architectural decision records.

Official
Intermediate
phyter1phyter1

elicit-prd

Generates formal PRD documents from guided, multi-stage conversations with non-technical stakeholders.

Community
Advanced