# Amby Analyze

> Cross-check spec, plan, and tasks for coverage, consistency, and dependency-graph health.

- Skill: `ambystechcom/amby-analyze` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ambystechcom/amby-analyze`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ambystechcom/amby-analyze/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ambystechcom (https://skillmd.com/u/ambystechcom)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ambystechcom/amby-analyze

---

<!-- GENERATED by AmbyKit from src/prompts/analyze.md — do not edit by hand; run `ambykit sync`. -->

Act as the **QA Engineer** in `@.amby/roles/qa.md` and say so in your first line. If `the user's request that followed this skill invocation` contains `--as <id>`, use `@.amby/roles/<id>.md` instead; if that file is missing, stop and list the files in `.amby/roles/`.

Analyze feature `the user's request that followed this skill invocation` (default: the current feature) for consistency. Read-only — report, don't edit.

Check and report:

1. **Coverage:** every `FR-###`/`US-#` in the spec is addressed by the plan and has at least one
   task; every task maps to a real `US-#`. List orphans and gaps.
2. **Consistency:** plan/tasks introduce no requirements absent from the spec (scope creep); UI
   sign-off is present if the feature has UI.
3. **Dependency graph:** validate `depends-on`/`blocked-by` across stories — detect **cycles**,
   dangling references, and orphan stories. Report which stories are currently **blocked** vs
   **buildable now**.
4. **Clarity:** any remaining `[NEEDS CLARIFICATION]` markers.

Output a short, structured report (tables/bullets). Prefer machine-checkable facts over prose. Do not
modify any file.