What is shipwrights-spec-revise?

A command for recording requested changes to a drafted software specification while preserving the previous plan as a revision.

Use it when a drafted specification has a missed constraint, an unsuitable approach, or incomplete acceptance criteria, so the next specification run can re-analyse the added note.

It keeps a history of what changed and prevents revisions from being applied to specifications that are already approved or in the wrong state.

shipwrights-spec-revise — Skill for Claude Code and Codex by shipwrigh

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 shipwrights/core --skill shipwrights-spec-revise

Clone the repo

git clone --depth 1 https://github.com/shipwrights/core

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/shipwrights/core/shipwrights-spec-revise/github.svg)](https://agentmods.dev/skills/shipwrights/core/shipwrights-spec-revise)

Your own site

<a href="https://agentmods.dev/skills/shipwrights/core/shipwrights-spec-revise"><img src="https://agentmods.dev/badge/skills/shipwrights/core/shipwrights-spec-revise/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/shipwrights/core/shipwrights-spec-revise"><img src="https://agentmods.dev/badge/skills/shipwrights/core/shipwrights-spec-revise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 476 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.

Model	Per session	Once invoked
Fable 5.1	$0.00069	$0.00476
Opus 5	$0.00034	$0.00238
Sonnet 5	$0.00014	$0.00095
Haiku 4.5	$0.00007	$0.00048

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

Security

Grade A, and why

shipwrights-spec-revise 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 8d 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/shipwrights-spec-revise/SKILL.md · 40 lines

What it actually says

/shipwrights-spec-revise — request changes to a drafted spec

You've read the plan and want substantive changes. Use this when the architect's analysis missed a constraint, picked the wrong approach, or the spec's acceptance is incomplete.

What you do

Validate spec exists and is at status: drafted.
Snapshot the current plan to .shipwrights/specs/<id>.r<N>.md (N = revision counter + 1).
Append the note to .shipwrights/specs/<id>.input.md under a ## Revision N heading.
Bump revisions in the plan frontmatter (or insert it if missing).
Leave status: drafted — the orchestrator skill will pick up the revised input next time /shipwrights-spec <id> is invoked.
Commit: chore(spec): request revision N on <id>.

Hard rules

Refuse if the spec isn't drafted. After approval, mid-pipeline changes need different handling (rerun specific stages, or cancel + new draft).
Refuse if no note is supplied. A revision without a note is meaningless.
Refuse if working tree is dirty.

Output

✓ Revision N recorded for <id>.
  Snapshot: .shipwrights/specs/<id>.r<N>.md
  Note appended to: .shipwrights/specs/<id>.input.md

Next: /shipwrights-spec <id>     # re-runs analyze + plan with the revision

Why snapshot the previous plan?

Audit trail. The user can compare revision N to revision N-1 by diff .shipwrights/specs/<id>.r<N>.md docs/backlog/specs/<id>-*.md. Useful when a chain of revisions is converging or diverging.

CLI implementation: lib/commands/spec-revise.mjs.

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.

8d ago First seen · 40 lines · 69 tokens per session scan A 896ae7e36f0e

Subscribe to this mod's changes

shipwrights-spec-revise is a skill published in the GitHub repository shipwrights/core (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 476 once invoked, about $0.0003 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-31.

Claude Code Orchestration Planning agentic-coding ai-agents claude-code-plugin epic-management

great_cto

Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.

avelikiy/great_cto · 32 tokens

vertical-real-estate

Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…

avelikiy/great_cto · 99 tokens

product-economics

Does this product make money at a price someone will pay? Forces contribution margin, a price with a stated basis, and a bottom-up market size — each number labelled measured / assumed / unknown, so a guess can never be read as a calculation.

avelikiy/great_cto · 55 tokens

anti-patterns

Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

avelikiy/great_cto · 59 tokens

cost-model

Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.