First Four Hours documentation

These pages are for the people who will still own the work after the agent says it is done. If that is you, start with why the suite exists. The skills themselves are instructions for coding agents; this documentation explains what they are for and how they fit together.

Get started

• Install First Four Hours: what you need, how to install the whole suite or one skill, and how to check that it worked.
• Your first run: start one skill on a real problem, see what it leaves behind, and learn how skills start.
• Choose a skill: find the smallest skill for the problem in front of you, and when to combine skills.

Understand the suite

• Why First Four Hours exists: the problem the suite addresses, and what it does not promise.
• How the suite works: what a skill is, how to pick the smallest one that helps, how skills hand work to each other, and how the suite is organized.
• Anatomy of a sealed blueprint: one illustrative plan, section by section, and why each part is there.

Skills

• Skills: one page per skill, grouped by domain: what it is for, how to start it, what it produces, and where it stops.
• How skills hand work to each other: the real handoffs between skills, where they are stored, and who starts the next step.

Solve a recurring problem

• Recipes: start from a problem you keep losing time to, such as a fix that only patches the symptom or a plan reopened halfway through editing, and see which skills deal with it.

Look something up

• Reference: exact facts about each skill, such as its domain, source folder, how it starts, and the Python it needs, and where every other fact is kept.

Fix a problem

• Troubleshooting: find the symptom you see, its likely cause, a check that changes nothing, and the next step.

Contribute

• Contributor guide: change the suite, validate the affected behavior, and maintain packages, releases, and documentation.

Other sources

• The repository README lists every skill by domain and shows how to install them.
• Each skill's SKILL.md, under skills/<domain>/<skill>/, is the contract its agent follows.
• Writing the documentation explains how these pages are organized and the rules for changing them.