How do I install the Working On An Issue skill?

Run npx skillmds@latest add tomevault-io/working-on-an-issue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Working On An Issue skill do?

Use when asked to work on, read, or implement a GitHub issue. It is listed under Coding & Dev Tools on SkillMD.

Is Working On An Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Working On An Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Working On An Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Working On An Issue?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Working On An Issue by tomevault-io

Name: Working On An Issue
Author: tomevault-io

File contents

Working on an Issue

Announce at start: "I'm using the working-on-an-issue skill to implement this GitHub issue."

Overview

A structured workflow for implementing GitHub issues with verification.

Core Principle: Understand → Plan → Verify → Implement → Verify Again

When to Use

Developer asks to work on a GitHub issue
Developer asks to implement an issue
Developer provides an issue URL or number

Pre-flight Checklist

Before starting:

Issue URL or number obtained
Repository cloned and on correct branch
CLAUDE.md exists (or run setting-up-a-project first)
Developer available for questions (or async mode agreed)

The Process

1. Read and Understand the Issue

Get the issue content via:

GitHub CLI: gh issue view <number>
Ask user to paste the issue content
Use GitHub MCP tools if available

Clarify before proceeding:

If requirements are ambiguous, ask specific questions
If acceptance criteria are missing, propose them
If scope is unclear, confirm boundaries

Do not assume or invent requirements not in the issue.

2. Write an Implementation Plan

Use the obra/writing-plans skill (if available) or create a brief plan covering:

What changes are needed
Which files will be modified/created
Order of implementation
Risks or unknowns

Save to docs/plans/issue-<number>-plan.md and get developer approval before proceeding.

3. Write a Verification Plan

Use the britt/writing-verification-plans skill to create acceptance tests for the issue.

4. Implement

Follow TDD practices if TDD.rules.md is present
Commit after each logical change
Pause and ask if you hit unexpected complexity

5. Execute Verification

Run the verification plan. Report results using the verification log format from britt/writing-verification-plans.

Absolute Rules

No assumptions: Ask if anything is unclear
No scope creep: Only implement what's specified
Verification required: Task is incomplete until verification passes or developer confirms manual verification
Blocked = Stop: If blocked, use summoning-the-user skill

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: working-on-an-issuedescription: Use when asked to work on, read, or implement a GitHub issue.---# Working on an Issue**Announce at start:** "I'm using the working-on-an-issue skill to implement this GitHub issue."## OverviewA structured workflow for implementing GitHub issues with verification.**Core Principle:** Understand → Plan → Verify → Implement → Verify Again## When to Use- Developer asks to work on a GitHub issue- Developer asks to implement an issue- Developer provides an issue URL or number## Pre-flight ChecklistBefore starting:- [ ] Issue URL or number obtained- [ ] Repository cloned and on correct branch- [ ] CLAUDE.md exists (or run `setting-up-a-project` first)- [ ] Developer available for questions (or async mode agreed)## The Process### 1. Read and Understand the IssueGet the issue content via:- GitHub CLI: `gh issue view <number>`- Ask user to paste the issue content- Use GitHub MCP tools if available**Clarify before proceeding:**- If requirements are ambiguous, ask specific questions- If acceptance criteria are missing, propose them- If scope is unclear, confirm boundaries**Do not assume or invent requirements not in the issue.**### 2. Write an Implementation PlanUse the `obra/writing-plans` skill (if available) or create a brief plan covering:1. What changes are needed2. Which files will be modified/created3. Order of implementation4. Risks or unknownsSave to `docs/plans/issue-<number>-plan.md` and get developer approval before proceeding.### 3. Write a Verification PlanUse the `britt/writing-verification-plans` skill to create acceptance tests for the issue.### 4. Implement- Follow TDD practices if `TDD.rules.md` is present- Commit after each logical change- Pause and ask if you hit unexpected complexity### 5. Execute VerificationRun the verification plan. Report results using the verification log format from `britt/writing-verification-plans`.## Absolute Rules- **No assumptions**: Ask if anything is unclear- **No scope creep**: Only implement what's specified- **Verification required**: Task is incomplete until verification passes or developer confirms manual verification- **Blocked = Stop**: If blocked, use `summoning-the-user` skill---> Converted and distributed by [TomeVault](https://tomevault.io/claim/britt) — claim your Tome and manage your conversions.

Frequently asked questions

Working On An Issue