to-spec

Generates a structured spec from conversation context and publishes it to the project issue tracker.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill to-spec-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/j172/bid/tree/main/agent/skills/to-spec
Command: npx skills add https://github.com/j172/bid --skill to-spec-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design conversation into a formal spec (PRD) is tedious and often requires re-interviewing stakeholders. This Skill synthesizes the existing conversation and codebase understanding directly into a publishable spec without asking redundant questions. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Converts the current discussion context into a structured spec covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Test Seam Planning: Identifies existing architectural seams for testing before writing the spec, preferring the fewest and highest-level seams, and confirms them with the user. - 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 and exploring the codebase, invoke this Skill to produce a complete spec with extensive user stories and post it as a triaged issue ready for implementation. ## Quick Start Turn our current conversation about this feature into a spec and publish it to the 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 product spec?

Invoke the 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. It does not re-interview you, and it publishes the result to the project issue tracker.

What sections does the generated spec template include?

The spec template includes Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. User stories follow the 'As an actor, I want a feature, so that benefit' format and are expected to be extensive.

Does the spec include specific file paths or code snippets?

No, the spec deliberately excludes file paths and code snippets because they become outdated quickly. The only exception is decision-rich snippets from prototypes, such as state machines, schemas, or type shapes, trimmed to the essential parts.

What are test seams and why check them before writing the spec?

Test seams are the boundaries at which the feature will be tested. The Skill prefers existing seams at the highest possible level, aims for as few seams as possible, and confirms the chosen seams with the user before writing the spec.

What happens after the spec is published to the issue tracker?

The spec is published as an issue and labeled with the `ready-for-agent` triage label, marking it ready for implementation without further triage. The tracker and label vocabulary come from running the setup command beforehand.