skills.rest
julianckt
juliancktCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal spec (PRD) is tedious and often loses decisions made along the way. 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 from existing discussion context, with no additional interview questions. - Test Seam Planning: Identifies and proposes testing seams in the codebase, preferring existing high-level seams 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 the AI and exploring the repo, invoke this Skill to produce a spec with problem statement, user stories, implementation decisions, testing decisions, and out-of-scope notes, 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 the to-spec skill after discussing the feature. It synthesizes the existing conversation and codebase context into a spec with problem statement, user stories, and implementation decisions, then publishes it to the project issue tracker.

Does the spec generation require answering more questions?▼

No. The skill explicitly avoids interviewing the user and works only from what has already been discussed. The only checkpoint is confirming that the proposed testing seams match your expectations.

What sections does the generated spec template include?▼

The template includes Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. It avoids specific file paths and code snippets except for decision-rich prototype fragments.

What are testing seams in spec planning?▼

Testing seams are the boundaries at which a feature will be tested. The skill prefers existing seams at the highest possible level, proposes new ones only when needed, and aims to minimize the total number across the codebase.

What happens after the spec is written?▼

The spec is published to the project issue tracker and labeled with the ready-for-agent triage label, making it immediately available for implementation without additional triage steps.

Related Skills

Explore More Product & Management Skills→
jwh3timesjwh3times
1

to-spec

Synthesizes conversation context into a structured spec published 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
ninthdayninthday

prototype

Build throwaway prototypes that answer design questions about logic or UI.

Community
Intermediate
josemariafsjosemariafs
3

bmad-agent-pm

Draft comprehensive PRDs from user interviews and requirements discovery.

Community
Advanced