analyze

name	analyze
description	Strategic system analysis for health assessment, pattern recognition, component deep dives, risk assessment, and architecture review. Use for proactive system understanding beyond reactive incident response.
disable-model-invocation	false
argument-hint	[mode] [target]
allowed-tools	Read, Grep, Glob, WebFetch, WebSearch, Write
wrought	{"version":"1.0","tools":{"capabilities":["read_file","search_content","find_files","web_fetch","web_search","write_file"]},"platforms":{"claude-code":{"allowed-tools":"Read, Grep, Glob, WebFetch, WebSearch, Write","disable-model-invocation":false}},"agent":{"role":"Systems Analyst","expertise":["system health assessment","pattern recognition","risk prioritization","architecture review"],"non_goals":["implementing fixes","incident response","code changes"]},"execution":{"default_mode":"tot","optional_modes":["react"],"max_iterations":15,"max_refine":2,"stop_conditions":["Analysis written to docs/analysis/","User approved analysis scope and findings","User instructed to stop"]},"output":{"format":"markdown","template":"docs/analysis/{YYYY-MM-DD_HHMM}_{scope}.md","required_sections":["Executive Summary","Scope","Findings","Risk Assessment","Recommendations"]},"confidence":{"threshold":"high","low_confidence_behavior":"Flag areas needing deeper investigation"},"context":{"max_tokens":16000,"artifact_loading":"on_demand","handoff_trigger":0.7},"pipeline":{"track":"audit","standalone":true,"prerequisites":[],"produces":["docs/analysis/*.md"],"suggested_next":["finding","investigate","design"]}}

Systems Analyst Skill

Trigger: /analyze {mode} [scope]

Purpose: Strategic-level system analysis that goes beyond reactive incident response to provide proactive system health assessment, pattern recognition across incidents, architectural insight, and risk prioritization.

---

Pre-flight Check

This skill is standalone — it can be invoked at any time without prerequisites.

If this invocation is part of an active workflow, check docs/findings/*_FINDINGS_TRACKER.md for a relevant tracker and note it for context, but do not enforce stage requirements.

---

Modes

/analyze health                    # Full system health assessment
/analyze patterns [time-period]    # Pattern recognition (default: last-7-days)
/analyze component [scope]         # Deep dive on specific component
/analyze risk [scope]              # Risk assessment with prioritization
/analyze architecture              # Architectural review + doc sync
/analyze discover                  # Build/refresh System Map only

---

Design Principles

1. Discovery-Based Scoping: No hard-coded component names. The skill discovers what exists.
2. Fully Interactive: ALL modes use AskUserQuestion at key decision points.
3. Artifact-Driven: System Map persists across analyses.
4. No File Edits Without Confirmation: Architecture mode previews changes before applying.
5. Escalation: When findings suggest redesign or corrective fix, offer to explore alternatives.

---

Step 0: Load or Create System Map

See system_map_template.md for the system map template and discovery process.

If system map exists at docs/analysis/system-map.md and is <24h old, load it. Otherwise, follow the template to create one.

---

Mode: Discover (/analyze discover)

Purpose: Build or refresh the System Map without full analysis.

Workflow

1. CP1 — Scope Confirmation [multi]: "I'll scan the project to build a System Map. What should I include?" → Backend services* | API layer | Data models | Frontend components | Configuration files | All of the above

2. CP2 — Exclusions: "Any directories or patterns to exclude from scanning?" → No exclusions (scan everything)* | Exclude tests/ | Exclude vendor/node_modules | Let me specify...