heapy/kotgent
Repository-aware task workflows using the kotgent CLI and git
Create focused kotgent backlog tasks from a user request, specification, issue list, or implementation plan, with repository and session provenance. Use when the user asks to create, add, file, split, or seed tasks in kotgent; do not use for comparing or reviewing an existing backlog.
Audit todo kotgent tasks against the current repository and recommend whether to keep, rewrite, merge, drop, or escalate them. Use when the user asks to review, groom, clean up, triage, or validate the todo backlog for completed, obsolete, conflicting, duplicate, absorbed, or incorrectly blocked tasks. This workflow is always read-only.
Compare active kotgent tasks with repository guidance, plans, code, tests, TODOs, and Git history, and report task/repository drift with evidence and proposed CLI commands. Use when the user asks to sync, reconcile, map, or compare the kotgent backlog with the current repository. This workflow is always read-only.
Safely claim a specific or next eligible kotgent task from a free session, detect blocked or concurrent work, and immediately continue through the work-task workflow. Use when the user asks to take, claim, pick up, start, or work the next kotgent task, optionally naming a task ref.
Execute the kotgent task linked to the current session, coordinate concurrent work, implement and verify repository changes, report meaningful progress or blockers, and submit the task for human review. Use when the user asks to work, continue, implement, finish, or resume a linked kotgent task.