From 25666248d4e105cfa65734ee66c2df4ee80f45c4 Mon Sep 17 00:00:00 2001 From: David Hu <159687+divad12@users.noreply.github.com> Date: Fri, 26 Jun 2026 20:17:32 -0300 Subject: [PATCH] task-observer: add schema-verification injection note to preflight TDD audit Incorporates observation 003 from journology/log.md: Plan-authored code stubs often carry wrong assumptions about schema field names and key structures. Inject a verification step before the first test for tasks touching data model types, API shapes, or cache key structures. --- .agents/skills/preflight/SKILL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.agents/skills/preflight/SKILL.md b/.agents/skills/preflight/SKILL.md index 6050116..02760bf 100644 --- a/.agents/skills/preflight/SKILL.md +++ b/.agents/skills/preflight/SKILL.md @@ -280,6 +280,8 @@ For each task, check whether the task has a `write failing test` + `verify test The plan file is never modified. `/fly` instructs implementers to honor both plan steps and `[INJECTED]` checklist-only steps. +For tasks touching data model types, external API shapes, or cache key structures (Prisma models, query-result shapes, cache keys), inject an additional verification step before the first test: `[INJECTED] Read and verify actual field names against plan assumptions`. Plan-authored code stubs often carry wrong assumptions about field names, key structures, and return shapes; verifying the source file before writing tests is cheaper than discovering the mismatch mid-implementation. + ### Manual-test convertibility analysis For each phase, sweep ALL manual verification work the plan calls out. Sources: