autonomous-operation

Use when user-facing features change.

Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full…

Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state

Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks

Use when user requests autonomous operation across multiple issues.

Analyze and resolve Sentry comments on GitHub Pull Requests.

Use when documentation drift is detected.

Use when API code changes (routes, endpoints, schemas).

Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity