skills.rest
ZubairImtiaz3
ZubairImtiaz3COMMUNITY
Explore all skills by this author →
Website𝕏@zubairimtiaz1GitHub

to-spec

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

Updated Sep 2, 2026
Search Tags:#requirements#issue tracker#spec generation#feature specification#user stories#conversation synthesis#triage label
One-click install
npx skills add https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal --skill to-spec-zubairimtiaz3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal --skill to-spec-zubairimtiaz3

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 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 repeating any requirements. ## Quick Start Ask the AI to turn the current conversation into a spec and publish it to the issue tracker using the to-spec skill.

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 structured spec with problem statement, user stories, and implementation decisions, then publishes it to the issue tracker.

Does the to-spec skill ask interview questions before writing the spec?▼

No. The skill explicitly does not interview the user; it only synthesizes what has already been discussed. The one exception is confirming proposed testing seams with the user before writing the spec.

What happens if the issue tracker is not configured?▼

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

What sections does the generated spec include?▼

The spec template includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. It avoids specific file paths except for decision-rich prototype snippets.

What are testing seams in a spec?▼

Testing seams are the boundaries at which the feature will be tested. The skill prefers existing seams at the highest possible level, aims for as few seams as possible, and checks the proposed seams with the user before writing the spec.

Related Skills

Explore More Product & Management Skills→
AO-HySAO-HyS

to-spec

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

Official
Intermediate
titanerictitaneric
1

to-spec

Synthesizes conversation context into a structured spec and publishes it 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
vvedantbvvedantb
99

write-a-prd

Convert stakeholder insights into a formal PRD for GitHub issues.

Community
Advanced