Vignette Todo Run

Run a batch of Vignette TODO items as a multi-agent worktree run. Use when Pete asks to "run the TODOs", "run items N to M", "do a todo run", or hands over queued items from docs/TODOS.md in the Vignette repo. The orchestrator plans, briefs, and reviews; delegated coding agents do every code change and every verification, each in its own worktree with its own scratch settings; an integrator merges, a reviewer attacks the merge, and the branch is handed to Pete unmerged. Not for a single small fix in the checkout, and not for a repo other than Vignette.

49 stars 10 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add petekp/claude-code-setup --skill vignette-todo-run
Manual install
git clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/vignette-todo-run ~/.claude/skills/vignette-todo-run

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Vignette TODO run

One run takes a base branch and a list of items from `docs/TODOS.md`, and ends with one
integration branch Pete tests by hand, which also removes the landed items from `docs/TODOS.md`,
and a run report in `~/Code/vignette-todo/reports/`.
Read `AGENTS.md` in the Vignette checkout before planning: the loop, the rules for several
builds on one Mac, and the measuring paragraphs are what the templates enforce.

Roles. The orchestrator (you) plans, briefs, orchestrates, and reviews, and writes no product
code. Delegated agents do the code and the verification, one worktree each. One integrator, one
adversarial reviewer, and, when asked, one architecture sweep. `launchers/claude.md` says how
to spawn them in Claude Code; in Codex use its own delegation with the same prompts.

Inputs to settle before anything is spawned: the base branch (`main` unless said), the run tag,
the items in Pete's words, and whether Pete is at the Mac (the templates assume he may be). The
tag is `todoN`, one more than the highest in the base's commit subjects, since a finished run's
branches are pruned: `git log --format=%s <base> | grep -o 'todo[0-9]*' | sort -V | tail -1`.

## 1. Plan, and show it

Group the items by the files they touch so agents do not collide. Read the items, grep for the
files each names, and check for a shared file between groups (`Settings.swift` and
`DebugPanel.swift` are shared by any item that adds a tweak; `AGENTS.md` and `README.md` by
Read the full skill on GitHub

Details

Skill name
vignette-todo-run
Path
skills/vignette-todo-run/SKILL.md
License
MIT
Repo updated
26 October 2026

FAQ

What does the Vignette Todo Run skill do?

Run a batch of Vignette TODO items as a multi-agent worktree run. Use when Pete asks to "run the TODOs", "run items N to M", "do a todo run", or hands over queued items from docs/TODOS.md in the Vignette repo. The orchestrator plans, briefs, and reviews; delegated coding agents do every code change and every verification, each in its own worktree with its own scratch settings; an integrator merges, a reviewer attacks the merge, and the branch is handed to Pete unmerged. Not for a single small fix in the checkout, and not for a repo other than Vignette.

How do I install the Vignette Todo Run skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill vignette-todo-run. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Vignette Todo Run popular?

It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.

Related skills

Catch Up

49

petekp/claude-code-setup

Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.

AI, LLMs & Agents10

Clean Copy

49

petekp/claude-code-setup

Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.

Writing & Content10

Code Comments

49

petekp/claude-code-setup

Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.

Software Development10

Dependency Analyzer

49

lis186/SourceAtlas

Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.

Productivity & Notes

Release Notes

49

petekp/claude-code-setup

Write release notes or a changelog entry that tell existing users what they will notice after updating, with the technical detail after it. Use when publishing a release, writing a changelog, or editing release notes.

Productivity & Notes10

Genome Query

43

glebis/genome-toolkit

Query Obsidian vault frontmatter with SQL-like syntax. Filter, sort, group, and aggregate notes by any frontmatter field. Replaces Dataview for CLI use. Triggers on: /genome-query, "query vault", "find notes", "list genes", "show protocols", "vault stats", "vault schema", "filter by".

Productivity & Notes

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.