Mesteriis Agent Squad
Use this skill when parallel agent work can reduce risk or time without creating file conflicts.
This skill is inspired by multi-agent terminal orchestrators. It is not a TUI installer. It defines the planning, isolation, review, and merge contract for Codex-compatible parallel work.
When To Use
Use for:
- large refactors with separable modules;
- implementation plus tests plus review lanes;
- independent security, performance, UI, and docs reviews;
- migration slices that can be validated independently;
- comparing alternative approaches before selecting one.
Avoid for:
- tiny changes;
- tasks where all lanes must edit the same file;
- unclear goals;
- work that needs secrets or production access in multiple contexts.
Lane Design
Each lane needs:
- goal;
- allowed files or directories;
- forbidden files or directories;
- validation command;
- expected artifact;
- merge owner.
Common lanes:
- implementation;
- tests/TDD;
- security review;
- architecture review;
- docs/update notes;
- regression validation.
Isolation Rules
- Prefer separate git worktrees or read-only subagents for parallel work.
- Do not let two write lanes own the same files.
- Keep secret-bearing files out of all lanes unless explicitly scoped.
- Merge through one owner after reviewing diffs.
- If lanes conflict, stop and re-plan before editing more.
Merge Contract
Before finalizing:
- Collect lane results.
- Deduplicate findings.
- Verify changed files against allowed scopes.
- Run integration validation from the main worktree.
- Summarize what was accepted, rejected, or deferred.
Output
Report:
- lanes created;
- isolation method;
- per-lane result;
- merge decision;
- final validation.