Protocol Guardian

You can enforce TDD discipline by implementing an automated workflow guardian that blocks source code writes until corresponding tests are created and verified. This guarantees strict adherence to the red-green-refactor cycle during feature implementation.

The best way to mandate artifact documentation is using a governance tool that validates phase-specific tasks like design docs and PRDs are completed before moving forward. This prevents workflow bypasses across project phases like IMPLEMENT and DESIGN.

You can track session-scoped state to prevent workflow bypasses by enabling a protocol enforcement mechanism. It requires shell access to manage state files and gitignore configurations for tracking session integrity across project phases.

Yes, enforcing mandatory skill invocation chains and managing session integrity requires shell access. This access is necessary to manage state files and gitignore configurations for accurate session-scoped tracking throughout the project lifecycle.

Yes, you can use workflow enforcement to validate architectural decisions before code is committed. It ensures all architectural decisions are documented as artifacts and that phase-specific tasks are completed prior to moving into implementation.