What problem does it solve? Teams using AI coding agents often lack mechanical enforcement of workflow rules: code gets written during the planning phase, destructive git commands run without confirmation, and credentials end up in the repository. This Skill installs a development harness that enforces a planning-vs-implementation phase gate and blocks dangerous operations at the tool-hook level. ## Core Features & Use Cases - Phase Gate Enforcement: Installs PreToolUse hooks that block Write/Edit and git mutations (commit, add, merge, rebase) while a change is in the 'proposal' phase, lifting restrictions once promoted to 'apply'. - Security Guardrails: Blocks writes to credential files (.env, private keys), path traversal outside the repo root, and destructive commands like git push, git reset --hard, and rm -rf. - Session Context Injection: A SessionStart hook reports the current branch, declared change phase, and presence of guide files at the start of every session. - Use Case: A team adopting spec-driven development wants the AI agent to produce only planning artifacts during proposal review. After installation, the agent physically cannot modify source code until the team runs the phase CLI to promote the change to 'apply'. ## Quick Start Ask the agent to install the development harness with phase gating into this project and configure it for the project's source and test directories.
