Skip to content

lawzava/megapowers / plugins/megapowers/skills/orchestrating

orchestrating

Verified

Use when two or more independent lanes can run in parallel, an output-only lane protects lead context from raw payload, or a handoff or durable run needs coordination. Covers fan out, spawn agents, split the work, delegate lanes, review while building, and independent files or services to inspect at once.

FileKindSize
SKILL.mdskill md3.3 KB
assets/agent-capabilities.mdmarkdown3.1 KB
references/fences.mdmarkdown1.5 KB
references/native-dispatch.mdmarkdown5.2 KB
references/review-contract.mdmarkdown1.3 KB

references/fences.md

View on GitHub
# Writer fences and lead-leak checks

Use normal Git and file tools to compare each worker against the immutable
commit recorded at dispatch. Record the worker root and permitted repo-relative,
case-sensitive paths before writing. Match directory fences to descendants,
not similarly named siblings. State prohibited work separately in the brief.

Fence syntax uses repo-relative exact files, `dir/` prefixes or `*` patterns.
`*` may match `/`; all other characters are literal. Quote patterns, use `/`
separators, and reject empty or absolute paths, backslashes, and `.` or `..`
path components.

Compare the union of committed, staged, unstaged and non-ignored untracked
changes. Check both rename endpoints. A revision comparison covers only its
tree; inspect a working checkout for uncommitted changes too. Reject ambiguous
revision or directory names. Quote unusual paths in findings.

Before dispatch, capture the lead HEAD, index, worktree and untracked contents
in a private baseline outside the checkout. Compare again before integration.
Existing user edits belong to that baseline. Account for the lead's own edits
before attributing drift to workers. Never discard user edits to clear a check.

Any fence violation or unexplained lead drift blocks integration. Reconcile a
needed scope change with the lead and acceptance boundary before widening a
fence. These checks do not provide an OS sandbox or detect edits restored
before inspection. Check submodule repositories separately. If Git or isolation
is unavailable, inspect paths manually and keep writing sequential.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall