weave-prompt
Skill0 starsChanged 17 days agoMITView on GitHub
Weave prompt: compare independent adversarial implementations, then adopt the single best one
1 other project uses a version of this.
Adopted by
Most recently taken up by
- GabrielKqw/weave-agent-workflowtheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- GabrielKqw/weave-agent-workflow★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- action-worktreeSkill
- action-worktreesSkill
- agent-messaging-session-relaySkill
- business-case-study-internalSkill
- business-case-study-publicSkill
- business-pr-releaseSkill
- business-report-leadershipSkill
- business-report-org-wideSkill
- business-researchSkill
- changelog-refreshSkill
- changelog-rewrite-aggressivelySkill
- changelogSkill
- commitSkill
- disk-reclaimSkill
- diskSkill
- disk-usageSkill
- double-check-alignSkill
- double-checkSkill
- gh-create-issueSkill
- gh-rendered-markdownSkill
- git-branch-redo-from-scratchSkill
- git-branch-soft-reset-and-recommitSkill
- github-actions-bumping-github-actionsSkill
- github-actions-update-actionSkill
- github-actions-update-actionsSkill
- goal-planner-auditSkill
- goal-planner-printSkill
- goal-planner-profileSkill
- goal-planner-synthesizeSkill
- lean-tightenSkill
- lean-trim-commentsSkill
- lean-writingSkill
- merge-pr-merge-manySkill
- merge-pr-merge-oneSkill
- model-cli-agySkill
- model-cli-codexSkill
- model-cli-cursorSkill
- package-updater-update-packageSkill
- package-updater-updateSkill
- package-updater-update-toolchainSkill
- package-updater-updating-packagesSkill
- pr-merge-commitSkill
- pr-refreshSkill
- pr-review-prSkill
- pr-rewriteSkill
- prSkill
- pytest-optimizer-00-scanSkill
- pytest-optimizer-01-benchmarkSkill
- pytest-optimizer-02-planSkill
- pytest-optimizer-03-executeSkill
- pytest-optimizerSkill
- rebaseSkill
- release-bumpSkill
- release-cutSkill
- release-update-downstream-packagesSkill
- repo-skills-deriveSkill
- research-assessSkill
- research-continueSkill
- research-foraySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Before any other unresolved configuration choice or operational step, read references/worker-backends.md (Caller contract).
- Distinctive: line 31
If interactive choice is unavailable, honor its documented headless default.
- Very specific: line 39
Write the plan per references/mutating-run.md (Shared phases, Orchestration plan).
- Very specific: line 47
Follow references/ensemble-core.md (Start the session) with --command prompt --mutating.
- Very specific: line 53
Use the worker prompt body of references/mutating-run.md (Shared phases), with the implementation prompt as <the task>.
- Very specific: line 65
Follow references/mutating-run.md (Refinement passes), repeating Phases 2 and 3.
- Very specific: line 71
Follow references/mutating-run.md (Apply gate and presentation): show the comparison and the recommended winner, and let the user choose …
- Very specific: line 82
If adopt refuses, follow references/mutating-run.md (Apply gate and presentation).
- Distinctive: line 84
Run the project's quality gates, then record the state:
- Very specific: line 94
Read references/present-results.md and references/prompt.md, and apply them with RESULT_KIND = prompt, ARTIFACT_PATH = …
- Very specific: line 100
Follow ensemble-core.md (Finish).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Weave Prompt
Run an implementation prompt across independent adversarial workers, using host-native sub-agents by default or separate model CLIs when selected. After all workers finish, compare the implementations and adopt the single best one, whole. Unlike the weave-execute skill, which cherry-picks the best parts of each worker's work, this command never merges code across implementations.
The implementation prompt comes from $ARGUMENTS. With no prompt, ask the user what they want implemented.
A request like this skill apply the latest session runs no workers: follow references/mutating-run.md (Apply a recorded session) with this skill's adopt and update commands from its final phase, and skip the other phases.
<engine> is references/engine.py resolved from this skill's directory to an absolute path, written literally in every command, and run with python3.
Worker selection
Before any other unresolved configuration choice or operational step, read
references/worker-backends.md (Caller contract). Resolve
worker_backend from --workers=subagents|model-clis using that reference;
if the flag is absent, ask its worker question first.
If interactive choice is unavailable, honor its documented headless default.
Orchestration Plan
Enter plan mode before the first edit. In Claude Code call EnterPlanMode; in Cursor, Codex, or Gemini use /plan or Shift+Tab. Where plan mode is unavailable, present the plan as text.
Write the plan per references/mutating-run.md (Shared phases, Orchestration plan).
Present it, wait for approval, and exit plan mode (ExitPlanMode).
Phase 1: Start the session
Follow references/ensemble-core.md (Start the session) with --command prompt --mutating; it asks each unresolved setting through ask-user-choice. Dispatch per references/mutating-run.md (Shared phases).
Phase 2: Implement in parallel
Use the worker prompt body of references/mutating-run.md (Shared phases), with the implementation prompt as <the task>.
Phase 3: Compare the implementations
Capture, run the gates, and record the pass per references/mutating-run.md (Shared phases). Compare per ensemble-core.md (Blind judging, Synthesis protocol), where the judge participant scores. The convergence mode is pick-winner: the highest-scoring implementation wins, and no code merges across implementations. Its brief asks it to verify what each implementation does against what its participant claims. A failing quality gate caps that implementation's Correctness at 3. Write the comparison (scores per implementation, quality-gate results, the winner and why) to <session_dir>/pass-NNNN/synthesis.md per references/prose-rules.md.
Phase 4: Multi-pass refinement
Follow references/mutating-run.md (Refinement passes), repeating Phases 2 and 3.
Phase 5: Adopt the chosen implementation
Follow references/mutating-run.md (Apply gate and presentation): show the comparison and the recommended winner, and let the user choose and wait before touching the main checkout.
Copy everything the winner captured into the main checkout, deletions included:
$ python3 <engine> adopt \ --session "<session_dir>" \ --pass <final N> \ --all <winner>If
adoptrefuses, followreferences/mutating-run.md(Apply gate and presentation).Run the project's quality gates, then record the state:
$ python3 <engine> update \ --session "<session_dir>" \ --event adoption_applied- Clean up per
references/mutating-run.md(Shared phases) (Apply), checkinggit diff --stat HEADagainst the winner's patch. - Read
references/present-results.mdandreferences/prompt.md, and apply them withRESULT_KIND=prompt,ARTIFACT_PATH=<session_dir>/pass-NNNN/synthesis.md,SESSION_DIR,PASS_COUNT=passes,IN_PLAN_MODE= false,LABEL_MAP_PATH=<session_dir>/pass-NNNN/label-map.json.
Finish
Follow ensemble-core.md (Finish). Report the winning participant, the quality-gate result, and unavailable participants with their failure class.
Portability notes
ask-user-choice— follow the source's choice contract. Hosts with a structured multiple-choice tool (Claude Code'sAskUserQuestion) should use it. Honor a documented headless default when the source defines one; otherwise print a numbered list and wait for a numbered reply. Never invent a choice.$ARGUMENTS— the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.
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.

