# Issue

> Start planning work on a GitHub issue Use when this capability is needed.

- Skill: `tomevault-io/issue-8` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/issue-8`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/issue-8/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/issue-8

---


## Task: Work on Issue $ARGUMENTS

Pull the specified GitHub issue and start planning work to complete it.

**Related skills:** Use `github` skill patterns for CLI commands. Follow `planning` skill workflow for the planning phase.

### Step 0: Parse arguments

`$ARGUMENTS` is the issue ref optionally followed by a note. The first token is the issue ref, everything after is a note providing additional context.

Example: `/issue 123 focus on the api endpoint, ignore the frontend for now` → issue ref: `123`, note: `focus on the api endpoint, ignore the frontend for now`

If a note is present, treat it as guidance throughout planning and execution — it may narrow scope, set priorities, or provide context not in the issue itself.

### Step 1: Parse the issue reference

Parse the issue ref to determine the repo and issue number:

| Format              | Example       | Meaning                               |
| ------------------- | ------------- | ------------------------------------- |
| Number only         | `123`         | Current repo, issue 123               |
| `owner/repo#number` | `foo/bar#123` | Repo `foo/bar`, issue 123             |
| `repo#number`       | `bar#123`     | Current owner + repo `bar`, issue 123 |

To get the current repo's owner:

```bash
gh repo view --json owner -q '.owner.login'
```

### Step 2: Fetch issue details

Use `github` skill patterns:

```bash
gh issue view <number> --repo <owner/repo>
```

### Step 3: Understand the requirements

- Read the issue description and comments
- Identify acceptance criteria
- Note linked issues or PRs

### Step 4: Start planning workflow

Follow the `planning` skill:

1. Understand the work from the issue
2. Explore the codebase for relevant files
3. Draft implementation plan
4. Exit plan mode for approval

### Step 5: Execute (after plan approval)

Per `planning` skill workflow:

- Track this as the active issue
- Do the work
- Create PR that closes the issue

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/joshmanders) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->