/goaldocslow riskintermediatesafety D · 50 · open-endedForward Futurepre-dates current gate · under review

Make onboarding work from zero

Follow the README in a throwaway environment, fix every hidden setup assumption, and restart until a clean clone just works.

prompt
→ Claude
Clone [repository] into a disposable environment and follow only its README to the documented ready state, such as running the app or building the package. When a step fails or assumes missing knowledge, record the gap, fix the setup or documentation issue, discard the environment, and start again. Carry no dependencies, configuration, credentials, or repairs between attempts. Stop when one uninterrupted fresh clone reaches that state, progress stalls, or [budget] ends. Return exact commands, gaps closed, and remaining blockers.
claude-code · codex

Use this when

Use this to test whether a repository's onboarding instructions work in a clean environment without undocumented help.

How it runs

  1. Create a disposable environment with no project dependencies or configuration carried over from another checkout.
  2. Fresh-clone the repository and follow only the README, recording every missing step, hidden assumption, and failure.
  3. Fix the smallest setup or documentation gap, discard the environment completely, and begin again.
  4. Repeat until one clean run reaches the documented ready state without intervention, then report the exact commands and gaps closed.

Done when

✓ A clean environment reaches the documented ready state using only the README. The final run uses only the onboarding guide and needs no unstated dependency, configuration, or manual repair.

Why it works

Destroying the environment after each repair prevents local state from hiding the next problem. The final uninterrupted run is direct evidence that the README, not the operator's memory, is sufficient.

Implementation note

Use an isolated disposable environment and review the repository before executing it. Never copy personal credentials into the test environment or run untrusted setup scripts on a production host.

Source: Forward Future ↗

More docs loops

Changelog generation from commits

/goalloopreponew

Turn the commit history since the last release tag into a human-readable, categorized CHANGELOG entry ready for the next version.

prompt
→ Claude
/goal CHANGELOG.md has a complete entry for the next release — read every commit since the last version tag, group changes into Added, Changed, Fixed, and Removed, write user-facing descriptions (not commit messages), link PR numbers, and flag anything that looks like a breaking change; stop after 5 turns
docslow risk

Close the gaps before you build

/loopForward Futurenew

Fill documentation gaps until requirements, technical design, acceptance criteria, and test strategy describe one buildable system.

prompt
→ Claude
Prepare [project] for implementation. Ensure its documents cover requirements, technical design, tasks with acceptance criteria, and test strategy. Each round, fix the largest gap or contradiction that could make two competent engineers build different systems. Keep details traceable, record assumptions, and ask before product forks. Recheck consistency, then have two independent reviewers describe the components, data model, dependencies, and definition of done. Stop when they materially agree and every artifact is testable, or a decision needs the user.
docslow risk

Fix doc drift, ship a PR

/scheduleForward Futurenew

Compare every doc against the current code, fix what's stale, verify commands and links, and open a reviewable PR.

prompt
→ Claude
Whenever a documentation pass is needed, review the codebase in full and make sure all documentation reflects the current implementation. Update stale documentation, verify the changes, then open a pull request.
docslow risk