skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-spec

Convert confirmed conversation decisions into an Agent OS specification document.

Updated Jul 29, 2026
Search Tags:#planning#specification#requirements#handoff#decision capture#feature spec#agent os
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill to-spec-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/to-spec
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill to-spec-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lose decisions made during long planning conversations, or restart requirements discovery from scratch when writing specs. This Skill synthesizes already-established decisions into a structured Agent OS specification without reopening the interview. ## Core Features & Use Cases - Decision Synthesis: Reads code, CONTEXT.md, ADRs, and existing feature state to capture what has already been decided. - Structured Spec Generation: Creates or updates agent-os/specs/YYYY-MM-DD-HHMM-<slug>/spec.md with user problem, acceptance criteria, implementation and testing decisions, out-of-scope items, and risks. - Workflow Handoff: Updates feature_list.json only after user approval (preserving WIP=1) and hands off to /prevc or writing-plans for task decomposition. - Use Case: After a design discussion about a new API endpoint, invoke this Skill to produce a dated spec file capturing the agreed behavior and testing approach, ready for planning. ## Quick Start Ask the agent to turn the decisions from our current conversation into an Agent OS spec using the to-spec skill.

Frequently Asked Questions about to-spec

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

FAQPage Schema
How do I turn conversation decisions into a software specification?▼

Invoke the to-spec skill after your design discussion. It reads the relevant code, CONTEXT.md, and ADRs, then writes a dated spec file under agent-os/specs capturing the user problem, acceptance criteria, implementation and testing decisions, out-of-scope items, and risks.

What is an Agent OS spec and where is it stored?▼

An Agent OS spec is a structured markdown document describing a feature's behavior and decisions. This Skill stores it at agent-os/specs/YYYY-MM-DD-HHMM-<slug>/spec.md, using the project template when one is available.

Does to-spec restart requirements gathering or interviews?▼

No. The Skill explicitly synthesizes decisions already made in the conversation and does not restart the interview. It only confirms newly proposed public verification seams with the user before writing the spec.

When does to-spec update feature_list.json?▼

It updates feature_list.json only after explicit user approval of the spec, and it preserves the WIP=1 constraint so only one feature remains in progress at a time.

What happens after the spec is written?▼

The Skill hands off to /prevc or writing-plans for task decomposition. The spec intentionally avoids brittle file-by-file implementation instructions, leaving detailed planning to those downstream skills.

Related Skills

Explore More Product & Management Skills→
seanmarsseanmars

spectra-discuss

Facilitate structured, goal-oriented discussions to converge on decisions without writing code.

Community
Intermediate
friedbotstudiofriedbotstudio
5

swarm-plan

Decompose an approved specification into a dependency-ordered swarm plan.

Official
Advanced
koukokouko
6

obsidian-tldr

Record session decisions and context as markdown notes in an Obsidian vault.

Community
Intermediate
striderZAstriderZA
72

quick-design

Generate lightweight design specifications for small game changes with acceptance criteria.

Community
Intermediate