implementation-orchestration
Skill1 starsChanged 51 days agoNo licenceView on GitHub
Plan and orchestrate a substantial piece of work — implement a PRD or spec, or run a migration, refactor, decommission, schema change, dependency upgrade, or greenfield build too big for one PR — as an agent harness loop: ordered, independently verifiable steps driven by a fresh-context worker → independent reviewer → fix loop with durable file-based state. Picks the driver (Claude Code dynamic workflow, in-context subagent orchestrator under /goal, or a /batch sweep) by decision tree and discovers the repo's own bootstrap/test/lint/CI/worktree conventions at runtime. Use for 'implement this PRD', 'plan the X migration', 'break this refactor into reviewable steps', 'turn this into a workflow', 'run this as a loop overnight'. Not for a one-PR change or for executing one already-written step.
- Reads credentials
In this repository8 other files it gives its agents.
- langsmith-prod-evalsSkill
- llm-pipeline-qualitySkill
- monorepo-navigationSkill
- monorepoSkill
- n8n-automation-builderSkill
- paywall-conversionSkill
- qwen-asr-realtimeSkill
- workers-ai-llm-pipelinesSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.