
What happened
A developer released idd-skills, whose idd-implement skill takes a GitHub Issue number and autonomously investigates, plans, implements, tests, and opens a PR, working in an isolated git worktree.
Why it matters
Specs and decisions stay recorded on the Issue rather than lost in chat history, so the workflow carries over between AI tools, and issues can be worked in parallel.
Summaries like this, every morning.
The workflow is built around GitHub as the single source of truth. Before writing code, idd-implement posts a spec with functional requirements, technical approach, and a verification plan as an Issue comment, and moves the GitHub Projects status to In Progress. Because all of this lives on the Issue, the developer notes that context survives switching AI tools or starting a new session, and the question-and-answer history serves as a decision record akin to an ADR.
Implementation runs in a fresh git worktree branch, leaving the main working directory untouched, which is what allows several Issues to be worked in parallel without conflicts. Tests, build, and type checks must pass before the branch is pushed and a PR linked with Closes #... is created and the status moves to In Review. Review comments can be fed back by rerunning the skill, and merging closes the Issue and sets the status to Done.
The author applied this flow to Nickmark, a Chrome extension for keyboard-driven access to nicknamed bookmarks, filing each feature and fix as an Issue and processing them one by one as PRs. Optional pieces include a GitHub App to post as a bot and GitHub Projects to auto-update statuses, while Node.js v18 or later is recommended for the bundled helper scripts.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.