lazy

Remove dead code safely from codebase

Implement feature from flexible input (story file, task ID, brief, or issue)

Generate or update documentation for the specified scope with the selected format.

Fix issues from story review report

Initialize new project with comprehensive documentation (overview, specs, tech stack, architecture)

Verify Memory MCP connectivity and list basic stats

Manage persistent knowledge via MCP Memory Graph

Create user story with inline tasks from feature brief

Answer questions about code or technical topics without creating artifacts

Review story and create PR with all committed tasks

Cleanup specialist. Removes dead code and unused imports. Use PROACTIVELY when detecting dead code, unused imports, or stale files.

Implementation specialist for coding tasks. Use PROACTIVELY when user requests code implementation, bug fixes, or security fixes.

Documentation specialist. Generates/updates docs, docstrings, README. Use PROACTIVELY when code lacks documentation or README needs updating.

Create US-story from feature brief with inline tasks. Use PROACTIVELY when user provides a feature brief or requests story creation.

Refactoring specialist. Simplifies code while preserving functionality. Use PROACTIVELY when code has high complexity, duplication, or architecture issues.

Research specialist for documentation and best practices. Use PROACTIVELY when user mentions unfamiliar technologies or needs documentation.

Senior code reviewer. Use PROACTIVELY after code changes to review quality, security, and performance.

Story-level code reviewer. Reviews all tasks in a story before creating PR. Use when story is complete and ready for review.

Testing specialist. Generates comprehensive test suites with edge cases. Use PROACTIVELY when code lacks tests or test coverage is below 80%.

Turn vague Acceptance Criteria into measurable checks and test assertions

Automatically selects the best specialized agent based on user prompt keywords and task type. Use when routing work to coder, tester, reviewer, research, refactor, documentation, or cleanup agents.

Structured ideation for options, trade-offs, and a clear decision

Detects backward-incompatible changes to public APIs, function signatures, endpoints, and data schemas before they break production. Suggests migration paths.

Request and process code review efficiently with a simple rubric and patch plan

Build a compact, high-signal context brief (files, symbols, recent commits) instead of pasting large code blocks

Keep changes narrowly scoped with a tiny patch plan and stop criteria

Evaluates if error handling is sufficient for new code - checks try-catch coverage, logging, user messages, retry logic. Focuses on external calls and user-facing code.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Create or update GitHub issue for the story and sub-issues for tasks

Use Git worktrees to isolate tasks and keep diffs small and parallelizable

Persistent memory graph skill using the MCP Memory server

Automatically choose the best output style (tables, bullets, YAML, HTML, concise) to improve scanability and save tokens

Detects performance anti-patterns like N+1 queries, nested loops, large file operations, and inefficient algorithms. Suggests fast fixes before issues reach production.

Automatically synchronize project documentation when major changes occur (new tech, architecture changes, requirements shifts). Detects significant updates and propagates changes across TECH-STACK.md, ARCHITECTURE.md, and SPECIFICATIONS.md.

Transforms project ideas into structured documentation (overview + specifications). Use when starting new projects or when brief needs project-level planning with vision, features, and technical requirements.

Evaluates and implements regression tests after bug fixes based on severity, code complexity, and coverage. Use when bugs are fixed to prevent future regressions.

Triggers for authentication, payments, user input, and API endpoints to check OWASP risks. Auto-evaluates security need and provides actionable fixes, not checklists.

Ensure Acceptance Criteria map to Tasks and Tests for PR-per-story workflow

Split features into atomic 2–4h tasks with independent tests and minimal dependencies

Design complete technology stack and system architecture from project requirements - generates TECH-STACK.md with frontend/backend/database/DevOps choices plus rationale, and ARCHITECTURE.md with components, data flow, and mermaid diagrams

Enforce RED→GREEN→REFACTOR micro-cycles and keep diffs minimal

3 hooks across 3 events