planner: name an <automated> check per task by default #17

New issue

Closed

opened 2026-07-18 22:05:17 +00:00 by crenshawdev · 1 comment

crenshawdev commented

2026-07-18 22:05:17 +00:00

(Migrated from github.com)

Tier: Improve Cadence (ranked #4) · mild tightening

Name an automated check per task by default in the planner template's <automated> field, keeping the existing human-verify escape.

Why: nudges each task toward a falsifiable, automated verification instead of a manual one, without a new schema.

Cost: template wording in the planner, not a new schema.

Source: internal GSD comparison note, 2026-07-18.

**Tier:** Improve Cadence (ranked #4) · mild tightening Name an automated check per task by default in the planner template's `<automated>` field, keeping the existing `human-verify` escape. **Why:** nudges each task toward a falsifiable, automated verification instead of a manual one, without a new schema. **Cost:** template wording in the planner, not a new schema. _Source: internal GSD comparison note, 2026-07-18._

crenshawdev commented

2026-07-28 17:11:47 +00:00

(Migrated from github.com)

Won't do. The <automated> field this is written against is a GSD-core concept that Cadence never had, and the behavior it asks for is already the planner contract: agents/cad-planner.md makes Verify default to "a command whose output settles it", with human-verify as a narrowly-gated escape that requires a command -v probe first. Not carrying it into the next milestone.

Won't do. The `<automated>` field this is written against is a GSD-core concept that Cadence never had, and the behavior it asks for is already the planner contract: `agents/cad-planner.md` makes Verify default to "a command whose output settles it", with `human-verify` as a narrowly-gated escape that requires a `command -v` probe first. Not carrying it into the next milestone.