agentplanelisted

# AgentPlane Use AgentPlane through its CLI instead of editing `.agentplane/` state directly. ## When to use - The repository already contains `AGENTS.md` or `.agentplane/`. - The user wants to initialize AgentPlane in a repository. - The user wants explicit planning, task IDs, verification evidence, or `branch_pr` worktrees. ## Startup 1. If the repository is not initialized, run `ap init` or `agentplane init`. 2. Run `ap quickstart`. 3. Inspect `AGENTS.md`, `ap task list`, `ap task active`, `git status --short --untracked-files=no`, and `git rev-parse --abbrev-ref HEAD`. 4. Use `ap task brief <task-id>` before owner-scoped execution; add `--remote` only when hosted PR/check/review state is needed. 5. Use `ap role ORCHESTRATOR` while planning and approvals are active. 6. Switch to `ap role <ROLE>` before owner-scoped execution or verification. ## Rules - Treat `AGENTS.md`, `ap quickstart`, and `ap role <ROLE>` as the policy surface. - Use `ap task ...`, `ap work ...`, `ap verify ...`, and `ap finish ...`; do not edit `.agentplane/tasks.json` manually. - Prefer `ap task brief <task-id>` and `ap task next-action <task-id> --explain` over manually combining task docs, route status, Verify Steps, PR metadata, and policy notes. - In `branch_pr`, use the concrete route command emitted by `task brief` or `task next-action` when available; fall back to `ap work start <task-id> --agent <ROLE> --slug <slug> --worktree` only as the low-level command contract. - Treat weak `sourc