skills.rest
tanqimin
tanqiminCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

10|3|Updated Jul 18, 2019
Search Tags:#requirements#issue tracker#feature planning#spec generation#user stories#conversation synthesis#triage label
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill to-spec-tanqimin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill to-spec-tanqimin

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, out-of-scope items) 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 without writing any documentation manually. ## 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 software spec?▼

Invoke the to-spec skill after discussing the feature with the AI. 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 generation 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 excluded except for decision-encoding prototype fragments.

What happens if the issue tracker is not configured?▼

The skill expects the issue tracker and triage label vocabulary to be provided beforehand. If they are missing, it instructs the user to run /setup-matt-pocock-skills instead of proceeding.

How are testing seams chosen for the spec?▼

The skill prefers existing seams over new ones and selects the highest-level seam possible, aiming for as few seams as possible across the codebase. Proposed seams are confirmed with the user before the spec is written.

Related Skills

Explore More Product & Management Skills→
flowelflowel

to-prd

Generate a Product Requirements Document from conversation context and publish it to the issue tracker.

Community
Intermediate
go-musicfoxgo-musicfox
2.6k

om-auto-write-spec

Autonomously converts a feature brief or issue into a spec document published on a ready pull request.

Official
Advanced
automatedigitalautomatedigital
1

grill-with-docs

Align software plans with domain glossaries and architectural decision records.

Official
Intermediate
sure-scalesure-scale
72

drafting

Drafts new legal documents into a matter as .docx files using templates or from-scratch markdown.

Official
Advanced