pev-cycle
Skill0 starsChanged 4 months agoMITView on GitHub
Plan-Execute-Verify cycle for feature work. Plan phase uses Conductor scaffold with budgets and approval gate; execute one slice at a time; verify externally.
In this repository138 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/context-budget.mdcCursor rule
- .cursor/rules/delegation-law.mdcCursor rule
- .cursor/rules/harness-doctrine.mdcCursor rule
- .cursor/rules/verification-law.mdcCursor rule
- agent-interface-designSkill
- agentloop-coreSkill
- agent-loopSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- conductor-planSkill
- context-auditSkill
- context-compactSkill
- context-surgeonSkill
- contrastingSkill
- deployment-auditSkill
- doctorSkill
- harness-designSkill
- humaniseSkill
- implementation-notesSkill
- implementation-planSkill
- interview-meSkill
- no-ai-slopSkill
- optional-ponytailSkill
- opus-promptingSkill
- persistent-memorySkill
- pitch-packagerSkill
- progressive-disclosureSkill
- quality-composeSkill
- reference-huntSkill
- seo-copywritingSkill
- ship-gateSkill
- subagent-swarmSkill
- ui-ux-auditSkill
- warroom-councilSkill
- writer-verifierSkill
- agent-interface-designSkill
- agentloop-coreSkill
- agent-loopSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- conductor-planSkill
- context-auditSkill
- context-compactSkill
- context-surgeonSkill
- contrastingSkill
- deployment-auditSkill
- doctorSkill
- harness-designSkill
- humaniseSkill
- implementation-notesSkill
- implementation-planSkill
- interview-meSkill
- no-ai-slopSkill
- optional-ponytailSkill
- opus-promptingSkill
- persistent-memorySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Do not verify by asking the model to re-read its own output alone.
- Very specific: line 17
If the map is fuzzy, run /unknowns before Conductor Plan.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PEV Cycle
- Plan (Conductor) — invoke
conductor-plan.- Adaptive scaffold, consumption estimates, parallelization map, agent recommendations, risks.
- Write
.agentloop/plan.md+.agentloop/stop.yaml. - Hard stop: wait for approval before Execute.
- Execute — one approved slice; no speculative files; update handoff at slice end (
context-surgeon). - Verify — run external gate; on fail, treat the error as the next prompt (keep log verbatim).
- Repeat until success or stop conditions fire (
max_turns, no-progress, budget abort, human escalation).
Do not verify by asking the model to re-read its own output alone.
If the map is fuzzy, run /unknowns before Conductor Plan.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.