---
name: To Spec
slug: to-spec-4
category: AI Engineering
description: To Spec synthesizes an implementation-ready spec from a conversation and relevant repository context. Use it when work needs to be captured as a PRD or scoped specification with behavior, constraints, and acceptance criteria.
github: "https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec"
language: Python
stars: 578
forks: 71
install: "npx degit https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec ~/.claude/skills/to-spec"
installs_to: ~/.claude/skills/to-spec
source_path: .agents/skills/to-spec/SKILL.md
collection_size: 25
category_size: 2451
collection_url: "https://dirskills.com/collections/stevesolun/ctx"
added: 2026-08-25T05:14:04.918Z
last_synced: 2026-08-25T05:14:04.918Z
canonical_url: "https://dirskills.com/skills/to-spec-4"
---

# To Spec

To Spec synthesizes an implementation-ready spec from a conversation and relevant repository context. Use it when work needs to be captured as a PRD or scoped specification with behavior, constraints, and acceptance criteria.

**Install:**

```bash
npx degit https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec ~/.claude/skills/to-spec
```

## README

# Create a spec

Capture the decisions already made. Resolve only gaps that would materially
change the intended behavior, scope, or feasibility; do not reopen settled
questions for the sake of completing a template.

Inspect the relevant implementation, tests, domain language, and architectural
decisions when they improve fidelity. Keep facts observed in the repository
distinct from decisions inferred from the conversation.

Describe:

- the user-visible problem and desired outcome;
- behavior, edge cases, and acceptance criteria;
- constraints and decisions that implementation must preserve;
- relevant interfaces or test seams when they are already known; and
- explicit exclusions and unresolved questions.

Prefer durable behavioral contracts over file paths and implementation recipes.
Include code or a type shape only when it records a decision more precisely than
prose.

Use the [spec format](SPEC-FORMAT.md) when a structured document helps. Return,
save, or publish the spec in the destination the user requested. Treat tracker
publication and label changes as separate mutations requiring clear scope.