!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,review_gate,automation,workflow,qa.level,gate_level,story_granularity,system_overrides

Resolved above, use as-is; --review overrides review_mode. No block → defaults in .claude/docs/config-resolution.md.

Ask with the question tool. Without one, list the options numbered and end your turn to wait. A skipped or dismissed question is not an answer: ask again in plain text.

Story Readiness

Checks that a story file holds everything a developer needs before writing code: no design questions mid-build, no guessing, no vague acceptance criteria.

Read-only. It never writes or edits a file. It reports, and offers to draft fixes in the conversation.

Verdicts, one per story. The first that matches wins, in this order:

1. BLOCKED: a finding the reader can clear. A referenced ADR is missing, Proposed, Deprecated or Superseded; a dependency story is missing or Draft; or a criterion holds an UNRESOLVED design question with no owner.
2. NEEDS WORK: a blocking checklist item fails. The story can be fixed now.
3. NOT ASSESSED: the story could not be evaluated. The file is unreadable, a referenced ADR has no readable ## Status, or the design document it names cannot be found. Name what could not be read. It is never READY: a story nobody could check has not been shown ready. It ranks below the two failures, because a known blocker is more useful than an unknown.
4. READY: every item passes, is N/A with a reason, or is advisory. Advisory gaps are still listed.

Asks follow .claude/docs/automation-modes.md (collaborative always asks, guided asks on major choices, autonomous logs and goes on; automation_always_ask categories always ask).

Phase 1: Scope