Agent skill

To Spec

by ordewell in ordewell/ordewell

Turn the current conversation into a product spec and save it to the project.

Apache-2.0Auto-check passedProduct & Project Management

Install To Spec

skills CLI
$ npx skills add ordewell/ordewell --skill to-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ordewell/ordewell to-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ordewell/ordewell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/to-spec .claude/skills/to-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
to-spec
GitHub stars
193
Token cost
~539 tokens
SKILL.md length
311 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Turn the current conversation into a product spec and save it to the project.

  • Works in 2 steps: Explore the repo to understand the… → Sketch out the seams at which you're…
  • Tasks that involve PRD writing
  • SKILL.md covers Process, Problem Statement, Solution and User Stories, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

To Spec is an agent skill from ordewell/ordewell. Turn the current conversation into a product spec and save it to the project.

Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing and User stories. The repository describes itself as: Multi-agent task orchestration for coding agents. Turn one goal into an ordered plan of tasks (each with its own runner, model and mode), then execute and verify the results. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve PRD writing
  • Tasks that involve User stories

Example prompts

  • “/to-spec”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary…
  2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam…

What it can do on your machine

Read from SKILL.md and the folder at commit 5fe17f2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

To Spec loads about 539 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 311 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~539

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ordewell/ordewell at commit 5fe17f2, republished under its Apache-2.0 licence (© ordewell). 311 words, ~539 tokens.

Download SKILL.mdSave it as .claude/skills/to-spec/SKILL.md (or your agent's skills folder).
name
to-spec
description
Turn the current conversation into a product spec and save it to the project.
disable-model-invocation
true

This skill takes the current conversation context and codebase understanding and produces a spec document. Do NOT interview the user — just synthesize what you already know.

Process

  1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec.

  2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. The fewer seams across the codebase, the better — the ideal number is one.

Check with the user that these seams match their expectations.

  1. Write the spec using the template below, then save it to .ordewell/spec.md in the project's working directory.
<spec-template>

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A long, numbered list of user stories. Each user story should be in the format of:

  1. As an <actor>, I want <feature>, so that <benefit>

This list of user stories should be extremely extensive and cover all aspects of the feature.

Implementation Decisions

A list of implementation decisions that were made. This can include:

  • The modules that will be built/modified
  • The interfaces of those modules that will be modified
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts

Do NOT include specific file paths or code snippets. They end up being outdated very quickly.

Testing Decisions

A list of testing decisions that were made. Include:

  • A description of what makes a good test (only test external behavior, not implementation details)
  • Which modules will be tested
  • Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this spec.

Further Notes

Any further notes about the feature.

</spec-template>

© ordewell, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/core/skills/to-spec of ordewell/ordewell.

Open the folder on GitHubat commit 5fe17f2

Compare with similar skills

To Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

To Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
To Spec this skillordewell/ordewell193—~539Automated safety check: PassApache-2.0
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
Ralph Tui Create JSONsubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
To Prdywwynm/EverythingDone14411 repos~777Automated safety check: PassGPL-3.0
Use Case Writerphucnt-bazone-vietnam/use-case-writer143—~4.1kAutomated safety check: PassMIT

Similar skills

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • To Prd

    ywwynm/EverythingDone

    Turn the current conversation context into a PRD and publish it to the project issue tracker.

    144 GitHub starsUsed in 11 repos~777 tokens
    Product & Project ManagementAuto-check passed
  • Use Case Writer

    phucnt-bazone-vietnam/use-case-writer

    Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).

    143 GitHub stars~4.1k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed
  • Project Planner

    adrianpuiu/claude-skills-marketplace

    Comprehensive project planning and documentation generator for software projects.

    100 GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

More from ordewell/ordewell

  • Scan the codebase for deepening opportunities, prioritize them, then turn as many as the user wants into ordered plan tasks.

    193 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Questions about To Spec

What does To Spec do?

Turn the current conversation into a product spec and save it to the project. To Spec is an agent skill from ordewell/ordewell. Turn the current conversation into a product spec and save it to the project.

When should I use To Spec?

To Spec fits situations like: tasks that involve PRD writing; tasks that involve User stories.

How do I install To Spec in Claude Code?

Run `npx skills add ordewell/ordewell --skill to-spec -a claude-code`. Or copy the skill folder (packages/core/skills/to-spec in ordewell/ordewell) into .claude/skills/to-spec in your project. Claude Code loads it when a task matches its description.

How do I install To Spec in Codex?

Run `npx skills add ordewell/ordewell --skill to-spec -a codex`. Or copy the skill folder (packages/core/skills/to-spec in ordewell/ordewell) into .agents/skills/to-spec in your project. Codex loads it when a task matches its description.

Can I use To Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ordewell/ordewell --skill to-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-spec, .gemini/skills/to-spec, .github/skills/to-spec and .opencode/skills/to-spec in your project.

What does To Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: To Spec is instructions for the agent only.

Does To Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is To Spec safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does To Spec use?

To Spec is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does To Spec use?

About 539 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to To Spec?

Skills that share tags, products or a category with To Spec: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Spec?

ordewell (a GitHub organization) maintains it in ordewell/ordewell, which has 193 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

Source: ordewell/ordewell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.