ai-dev

Bridge GitHub Issue to Technical Implementation Plan. Reads issue context, strategic documents, and generates a detailed technical plan.

Sync GitHub state (closed issues, merged PRs) back to /strategy/ documentation

Commit staged changes and push directly to the current branch. Supports main-branch development workflow with quality gates.

Create a conventional commit with auto-generated message based on staged changes.

Pull the latest changes from origin. Essential for trunk-based development.

Automatically fix linting issues in the codebase.

Execute the project's test suite with detailed reporting.

Scan the codebase for security vulnerabilities and issues.

Break down OKRs into major work streams (Epics) and create them as GitHub Milestones

Define success metrics, leading indicators, and failure thresholds for your project

Define your project's north star, vision, and mission through rigorous questioning

Define Objectives and Key Results that connect your vision to measurable outcomes

Define your project's strategy, competitive positioning, and explicit non-goals

Generate detailed user stories and create them as GitHub issues with acceptance criteria

Survey project state and recommend the next ai-dev command to run

Full strategic planning workflow - guides you through defining north star, vision, mission, strategy, non-goals, success metrics, OKRs, epics, and user stories as GitHub issues

Review chat session and capture learnings (gotchas, decisions, patterns) to the learnings/ directory

Interactive technical planning workflow. Gathers requirements through Q&A, researches patterns, and outputs a detailed implementation plan.

Multi-agent code review. Runs code-reviewer, security-auditor, test-architect, and product-reviewer in parallel, then synthesizes findings.

Execute an implementation plan using TodoWrite for task tracking and incremental commits to main.

Expert debugging specialist for errors, test failures, crashes, and unexpected behavior.

Documentation specialist for creating and maintaining clear, comprehensive documentation.

Code refactoring specialist for improving code quality, reducing complexity, and enhancing maintainability without changing behavior.

Master coordinator for complex multi-step tasks. Use proactively when work involves multiple modules, requires specialist delegation, needs architectural planning, or involves PR workflows.

Socratic planning agent that guides users through 8-phase strategic planning from problem space to user stories.

Research agent that analyzes project structure, patterns, dependencies, and conventions to inform implementation decisions.

Audits GitHub project state including milestones, issues, labels, and PRs. Use when assessing work status or identifying next tasks to execute.

Audits /strategy/ documentation for completeness, gaps, and actionable next steps. Use when assessing project planning status or identifying strategic gaps.

Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, or when asked to review changes.

Product management specialist for evaluating whether changes align with product vision, strategy, and user value.

Security specialist for identifying vulnerabilities, analyzing attack surfaces, and recommending mitigations.

Testing specialist for designing test strategies, writing comprehensive tests, and ensuring quality coverage.

Knowledge and patterns for understanding project structures, architectures, and codebases.

Knowledge and patterns for designing RESTful and GraphQL APIs.

Knowledge and patterns for designing software architectures and system design.

Knowledge and patterns for designing comprehensive test strategies and writing effective tests.

Knowledge and patterns for Git workflows with emphasis on trunk-based development for rapid iteration.

Knowledge and patterns for identifying and resolving performance issues.

Automatically detects when users are discussing project planning, strategy, or feature prioritization. Guides them toward structured planning artifacts when appropriate. Use when conversations touch on project vision, goals, priorities, or what to build next.

7 hooks across 6 events