tdd-spike

A time-boxed spike explores specific design questions before committing to an implementation approach. It captures hypothesis, success criteria, experiments, and demos in a structured design.md artifact to validate decisions within a fixed duration.

Generate a structured design.md file under docs/tdd-designs/<spike-name>/ containing hypothesis, success criteria, experiments, and demos. The workflow enforces collaboration preflight, parent linkage checks, and vision alignment to ensure proper context continuity.

Yes, design spikes support optional parent linkage and project vision alignment. The workflow enforces parent linkage checks and vision alignment during preflight to ensure context continuity and automatically links generated artifacts to the design inventory.

Yes, the design spike workflow enforces collaboration preflight before starting. This preflight validates parent design linkage and project vision alignment to ensure all stakeholders share context before producing the structured design.md output.

Run a time-boxed spike workflow that captures hypothesis, success criteria, experiments, and demos in a structured design.md. It enforces collaboration preflight, parent linkage checks, and vision alignment to validate design decisions before committing to an implementation approach.

Avoid time-boxed spikes when design questions are already resolved or lack parent design context for linkage. Spikes require collaboration preflight and vision alignment, making them unsuitable for isolated decisions lacking project-level design continuity or structured hypothesis validation.