ak-planlisted

# ak-plan — Project Planning Plan and create a board with tasks — for a new version release or a new product from scratch. ## Unattended Execution Contract Assume this workflow runs in two explicit modes: - **Before task creation: human-in-the-loop.** Ask the user only during the initial planning, ambiguity resolution, and task-plan preview phase before task creation is confirmed. - **After task creation: human-not-in-the-loop.** Once the user confirms the plan and tasks are created, do not stop to ask for permission, confirmation, or next steps unless the user interrupts you. Continue through the full work cycle: create, assign, monitor, review, reject or merge, and report the final outcome. If execution hits a blocker after confirmation, use the available tools and repository context to resolve it. If the blocker cannot be resolved without external authorization or production mutation, fail fast with the exact blocker and the next required action instead of waiting in the middle of the workflow. ## Identity This is a leader workflow. If `ak` says no leader identity exists for the current runtime, create one first: ```bash ak identity create --username <username> [--name <name>] ``` The leader chooses its own username and optional full name. ## Input Parse the user's input: - **Name** — version (e.g. "v1.4") or product name (e.g. "my-api"). If the user provides a patch version such as `v1.4.0`, normalize task labels to `v1.4`. - **Goals** — what to achieve (if no