spec

Transforms raw ideas into structured execution specs with workstreams and acceptance criteria.

2|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/coroboros/agent-skills --skill spec-coroboros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/coroboros/agent-skills/tree/main/skills/spec
Command: npx skills add https://github.com/coroboros/agent-skills --skill spec-coroboros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague ideas into structured, actionable execution specs with clear scope, dependencies, and acceptance criteria, bridging thinking and building.

Core Features & Use Cases

  • Decomposes ideas into 3-7 executable workstreams with explicit priority, complexity, and dependencies.
  • Produces a canonical spec document ready for execution via /apex or GitHub issues, including acceptance criteria and cross-workstream references.
  • Guides teams from brainstorming to concrete implementation with a repeatable blueprint.

Quick Start

Provide your idea and let the tool generate a complete, ready-to-implement spec document.

Frequently Asked Questions about spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a brainstorming idea into a structured execution spec?

To convert an idea into an execution spec, you provide the raw concept and the tool decomposes it into 3-7 executable workstreams. This structured spec includes explicit priorities, complexities, dependencies, and acceptance criteria.

What is the best way to define dependencies and acceptance criteria for workstreams?

The best way to define dependencies and acceptance criteria is by generating a canonical spec document from your idea. This document automatically maps cross-workstream references and assigns specific complexities and priorities.

How do I break down issue descriptions into actionable workstreams with priorities?

You break down issue descriptions by feeding the raw text into the spec generator. It analyzes the input and outputs 3-7 prioritized workstreams complete with complexity ratings and actionable steps.

Can I use this generated spec document for execution via /apex or GitHub issues?

Yes, you can use the generated canonical spec document directly for execution via /apex or GitHub issues. The output is specifically formatted to bridge thinking and building with ready-to-implement steps.

Do I need a specific format to formalize conversation steps into a canonical spec?

You do not need a specific input format to formalize conversation steps. The tool directly translates raw conversations and brainstorming outputs into a structured execution spec with clear scope.