skills.rest
kpayakv2
kpayakv2COMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Jul 12, 2025
Search Tags:#requirements#issue tracker#spec generation#feature specification#user stories#conversation synthesis#triage label
One-click install
npx skills add https://github.com/kpayakv2/check-products --skill to-spec-kpayakv2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/kpayakv2/check-products/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/kpayakv2/check-products --skill to-spec-kpayakv2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into an actionable 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 the highest-level testing seams in the codebase before writing the spec, confirming them with the user. - 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 with extensive user stories, without repeating any requirements. ## 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.

Does the spec workflow require answering more questions?▼

No. The skill explicitly avoids interviewing the user and only synthesizes what has already been discussed. The single checkpoint is confirming the proposed testing seams before the spec is written.

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 generally excluded from decisions.

What happens if the issue tracker is not configured?▼

The skill expects the issue tracker and triage label vocabulary to be provided beforehand. If missing, it instructs the user to run /setup-matt-pocock-skills to configure the environment first.

Can this skill be invoked automatically by the AI?▼

No. The skill sets disable-model-invocation and its policy disallows implicit invocation, so it only runs when the user explicitly requests it.

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
SevWrenSevWren
1

to-spec

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

Community
Intermediate
babuallybabually
1

grill-with-docs

Challenge proposed plans against codebase terminology and documented ADR decisions.

Community
Advanced
tomholfordtomholford
6

write-a-prd

Create a PRD from interviews, codebase exploration, and module design.

Community
Advanced