writing-specs

writing-specs is a skill for Claude Code from arittr/spectacular. It costs 37 tokens per session (5,755 once invoked), scanned A, original, MIT.

A workflow for writing a lean feature specification, which describes what should be built and why before implementation begins.

In plain words
What is it for?
Use it to create a run record, explore requirements, write a specification, and check its architecture against project rules.
Why use it?
It separates requirements and architecture from the later task plan, helping teams agree on the feature before coding.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; names the TodoWrite tool.

Part of the spectacular plugin — 14 skills, 5 commands, 1 hook shipped together

Good fit Use it to create a run record, explore requirements, write a specification, and check its architecture against project rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arittr/spectacular/writing-specs
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add arittr/spectacular --skill writing-specs
Clone the repo
git clone --depth 1 https://github.com/arittr/spectacular

Made for: Claude Code.

Or install spectacular, the plugin that ships this one along with the rest of its 14 skills, 5 commands, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for writing-specs

README.md
[![agentmods](https://agentmods.dev/badge/skills/arittr/spectacular/writing-specs/github.svg)](https://agentmods.dev/skills/arittr/spectacular/writing-specs)
Your own site
<a href="https://agentmods.dev/skills/arittr/spectacular/writing-specs"><img src="https://agentmods.dev/badge/skills/arittr/spectacular/writing-specs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for writing-specs

Your own site · 80×15
<a href="https://agentmods.dev/skills/arittr/spectacular/writing-specs"><img src="https://agentmods.dev/badge/skills/arittr/spectacular/writing-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,755 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.05755
Opus 5 $0.00018 $0.02877
Sonnet 5 $0.00007 $0.01151
Haiku 4.5 $0.00004 $0.00575

Measured 9d ago against content hash a81853786b18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

writing-specs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/writing-specs/SKILL.md · 759 lines

How it starts

The opening of the file, as written. The whole thing — 759 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Specifications

Overview

A specification defines WHAT to build and WHY. It is NOT an implementation plan.

Core principle: Reference constitutions, link to docs, keep it lean. The /plan command handles task decomposition.

Spec = Requirements + Architecture Plan = Tasks + Dependencies

When to Use

Use this skill when:

  • Invoked from /spectacular:spec slash command
  • Creating a new feature specification from scratch
  • Need the complete spec workflow (Run ID, worktree, brainstorm, spec, validation)

Do NOT use for:

  • Implementation plans with task breakdown - Use /spectacular:plan instead
  • API documentation - Goes in code comments or separate docs
  • Runbooks or operational guides - Different document type

Announce: "I'm using the writing-specs skill to create a feature specification."

Workspace Detection

Before starting the spec workflow, detect the workspace mode:

# Detect workspace mode
REPO_COUNT=$(find . -maxdepth 2 -name ".git" -type d 2>/dev/null | wc -l | tr -d ' ')
if [ "$REPO_COUNT" -gt 1 ]; then
  echo "Multi-repo workspace detected ($REPO_COUNT repos)"
  WORKSPACE_MODE="multi-repo"
  WORKSPACE_ROOT=$(pwd)
  # List detected repos
  find . -maxdepth 2 -name ".git" -type d | xargs -I{} dirname {} | sed 's|^\./||'
else
  echo "Single-repo mode"
  WORKSPACE_MODE="single-repo"
fi

Single-repo mode (current behavior):

  • Specs stored in specs/{runId}-{feature}/spec.md at repo root
  • Worktree created at .worktrees/{runId}-main/
  • Constitution referenced from @docs/constitutions/current/

Multi-repo mode (new behavior):

  • Specs stored in ./specs/{runId}-{feature}/spec.md at WORKSPACE root
  • NO worktree created (specs live at workspace level, not inside any repo)
  • Each repo's constitution referenced separately

Constitution Adherence

All specifications MUST follow: @docs/constitutions/current/

  • architecture.md - Layer boundaries, project structure
  • patterns.md - Mandatory patterns (next-safe-action, ts-pattern, etc.)
  • schema-rules.md - Database design philosophy
  • tech-stack.md - Approved libraries and versions
  • testing.md - Testing requirements

Read the full file on GitHub · 759 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 759 lines · 37 tokens per session scan A a81853786b18

Subscribe to this mod's changes

writing-specs is a skill published in the GitHub repository arittr/spectacular (20 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 5,755 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens