devbooks-proposal-author

An auditable change proposal requires a formal proposal.md entry detailing Why, What, and Impact. It enforces strict structure with acceptance criteria, risk flags, and traceable rationales to reduce ambiguity in cross-team scenarios.

A Debate Packet documents design decision alternatives, their pros and cons, and explicit points requiring user adjudication. It prevents unilateral decisions by outlining evidence-based options for cross-team review within the proposal.

Record traceable rationales by versioning your change package and maintaining a decision log within the proposal.md. This creates an evidence loop linking design decisions to supporting data, enhancing audit and rollback capabilities.

Yes, the approach strictly enforces risk flags and acceptance criteria within the proposal structure. This ensures potential impacts are formally evaluated and documented before proceeding with downstream design and review processes.

Create a proposal.md entry when proposing evidence-based design decisions for cross-team scenarios. It serves as the formal starting point for subsequent Design, Spec, and Plan workflows by defining the target, scope, and impact.