ak-task

# ak-task — Task Lifecycle Create a task, assign it, then monitor it to completion. Review ownership depends on whether the selected board has an active maintainer. ## Identity This is a leader workflow. If `ak` says no leader identity exists for the current runtime, create one first: ```bash ak auth login --leader-agent --username <username> [--name <name>] ``` The leader chooses its own username and optional full name. ## 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 clarification and task preview phase, before task creation is confirmed. - **After task creation: human-not-in-the-loop.** Once the user confirms the task and it is created, do not stop to ask for permission, confirmation, or next steps unless the user interrupts you. Continue through the full work cycle and report the outcome. On a board with an active maintainer, monitor while the maintainer owns review and completion. Otherwise, review, reject, or merge as leader. 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. ## Workflow Checklist Immediately after this skill is invoked, create and maintain an explicit task plan/checklist...