skills.rest
wenyue
wenyueCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

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

Updated May 19, 2026
Search Tags:#requirements#issue tracker#feature specification#user stories#spec#triage#test seams
One-click install
npx skills add https://github.com/wenyue/SmartKit --skill to-spec-wenyue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/wenyue/SmartKit/tree/main/skills/to-spec
Command: npx skills add https://github.com/wenyue/SmartKit --skill to-spec-wenyue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal specification usually requires tedious re-interviewing and manual write-up. This Skill converts the existing conversation and codebase understanding directly into a structured spec and publishes it to the project issue tracker without asking redundant questions. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a complete spec from the current conversation context, with no interview phase. - Test Seam Planning: Identifies existing or proposed testing seams in the codebase and confirms them with the user before writing. - 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 spec covering problem statement, user stories, implementation decisions, testing decisions, and out-of-scope items, then file it as a triaged issue. ## 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 spec with problem statement, user stories, implementation decisions, and testing decisions, without re-interviewing you.

How does the spec get published to an issue tracker?▼

After writing the spec from its built-in template, the skill publishes it to the configured project issue tracker and applies the ready-for-agent triage label, so no additional triage step is needed.

What are test seams in spec writing?▼

Test seams are the boundaries where a feature will be tested. The skill prefers existing seams over new ones, proposes new seams at the highest possible level, and asks you to confirm them before writing the spec.

Does the spec include file paths or code snippets?▼

No, implementation decisions avoid specific file paths and code snippets because they become outdated quickly. The only exception is a prototype snippet that encodes a decision more precisely than prose, such as a state machine or schema.

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 you to run the setup command for the skill bundle before proceeding.

Related Skills

Explore More Product & Management Skills→
bnfergusonbnferguson

to-spec

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

Community
Intermediate
J0JngJ0Jng
7

to-spec

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

Community
Intermediate
arthur-debertarthur-debert

grill-me-with-docs

Challenge plans against CONTEXT.md, ADRs, and spec documents.

Community
Advanced
AskTinNguyenAskTinNguyen

test-driven-development

Enforce test-first development with Red-Green-Refactor and Prove-It patterns.

Community
Advanced