skills.rest
danielsuguimoto
danielsuguimotoCOMMUNITY
Explore all skills by this author →
𝕏@djsuguimotoGitHub

to-specs

Convert requests or tickets into structured specs and sync them to the ticket system.

Updated Jul 11, 2026
Search Tags:#planning#requirements#issue tracker#clarification#spec#ticket#read-only
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill to-specs-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-specs
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/to-specs
Command: npx skills add https://github.com/danielsuguimoto/skills --skill to-specs-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague request or ticket into an actionable, implementation-ready spec requires clarifying requirements, inspecting the codebase, and structuring decisions — a process that is often skipped or done inconsistently. This Skill enforces a disciplined, read-only workflow that produces a complete spec with patch-level implementation items and syncs it to the ticket system. ## Core Features & Use Cases - Clarification-First Planning: Runs a mandatory grilling interview, asking only questions the codebase cannot answer, and resolves everything else by inspecting the repo, schema, docs, and existing tickets. - Patch-Ready Spec Generation: Produces a spec with Destination, Problem Statement, Solution, and Notes, plus requirement items containing file, symbol, location, instruction, and minimal patch code. - Ticket System Sync: Updates or creates tickets with the spec description, Implementation and Validation checklists, and a patches comment containing full structured code blocks. - Use Case: A product manager files a ticket asking to lock archived models. The Skill loads the ticket, inspects the model and policy layers, grills the user on scope boundaries, then syncs a spec with per-file patch items and a validation checklist back to the ticket. ## Quick Start Turn ticket PROJ-123 into a spec and sync it back to the ticket system without making any code changes.

Frequently Asked Questions about to-specs

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

FAQPage Schema
How do I turn a ticket into an implementation spec?▼

Provide the ticket URL or reference, and the workflow loads the ticket context, inspects the repository for ground truth, grills you only on decisions the code cannot settle, then shapes a spec with patch-level requirement items and syncs it back to the ticket.

Does this workflow make any code changes?▼

No, it is strictly read-only. It never edits code, implements, or executes the spec. If you ask it to implement, it declines and directs you to run the separate implementation workflow instead.

What questions will it ask during requirement clarification?▼

It only asks about decisions the codebase cannot resolve: scope boundaries, business rules, product behavior choices, trade-offs between valid approaches, and naming when no existing pattern guides it. Anything answerable by inspecting the repo, schema, or docs is resolved by inspection.

How are implementation items synced to the ticket system?▼

The spec description contains only Destination, Problem Statement, Solution, and Notes. Implementation and Validation items sync as checklists in short encoded form, while full structured blocks with patch code are posted as a comment to avoid overflowing card body limits.

When can the clarification interview be skipped?▼

Only when all skip-gate conditions hold: a single atomic edit with no design decisions, a concrete and unambiguous technical direction, no conflicting comments or open questions, repo inspection confirming the direction, and explicit user confirmation. The skip must be justified in the output.

Related Skills

Explore More Product & Management Skills→
unblockedunblocked
13

headless-enrich-ticket

Gather context and attach structured enrichment documents to issue tracker tickets.

Official
Advanced
searchandrescueggsearchandrescuegg

speckit-checklist

Generate QA-ready checklists from feature briefs, specs, and task plans.

Official
Advanced
usetheodevusetheodev

grill-me

Resolve unclear requirements through one-question-at-a-time interview workflows.

Community
Advanced
cenconq25cenconq25
39

quick-design

Generate compact Markdown design specs for embedding into story files.

Community
Intermediate