Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Create and manage todo tracking documents for features, bugs, and multi-step tasks.
Install New Work
$ npx skills add posit-dev/skills --skill new-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install posit-dev/skills new-work --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/posit-dev/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/posit-dev/new-work .claude/skills/new-work && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "new-work" agent skill from https://github.com/posit-dev/skills/tree/main/posit-dev/new-work into .claude/skills/new-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-work", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/posit-dev/skills/tree/main/posit-dev/new-workType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add posit-dev/skills --skill new-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install posit-dev/skills new-work --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/posit-dev/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/posit-dev/new-work .agents/skills/new-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "new-work" agent skill from https://github.com/posit-dev/skills/tree/main/posit-dev/new-work into .agents/skills/new-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-work", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add posit-dev/skills --skill new-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install posit-dev/skills new-work --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/posit-dev/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/posit-dev/new-work .cursor/skills/new-work && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "new-work" agent skill from https://github.com/posit-dev/skills/tree/main/posit-dev/new-work into .cursor/skills/new-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-work", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/posit-dev/skills.git --path posit-dev/new-work--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add posit-dev/skills --skill new-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install posit-dev/skills new-work --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/posit-dev/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/posit-dev/new-work .gemini/skills/new-work && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "new-work" agent skill from https://github.com/posit-dev/skills/tree/main/posit-dev/new-work into .gemini/skills/new-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-work", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install posit-dev/skills new-workInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add posit-dev/skills --skill new-work -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/posit-dev/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/posit-dev/new-work .github/skills/new-work && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "new-work" agent skill from https://github.com/posit-dev/skills/tree/main/posit-dev/new-work into .github/skills/new-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-work", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add posit-dev/skills --skill new-work -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install posit-dev/skills new-work --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/posit-dev/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/posit-dev/new-work .opencode/skills/new-work && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "new-work" agent skill from https://github.com/posit-dev/skills/tree/main/posit-dev/new-work into .opencode/skills/new-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-work", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
new-work- GitHub stars
- 529
- Token cost
- ~626 tokens
- SKILL.md length
- 218 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and manage todo tracking documents for features, bugs, and multi-step tasks.
- Starting new work that benefits from a persistent record of decisions
- SKILL.md covers Storage Location, File Naming, File Contents and Lifecycle, plus 1 more section
- Reaches github.com
What it does
New Work is an agent skill from posit-dev/skills. Create and manage todo tracking documents for features, bugs, and multi-step tasks. Use when starting new work that benefits from a persistent record of decisions, progress, and context.
Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: A collection of Claude Skills from Posit. The licence is MIT.
When your agent uses it
- Starting new work that benefits from a persistent record of decisions
Example prompts
- “/new-work”
What it can do on your machine
Read from SKILL.md and the folder at commit 0300946. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
New Work loads about 626 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 218 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from posit-dev/skills at commit 0300946, republished under its MIT licence (© posit-dev). 218 words, ~626 tokens.
Download SKILL.mdSave it as
.claude/skills/new-work/SKILL.md (or your agent's skills folder).- name
- new-work
- description
- Create and manage todo tracking documents for features, bugs, and multi-step tasks. Use when starting new work that benefits from a persistent record of decisions, progress, and context.
- disable-model-invocation
- true
- metadata.author
- Garrick Aden-Buie (@gadenbuie)
- metadata.version
- 1.0
- license
- MIT
New Work
Todo notes track work items as markdown files with YAML front matter capturing status, context, and progress.
Storage Location
Use _dev/todos/ if it exists in the repository root; otherwise ask the user where to store todo notes before creating anything. It contains two subdirectories: pending/ (active) and done/ (finished).
File Naming
YYYY-MM-DD_short-kebab-slug.md, e.g. 2026-02-18_add-oauth-support.md.
File Contents
YAML front matter plus a markdown body. Only status is required.
---
status: pending # pending | in progress | review | blocked | done
issue: https://github.com/org/repo/issues/123 # optional
pr: https://github.com/org/repo/pull/456 # optional
---
# Title
Overview of what this is about and why it matters.
## Key Files
- `src/relevant-file.ts` — what it does
- `src/other-file.ts:functionName()` — why it matters
## Work Items
- [ ] First thing to do
- [ ] Second thing to do
## Design Decisions
Context, constraints, or choices worth capturing.
## Decision Log
<!--
### YYYY-MM-DD — Short Decision Title
**Decision:** What was decided?
**Rationale:** Why?
-->Lifecycle
- Create: make
pending/if needed, create the date-prefixed file withstatus: pending, and write enough context to resume later. - In progress: update
status; addissue/prlinks when they exist; check off Work Items (- [ ]→- [x]); record significant decisions in the Decision Log. - Complete: set
status: doneandmvthe file frompending/todone/.
Keeping the Document Current
Treat the todo as a living record for the rest of the session. Update it after any decision, newly discovered problem or requirement, issue raised/resolved, significant implementation work, or commit. When in doubt, update it.
When you form a plan — whether in response to a user request or on your own initiative — write it to the todo document rather than presenting it only in chat. The document is the persistent record; the chat is not.
To resume in a future session, use /working-on <path-to-todo> — same live-document behavior without re-creating the file.
© posit-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in posit-dev/new-work of posit-dev/skills.
Open the folder on GitHubat commit 0300946
Compare with similar skills
New Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| New Work this skillposit-dev/skills | 529 | — | ~626 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from posit-dev/skills
All 17 skills in this repoR CLI App
posit-dev/skills
Build command-line apps in R using the Rapp package. An agent skill from posit-dev/skills.
R Lifecycle
posit-dev/skills
Guidance for managing R package lifecycle according to tidyverse principles using the lifecycle package.
PR Create
posit-dev/skills
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes.
Shiny Bslib
posit-dev/skills
Build modern Shiny dashboards and applications using bslib (Bootstrap 5).
Shiny Bslib Theming
posit-dev/skills
Advanced theming for Shiny apps using bslib and Bootstrap 5.
Critical Code Reviewer
posit-dev/skills
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases.
Related
Categories
Questions about New Work
What does New Work do?
Create and manage todo tracking documents for features, bugs, and multi-step tasks. New Work is an agent skill from posit-dev/skills. Create and manage todo tracking documents for features, bugs, and multi-step tasks.
When should I use New Work?
New Work fits situations like: starting new work that benefits from a persistent record of decisions.
How do I install New Work in Claude Code?
Run `npx skills add posit-dev/skills --skill new-work -a claude-code`. Or copy the skill folder (posit-dev/new-work in posit-dev/skills) into .claude/skills/new-work in your project. Claude Code loads it when a task matches its description.
How do I install New Work in Codex?
Run `npx skills add posit-dev/skills --skill new-work -a codex`. Or copy the skill folder (posit-dev/new-work in posit-dev/skills) into .agents/skills/new-work in your project. Codex loads it when a task matches its description.
Can I use New Work in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add posit-dev/skills --skill new-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/new-work, .gemini/skills/new-work, .github/skills/new-work and .opencode/skills/new-work in your project.
What does New Work need to run?
SKILL.md names no scripts, command-line tools or credentials: New Work is instructions for the agent only.
Does New Work access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is New Work safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does New Work use?
New Work is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does New Work use?
About 626 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to New Work?
Skills that share tags, products or a category with New Work: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains New Work?
posit-dev (a GitHub organization) maintains it in posit-dev/skills, which has 529 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: posit-dev/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.