Menu
Start here. Sage reads project state, routes via keywords, classifies intent, and guides you to the right workflow.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | sage |
| description | Start here. Sage reads project state, routes via keywords, classifies intent, and guides you to the right workflow. |
| disable-model-invocation | true |
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
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".
Enforces test-driven development: write failing test, write minimal code to pass, refactor. Mandatory for all implementation work. Use when writing any production code, implementing features, fixing bugs, refactoring, or when the user says "write code", "implement", "fix this", or "add a feature". Code written before its test is deleted.
Configure Sage preset and project settings. Switch between base, startup, enterprise, or opensource constitution presets. Use when the user says "configure sage", "change preset", or "sage settings".
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".
Architecture Decision Records, System spec, Milestone plan
Brief (medium+ tasks), Spec, Implementation plan
