!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys workflow,automation

Automation mode: Resolve modes.automation (project.local.yaml → project.yaml → default collaborative). Every AskUserQuestion call and every file write follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

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

Content Audit

Resolve modes.workflow before auditing: this skill's tier-dependent behaviour ("audit only specs in the required sections") follows the resolved tier, never an assumed one. When a required input such as design/gdd/systems-index.md is absent, report NOT ASSESSED, NO DATA rather than computing a gap percentage (which divides by zero when nothing is specified).

When this skill is invoked:

Parse the argument:

• No argument → full audit across all systems
• [system-name] → audit that single system only
• --summary → summary table only, no file write

---

workflow (see .claude/docs/workflow-modes.md):

• full, full content-count audit against all GDD specs.
• standard, audit only specs in the required sections; list any count found outside them as not audited at this tier.
• minimal, cannot run (no systems index exists).

Insufficient input, check this before producing any report

If the inputs this skill needs do not exist, the answer is "could not run", not a filled-in report. Check first, and stop if the check fails.