tools/sage-claude-plugin/skills/sage/SKILL.md
Start here. Sage reads project state, routes via keywords, classifies intent, and guides you to the right workflow.
npx skillsauth add xoai/sage sageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
RULES (apply to every step — non-negotiable):
Sage's intelligent entry point. Assess the project and guide the user.
Scan .sage/work/ for active initiatives (read frontmatter: title,
status, phase). Scan .sage/docs/ for project-level artifacts.
Read .sage/decisions.md for recent context.
Present what you found, then structured options based on context.
If work is in progress:
Sage: [Project name] — [feature] is in progress, [phase] phase.
[1] Continue [feature] — resume from [next step] [2] Start something new [3] Review what's been done
If no work in progress but artifacts exist:
Sage: [Project name] — no active work. Previous: [list initiatives].
[1] Start a new task — describe what you want to build [2] Review existing artifacts [3] Learn the codebase
If fresh project:
Sage: Fresh project, no work in progress.
[1] Build something — describe what you want to create [2] Learn the codebase first [3] Something else — describe what you need
Based on user's choice or free-form input, classify scope and route:
For complex routing or gap detection, read the sage-navigator at
sage/core/capabilities/orchestration/sage-navigator/SKILL.md.
$ARGUMENTS
development
Branch-per-initiative git discipline for all delivery workflows. Defines branch naming by workflow, the propose-confirm creation protocol, dirty-tree and detached-HEAD handling, the always user-gated merge protocol, worktree support for parallel sessions, and abandonment cleanup. Activates only in git repositories — silently inactive everywhere else. Use when starting /build, /fix, /architect, or /build-x at Standard+ scope, when resuming an initiative, when offering a merge at a completion checkpoint, or when the user wants a second concurrent initiative.
development
Drives task-by-task execution from an approved plan with quality gates between each task. Reads the plan, finds the next incomplete task, dispatches implementation, validates, updates progress, and continues. Use after a plan is approved and the user says "go", "start building", "execute the plan", or "implement the feature".
testing
Preserves and restores context across agent sessions using plan file checkboxes as source of truth. Use when starting a new session, resuming previous work, ending a session, or when the user says "continue from last time", "what was I doing", or "save progress".
tools
Captures agent mistakes, corrections, and discovered gotchas so they are not repeated. Use when: (1) a command or operation fails unexpectedly, (2) the user corrects the agent, (3) the agent discovers non-obvious behavior through debugging, (4) an API or tool behaves differently than expected, (5) a better approach is found for a recurring task. Also searches past learnings before starting tasks to avoid known pitfalls. Activate alongside the sage-memory skill — they share the same MCP backend but serve different purposes (sage-memory = codebase knowledge, sage-self-learning = agent mistakes and gotchas).