backlog

Run /backlog add followed by a short description. The skill reserves a unique ID, checks for duplicates, confirms the item type, writes a markdown file under .planning/backlog, and appends a created event to the event log.

Use /backlog promote with the item number or a range like N-M. The skill appends a promoted event and hands the item off to the /recon workflow, which links it into the plan body without moving the original file.

Parallel git worktrees each see only their own tree, so writing an item inside a worktree produces colliding IDs. All write flows run from the primary checkout on the base branch, then commit and push immediately so other worktrees see the new ID.

State is derived from an append-only .planning/events.jsonl log. Each lifecycle action (created, promoted, completed, cancelled) appends one event, and a fold script rebuilds the current status table from those events.

Yes, /backlog pending group clusters active items by shared domain and type affinity into plan-sized groups. The auto variant produces a dependency-ordered numbered list that can be pasted into /orchestrate.