Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Assistance with triage of unprioritized issues. Use when the user asks for help with triage.

Ensure the plugin remains compatible with the latest IntelliJ Platform releases and EAP (Early Access Program) builds.

Eliminate plugin verification warnings and errors (Internal API usage, Override-only API usage, etc.) identified by ./gradlew verifyPlugin.

Remove support for an older IntelliJ Platform / Android Studio version from the project and clean up obsolete code, baselines, and CI configurations.

Optimize memory usage, consistency, and performance by migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations.

Perform a pedantic, multi-perspective code review on the current diff or git changes against the styleguide and software engineering best practices.

Reduce plugin size by scanning resources/icons and removing unreferenced assets.

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

Prevent UI freezes and ensure a responsive user experience by validating threading rules and migrating blocking calls off the Event Dispatch Thread (EDT).

Optimize plugin size and security by removing unused dependencies and updating outdated libraries.

Ensure the plugin's custom UI components are accessible to users with screen readers and other assistive technologies.

Add a new unit test for a class that currently lacks one or add a new test case to an existing test file, verifying improvement with Kover.

Cost-and-speed-optimized development workflow for a cheap fast implementing model consulting expensive advisor subagents (design-advisor, principal-advisor, quality-reviewer). Use for design-bearing or high-risk implementation - new/changed public contracts, schemas, state/lifecycle, concurrency, security, persistence, compatibility - or after repeated failed attempts. Do not invoke for trivial edits or solely because a change touches multiple files.

Produce the EdgeQuake WebUI UX/UI map one route at a time (capture screenshots, then immediately write per-page docs and per-page analysis requests). Use when asked to map UI, capture screens page-by-page, avoid agent memory saturation, or generate ux_ui_map artifacts.

Analyze exactly one captured UI page (from ux_ui_map screenshots + request JSON) and immediately write/update ux_ui_map/pages/{page}.md in neutral descriptive language. Use when asked to analyze screenshots, rewrite corresponding analysis immediately, or avoid memory/context saturation.

Automatically generate comprehensive documentation for Rust and TypeScript codebases by analyzing code structure, patterns, and relationships. Supports trait-based patterns, async operations, React components, and Next.js applications.