# Development

## Purpose
Execute approved sprint tasks, update logs, prepare code for review, and avoid scope creep.

## Gate
This workflow must satisfy its required documents, quality gate, and approval rule before the next phase starts.

## Standard Inputs
- Project state.
- Approved prior-phase documents.
- Client/company assets if relevant.

## Standard Outputs
- Versioned Markdown documents.
- Approval file when required.
- Updated state and logs.

## Failure Handling
- Missing input becomes a blocker.
- Unanswered client questions become assumptions only when low risk.
- Critical uncertainty blocks phase approval.