A repair tool for issues found during a review of product requirements and an implementation plan. It treats the documents as connected graphs of items, relationships, and facts.

Use it to repair missing or conflicting requirements, implementation-plan issues, dependency cycles, and related design-document problems.

It helps correct specification and planning problems while keeping requirement identifiers stable and separating changes that need human approval.

fix-plan — Skill for Claude Code by context4ai/workflow

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 context4ai/workflow --skill fix-plan

Clone the repo

git clone --depth 1 https://github.com/context4ai/workflow

Made for: Claude Code.

Or install kgdd, the plugin that ships this one along with the rest of its 10 skills.

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/context4ai/workflow/fix-plan/github.svg)](https://agentmods.dev/skills/context4ai/workflow/fix-plan)

Your own site

<a href="https://agentmods.dev/skills/context4ai/workflow/fix-plan"><img src="https://agentmods.dev/badge/skills/context4ai/workflow/fix-plan/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/context4ai/workflow/fix-plan"><img src="https://agentmods.dev/badge/skills/context4ai/workflow/fix-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,916 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.00042	$0.01916
Opus 5.5	$0.00017	$0.00766
Sonnet 5.5	$0.00008	$0.00383
Haiku 4.5	$0.00004	$0.00192

Measured 1mo ago against content hash 8274c88a7b59, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fix-plan 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 1mo 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/fix-plan/SKILL.md · 176 lines

How it starts

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

/fix-plan - PRD and Plan Issue Repair

Fix issues in the PRD (Product-layer graph) and Plan (Code-layer graph) based on /review results.

Design Workspace (design-dir)

The default workspace for design documents is design/. On startup the Agent checks:

design/ directory exists --> use design/ as <design-dir>
design/ does not exist --> pause and ask the user for the design workspace path, explaining the accepted directory structure:
```
<design-dir>/<version>/(prd|plan).md
Examples: design/v1.0.1/prd.md, design/v0.5.0/plan.md
```

design/archive/: Archived or inactive design documents. When exploring existing graph structures, treat as low-priority reference -- read active version directories first and fall back to archive only when relevant context cannot be found in active versions.

All paths below use <design-dir> to refer to this directory.

TL;DR -- Hard Rules

Input: /review results + PRD + Plan
PRD is the contractual authority: Downstream changes to the Plan can be made directly; upstream changes to the PRD require human approval
Fix = graph operations: Add/delete/modify Nodes, Edges, and Facts -- not free-form text editing
Fact changes must use [-] + [+] + supersedes -- do not use [~]
Spec IDs are identity IDs, never reused: Modification = [-Sn] + [+Snew] + supersedes
Re-run /review after fixing to verify

Agent Responsibility Boundaries

Yes: Fix PRD and Plan issues based on review results
Yes: Add missing specs, Nodes, Edges, and Facts
Yes: Resolve logic conflicts
No: Do not make changes beyond the scope of review results
No: Do not recommend next steps after completion

Layer Hierarchy

Layer	Modeling Language	Authority
Product (PRD)	Product(domain/application/story) + Fact (specs attach only to stories)	Contractual authority
Code (Plan)	Package/Symbol Node + guide/spec/warning/example/decision	Execution guidance

Read the full file on GitHub · 176 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.

1mo ago First seen · 176 lines · 42 tokens per session scan A 8274c88a7b59

Subscribe to this mod's changes

fix-plan is a skill published in the GitHub repository context4ai/workflow (4 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 1,916 once invoked, about $0.0002 per session on Opus 5.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.

Code review Planning

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens