plan

To generate a development plan with phased milestones, you outline feature goals and compliance requirements to produce a structured DEVELOPMENT_PLAN.md document with phase-based gating and conflict checks.

Phase-based gating in feature work planning is a structured approach that creates formal milestones within a DEVELOPMENT_PLAN.md, ensuring conflict and compliance checks pass before advancing to the next development phase.

Document architecture reviews and risk assessments for repository compliance by generating a formal plan document that aligns with file-placement standards and includes empty placeholders for notes and decisions.

Yes, the generated development plan aligns with existing repository rules and architecture by integrating compliance checks directly into the document structure, ensuring feature work follows project standards.

The DEVELOPMENT_PLAN.md file is saved in the documentation/jobs/temp_job_<name>/ directory, providing a ready-to-use plan document for organizing feature work and compliance notes.

The best way to structure development planning for complex feature work is to use a phase-based document with formal gates, conflict checks, and compliance integration, reducing rework and miscommunication across teams.