pm-planning

# PM planning — decompose ARCH into tasks The pm agent's job is to take the architect's ARCH document and produce 2 things: 1. A `PLAN-<feature>.md` for humans 2. A sequence of `bd create` tasks for senior-dev to claim The plan is good if a fresh senior-dev (no prior context) can pick up the bd tasks and ship without coming back for clarification. ## The decomposition rules ### Rule 1. Tasks ≤ 4 hours Anything bigger gets split. If the task is "build the auth system", split into: - Schema migration for user table - Signup endpoint with hashing - Login endpoint with JWT issuance - Logout / token revocation - Tests Each ≤ 4h. If you can't split, the task is unclear — go back to ARCH and clarify. ### Rule 2. Single output artefact per task Each task produces ONE of: - A code file (new or modified) - A database migration - A test file - A documentation update - A config change If a task produces multiple unrelated artefacts, split it. ### Rule 3. Explicit dependencies via `--blocks` When task B requires task A's output: ```bash bd create "Task A: schema migration" -p P1 # returns id: my-proj-001-abc bd create "Task B: signup endpoint" -p P1 \ --blocks-on my-proj-001-abc \ --label senior-dev ``` The pipeline orchestrator reads `bd ready --assignee senior-dev` to know what's claimable. Tasks blocked on incomplete predecessors don't appear. ### Rule 4. Acceptance criteria — what does "done" mean? Every task description ends with a bulleted "Done when:" section. ...