Skip to content

Ship the spike-report template (BACKLOG B1) and surface declared-but-missing secondary outputs at validation #101

Description

@TheAmericanMaker

Two small gaps, both observed in the deepseek-harness run:

1. Spike reports have no template or home (BACKLOG B1)

The spec-delta-application skill cites spike reports (spikes/<spike-id>/<scenario>.md plus CONSOLIDATED-DELTA.md) as a canonical delta source, and the run registered six spikes (SP1–SP6) in post_pipeline — but the framework ships no spike template and defines no directory convention. The run improvised scratch/deltas/.

Fix (B1's "smallest viable form", per the BACKLOG entry itself): ship templates/spike-report.md (Goal / Method / Measurements / Findings / Recommended Deltas), document scratch/spikes/ in GUIDE.md and the spec-delta skill, remove B1 from the shipped BACKLOG. No workflow machinery.

2. Declared-but-missing secondary outputs are invisible at validation

The architecture phase declares five secondary_outputs; the run wrote four and silently dropped runtime-lifecycle.md (deferred via a handoff decision that nothing routed). codecarto_validate checks only the primary output's validation block, so a declared secondary output can vanish without any surface noticing.

Fix: codecarto_validate result gains a non-gating NOTE listing the phase's declared secondary_outputs with exists/missing status. (Secondary outputs are "created only when needed" per GUIDE, so a hard gate would be wrong — visibility forces the session to either write or route the gap.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions