Fragment

Fragment is a set of plain-text file protocols that runs nothing; the core files include docs/AGENT-PROTOCOL.md, CLAUDE.md, AGENTS.md, docs/STATE.md and scripts/docs-check.sh.

Fragment's STATE.md contains a dedicated section recording decisions already made (for example, registering with a phone number instead of an email, and why), for the next session to read before asking questions.

The Fragment project was used by two people on two operating systems with two different agents, completing 25 commits in 18 hours.

Without any teaching, the second team member's seven commits all showed the same three-file shape (index, board, actual work); simply reading the same protocol file, they converged on the same actions.

Fragment's limitations include: sample size n=2, with both production repositories run by the author himself; concurrency beyond two people is untested; Fragment does not prove it prevents bugs—what it prevents is context loss and re-arguing matters already decided.

In Claude Code, you can try Fragment by running npx skills add hematenergi/fragment --skill fragment, or by pasting the install prompt from the website into the agent you use.

The author's attempt to maintain just a single notes file broke down after about five days: one session forgot to update it, the next session trusted the stale board, and so it was back to the briefing loop from the beginning.

Fragment separates the check layer from the business rules: repository-specific rules live in local files that are sourced in by the shared check script, so updating the check logic never touches these local rules.