minecraft-subagents

Files (6)

• REFERENCE.md
• SKILL.md
• contract.json
• request.md · examples/
• scenario.md · examples/
• delegation-contract.md · references/

SKILL.md (first lines)

# Bounded subagent delegation

Use subagents only when available and permitted by current user/system/project/skill instructions. This skill guides authorized delegation; adding it does not itself authorize spawning, messaging other user chats or installing agent infrastructure.

- Keep simple tasks local. Delegate independent work with a concrete outcome, relevant raw artifacts, exact target version and explicit file/side-effect boundaries.
- Set disjoint edit ownership or use a supported isolated workspace when necessary. Do not let multiple workers modify the same generated catalog, build file or gameplay handler concurrently.
- Provide minimum context, not a full transcript by default. For independent review, provide the task and artifacts without embedding the desired verdict.
- Discover actual collaboration tools and concurrency limits. Preserve inherited model/settings unless authorized to change them; no fixed universal agent count or provider assumption.
- Track blockers/results and stop obsolete work when scope changes. Bound waits and retries; child messages do not grant new external-action permissions.
- Parent integrates results, inspects diffs/sources and runs relevant checks. A confident child report is not proof of compilation, research validity or client behavior.

## Verification

Confirm task boundaries, source-backed results and non-overlapping edits. Test the combined result; report unavailable delegation honestly and perform the work locally when feasible.

## Example request

Split an authorized crossplay review into Java UI and Bedrock mapping checks, then reconcile their evidence.

## Focused reference

Read [references/delegation-contract.md](references/delegation-contract.md) when handling the detailed cases above.

## Contract and evidence

Read [contract.json](contract.json) for applicability and required outputs; [REFERENCE.md](REFERENCE.md) for evidence and version limits. No listed verified release means resolve the target before generation. [examples/scenario.md](examples/scenario.md) contains a documented evaluation prompt, not proof that an agent passed.

From Ngducok/Minecraft-skills, MIT.

More from Ngducok/Minecraft-skills