skills.rest
mikalv
mikalvCOMMUNITY
Explore all skills by this author →
Website𝕏@mikalvGitHub

to-spec

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

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

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 current conversation and codebase understanding directly into a structured spec and publishes it to the project issue tracker 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, preferring existing high-level seams over new ones. - 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 agent, invoke the 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 agent to turn the current conversation into a spec and publish it to the 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 spec or PRD?▼

Invoke the skill after discussing the feature with your agent. It synthesizes the existing conversation and codebase context into a structured spec covering problem statement, user stories, implementation and testing decisions, then publishes it to your issue tracker.

Does the spec generation require answering more questions?▼

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

What issue tracker setup is required before using this skill?▼

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

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. It avoids specific file paths and code snippets except for decision-rich prototype excerpts.

What are testing seams and why does the skill check them?▼

Testing seams are the boundaries at which a feature will be tested. The skill prefers existing high-level seams over creating new ones, aiming for as few seams as possible, and asks you to confirm the proposed seams before writing the spec.

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
volter-aivolter-ai

approver

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

Official
Basic
a35506322a35506322

grill-with-docs

Stress-test project plans against domain documentation, codebase, and ADRs.

Community
Intermediate
ladislasladislas
2

pac-to-prd

Synthesize conversation, issue, or draft context into structured PRD drafts.

Community
Intermediate