evidence-groundinglisted

# Evidence Grounding (internal) One shared owner of the evidence discipline that every authoring skill uses before it asks for an independent review. It prepares and checks; **it never reviews and can never emit a review PASS**. ## When to use - `design-feature` — while writing or upserting a Product half. - `plan-feature` / `plan-feature-scaffold` — while filling the Engineering half and cutting phases. - `plan-fix` — while drafting a fix SPEC and its phases. - Nothing else. A reviewer does not load this skill: its readiness verdicts are authoring-quality gates, not review verdicts. The shared review cycle and the planning-ledger shapes belong to `pre-execution-review`; the plan-stage row of the evidence table is restated here only as a pointer. ## Hard rule — authority boundary This skill may emit only these two vocabularies, and only at the step that owns them: | Emitted by | Closed outcomes | |---|---| | a grounding pass (§Ordered passes, step 2) | `CONTEXT-PREPARED \| NEEDS-EVIDENCE \| NEEDS-DESIGN` | | a readiness preflight (§Ordered passes, step 5) | `READY-FOR-REVIEW \| NEEDS-EVIDENCE \| NEEDS-DESIGN \| NEEDS-REPLAN` | `SPEC-REVIEW-PASS`, `PLAN-REVIEW-PASS` and any `*_REVIEW-PASS` string are **forbidden outputs here** — they belong to `review-spec` / `review-plan` running in a context that did not author the artifact. A same-context readiness `READY-FOR-REVIEW` is a statement that the artifact is *shaped* for review; it is not approval and must never be