to-spec

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill to-spec-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/skills-main/skills/engineering/to-spec
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill to-spec-kunj-sharma03

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 discussion you have already had into a structured spec and publishes it directly to your project issue tracker, eliminating duplicate effort. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a complete spec from existing conversation context and codebase understanding without interviewing the user again. - Test Seam Planning: Identifies and proposes testing seams in the codebase, preferring existing high-level seams, and confirms them with the user before writing. - Issue Tracker Publishing: Writes the spec using a fixed template (problem statement, user stories, implementation and testing decisions, out of scope) and publishes it with the ready-for-agent triage label. - Use Case: After discussing a new feature with your AI assistant, invoke this Skill to produce a ready-for-implementation spec issue that an agent or teammate can pick up immediately. ## Quick Start Ask the assistant 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 with your AI assistant. It synthesizes the existing conversation and codebase context into a structured spec with problem statement, user stories, and implementation decisions, then publishes it to your issue tracker.

How do I write user stories for a software specification?

The skill generates an extensive numbered list of user stories in the format 'As an <actor>, I want a <feature>, so that <benefit>'. It covers all aspects of the feature based on what was discussed, without requiring a new interview.

Does to-spec require setup before use?

Yes, the issue tracker and triage label vocabulary must be configured first by running /setup-matt-pocock-skills. Without that setup, the skill cannot publish the spec or apply the ready-for-agent label.

What are test seams in spec writing?

Test seams are the boundaries at which a feature will be tested. The skill prefers existing seams at the highest possible level, proposes new ones only when needed, and confirms the choice with the user before writing the spec.

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

Avoid it when requirements are still unclear or undiscussed, since the skill does not interview the user and only synthesizes existing context. It is also unsuitable when no issue tracker integration has been configured.