What problem does it solve? Teams risk costly rework when architecture or ownership decisions are made informally and implementation starts before stakeholders agree. This discipline enforces a recorded, concluded consensus before any code is written for material, cross-owner, or expensive-to-reverse decisions. ## Core Features & Use Cases - Independent Research Phase: Each participant researches code, project management records, and canonical documents on their own before discussion. - Structured Consensus Protocol: Runs the Discuss turn protocol and records final stances, concluding only with complete consensus, disagreement, or open-question outputs. - Plan Binding and Review: After operator approval, binds the consensus reference to a Projectman task and sprint plan, requiring plan review before implementation begins. - Use Case: When deciding between SQLite and PostgreSQL for a project, use this discipline to have agents research independently, reach a recorded consensus, and only then bind the decision to a sprint plan for reviewed implementation. ## Quick Start Use the design-first-consensus discipline to research the database choice independently, record a concluded consensus, and bind it to a sprint plan before implementation.
