create_plan

To create an implementation plan, provide task context or a ticket reference to initiate interactive research that reads related files and generates a structured, phase-based artifact with explicit milestones and success criteria.

Phase-based planning breaks down non-trivial codebase changes into sequential execution steps with concrete modifications, testing criteria, and measurable milestones to guide cross-team design and architecture implementation.

Yes, you can generate a structured plan artifact from a ticket reference by using it as input context to trigger parallel research, dependency capture, and draft outline generation suitable for review and storage.

Interactive research-driven planning is designed specifically for non-trivial software engineering tasks, applying structured workflows to surface risks, resource needs, and measurable criteria for complex codebase modifications.

The best way to document phased execution milestones is to generate a structured artifact that captures concrete changes, verification steps, and both automated and manual success criteria for each implementation phase.

Automated planning for cross-team design requires manual review of the draft outline and success criteria, as the generated artifact surfaces risks and dependencies but cannot validate domain-specific architectural decisions without human input.