AgentsAtlas

Complete the current milestone and prepare next work by following the canonical complete command doc.

Execute the current plan (from STATE.md -> PLAN.md) by following the canonical execute command doc. Make code changes + run necessary checks.

Initialize project with CLAUDE.md, STATE.md, and ROADMAP.md by following the canonical init command doc.

Create executable plan for the current phase (3-5 tasks). Reads the canonical plan command doc and produces/updates the current PLAN.md referenced from STATE.md. No implementation.

Review code changes and capture learnings for CLAUDE.md by following the canonical review command doc.

Check project progress and suggest the next action by following the canonical status command doc.

Restore project context after clear/new session by following the canonical sync command doc.

Pull and triage issues from external sources for planning by following the canonical triage command doc.

Use before any creative work - creating features, building components, adding functionality. Explores requirements and design through collaborative dialogue before implementation.

Creates quality git commits with conventional commit format. Use when asked to commit changes or create a commit message.

Creates pull requests with quality descriptions. Use when asked to create a PR, open a pull request, or ship code for review. Requires test verification before PR creation.

Use when encountering any bug, test failure, error, or unexpected behavior - before proposing fixes. Requires root cause investigation first.

Explains code with diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when asked "how does this work?"

Use when receiving code review feedback or corrections - before implementing suggestions. Requires technical verification and reasoned evaluation, not blind agreement or performative responses.

Refactors code safely with test verification. Use when asked to refactor, restructure, clean up, or improve code organization.

Generates boilerplate following project conventions. Use when asked to create a new component, module, service, or scaffold code.

Audits code for security vulnerabilities. Use when asked to check security, find vulnerabilities, or audit for OWASP issues.

Use when implementing any feature or bugfix - before writing implementation code. Write the test first, watch it fail, then implement.

Use when about to claim work is complete, fixed, or passing - before committing or creating PRs. Requires running verification commands and confirming output before any success claims.