skills.rest
bbenefield89
bbenefield89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ticket-to-spec

Appends a synthesized specification to an existing lightweight ticket.

Updated Jul 7, 2026
Search Tags:#documentation#specification#requirements#agile#user stories#synthesis#ticket
One-click install
npx skills add https://github.com/bbenefield89/skills --skill ticket-to-spec-bbenefield89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-to-spec
Source: https://github.com/bbenefield89/skills/tree/main/skills/ticket-to-spec
Command: npx skills add https://github.com/bbenefield89/skills --skill ticket-to-spec-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often discuss and clarify a feature inside a lightweight ticket, but the agreed decisions remain scattered across comments and conversation. This Skill consolidates that discussion into a structured specification and appends it directly to the original ticket, so the ticket becomes the single authoritative source without creating a separate issue. ## Core Features & Use Cases - Specification Synthesis: Converts the existing ticket discussion, comments, and repository context into a structured specification with problem statement, user stories, implementation decisions, testing decisions, and scope boundaries. - In-Place Ticket Update: Appends the specification to the original ticket body after a thematic break while preserving the title, TL;DR, comments, and metadata, then removes the needs-details state. - Repository-Aware Writing: Reads ADRs, domain glossaries, and codebase areas so the specification uses the project's actual vocabulary, and applies the shared ASD-STE100 writing standard. - Use Case: After a team discusses a new feature in a ticket and reaches agreement, run this Skill to turn that conversation into a formal specification attached to the same ticket, ready for task breakdown. ## Quick Start Synthesize the current discussion into a specification and append it to ticket number 42.

Frequently Asked Questions about ticket-to-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a ticket discussion into a specification?▼

Run this Skill against the clarified ticket. It reads the full ticket body, comments, and current conversation, then synthesizes a specification with problem statement, user stories, implementation and testing decisions, and appends it to the original ticket.

Does this create a separate specification issue?▼

No. The specification is appended to the original ticket body after a thematic break. The existing title, TL;DR, comments, release grouping, and ticket classification are preserved.

What happens if the ticket already has a specification section?▼

The Skill stops and asks how you want to proceed. It does not replace or duplicate an existing specification automatically, so you stay in control of the ticket content.

What context does the specification use from the repository?▼

It reads relevant repository instructions, domain glossaries, ADRs, codebase areas, and prior tests. The specification uses the project's current vocabulary and omits file paths and code snippets except for decision-rich prototype excerpts.

What happens if appending succeeds but state removal fails?▼

The Skill reports the partial result without rolling back the appended specification. You can then remove the needs-details state manually while keeping the published specification intact.

Related Skills

Explore More Product & Management Skills→
udecodeudecode
240

ce-brainstorm

Explore feature ideas and problem statements through guided dialogue and research.

Official
Intermediate
Cogni-DAOCogni-DAO

task

Decompose large work items into atomic PR-sized tasks with acceptance criteria.

Official
Intermediate
CommunityToolkitCommunityToolkit
622

architectural-proposals

Write structured architectural proposals with problem statements, decisions, risks, and scope definitions.

Official
Intermediate
MoofonLiMoofonLi
2

to-spec

Synthesizes conversation context into a structured spec document committed to the repository.

Community
Intermediate