Pure execution agent for creating implementation plans based on provided requirements and control flags. This agent executes planning tasks without complex decision logic - it receives context and flags from command layer and produces actionable development plans. Examples: Context: Command provides requirements with…
Generic planning agent for lite-plan, collaborative-plan, and lite-fix workflows. Generates structured plan JSON based on provided template reference. Spawned by lite-plan, collaborative-plan, and lite-fix orchestrators. Core capabilities: Template-driven output (plan-overview-base-schema or plan-overview-fix-schema)…
Specialized agent for requirement-level roadmap planning with issue creation output. Decomposes requirements into convergent layers (progressive) or topologically-sorted task sequences (direct), each with testable convergence criteria, then creates issues and generates execution plan for team-planex. Core…
Agent "README" from qdhenry/Claude-Command-Suite, covering 🤖 claude command suite ai agents, 🌟 what are claude code agents?, why use agents?, 🚀 quick start and 1. basic usage.
A highly advanced AI agent that functions as a master orchestrator for complex, multi-agent tasks. It analyzes project requirements, defines a team of specialized AI agents, and manages their collaborative workflow to achieve project goals. Use PROACTIVELY for comprehensive project analysis, strategic agent team…
Azure DevOps and cloud infrastructure specialist with comprehensive knowledge of all Azure services. MUST BE USED for Azure service configuration, deployment pipelines, infrastructure testing, and DevOps operations. Expert in using Azure CLI (az command) via Bash for all Azure operations, Azure Resource Manager, and…
Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
Advisory, non-authoring reviewer of a /debug or /fix hand-off (a Debug Report + needs-verification, or a batch-PR body). Checks that the hypothesis is evidence-backed, the root cause is real (not a symptom), the verification is falsifiable, systemic-patterns was consulted (by-design? regression? shared root?), the fix…
Advisory, non-authoring reviewer of a /pr-dev or /pr-main hand-off before merge. Checks PR base (dev, never master for /pr-dev; the release PR opened not merged for /pr-main), batch-cohesion, CHANGELOG issue-linking + rc-skip correctness, FAQ touch-up when a user-visible surface changed, CLAUDE.md.
Advisory, non-authoring reviewer of a /qa run. Checks that the chosen level (QA-0..QA-5) matched the target's risk, the live-bot drive stayed inside the guardrails (allowlisted dev bot only, bounded volume/pacing/retries, run-ID-tagged messages, fail-closed on a non-dev target), findings were capped (≤5) + de-duped +…
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Proactive validation agent for hook-driven test framework setups. Use PROACTIVELY when the user modifies test infrastructure, adds new hooks, or reports test execution issues. Diagnoses configuration problems and suggests fixes.
Proactive test generation agent for hook-driven test frameworks. Use PROACTIVELY when the user creates new MCP tools, commands, skills, or hooks that should have test coverage. Analyzes component implementations to generate comprehensive test definitions with appropriate expectations.
Reviews code in two passes: first spec compliance (does it do what was asked?), then code quality (is it well-written and secure?). Use after writing or modifying code.
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to any engine and model through the shared runtime.