tactic-lean-orchestrate
Skill0 starsChanged 3 months agoMITView on GitHub
Explicitly request lean Codex CLI orchestration for a material task. Use only when the user intentionally wants independent subagent coordination; do not use for normal automatic routing or simple work.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- more-with-lessSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- tactic-spec-brainstormSkill
- tactic-spec-grillSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use KISS. This skill is an explicit override, not the default path.
- Distinctive: line 12
Read-only delegation never transfers write ownership.
- Distinctive: line 13
Add parallel read-only workers only for genuinely independent questions.
- Distinctive: line 15
Keep one active writer unless scopes are demonstrably disjoint.
- Distinctive: line 16
Use one automatic rework cycle for concrete material defect, then stop and surface blocker.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Lean Orchestrate
Use KISS. This skill is an explicit override, not the default path.
- Choose smallest route: R0 direct; R1 primary plus fresh
verifier; R2 boundedscoutdiscovery, primary, freshverifier; R3 one explicitimplementerboundary plus freshverifier; exceptional R4 isolated disjoint implementation. - Skip
scoutwhen scope is already clear. - Read-only delegation never transfers write ownership; primary remains authority and writer unless R3 explicitly transfers one boundary.
- Add parallel read-only workers only for genuinely independent questions.
- R4 needs disjoint ownership and isolation; primary owns shared OpenSpec ledger and canonical apply.
- Keep one active writer unless scopes are demonstrably disjoint.
- Use one automatic rework cycle for concrete material defect, then stop and surface blocker.
For OpenSpec work, preserve canonical .agents/skills/openspec-* unchanged. Primary invokes canonical $openspec-apply-change for R1/R2 and owns shared R4 tasks.md; only explicit R3 delegation gives canonical apply to Implementer. Verifier uses canonical $openspec-verify-change when installed. Do not recreate OpenSpec planning or verification inside this skill.
Model starting points:
- scout: GPT-5.6 Terra, low;
- implementer: GPT-5.6 Sol, medium;
- verifier: GPT-5.6 Terra, high;
- high-risk verifier: GPT-5.6 Sol, high.
Return the final result after verification without narrating internal orchestration history unless it affects the user's decision.
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.

