blueprint-create

To create a unified technical design and product definition, you can run a single back-and-forth design discussion that captures both aspects in one continuous blueprint, reducing drift and ensuring all decisions are aligned in a single artifact.

An ADR-ready feature blueprint is best written through a disciplined back-and-forth design discussion that traces decisions, ensuring the final document captures durable design rationale aligned with handbook principles for architectural decision records.

Structure your design discussion as a single continuous conversation that concludes by writing the unified blueprint directly to docs/features/{feature}/blueprint.md, ensuring the technical design and product definition are captured in one markdown file.

This structured design approach does not work for small bug fixes or open-ended brainstorming sessions without committing to a document, as it enforces a single-document artifact specifically for unified product and technical feature design.

You need a single blueprint to reduce drift between product definition and technical design, ensuring that both aspects of a feature are captured, traced, and aligned in one durable, ADR-ready artifact rather than scattered across separate documents.