team-shinchan:verification-before-completion

To require verification evidence before a git commit or PR, you must capture exact command outputs and verdicts for each verification step. This approach blocks task completion until explicit confirmations pass, ensuring every commit is backed by an audit trail.

Evidence-driven task verification for code review means providing exact commands, outputs, and verdicts before marking work complete. It prevents moving to the next task until confirmations pass, creating a reliable audit trail for team collaboration.

You block task completion without verification outputs in CI by enforcing guardrails at key triggers like commits, PR creation, and task completion. This requires exact commands and outputs to be provided as evidence before any work is marked complete.

Yes, you can use this verification approach for team collaboration guardrails. It prevents team members from moving to the next task until all explicit verification confirmations pass, ensuring strict compliance with evidence-driven reporting standards.

You should not use evidence-driven verification before completion for rapid prototyping or experimental coding where capturing exact command outputs and audit trails slows down iteration speed without providing immediate team collaboration value.