faffter-noon-prd

PRD readiness is checked by judging whether its done-criteria are machine-verifiable, such as Given/When/Then scenarios or single MUST/comparator assertions. The skill emits a prd-readiness verdict block that the deterministic faff contract prd-readiness validator uses to admit or refuse the run.

A stop-condition is verifiable when written as a Given/When/Then scenario or a single MUST/comparator assertion. Loose prose like "the system should be stable" or "users will be satisfied" is not verifiable, and at least one verifiable condition is required for an admissible verdict.

No, the check is code-blind by construction and reads only the PRD document at the given absolute path. It never inspects the codebase, tracker, run context, or specs, so the verdict describes the PRD alone and cannot be influenced by plausible code.

The verdict is not-ready with a non-empty reason from the closed reason set, and the gate refuses the run. The gate is fail-safe toward refusal, so a malformed or missing verdict block never coerces toward admissible.

creative_licence classifies the PRD as broad or tight, describing how much implementation latitude the team has. It is forward-carried to calibrate downstream scope strictness but is never gate-decisive for the admit/refuse decision.