system-reminder

To enforce read-only mode for an AI agent during planning phases, this Skill restricts file edits and state-changing shell commands based on the active workflow phase. It prevents accidental modifications during planning, design, and review stages by querying a dashboard state endpoint to determine current access constraints.

Yes, you can automatically toggle AI file edit permissions based on the workflow phase. This Skill handles mode transitions by clearing read-only constraints when entering implement or learn phases, and automatically re-enabling them when transitioning back to planning, discovery, or verification stages.

Workflow phases that should restrict AI state-changing commands include planning, discovery, design, governance, accept, and verify. During these stages, read-only constraints are enforced to ensure the AI meticulously plans and reviews features before making any code changes.

Yes, the read-only AI constraint requires API calls to a dashboard state endpoint to function. The Skill queries this endpoint to determine the active workflow phase and dynamically applies or removes operational constraints on file edits and shell commands based on the returned state.

Preventing AI code modifications during planning and review stages ensures adherence to structured development workflows. By blocking premature or unvetted changes, the AI is forced to thoroughly plan and review a feature first, preventing accidental modifications before implementation begins.

You should not use automated phase-based access control for AI if your development workflow lacks distinct planning, implementation, and review stages. The system relies on querying a dashboard state endpoint to transition modes, making it unsuitable for environments without defined workflow phases.