planner

Run the `planner:linear-issue-create` skill with any arguments the user provided: $ARGUMENTS

Run the `planner:linear-milestone-create` skill with any arguments the user provided: $ARGUMENTS

Run the `planner:linear-project-create` skill with any arguments the user provided: $ARGUMENTS

Run the `planner:planner-batch` skill with any arguments the user provided: $ARGUMENTS

Run the `planner:planner-create` skill with any arguments the user provided: $ARGUMENTS

Orchestrate batch plan execution with dependency resolution and parallelism. Spawned by planner-batch skill. Builds dependency graph, executes in rounds, spawns plan-executor agents.

Create plan files with dependency configuration. Spawned by planner-create skill.

Execute a single plan file with dependency validation and config options. Spawned by planner-exec skill or planner-batch skill. Handles dependency checks, execution, PROGRESS.md updates, and config actions (auto-commit, project CLAUDE.md updates).

Create specification files with comprehensive requirements, technical details, and acceptance criteria. Performs deep codebase analysis to infer context. Spawned by spec-create skill.

Create Linear issues from plan files. Reads plans from PROGRESS.md, lets user select which plans to create issues for, and updates plan files with Linear issue URLs. Use when user wants to create Linear issues from their plans.

Create a milestone within an existing Linear project and optionally create issues from plans. Lists user's projects for selection, suggests milestone names, and can associate plan-based issues with the milestone. Use when user wants to add milestones to Linear projects.

Create a Linear project from a set of plans with a specific prefix. Generates a comprehensive project spec from all related plans, creates the project in Linear, and optionally creates issues for each plan. Use when user wants to sync plans to a Linear project.

Execute multiple plans with automatic dependency resolution and parallel execution. Builds dependency graph, runs independent plans simultaneously, handles sequential dependencies, and applies configuration options. Use when user wants to run multiple plans, batch execute plans, or execute all plans for a feature.

Handle git commits for plan execution with support for Conventional Commits or simple format. Called by plan-executor when auto_commit is enabled.

1 hook across 1 event