Agent skill

Spec Writing

by itseffi in itseffi/agentic-os

Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

MITAuto-check passedProduct & Project Management

Install Spec Writing

skills CLI
$ npx skills add itseffi/agentic-os --skill spec-writing -a claude-code

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

GitHub CLI
$ gh skill install itseffi/agentic-os spec-writing --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/itseffi/agentic-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/spec-writing .claude/skills/spec-writing && 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
spec-writing
GitHub stars
115
Token cost
~464 tokens
SKILL.md length
156 words
Files
2
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

  • Works in 4 steps: Validate inputs → Define scope boundaries → Define solution design → …
  • Tasks that involve PRD writing
  • SKILL.md covers The Process, Output Format, Quality Bar and When to Use, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec Writing is an agent skill from itseffi/agentic-os. Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Product & Project Management, covering PRD writing and User stories. The repository describes itself as: Agentic personal OS to automate high-leverage workflows with Codex, Claude Code, Pi, OpenClaw and other coding agents/ runtime platforms. The licence is MIT.

When your agent uses it

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

Example prompts

  • “/spec-writing”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Validate inputs
  2. Define scope boundaries
  3. Define solution design
  4. Define acceptance and verification

What it can do on your machine

Read from SKILL.md and the folder at commit e54d0ac. 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 (its code samples are markdown).

    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

Spec Writing loads about 464 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 156 words of instructions outside code blocks.

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

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 itseffi/agentic-os at commit e54d0ac, republished under its MIT licence (© itseffi). 156 words, ~464 tokens.

Download SKILL.mdSave it as .claude/skills/spec-writing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
spec-writing
description
Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

Spec Writing

Use this skill to produce an implementation-ready spec before planning or coding.

The Process

Step 1: Validate inputs

Require one of:

  • approved PRD
  • clear requirements with goals and constraints

If inputs are missing or ambiguous, list assumptions and open questions first.

Step 2: Define scope boundaries

Document:

  • in scope
  • out of scope
  • constraints (time, dependencies, compliance, platform)
Step 3: Define solution design

Specify:

  • architecture overview (high-level components)
  • interfaces/contracts
  • data model changes
  • rollout and migration approach
Step 4: Define acceptance and verification

Include:

  • acceptance criteria (testable)
  • non-functional expectations (performance, security, reliability)
  • verification commands/checks required before completion

Output Format

markdown
# [Feature Name] Technical Spec

## Goal
[What this spec delivers and why]

## Scope
- In scope:
- Out of scope:
- Constraints:

## Design
- Architecture:
- Interfaces/contracts:
- Data model changes:
- Migration/rollout:

## Risks and Dependencies
- Risks:
- Dependencies:
- Mitigations:

## Acceptance Criteria
- AC1:
- AC2:
- AC3:

## Verification Plan
- Required checks:
- Commands:
- Evidence to capture:

## Open Questions
- Q1:
- Q2:

Quality Bar

  • No vague placeholders in final output
  • Acceptance criteria must be measurable
  • Verification plan must include explicit commands

When to Use

Use this skill when the task directly matches the workflow described above.

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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

Files

SKILL.md and 1 other file in .agents/skills/spec-writing of itseffi/agentic-os.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e54d0ac

Compare with similar skills

Spec Writing 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.

Spec Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec Writing this skillitseffi/agentic-os115—~464Automated safety check: PassMIT
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
Ralphjulianromli/opencode-template1441 repos~1.1kAutomated safety check: PassNone

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
  • Ralph

    julianromli/opencode-template

    Autonomous agent loop for completing features. An agent skill from julianromli/opencode-template.

    144 GitHub starsUsed in 1 repo~1.1k 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).

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

More from itseffi/agentic-os

All 29 skills in this repo
  • Atlassian Jira Sync

    itseffi/agentic-os

    Sync Jira issues with local tasks. An agent skill from itseffi/agentic-os.

    115 GitHub stars~515 tokensUpdated yesterday
    Auto-check passed
  • Davci

    itseffi/agentic-os

    Define clear decision rights - Decider, Approver, Veto, Consulted, Informed.

    115 GitHub stars~563 tokensUpdated yesterday
    Auto-check passed
  • Check Google Calendar for today's schedule. An agent skill from itseffi/agentic-os.

    115 GitHub stars~467 tokensUpdated yesterday
    Auto-check passed
  • Granola Meeting Sync

    itseffi/agentic-os

    Sync new Granola meetings to local Knowledge folder. An agent skill from itseffi/agentic-os.

    115 GitHub stars~535 tokensUpdated yesterday
    Auto-check passed
  • Linear Issue Sync

    itseffi/agentic-os

    Sync Linear issues with local tasks. An agent skill from itseffi/agentic-os.

    115 GitHub stars~468 tokensUpdated yesterday
    Auto-check passed
  • Slack Message Check

    itseffi/agentic-os

    Check Slack for important messages and activity. An agent skill from itseffi/agentic-os.

    115 GitHub stars~465 tokensUpdated yesterday
    Auto-check passed

Questions about Spec Writing

What does Spec Writing do?

Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria. Spec Writing is an agent skill from itseffi/agentic-os. Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

When should I use Spec Writing?

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

How do I install Spec Writing in Claude Code?

Run `npx skills add itseffi/agentic-os --skill spec-writing -a claude-code`. Or copy the skill folder (.agents/skills/spec-writing in itseffi/agentic-os) into .claude/skills/spec-writing in your project. Claude Code loads it when a task matches its description.

How do I install Spec Writing in Codex?

Run `npx skills add itseffi/agentic-os --skill spec-writing -a codex`. Or copy the skill folder (.agents/skills/spec-writing in itseffi/agentic-os) into .agents/skills/spec-writing in your project. Codex loads it when a task matches its description.

Can I use Spec Writing 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 itseffi/agentic-os --skill spec-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-writing, .gemini/skills/spec-writing, .github/skills/spec-writing and .opencode/skills/spec-writing in your project.

What does Spec Writing need to run?

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

Does Spec Writing 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 Spec Writing 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 Spec Writing use?

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

How many tokens does Spec Writing use?

About 464 tokens (SKILL.md is roughly 1.9k 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 Spec Writing?

Skills that share tags, products or a category with Spec Writing: 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 Spec Writing?

itseffi (a GitHub user) maintains it in itseffi/agentic-os, which has 115 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

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