# Optional external process frameworks

Superpowers is not a prerequisite or a default integration in 1.0. AAPB does not install or enable it. Existing disabled settings should remain disabled unless the user intentionally chooses a change.

## When evaluating another framework

Compare its actual instructions with host behavior, project rules, and the task. A unique contract or useful example may deserve preservation; a repeated requirement to plan, open a worktree, ask approval, or run a fixed review sequence may add burden without helping that task.

Do not treat this as evidence that all third-party skills are harmful. Record the version, distinctive capability, required tool access, extra reading/execution, observed result, and recovery route. If the user selects a framework, resolve real instruction conflicts and preserve existing permissions rather than silently combining every procedure.

## Keep ownership and recovery separate

Disabling AAPB skills does not uninstall a framework, remove its cache, or change account-level connections. AAPB's skill lifecycle only manages its own marked directories. Preserve other projects and user-selected model/budget settings.

Use [Environment profiles](environment-profiles.md) for broader inventory and [Capability selection](capability-taxonomy.md) for choosing needed guidance. Normal AAPB use remains available with the project's existing tools.