to-spec

Convert conversation context into a spec and publish it to the project issue tracker.

Updated Jun 25, 2026

Search Tags:#planning #documentation #requirements #issue tracker #spec #conversation synthesis

One-click install

npx skills add https://github.com/richard-jh-mccrae/PokemonAI --skill to-spec-richard-jh-mccrae

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/richard-jh-mccrae/PokemonAI/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/richard-jh-mccrae/PokemonAI --skill to-spec-richard-jh-mccrae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long planning discussion, key decisions and requirements often stay buried in chat history. This Skill synthesizes the current conversation into a structured specification and publishes it directly to the project's issue tracker, without re-interviewing you for details already discussed. ## Core Features & Use Cases - Conversation Synthesis: Distills the existing discussion into a coherent spec without asking redundant questions. - Issue Tracker Publishing: Publishes the resulting spec to the project's issue tracker as a trackable work item. - Use Case: After brainstorming a new feature with your AI assistant, invoke this Skill to turn the agreed-upon design into a spec issue that the team can reference and implement. ## Quick Start Turn our 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 spec?▼

Invoke the to-spec skill after your planning discussion. It synthesizes the requirements and decisions already present in the conversation into a specification, then publishes it to the project issue tracker without asking further questions.

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

No. The skill is explicitly designed to skip interviews and synthesize only what has already been discussed in the current conversation, producing the spec directly from existing context.

Where does the generated spec get published?▼

The spec is published to the project's issue tracker, making it a trackable work item that the team can reference, assign, and implement.

When should I not use conversation-to-spec synthesis?▼

Avoid it when the conversation lacks concrete decisions or requirements, since the skill only synthesizes existing discussion. In that case, continue refining the design in conversation before generating the spec.