agentleFS
sagarchauhan005sagarchauhan005/agent-sage/.cursor/skills/about-sage/SKILL.md

about-sage

Skill0 starsChanged 5 months agoMITView on GitHub

Brief overview of the Sage SDLC agent system and each agent's role. Use when the user asks what Sage is, how it works, or about Sage agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When invoked, give a short overview of Sage, then the agent table below.

    line 9

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

About Sage

When invoked, give a short overview of Sage, then the agent table below. Keep it brief. Do not dump Agents.md or phase workflows unless asked.

What Sage is

Sage is an SDLC agent orchestration system. Specialized agents run phases of software delivery (plan, design, architect, build, qa, devops, release) in order. An orchestrator routes work by workflow profile, writes handoffs between phases, and stores run artifacts under runs/<run-id>/. Each agent reads Agents.md first, then its role file in agents/.

Agents

AgentWhat it doesPrimary role
Sage OrchestratorRuns the pipeline, picks profile, enforces gatesOrchestrate
Sage PlannerClarifies requirements; plan.md in full or steps formatPlan
Sage DesignerUI/UX specs, components, asset structureDesign
Sage ArchitectSchemas, boundaries, deployment impact, test strategyArchitect
Sage EngineerFull-stack implementation, tests, wiringBuild
Sage QATests, lint, verification against planVerify
Sage DevOpsDocker, CDN sync, nginx, deploy prepPackage
Sage ReleaseCommits, branches, PRsShip
Sage StatusReports run phase, profile, gates, next commandStatus
Sage HandoffWrites or validates phase handoff documentsHandoff
Sage InitBootstraps ./runs/ and project Sage configInit

Slash commands

Each phase agent maps to a /sage-* command. Use /sage-plan steps when the problem is unfamiliar (plain breakdown). Use /sage-plan or /sage-plan full for the handoff-ready spec. Start a run with /sage-orchestrator.

Skills live in .cursor/skills/ and must match the Skills mirror table in Agents.md. One skill folder per registry row; no orphan skills.

For profile paths and global rules, point to Agents.md and workflows/profiles.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.