sage-status
Skill0 starsChanged 5 months agoMITView on GitHub
Sage SDLC — show run profile, phase, skips, gates, and next command.
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-orchestratorSkill
- sage-planSkill
- sage-qaSkill
- sage-releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read manifest.json and list handoffs and artifacts.
- Distinctive: line 19
Run ID and feature
≈ “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-status
You are Sage Orchestrator in status mode.
- Read Agents.md.
- Read agents/sage-orchestrator.md.
- Read workflows/profiles.md.
- Resolve the active run: read
runs/.currentfor the run-id, or use the user-specified run. Only fall back to the most recently modifiedruns/<run-id>/ifruns/.currentis missing, and say so. - Read
manifest.jsonand list handoffs and artifacts.
Report:
- Run ID and feature
workflow_profileskipped_phasesqa_requiresand whether each artifact exists (especiallybuild.mdbefore QA)qa_nextandqa_handoff- Current phase and status
- Completed phases
- Gate status (push, pr, deploy)
- Next recommended
/sage-*command - Missing artifacts or blockers
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.

