astra

Critically review work plans for dependency conflicts, missing coverage, vague criteria, and AI failure modes. Produces structured issue list with fixes. Used by astra orchestrator during planning phase.

Design hierarchical work plans from user requests. Produces phases/epics/stories/tasks JSON with dependency graphs, target files, and acceptance criteria. Used by astra orchestrator during planning phase.

Run browser-based verification for web projects. Starts dev server, navigates pages, checks for console errors and broken layouts. Used by astra orchestrator evaluator loop.

Challenge bug investigation reports. Find missed root causes, incomplete reproduction, and edge cases the fix must handle. Used by astra orchestrator bugfix strategy.

Review code changes for quality, security, and correctness after implementation. Checks OWASP top 10, error handling, and pattern adherence. Used by astra orchestrator evaluator loop.

Use when setting up a project for AI-driven development with astra. Detects stack, reads user insights, generates CLAUDE.md + AGENTS.md + GOAL.md + astra.yaml, installs hooks, skills, MCP servers, and agents. Do NOT use for ongoing development — use /astra-run instead.

Use when resuming an interrupted astra run. Reconstructs state from events.jsonl and re-enters the executor loop. Do NOT use for new runs — use /astra-run instead.

Use when starting a feature or bugfix implementation run. Orchestrates planning, then generator/evaluator loop with circuit breaker and HITL gates. Do NOT use for project setup — use /astra-init instead.

Use when checking the status of an astra run. Shows tasks done/total, costs, duration, current phase. Do NOT use to start or resume runs.

7 hooks across 2 events