to-spec

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

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill to-spec-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/to-spec
Command: npx skills add https://github.com/ankaboot-source/boucle --skill to-spec-ankaboot-source

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 converts the current conversation and codebase understanding directly into a structured spec published to your project issue tracker, with no repeated questioning. ## Core Features & Use Cases - Conversation-to-Spec Synthesis: Generates a complete spec from existing discussion context without interviewing the user again. - Test Seam Planning: Identifies existing or new test seams in the codebase, preferring the highest-level seam, and documents rationale in CI mode. - Issue Tracker Publishing: Writes the spec using a fixed template (Problem Statement, User Stories, Implementation Decisions, Testing Decisions, Out of Scope) and applies the ready-for-agent triage label. - Use Case: After discussing a new feature with your AI assistant, invoke this Skill to produce a full PRD-style issue in GitHub or GitLab, ready for an autonomous agent to pick up and implement. ## Quick Start Ask the assistant to turn our current conversation 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 automatically?

Invoke the to-spec skill after discussing a feature with your AI assistant. It synthesizes the conversation and codebase context into a structured spec with problem statement, user stories, and implementation decisions, then publishes it to your issue tracker.

How to generate a PRD without re-answering questions?

This skill explicitly avoids interviewing the user. It relies entirely on the existing conversation context and repository exploration to draft the spec, so no repeated questioning occurs.

Does the spec get published to GitHub or GitLab issues?

Yes, the skill publishes the generated spec to the configured project issue tracker and applies the ready-for-agent triage label. The tracker and label vocabulary must be set up beforehand via the setup command.

What sections does the generated spec template include?

The template includes Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. It avoids specific file paths or code snippets except for decision-rich prototype excerpts.

What are test seams in spec planning?

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 documents the rationale inline when running in CI mode.