Skip to content

doctor: does not catch unparseable step headings ('## Step' h2 vs '### Step' h3) — false-passes a task that will silently no-op #615

Description

@HenryLach

Summary

taskplane doctor reports "All checks passed" for a task whose PROMPT.md step headings are the wrong level (## Step h2 instead of ### Step h3) and therefore do not parse into executable steps. Doctor should catch this — it is the exact condition that causes the silent false-success in the companion P0 issue.

Severity

P1 — validation gap that lets a fatal authoring error through to execution.

Repro

  1. Author a PROMPT.md with ## Step 0:, ## Step 1: … (h2).
  2. taskplane doctor → "All checks passed".
  3. Running the task silently no-ops and is marked succeeded (see P0).

Expected

doctor should validate that:

  • Each task PROMPT.md contains at least one parseable ### Step (h3) heading (i.e., the step parser finds ≥1 step).
  • Ideally: the number/labels of ### Step headings in PROMPT.md reconcile 1:1 with the step sections in STATUS.md.
  • Flag h2 ## Step headings specifically as a likely-miswritten step (common mistake).

Environment

Taskplane 0.30.4. Companion to the P0 "false success on unparseable steps" issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions