← ClaudeAtlas

implementlisted

Implement one issue, review it, close it and ship it. With 2 or more issue numbers, each issue gets its own session.
praisethebit/skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill praisethebit/skills
Arguments: `$ARGUMENTS`. Local extension: read `~/.claude/local/implement.md` when it exists, and follow its steps. With 2 or more issue numbers, do not implement an issue. Follow the local extension for many issues. With no local extension, tell the user to start one session for each issue, each in its own worktree (`claude -w <NNN>`), and stop. When the user later asks for the state, look in `<work folder>/issues/done/` first: `close-issue` moves a closed issue there. With one number, implement issue $ARGUMENTS. Each step ends on its completion criterion. Each `AskUserQuestion` call of this skill (a blocker, the recommended issues of step 4.7, a gap) holds 3 parts: the decision, what each option changes for the user, and the recommended option. The question text starts at the decision. It does not tell how the session got to the question. A question for a blocker also keeps the blocked requirement, the exact command or error, what you tried, and each step that the user must do, as the Blockers rule in `~/.claude/workflow.md` asks. 1. **Read.** Find the issue file at `<work folder>/issues/NNN-*.md`. Read it with the `Read` tool, not with `cat` in Bash. Why: the workflow review keeps the full output only of a `Read` call on an issue file, and its Outcome scorer needs all acceptance criteria. State its number, title and exact path. Compare its `model` value (frontmatter key) with your model. If they differ, stop and tell the user to press `s` in `/model` and pick that mod