Skip to content

P2: Failures-log structural read-enforcement in /dev #34

@ramdhanyk

Description

@ramdhanyk

Source: 2026-04-20 multi-expert AADM audit. Skeptical-PM auditor.

Problem

CLAUDE.md says check docs/failures/ during ambiguity passes. Nothing verifies Claude actually did. START-HERE.md itself predicts the failures log decays into a graveyard within two sprints.

Fix

  • Update tooling/.claude/skills/dev.md — add step 0: list docs/failures/ filenames touching the task's domain (grep filenames for keywords from the task title), output the list in the response.
  • Update tooling/scripts/reconcile.py --strict to reject PRs whose /dev session log lacks a failures-checked: [filenames] line.

Acceptance

A /dev session that skipped the failures check fails CI, with the missing filenames listed in the failure message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium — adoption ergonomics and docs surfaceaudit-followupFrom the 2026-04-20 multi-expert AADM audit

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions