thrifty-brief

Generate concise unit briefs from terse specs using CONTRACT.md.

15|Updated May 28, 2026

Search Tags:#automation #planning #contract #haiku #brief #unit-spec #thrifty

Ready to run

npx skills add https://github.com/2389-research/thrifty --skill thrifty-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: thrifty-brief
Source: https://github.com/2389-research/thrifty/tree/main/skills/thrifty-brief
Command: npx skills add https://github.com/2389-research/thrifty --skill thrifty-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brief-writer subskill for thrifty's split planning mode expands one terse unit spec into a full, self-contained brief (briefs/UNIT-NNN.md) that a Haiku executor can run with minimal ambiguity, while respecting the cross-unit contract.

Core Features & Use Cases

Expands a terse unit spec into a full, self-contained brief with concrete acceptance criteria.
Maintains within-unit authority and references CONTRACT.md for cross-unit decisions.
Produces machine-checkable briefs that can drive Haiku execution and automated verification.

Quick Start

Generate briefs/UNIT-NNN.md from UNIT-SPECS using CONTRACT.md as the cross-unit reference for Haiku execution.

Frequently Asked Questions about thrifty-brief

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

FAQPage Schema

How do I generate unit briefs for Haiku from terse unit specs?▼

To generate unit briefs for Haiku, expand terse unit specs into full, self-contained briefs using the cross-unit CONTRACT.md as the authority to preserve acceptance criteria and cross-module references.

What is a unit brief in automated planning and contract management?▼

A unit brief is a concise, self-contained document that expands a terse unit spec with concrete acceptance criteria while referencing CONTRACT.md to maintain within-unit autonomy and cross-unit decisions.

How does CONTRACT.md maintain authority across multiple unit briefs?▼

CONTRACT.md maintains authority by serving as the cross-unit reference document, ensuring that all generated unit briefs preserve cross-module references and adhere to established cross-unit decisions without overriding them.

Can I use thrifty planning mode to create machine-checkable briefs for automated execution?▼

Yes, thrifty planning mode produces machine-checkable briefs that define concrete acceptance criteria and cross-module references, driving Haiku execution and enabling automated verification with minimal ambiguity.

Do I need a cross-unit contract to expand unit specs into Haiku execution briefs?▼

Yes, a cross-unit contract is required to expand unit specs into Haiku execution briefs, ensuring that within-unit constraints preserve cross-unit decisions and all acceptance criteria are accurately maintained.

Why does my generated unit brief lose cross-module references during Haiku execution?▼

Generated unit briefs lose cross-module references when within-unit constraints fail to properly reference CONTRACT.md, causing the expansion process to drop necessary cross-unit decisions required for Haiku execution.