A planning command that turns a product requirements document, technical design, decisions, and known risks into a backlog, milestones, and tests. A backlog is a prioritized list of work to do.

Use it to create an implementation plan, group work into milestones, define acceptance criteria, and map requirements and risks to test cases.

It connects planned work to earlier decisions and risks, so important safeguards and validation are not forgotten. It also gives the project a clearer order of implementation.

ledger-plan — Command for Claude Code by synaptiai

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.

Clone the repo

git clone --depth 1 https://github.com/synaptiai/synapti-marketplace

Made for: Claude Code.

Or install context-ledger, the plugin that ships this one along with the rest of its 5 skills, 8 commands, 5 agents.

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/commands/synaptiai/synapti-marketplace/ledger-plan/github.svg)](https://agentmods.dev/commands/synaptiai/synapti-marketplace/ledger-plan)

Your own site

<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/ledger-plan"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/ledger-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/commands/synaptiai/synapti-marketplace/ledger-plan"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/ledger-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,600 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.00016	$0.01600
Opus 5	$0.00008	$0.00800
Sonnet 5	$0.00003	$0.00320
Haiku 4.5	$0.00002	$0.00160

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

Security

Grade A, and why

ledger-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 10d 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.

plugins/context-ledger/commands/ledger-plan.md · 266 lines

How it starts

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

Generate Plan

Generate implementation plan including backlog, milestones, and test plan.

Risk-Aware Planning: Plan items link to decisions and explicitly address identified risks with mitigations built into milestones.

Arguments

$ARGUMENTS: Optional plan focus or format.

Optional flags:

--format <format> - Output format (markdown, yaml, json)
--milestones <n> - Number of milestones to generate
--include-tests - Include detailed test plan

Prerequisites

Specs complete (/ledger-spec)
06-prd/PRD.md exists
07-architecture/ARCHITECTURE.md exists
04-decisions/DECISIONS.yaml exists
05-risks/RISKS.yaml exists

Workflow

Load All Artifacts
- Read PRD requirements
- Read architecture components
- Read decisions and risks
Generate Backlog
- Extract work items from PRD/Architecture
- Link items to decisions
- Prioritize by decision status and risk
Create Milestones
- Group items into logical milestones
- Include risk mitigations in early milestones
- Define acceptance criteria
Generate Test Plan
- Map requirements to test cases
- Include risk validation tests
- Define test priorities
Write PLAN.md
- Comprehensive implementation plan
- Traceability to decisions/risks

Example Usage

Full plan generation

/ledger-plan

With specific milestone count

/ledger-plan --milestones 4

Include detailed tests

/ledger-plan --include-tests

YAML format for tooling

/ledger-plan --format yaml

Output

## Plan Generation Complete

**Backlog Items:** 47
**Milestones:** 4
**Test Cases:** 32

### Plan Summary

#### Milestone 1: Foundation (Weeks 1-3)
- Items: 12
- Risk mitigations: RISK-tech-cold-start, RISK-tech-llm-cost
- Key decisions: DEC-tech-serverless, DEC-tech-postgres-primary

#### Milestone 2: Core Features (Weeks 4-7)
- Items: 18
- Risk mitigations: RISK-retention-expert-churn
- Key decisions: DEC-scope-power-users-first, DEC-ux-simplified-onboarding

#### Milestone 3: Monetization (Weeks 8-10)
- Items: 10
- Risk mitigations: RISK-economics-free-tier
- Key decisions: DEC-pricing-freemium

#### Milestone 4: Launch Prep (Weeks 11-12)
- Items: 7
- Risk mitigations: RISK-ops-support-volume
- Key decisions: DEC-ops-support-model

### Files Generated
- `08-plan/PLAN.md`

### Next Steps
- Begin implementation following milestone sequence
- Run `/ledger-update` when new learnings emerge

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

10d ago First seen · 266 lines · 16 tokens per session scan A c16ff6fa4ee7

Subscribe to this mod's changes

ledger-plan is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,600 once invoked, about $0.0001 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.

Planning agentic-design-patterns agentic-development agentic-workflow ai-developer-tools ai-first claude-code-plugin

create-worktree

Follow these steps to create a git worktree.

CaptainMe-AI/lead-dev-os · 0 tokens

paper-trail-review

Review and arbitrate problematic references (cascade-exhausted, unresolved UID, awaiting OCR). Generates an up-to-date report, walks through cases by category, and applies arbitration decisions to the registry.

roomi-fields/paper-trail · 39 tokens

paper-trail-new-paper

Start writing an academic paper (IMRaD structure) on a topic, with anti-hallucination citation verification at every step. Builds on existing audited SOTAs.

roomi-fields/paper-trail · 35 tokens

paper-trail-registry-cleanup

Nettoyage historique du registre des fiches bibliographiques (les 900 fiches existantes). Cible les vieilles fiches mal nommées (0000, untitled) ET les duplicates avec suffixes numériques (foo2020bar2, 234) qui sont des artefacts de runs INGEST passés. Délègue les décisions au sub-agent textbook-resolver. Les merge…

roomi-fields/paper-trail · 109 tokens

paper-trail-cascade

Acquire PDFs via the 8-source cascade (11 with opt-in extended sources) for a single ref by slug, or a batch filtered by state. Validates page 1 anti-homonymy on each download.

roomi-fields/paper-trail · 44 tokens

cc-refactor

(Conductor) Refactor a file or module for clarity and simplicity.

yeisonrestrepo/code-conductor · 14 tokens