to-spec

Creates implementation-ready specifications and self-contained task packets for agent-driven development.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill to-spec-wesbragagt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/to-spec
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill to-spec-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation agents receive only a single task file, requirements and decisions from earlier conversations get lost. This Skill produces a durable specification and standalone task packets so any agent can complete assigned work without prior chat context. ## Core Features & Use Cases - Structured Specification: Generates a spec.md with atomic requirement identifiers (FR, NFR, AC), behavior flows, decisions, acceptance criteria, and a traceability matrix. - Self-Contained Task Packets: Writes dependency-ordered tasks.yaml plus per-task Markdown files containing objective, context snapshot, implementation contract, and acceptance checks. - Worktree-Aware Output: Resolves git worktree state and writes specs to the main checkout's .specs directory, then validates the task graph before delivery. - Use Case: Before handing a feature to coding agents, run this Skill to turn a feature request into a verified specification and task set that survives context loss between sessions. ## Quick Start Ask the agent to create a specification for your feature by providing a feature name and description, for example requesting a spec for user-authentication with a short description of the desired behavior.

Frequently Asked Questions about to-spec

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

FAQPage Schema
How do I break a feature into tasks for AI coding agents?▼

Provide a feature name and description, and the Skill inspects the repository, resolves ambiguities, then writes a spec.md plus a tasks.yaml with standalone task packets. Each packet contains all context an agent needs without prior conversation history.

What makes a task file self-contained for implementation agents?▼

Each task packet includes eight required sections: objective, context snapshot, dependencies, scope, implementation contract, repository guidance, acceptance checks, and a handoff record. Critical constraints are repeated in every affected task so no chat context is needed.

Does the specification workflow work inside git worktrees?▼

Yes. The Skill runs git rev-parse to detect linked worktrees and writes specs to the main checkout's .specs directory instead of the worktree, stating the resolved output path before writing files.

When should I use the --quick flag for specification?▼

Use --quick to skip external research when the feature depends only on repository-internal behavior. Repository inspection still runs, so existing conventions and interfaces are captured in the specification.

How are requirements traced to tasks and acceptance criteria?▼

The spec assigns stable identifiers like FR-01 and AC-01, includes a traceability matrix, and each task lists its requirement and acceptance identifiers. Validation confirms every requirement maps to at least one criterion and task before delivery.