Individual skill

requirement-ledger

Track a project's long-lived requirements and recall what earlier deliveries decided. Use before clarifying a new request in an evolving project, and when a run starts, finishes or is archived.

skills/requirement-ledger/SKILL.md

Read pinned source

Source commit ed8aa57b1aca020e35f1eb85838bd2b21f56d266

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 11
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

matt-pocock Repository topic
paseo Repository topic
workloop Repository topic
agent Repository topic
claude-code-skills Repository topic
codex-skill Repository topic
skills Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 5,034 bytes
reference/authorization.mddoc · 6,602 bytes
reference/context.mddoc · 4,050 bytes
reference/domain.mddoc · 2,331 bytes
reference/lookup.mddoc · 4,594 bytes
reference/storage.mddoc · 7,847 bytes
scripts/context.mjsruns · 24,205 bytes
scripts/doctor.mjsruns · 12,487 bytes
scripts/lookup.mjsruns · 13,590 bytes
scripts/record.mjsruns · 5,272 bytes
scripts/refs.mjsruns · 4,417 bytes
scripts/relations.mjsruns · 8,644 bytes
scripts/req.mjsruns · 35,132 bytes
scripts/runstate.mjsruns · 7,383 bytes
scripts/store.mjsruns · 21,420 bytes
scripts/test/acceptance.test.mjsruns · 32,707 bytes
scripts/test/context.test.mjsruns · 33,225 bytes
scripts/test/doctor.test.mjsruns · 20,297 bytes
scripts/test/integration.test.mjsruns · 32,628 bytes
scripts/test/lookup.test.mjsruns · 26,922 bytes
scripts/test/spawn.mjsruns · 675 bytes
scripts/test/store.test.mjsruns · 43,332 bytes
scripts/time.mjsruns · 790 bytes
scripts/yaml.mjsruns · 11,462 bytes

Read excerpt


# Requirement Ledger

A **requirement** is one long-lived business capability of a project, named `REQ-<n>`. It outlives any single delivery: the product evolves and the same requirement gains new runs. The ledger keeps one Markdown record per requirement — its current summary, plus *references* to the runs, specs, ADRs, deliveries and code behind it. It holds pointers, never copies.

Two boundaries hold throughout this skill:

- **Workloop is the only coding orchestration centre.** It owns runs, tickets, attempts, verdicts, delivery state and the run state machine; the ledger owns none of that, and reads a run's `state.json` without writing it.
- **The ledger executes nothing.** It runs no code, starts no agents, creates no tickets and pushes nothing. It answers two questions: which requirement is this, and where is that requirement's history.

## Look up before you clarify

Before a request becomes a spec, a ticket or a change, run the lookup on the user's own words:

```