# Spec Analyst

> Use when `spec.md` is missing, ambiguous, under-scoped, or missing testable acceptance criteria.

- Skill: `shaowei-g/spec-analyst` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add shaowei-g/spec-analyst`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shaowei-g/spec-analyst/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: shaowei-g (https://skillmd.com/u/shaowei-g)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/shaowei-g/spec-analyst

---


# Spec Analyst

Use this skill when specification is the current phase for one feature.

## Shared Contracts

Load this shared shortcut first:

- `../references/shared-specialist-contract.md`

Open the deeper canonical shared references only when the shortcut is insufficient for the current situation.

## Purpose

Use this skill when at least one is true:

- `spec.md` is missing
- `spec.md` is ambiguous, incomplete, or stale
- acceptance criteria are not testable
- scope boundaries are unclear
- a new feature request must be turned into a bounded specification

## Execution Mode

- This specialist is normally write-owning.
- When the assigned scope includes `spec.md` or checklist updates, the delegated agent must be able to edit workspace files.
- A read-only exploration agent is not a valid substitute for this skill.

## Read Order

- `.codex/prompts/speckit.specify.md` first
- `.codex/prompts/speckit.constitution.md` if present
- `.codex/prompts/speckit.clarify.md` only when clarification is part of the assigned scope
- `specs/<feature>/spec.md` if present
- adjacent workflow artifacts only when needed to preserve alignment

## Owned Outputs

- `spec.md`
- specification-phase checklist artifacts when the repository workflow expects them for spec readiness
- clarified scope boundaries
- explicit acceptance criteria and constraints for the assigned feature

## Phase-Specific Rejected Criteria

Return `rejected` if specification work is requested but the actual need is planning, tasking, implementation, or verification.

## Phase-Specific Blocked Criteria

Return `blocked` if essential product intent is missing and clarification cannot be resolved from artifacts or the assigned scope.