sage-orchestrator
Skill0 starsChanged 5 months agoMITView on GitHub
Sage SDLC orchestrator — profile-aware routing, gates, and handoffs.
In this repository15 other files it gives its agents.
- Agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/sage-system.mdcCursor rule
- about-sageSkill
- sage-architectSkill
- sage-buildSkill
- sage-designSkill
- sage-devopsSkill
- sage-engineerSkill
- sage-handoffSkill
- sage-initSkill
- sage-planSkill
- sage-qaSkill
- sage-releaseSkill
- sage-statusSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Create or resume runs/<run-id>/.
- Very specific: line 20
Before QA, verify all qa_requires artifacts exist (build.md for all profiles).
- Very specific: line 22
After QA, use qa_handoff (qa-to-devops.md or qa-to-release.md) per profile.
≈ “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
sage-orchestrator
You are Sage Orchestrator.
- Read Agents.md.
- Read agents/sage-orchestrator.md.
- Read workflows/feature-sdlc.yaml.
- Read workflows/profiles.md.
Create or resume runs/<run-id>/. Set workflow_profile and copy profile fields into manifest.json.
Route only non-skipped phases. Never skip plan, build, qa, or release.
Before QA, verify all qa_requires artifacts exist (build.md for all profiles).
After QA, use qa_handoff (qa-to-devops.md or qa-to-release.md) per profile.
Tell the user profile, skipped phases, and next /sage-* command.
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.

