aa-ma-plan-workflow

Execution-ready plans for multi-session architectural refactors are created using a structured five-phase planning workflow with validation gates. This process transforms complex feature requests into complete AA-MA artifacts containing acceptance criteria, risks, effort estimates, and next actions.

To prevent scope creep and context loss during multi-session execution, use an agentic memory planning workflow that enforces artifact-first deliverables. This approach maintains an audit trail and rollback provenance across dependency-heavy tasks, ensuring decisions are not repeated.

Complexity routing for high-impact architectural changes flags modifications with a 60% or higher impact rate. Changes reaching 80% or above require a deep architectural review before proceeding to downstream artifact creation.

An AA-MA plan with validation gates and audit trails is needed for complex, dependency-heavy tasks such as integrations and architectural refactors. It is required when work spans multiple sessions and demands rollback capabilities or provenance tracking.

This planning workflow is not designed for simple feature requests without dependencies. It applies to multi-session, dependency-heavy tasks requiring research, impact analysis, and mandatory artifact creation for downstream execution.

To start planning a complex integration, ask your agent to use the aa-ma-plan-workflow to create an AA-MA plan. The structured workflow runs research and impact analysis phases, then proceeds to mandatory AA-MA artifact creation for execution.