# Requirements Checklist - Spec 325

**Purpose**: Validate Spec 325 preparation completeness and implementation-readiness.
**Created**: 2026-05-17
**Feature**: `specs/325-screenshot-anchored-strategic-target-images/spec.md`

## Scope

- [x] Spec remains docs/image target artifact work.
- [x] No product runtime UI is changed by the prepared spec.
- [x] No routes are changed by the prepared spec.
- [x] No Filament/Livewire/Blade runtime files are changed by the prepared spec.
- [x] No business logic is changed by the prepared spec.
- [x] No database schema is changed by the prepared spec.

## Selection

- [x] Selected surfaces must come from Spec 323 artifacts.
- [x] No more than 10 surfaces may be selected.
- [x] P0/P1 rationale is required.
- [x] Deferred strategic surfaces are required.

## Screenshot Anchoring

- [x] Every selected surface must reference a current screenshot and/or page report.
- [x] Every brief must describe concrete current-state problems.
- [x] Every target image must have source/brief/sidecar.
- [x] No target image may be accepted as standalone truth.

## Target Briefs

- [x] Every selected surface requires a target experience brief.
- [x] User promise is required.
- [x] Primary persona is required.
- [x] First-five-seconds target is required.
- [x] Primary decision is required.
- [x] Primary action is required.
- [x] Information hierarchy is required.
- [x] Main view / detail drawer / advanced split is required.
- [x] Visual target direction is required.
- [x] Status/trust model is required.
- [x] Repo-truth classifications are required.
- [x] Image generation prompt is required.
- [x] Implementation pattern requirements are required.

## Target Images

- [x] Every selected surface requires at least one target image.
- [x] Customer/auditor/management-facing surfaces require light target image or documented reason.
- [x] Target images must be screenshot-anchored.
- [x] Target images must not be generic SaaS dashboards.
- [x] Target images must not imply false product truth.
- [x] Target images must not present conceptual-future-state as implemented.
- [x] Target images must avoid fake green success.
- [x] Target images must be readable and reviewable.

## Customer / Risk

- [x] Customer-facing surfaces must be customer-safe.
- [x] Dangerous actions must include guardrail concepts.
- [x] Evidence/audit paths must be represented where relevant.
- [x] Technical diagnostics must be secondary.

## Coverage Artifacts

- [x] Strategic surfaces file update is required.
- [x] Design coverage matrix update is required if target-image coverage is tracked.
- [x] Grouped follow-up candidates update is required.
- [x] Follow-up implementation candidates creation is required.
- [x] README links to artifacts are required.

## Validation

- [x] `bash scripts/check-ui-productization-coverage HEAD` is required during implementation.
- [x] `git diff --check` is required during implementation.
- [x] Full Pest/runtime suite must be intentionally not run unless runtime files changed.
- [x] Pint must be intentionally not run unless PHP files changed.

## Candidate Selection Gate

- [x] Candidate is directly user-provided.
- [x] Candidate aligns with Spec 323/324 product direction.
- [x] Existing related completed specs are treated as historical context only.
- [x] Existing `specs/325-tenantial-strategic-surface-target-mockups/` contains no tracked completed spec artifacts.
- [x] Scope is bounded to a small docs/image target-artifact slice.
- [x] Adjacent pattern-library work is deferred to Spec 326.

## Spec Readiness Gate

- [x] `spec.md` exists.
- [x] `plan.md` exists.
- [x] `tasks.md` exists.
- [x] `checklists/requirements.md` exists.
- [x] Problem statement, user value, functional requirements, non-goals, acceptance criteria, risks, and assumptions are present.
- [x] Plan identifies affected repo surfaces and no-runtime constraints.
- [x] Tasks are ordered, small, and verifiable.
- [x] Workspace/environment context, RBAC/customer-safety, audit/evidence, OperationRun truth, and dangerous-action UX expectations are addressed where relevant.
- [x] No open question blocks safe implementation.