thrifty-plan

Decompose projects into units and generate CONTRACT.md, LEDGER.md, and per-unit BRIEF documents.

15|Updated May 28, 2026
One-click install
npx skills add https://github.com/2389-research/thrifty --skill thrifty-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thrifty-plan
Source: https://github.com/2389-research/thrifty/tree/main/skills/thrifty-plan
Command: npx skills add https://github.com/2389-research/thrifty --skill thrifty-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined planning workflow for thrifty by decomposing complex work into units, producing a cross-unit CONTRACT.md, per-unit BRIEF documents, and an initial LEDGER to keep units aligned across sprints.

Core Features & Use Cases

  • Establish cross-unit strategy: choose decomposition mode (partition, relay, or layered) and decide the planning tier (direct vs split) to structure work.
  • Contract and ledger generation: create a CONTRACT.md that pins cross-unit interfaces and a LEDGER.md to track unit status and dependencies.
  • Generate unit briefs or specs: produce per-unit BRIEF documents (direct tier) or UNIT-SPECS.md (split tier) to formalize acceptance criteria and ownership.
  • Plan governance: define the dependency graph, unit order, and orchestration flow so Thrify can coordinate multiple executors and checks.

Quick Start

Choose a decomposition mode, select a tier, and generate CONTRACT.md, LEDGER.md, and per-unit briefs to begin thrifty planning.

Frequently Asked Questions about thrifty-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan multi-unit task sprints using contract management?

Plan multi-unit task sprints by decomposing complex work into units, pinning cross-unit decisions with a CONTRACT.md, and tracking dependencies through a LEDGER.md to keep all units aligned.

What is the best way to coordinate cross-unit work in a sequentially developed project?

Coordinating cross-unit work requires generating a central CONTRACT.md to pin interfaces and a LEDGER.md to track unit status, allowing an orchestrator to manage the dependency graph and execution order.

How do I generate per-unit briefs and acceptance criteria for partitioned projects?

Generate per-unit briefs by selecting a planning tier, which produces BRIEF documents for the direct tier or a UNIT-SPECS.md file for the split tier to formalize acceptance criteria and ownership.

Can I use a ledger and contract system for projects with layered decomposition modes?

Yes, the ledger and contract system supports partition, relay, and layered decomposition modes, allowing you to structure work and define the orchestration flow across multiple executors.

Do I need a central architect to manage cross-unit interfaces and task briefs?

Yes, a central architect is required to write the cross-unit contracts and briefs, define the dependency graph, and coordinate the execution flow through the orchestrator.

When should I choose split tier planning over direct tier briefs for task sprints?

Choose split tier planning to generate a consolidated UNIT-SPECS.md instead of individual per-unit BRIEF documents when you need a unified specification format for formalizing acceptance criteria across multiple units.