structured-dev-cycle

A stage-based development lifecycle enforces planning by applying tool restrictions during the planning and verification stages, preventing premature coding. It uses a temporary marker file to block unsafe actions until the workflow advances to the implementation stage.

Yes, you can use PreToolUse hooks for development workflow governance. The lifecycle integrates these hooks to enforce stage-based tool restrictions, ensuring developers follow the controlled workflow before executing implementation or deployment actions.

Multi-model verification in a software development cycle is an optional governance mechanism that validates planning and implementation outputs using multiple models. It ensures robust quality control before transitioning between the six lifecycle stages.

You manage stage tracking across a six-stage development workflow using marker-based transitions. This system provides auditability and controlled progress across projects by maintaining a temporary marker file that gates tool access until stage requirements are met.

You should not use a structured development cycle with stage-based tool restrictions for rapid prototyping or exploratory coding where immediate execution is required. The marker-based blocks and strict governance are designed for complex feature development needing controlled workflows.