to-spec

Synthesizes the current conversation into a structured spec and publishes it to the project issue tracker.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/kashman001/ai-workspace-template --skill to-spec-kashman001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/kashman001/ai-workspace-template/tree/main/skills/to-spec
Command: npx skills add https://github.com/kashman001/ai-workspace-template --skill to-spec-kashman001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long design discussion, turning scattered conversation context into a formal, actionable specification is tedious and error-prone. This Skill converts what has already been discussed 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 spec from existing conversation context and codebase understanding, with no additional user interview. - Test Seam Planning: Identifies the highest-level existing seams for testing the feature and confirms them with the user before writing. - Structured Spec Template: Produces a spec with Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes sections. - 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 billing feature with an AI agent, invoke this Skill to produce a complete spec with numbered user stories and publish it as a triaged issue ready for implementation. ## Quick Start Ask the agent 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 software spec?▼

Invoke this Skill after discussing a feature with the agent. It synthesizes the existing conversation and codebase context into a structured spec covering problem statement, solution, user stories, and implementation decisions, then publishes it to the issue tracker.

What sections does the generated spec template include?▼

The spec template includes Problem Statement, Solution, a long numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. User stories follow the format: as an actor, I want a feature, so that a benefit.

Does this Skill interview the user before writing the spec?▼

No. The Skill explicitly avoids interviewing the user and instead synthesizes what has already been discussed. It only checks with the user that the proposed test seams match their expectations before writing the spec.

What issue tracker setup is required to publish specs?▼

The Skill expects the issue tracker and triage label vocabulary to be provided beforehand, normally via the workspace's issue tracker documentation. If missing, it instructs the user to run the setup command before proceeding.

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

Avoid it when the feature has not been discussed yet, since the Skill relies entirely on existing conversation context. It is also unsuitable when requirements need direct stakeholder interviews or formal requirements-gathering sessions.