to-spec

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

1|Updated Apr 25, 2025
One-click install
npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill to-spec-gabr1elaugus700
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/Gabr1elaugus700/WorkaPool/tree/main/.agents/skills/to-spec
Command: npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill to-spec-gabr1elaugus700

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 into a structured spec with problem statement, solution, user stories, implementation decisions, testing decisions, and scope boundaries. - 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 automatically. - Use Case: After discussing a new feature with your AI assistant, invoke this Skill to produce a complete spec aligned with your project's glossary and ADRs, ready for an implementation agent to pick up. ## Quick Start Ask the assistant to turn the 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?

Invoke the to-spec skill after discussing a 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 your issue tracker.

How to write a PRD without interviewing stakeholders again?

This skill avoids re-interviewing by synthesizing what was already discussed in the conversation. It explores the repository for context, respects existing ADRs and glossary vocabulary, and drafts the spec from that accumulated understanding.

What is a test seam in feature planning?

A test seam is a boundary in the codebase where behavior can be observed and tested. The skill prefers existing seams at the highest architectural level possible, aiming for as few seams as possible, and confirms them with you before writing the spec.

Does the spec include file paths or code snippets?

No, the spec deliberately excludes specific file paths and code snippets because they become outdated quickly. The only exception is a prototype snippet that encodes a decision more precisely than prose, such as a state machine or schema.

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

The skill applies the ready-for-agent triage label to the published spec, signaling it is ready for an implementation agent to pick up. No additional triage steps are required.