planning

Drafting an implementation plan involves researching requirements, designing architectures, and detailing phased roadmaps. It generates plan.md and phase-*.md artifacts to align teams and govern multi-team system redesigns.

Design docs and phased roadmaps are structured plan artifacts that detail system architectures and requirements analysis. They enforce YAGNI, KISS, and DRY principles to guide feature introductions and architecture evolution.

Yes, you can generate comprehensive plan documentation for project management. It produces structured plan.md and phase-*.md artifacts to guide implementation governance and maintainable deliverables across teams.

The best way to structure requirements analysis is by researching requirements and detailing phased roadmaps. This approach enforces planning principles like YAGNI and DRY to produce maintainable artifacts for feature migrations.

You should avoid automated planning artifacts when a task lacks clear requirements or architectural scope. It is designed for detailed technical implementations and multi-team projects, not simple or undefined ad-hoc coding tasks.