name	spec-first
description	Write the goal spec on disk before the agent acts, so it can't drift. Use before any multi-step task.
when_to_use	a task with more than 2 steps, a long-running job, "build X", agent drifting

Spec First

Without an external contract, the agent drifts after ~3 iterations — and the failure looks like progress (code written, tests pass, wrong goal solved). Write PROMPT.md BEFORE acting:

Goal — one sentence.
Done when — concrete, checkable conditions. "Test suite green: ".
Never touch — files/areas off-limits.
Stop if — more than N files outside scope change; a passing test starts failing. The agent re-reads this file every iteration. State (what's done) goes in a separate IMPLEMENTATION_PLAN.md it updates in place. If you can't write "done when" concretely, the task isn't ready — clarify before coding.

Más de este repositorio

mismo repositorio

adversarial-verify

YaoYinYing/REvoDesign

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

2026-07-122

authz-check

YaoYinYing/REvoDesign

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

2026-07-122

bisect-regression

YaoYinYing/REvoDesign

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

2026-07-122

changelog-from-diff

YaoYinYing/REvoDesign

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

2026-07-122

clean-commits

YaoYinYing/REvoDesign

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

2026-07-122

context-budget

YaoYinYing/REvoDesign

Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.

2026-07-122

name	spec-first
description	Write the goal spec on disk before the agent acts, so it can't drift. Use before any multi-step task.
when_to_use	a task with more than 2 steps, a long-running job, "build X", agent drifting

Spec First

Without an external contract, the agent drifts after ~3 iterations — and the failure looks like progress (code written, tests pass, wrong goal solved). Write PROMPT.md BEFORE acting:

Goal — one sentence.
Done when — concrete, checkable conditions. "Test suite green: ".
Never touch — files/areas off-limits.
Stop if — more than N files outside scope change; a passing test starts failing. The agent re-reads this file every iteration. State (what's done) goes in a separate IMPLEMENTATION_PLAN.md it updates in place. If you can't write "done when" concretely, the task isn't ready — clarify before coding.