AgentPlane
Use AgentPlane through its CLI instead of editing .agentplane/ state directly.
When to use
- The repository already contains
AGENTS.mdor.agentplane/. - The user wants to initialize AgentPlane in a repository.
- The user wants explicit planning, task IDs, verification evidence, or
branch_prworktrees.
Startup
- If the repository is not initialized, run
ap initoragentplane init. - Select ready work with
ap task active. - Request one bounded external-agent action with
ap task advance <task-id> --agent-json. - When
action.kind=agent_episode, perform only the supplied semantic objective inside the supplied authority and write the typed result toexchange.result_path. - Resume with the exact
exchange.resume_argvand request a fresh packet after every state change.exchange.return_invocationis compatibility-only. - If the repository has a configured managed runner, use
ap task run <task-id>instead of the external exchange loop.
Rules
- Treat
AGENTS.md,ap quickstart, andap role <ROLE>as the policy surface. - Use
ap task advanceorap task runas the normal protocol; do not edit.agentplane/state directly. - Do not invoke work start, start-ready, verify, finish, integrate, cleanup, Git branch/worktree, commit, or PR lifecycle commands during a normal semantic episode.
- Treat approval, human, hosted/external, stale-state, and effect-in-doubt stops as hard boundaries; return control instead of reconstructing the process.
- Use
task brief,task status --route, andtask next-action --explainonly for an explicit operator/recovery request. - Keep repository artifacts in English unless the user explicitly requests another language for a specific artifact.
- Return semantic check evidence through the typed result; AgentPlane persists verification and terminal evidence separately.
Limits
- This plugin bundles workflow guidance only. It does not install the
ap/agentplanebinary for you. - If both
apandagentplaneare missing fromPATH, install AgentPlane first, then use the workflow commands above.