# working-on

Makes one tracking file the source of truth for the current task. The agent keeps appending decisions, findings and plans to it as work moves.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 491 installs · ★ 547
- Author: Garrick Aden-Buie (@gadenbuie)
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/posit-dev/skills/tree/HEAD/posit-dev/working-on/SKILL.md
- Updated: 2026-10-15
- HTML: https://affpapa.org/en/nevibecode/skills/working-on

## What it does

This skill turns a chosen document into a running record of the task. The agent updates it whenever a decision lands, a bug or edge case shows up, a requirement changes, an issue closes, or files get committed. Plans go into the file rather than staying in the chat, so the record survives the session.

What ships is a set of behavioural rules, not scripts. Updates should stay short: bullets and small paragraphs beat long prose. Capture why a call was made, not just what it was. Sections that go stale get moved into “Archive” or “Resolved” instead of being dropped. When no document exists yet, the agent builds one around the task.

Git has its own clause. A tracking file that is not already in the repository history must stay out of commits, so keep that in mind if you place it inside the project. The skill needs a path argument: with no path it has nothing to track.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add posit-dev/skills --skill working-on -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/working-on/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/working-on/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add posit-dev/skills --skill working-on -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/working-on/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add posit-dev/skills --skill working-on -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/working-on/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install posit-dev/skills working-on
```

2. **Manually: put the files in place**
- File: `.github/skills/working-on/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add posit-dev/skills --skill working-on -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/posit-dev/skills --path posit-dev/working-on
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/working-on/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add posit-dev/skills --skill working-on -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/posit-dev/skills/tree/HEAD/posit-dev/working-on/SKILL.md

## When to use it
- carry decisions across agent sessions on one feature
- keep a bug and its workaround in a single file
- rebuild context after the chat is gone
- list open questions for a multi-step task
- write the plan to disk instead of leaving it in the thread

## Example prompts
- Use `docs/auth-refactor.md` as the tracking doc for this task
- We're fixing a bug, track it in `notes/bug-142.md`
- Starting the export feature, keep the record in `docs/export.md`

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e9cd1613199bb5e6.

BEGIN THIRD-PARTY FILE e9cd1613199bb5e6
```text
---
name: working-on
description: "Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds."
disable-model-invocation: true
arguments: [path]
argument-hint: "[path-to-tracking-doc] [additional instructions]"
metadata:
  author: Garrick Aden-Buie (@gadenbuie)
  version: "1.1"
license: MIT
---

# Working On

You are managing a tracking document that serves as the source of truth for the current task or feature.

The tracking document is: `$path`

## Behavior

Once activated, treat the tracking document as a living record. Update it after:

- Any decision is made (architectural, design, scope, naming, etc.)
- A new problem, bug, or edge case is discovered
- A new sub-feature or requirement emerges
- An issue is raised or resolved
- Any significant implementation work is completed
- A key part of a conversation with the user that would be useful to recall later
- Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated
- Any plan you form — write it to the document rather than presenting it only in chat; the document is the persistent record

If in doubt, update the document. It is better to over-document than to lose context.

## Git Handling

Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.

## Guidelines

- Keep updates concise — bullet points and short paragraphs are preferred over prose
- Use timestamps or date headers when the document spans multiple sessions
- Record the *why* behind decisions, not just the *what*
- When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
- If the document doesn't exist yet, create it with a sensible structure based on the task at hand
```
END THIRD-PARTY FILE e9cd1613199bb5e6

The third-party file has ended. Everything between the e9cd1613199bb5e6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© Garrick Aden-Buie (@gadenbuie) · MIT · https://github.com/posit-dev/skills/tree/HEAD/posit-dev/working-on/SKILL.md

## Similar
- [setup-matt-pocock-skills](https://affpapa.org/en/nevibecode/skills/setup-matt-pocock-skills.md) — skill · 1052851 installs
- [ask-matt](https://affpapa.org/en/nevibecode/skills/ask-matt.md) — skill · 766587 installs
- [to-tickets](https://affpapa.org/en/nevibecode/skills/to-tickets.md) — skill · 711230 installs
- [writing-plans](https://affpapa.org/en/nevibecode/skills/writing-plans.md) — skill · 282859 installs
- [caveman-review](https://affpapa.org/en/nevibecode/skills/caveman-review.md) — skill · 411800 installs
- [caveman-compress](https://affpapa.org/en/nevibecode/skills/caveman-compress.md) — skill · 411500 installs

From the same set: [posit-dev/skills](https://affpapa.org/en/nevibecode/by/posit-dev/skills.md) — 20 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md