How do I install the Issue Driven Development skill?

Run npx get-skill add tomevault-io/issue-driven-development 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.

Is Issue Driven Development safe to use?

SkillMD's automated safety review verdict for this skill is PASS. 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 Issue Driven Development?

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 Issue Driven Development free to use?

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

Who published Issue Driven Development?

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

Issue Driven Development by tomevault-io

Name: Issue Driven Development
Author: tomevault-io

File contents

Issue-Driven Development Workflow

This skill defines the standard process for handling development tasks in this repository. It ensures clear requirements, user approval at critical stages, and proper linkage between issues, branches, and pull requests.

Workflow Steps

1. Requirement Analysis & Issue Drafting

Analyze user requirements and summarize them.
Create a draft GitHub Issue (usually as an implementation_plan.md artifact).
DO NOT make any code changes at this stage.

2. User Review (Draft)

Present the draft to the user for review.
Refine the draft based on feedback until approved.

3. Issue & Branch Creation

Once the draft is approved:
- Create the actual GitHub Issue.
- Create a working branch (e.g., fix/issue-<number>-<title>).
- Link the branch to the issue.
- Switch to the working branch.
Prepare the environment (e.g., install dependencies, clean directories).

4. Permission to Start Implementation

MANDATORY: Confirm with the user before starting any code changes.
Wait for user approval to proceed.

5. Implementation Phase

Implement the changes as planned.
Follow TDD and architecture guidelines.

6. Draft Commit Message & Completion Report

Once implementation is complete:
- Draft a clear, descriptive commit message.
- Report the completion and provide the draft message to the user.
- DO NOT commit or push yet. The changes should remain local.

7. Iterative Refinement

Address any additional feedback or instructions from the user.
Repeat until the user is satisfied.

8. Final Approval & PR Creation

Once the changes and the commit message are finalized and approved:
- Commit the changes locally.
- Create a Pull Request (PR) on GitHub.
- Ensure the PR is linked to the original Issue (e.g., using "Closes #22").

Best Practices

Never skip checkpoints: User approval is required before starting work and before finalizing changes.
Traceability: Always link branches and PRs to the issue number.
Atomic Commits: If a task is large, coordinate with the user on whether to split it into multiple PRs.

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

---name: issue-driven-developmentdescription: Use when working with a workflow for issue-driven development, from drafting an issue to PR creation with user checkpoints.---# Issue-Driven Development WorkflowThis skill defines the standard process for handling development tasks in this repository. It ensures clear requirements, user approval at critical stages, and proper linkage between issues, branches, and pull requests.## Workflow Steps### 1. Requirement Analysis & Issue Drafting- Analyze user requirements and summarize them.- Create a draft GitHub Issue (usually as an `implementation_plan.md` artifact).- **DO NOT** make any code changes at this stage.### 2. User Review (Draft)- Present the draft to the user for review.- Refine the draft based on feedback until approved.### 3. Issue & Branch Creation- Once the draft is approved: - Create the actual GitHub Issue. - Create a working branch (e.g., `fix/issue-<number>-<title>`). - Link the branch to the issue. - Switch to the working branch.- Prepare the environment (e.g., install dependencies, clean directories).### 4. Permission to Start Implementation- **MANDATORY**: Confirm with the user before starting any code changes.- Wait for user approval to proceed.### 5. Implementation Phase- Implement the changes as planned.- Follow TDD and architecture guidelines.### 6. Draft Commit Message & Completion Report- Once implementation is complete: - Draft a clear, descriptive commit message. - Report the completion and provide the draft message to the user. - **DO NOT** commit or push yet. The changes should remain local.### 7. Iterative Refinement- Address any additional feedback or instructions from the user.- Repeat until the user is satisfied.### 8. Final Approval & PR Creation- Once the changes and the commit message are finalized and approved: - Commit the changes locally. - Create a Pull Request (PR) on GitHub. - Ensure the PR is linked to the original Issue (e.g., using "Closes #22").## Best Practices- **Never skip checkpoints**: User approval is required before starting work and before finalizing changes.- **Traceability**: Always link branches and PRs to the issue number.- **Atomic Commits**: If a task is large, coordinate with the user on whether to split it into multiple PRs.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sun-flat-yamada) — claim your Tome and manage your conversions.

Frequently asked questions

Issue Driven Development