to-spec

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

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill to-spec-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill to-spec-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into an actionable engineering spec is tedious and error-prone. This Skill converts the current conversation and codebase context 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 the highest-level existing seams in the codebase for testing 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 dashboard feature with the AI, invoke this Skill to produce a ready-for-implementation issue with extensive user stories and architectural decisions, respecting the project's domain glossary and ADRs. ## Quick Start Ask the AI to turn the current conversation into a spec and publish it to the issue tracker with the ready-for-agent label.

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 spec for my issue tracker?▼

Invoke the to-spec skill after discussing the feature. It synthesizes the conversation and codebase context into a structured spec with user stories and implementation decisions, then publishes it to the project issue tracker with the ready-for-agent label.

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

No. The skill explicitly does not interview the user; it synthesizes what has already been discussed. The only checkpoint is confirming the proposed test seams match your expectations before the spec is written.

What sections does the generated spec template include?▼

The spec 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 and code snippets except for decision-rich prototype fragments.

What happens if the issue tracker and triage labels are not configured?▼

The skill expects 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 first.

How does the skill decide where to test a new feature?▼

It prefers existing test seams over new ones and chooses the highest seam possible, aiming for as few seams as possible across the codebase. Proposed seams are confirmed with the user before the spec is finalized.