Execute a tracker issue end-to-end with TDD until acceptance criteria are met.
npx skills add https://github.com/kenlck/skills --skill work-issue-kenlck
Please help me install this Agent Skill. Skill: work-issue Source: https://github.com/kenlck/skills/tree/main/ken-loop/skills/work-issue Command: npx skills add https://github.com/kenlck/skills --skill work-issue-kenlck
Headless executor for one loop-ready issue: reads the issue, implements it with TDD against its acceptance criteria, and ends in exactly one of two exits, DELIVERED (branch + PR) or BLOCKED (findings comment + needs-human).
Invoke this skill on a specific tracker issue to execute it end-to-end with TDD until acceptance criteria are met.
High-intent search queries and answers about installing and using this skill.
Automating issue execution with TDD requires a non-interactive executor that reads a single tracker issue, implements the code via test-driven development, and validates against explicit acceptance criteria. The process ends in either a DELIVERED or BLOCKED state.
Headless execution can generate a pull request for a single tracker issue by creating a deterministic loop/issue-<n> branch, implementing the changes, and validating the acceptance criteria before reporting progress and exiting with a DELIVERED state.
Non-interactive workflows report blockers during automated issue execution by terminating the run with a BLOCKED exit state, logging evidence in a findings comment, and flagging the issue as needs-human to ensure the blocker is reviewed.
Automated issue execution does not support multiple issues per run, as the design strictly enforces deterministic, non-interactive execution of a single tracker issue per invocation to ensure accurate validation against its specific acceptance criteria.
The best way to enforce deterministic branching for TDD issue automation is to map each single tracker issue to a specific loop/issue-<n> branch, ensuring non-interactive execution tracks progress and validates acceptance criteria accurately before a PR is created.
Automated TDD issue execution requires explicit acceptance criteria because the headless executor validates the implementation against these predefined conditions to determine whether the run should exit as DELIVERED or BLOCKED with a findings comment.
jeremy-newhouseDevelop a tracker issue into a tested feature change with PR creation.
edlngPost structured GitHub pull request review comments from Obsidian markdown notes.
amo-tech-aiManage Linear project workflows with structured issue creation and automation.
aroidoAutomates feature implementation workflow from issue tracking to pull request merging.
