skills.rest
tlipoca9
tlipoca9COMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated Feb 22, 2024
Search Tags:#requirements#issue tracker#spec generation#feature specification#user stories#conversation synthesis#triage label
One-click install
npx skills add https://github.com/tlipoca9/dotfiles --skill to-spec-tlipoca9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/to-spec
Command: npx skills add https://github.com/tlipoca9/dotfiles --skill to-spec-tlipoca9

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, scope) from what has already been discussed. - Test Seam Planning: Identifies existing or proposed testing seams in the codebase and confirms them with the user 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 codebase, invoke this Skill to produce a ready-for-implementation spec issue without writing it 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 feature spec?▼

Invoke the to-spec skill after discussing the feature with the AI. It synthesizes the existing conversation and codebase understanding into a structured spec with problem statement, user stories, and implementation decisions, then publishes it to the issue tracker.

Does to-spec interview the user before writing the spec?▼

No, to-spec explicitly does not interview the user. It synthesizes only what has already been discussed in the conversation, though it does ask the user to confirm the proposed testing seams before writing the spec.

What sections does the generated spec template include?▼

The spec 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 snippets.

Why does to-spec say the issue tracker is not configured?▼

The skill requires 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 to configure the environment.

What are testing seams in the to-spec workflow?▼

Testing seams are the boundaries at which the feature will be tested. The skill prefers existing seams over new ones, chooses the highest seam possible, and aims for as few seams as possible, ideally one.

Related Skills

Explore More Product & Management Skills→
changfengprochangfengpro

to-prd

Generate a PRD from conversation context and publish it to the project 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
mst-software-vnmst-software-vn
1

to-issues

Breaks plans and specs into vertical-slice issues on a project issue tracker.

Official
Intermediate
tanqimintanqimin
10

to-spec

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

Community
Intermediate