tools/sage-claude-plugin/skills/analyze/SKILL.md
Audit findings, Evaluation report, Severity scores
npx skillsauth add xoai/sage analyzeInstall 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.
Evaluate what exists. Audit, measure, score, find gaps.
Scan .sage/docs/ for existing evaluation artifacts (ux-audit-,
ux-evaluate-, analysis-*). If prior analysis exists, build on it.
Read .sage/decisions.md for context.
Sage → analyze workflow. What are you evaluating?
[1] UX quality — UX audit → usability evaluation (2 steps) [2] User needs — JTBD analysis on existing product (1 step) [3] Content quality — content evaluation (1 step) [4] Custom — describe what you want to evaluate
Pick 1-4, type / for commands, or describe what you need.
Based on scope, load and execute skills in sequence:
| Scope | Skill Chain | |-------|-------------| | UX quality | ux-audit → ux-evaluate | | User needs | jtbd (applied to existing product) | | Content | ux-writing (evaluation mode) | | Custom | select best-matching skill from installed skills |
For each skill in the chain:
sage/skills/[skill]/SKILL.md and follow its process.sage/docs/[skill-prefix]-[topic].mdSage: [Skill] findings for [topic]:
[A] Approve — continue to next step [R] Revise
Pick A/R, or tell me what to change.
After all skills complete:
🔒 FINDINGS CHECKPOINT (Zone 2):
Sage: Analysis complete.
Critical: [N findings — brief summary] Major: [N findings — brief summary] Minor: [N findings]
Top priority: [most impactful finding with rationale]
Artifacts: .sage/docs/[skill-prefix]-[topic].md
Decision: [analysis conclusions]. (appended to decisions.md)
[A] Approve findings [R] Revise [N] New session → /design to continue
Pick A/R/N, or tell me what to change.
Findings quality check (before presenting):
Next steps: /design — brief → spec → copy (address the issues found) /fix — diagnose → scope → fix → verify (fix specific issues) /reflect — review evaluation quality, extract patterns /research — deeper understanding of why issues exist
Type a command, or describe what you want to do next.
Good analysis output:
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).