to-spec

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill to-spec-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/to-spec
Command: npx skills add https://github.com/marjorg/setup --skill to-spec-marjorg

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 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 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 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. 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 project issue tracker.

Does the spec generation require answering more questions?

No. The skill explicitly avoids interviewing the user and only 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 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 and code snippets except decision-rich prototype excerpts.

Why does the skill say the issue tracker is not configured?

The skill requires the issue tracker and triage label vocabulary to be provided beforehand. If they are missing, it instructs you to run /setup-matt-pocock-skills to complete the setup before generating specs.

What are test seams in spec planning?

Test seams are the boundaries at which a feature will be tested. The skill prefers existing seams over new ones, chooses the highest seam possible, and aims to minimize the total number of seams across the codebase.