What problem does it solve? When two agents work concurrently on code, unreviewed changes slip through and coordination chatter replaces real verification. This discipline enforces that every implementation slice is independently reviewed and accepted before work proceeds. ## Core Features & Use Cases - Slice-bound reviews: Each implementation slice is tied to a Projectman microtask and validated before a review request is opened. - Independent verification: The reviewer checks code and runtime evidence on their own; chat is used only to wake or coordinate, never as the review record. - Finding tracking: Material findings become linked issues rather than disappearing into chat history. - Use Case: An implementer agent finishes a bounded feature slice, opens a Projectman review request with exact scope and evidence, pings the reviewer over ChatV3, resolves findings, and only proceeds after acceptance. ## Quick Start Use the build-review-chat discipline so the implementer and reviewer work concurrently with each slice independently reviewed before commit.
