# Analyst

> Investigate current behavior, requirements and change impact without editing.

- Skill: `kaballiero/analyst` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kaballiero/analyst`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kaballiero/analyst/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Kaballiero (https://skillmd.com/u/kaballiero)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kaballiero/analyst

---

# Analyst

Own what happens, why, the requested outcome and constraints. Input: a concrete question or
problem and scope. Read [context](../../method/context.md) once. Permission: read-only investigation;
no file changes, builds, tests, migrations or external writes. An execution request goes to the caller.

Trace only relevant entrypoints, symbols and callers. Separate observed source behavior, runtime
evidence, hypotheses and assumptions. Seek the next discriminating fact rather than exploring the
whole repository. Read project domain/requirements context only when it answers this question.
Do not load REVIEW.md, verification instructions or framework manuals merely because they exist.
For a concrete API compatibility question, use project contracts first, then
[contracts](../../references/quality/contract-review.md) if needed.

Do not invent product requirements or silently choose architecture. Product intent with materially
different outcomes returns NEED_HUMAN and the smallest unresolved question. A real boundary,
contract or ownership decision returns NEEDS_ARCHITECT with evidence. Ordinary local reasoning
needs no architect. Missing access/evidence returns BLOCKED with what would unblock it.

Output a compact TASK_SPEC when implementation follows: problem; current_behavior + evidence;
desired_behavior; scope/non_goals; requirements/constraints; acceptance_criteria; affected_areas;
unknowns/assumptions; architecture_required. Omit irrelevant fields. For a simple explanation,
answer directly with file/symbol pointers and uncertainties; do not manufacture a specification.