start-work
Skill0 starsChanged 18 days agoMITView on GitHub
Use when someone wants to work on something in claude-session-restore ("let's do #12", "pick up the restore bug", "make it work on macOS", "fix Y"), before any code or docs change. Finds or creates the issue, reads the code and the APIs it touches, decides whether it needs a plan, writes the plan and reviews it with review-plan until it is approved, then starts the branch from origin/main with the plan as its first commit.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- morochena/skillstheir own version, first seen Nov 15, 2026
- timamikh/very-ai-product-loopstheir own version, first seen Nov 8, 2026
- elpiarthera/vantage-startertheir own version, first seen Nov 1, 2026
- spalladino/claude-skillstheir own version, first seen Nov 1, 2026
- Spaghetticoders/developer-skillstheir own version, first seen Nov 1, 2026
- ambroselittle/agent-skillstheir own version, first seen Oct 30, 2026
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- liferay/liferay-portal★ 2.3ksame name
- zephyrwang6/myskill★ 339same name
- notum-cz/strapi-next-monorepo-starter★ 316same name
- dannys-code-corner/incan★ 73same name
- SpaceZephyr/allSkills★ 14same name
- timamikh/very-ai-product-loops★ 8same name
- vantageos-agency/vantage-peers★ 4same name
- UtsavBalar1231/oh-my-claudeagent★ 3same name
- dmzoneill/skills★ 2same name
- wjgoarxiv/litopencode★ 2same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- finish-workSkill
- review-codeSkill
- review-planSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Every change reaches main through a PR (AGENTS.md, How a change lands).
- Distinctive: line 22
Read before planning,: never from memory:
- Very specific: line 26
every hooks API it will call, in plugin/.claude-plugin/types/claude-code/index.d.ts (load the mod once with claude --plugin-dir plugin if …
- Distinctive: line 58
Write code before the plan is approved, or on main.
- Distinctive: line 60
Keep a plan only in the session, an issue comment or a PR body: the plan is a file.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start a change
Every change reaches main through a PR (AGENTS.md, How a change lands). This skill gets a change to where code can
start: an issue, a plan when it needs one, the plan approved, and a branch. finish-work closes it.
Steps
- Find the issue.
- A number:
gh issue view <n> --comments, read in full. Closed? Ask before going on. - A sentence: look for an open one first,
gh issue list --search "<words>". None fits: write the body to.local/issue-body.md(what and why, no tool attribution) and rungh issue create --title "<title>" --body-file .local/issue-body.md. A typo or comment fix needs no issue.
- A number:
- Read before planning, never from memory:
- the code of every file the change touches, and its tests:
plugin/hooks/register.tsxfor the hooks and the drawing,plugin/hooks/lib.tsfor the logic,plugin/types/index.d.tsfor the record; docs/design.md, the READMEs andREVIEW.md;- every hooks API it will call, in
plugin/.claude-plugin/types/claude-code/index.d.ts(load the mod once withclaude --plugin-dir pluginif it is not there), and anything outside Claude Code (Windows Terminal, PowerShell, a process API) through Context7 or the vendor's docs (AGENTS.md, Look up APIs before coding against them).
- the code of every file the change touches, and its tests:
- Decide whether it needs a plan, by the rule in
docs/plans/README.md. Unsure: ask, and recommend one for anything that touches a one-way door, a command line the plugin builds, or the record's fields. - Write the plan at
docs/plans/<today>-<slug>.mdfrom the template indocs/plans/README.md, withissueset. Fill every section; "none" is an answer, a blank is not. A one-way door it changes is named under Compatibility. - Review it with
review-planuntil its verdict isapproved. - Get it approved by the maintainer: give the plan's path and the review's verdict, and ask. No code before the
yes. Then set
status: approved,approved_by(their GitHub login) andapproved_atin the frontmatter.- Someone outside the maintainers: do steps 7 and 8 first, push the branch to your fork, and open a draft PR titled
Plan: <title>that links the issue. The maintainer approves it there, and the code lands on the same branch.
- Someone outside the maintainers: do steps 7 and 8 first, push the branch to your fork, and open a draft PR titled
- Start the branch
<n>-<slug>fromorigin/main, aftergit fetch origin. Ask where, as one question with a recommendation:- a new branch here,
git switch -c <n>-<slug> origin/main, when the checkout is clean and nothing else runs in it; - a new worktree,
git worktree add .claude/worktrees/<n>-<slug> -b <n>-<slug> origin/main, when other work is in flight; then move the session there, and runnpm ciin it. post-checkout:lines name AI setup files that changed on the way: re-read the ones you already read, this skill among them.
- a new branch here,
- Commit the plan as the branch's first commit: subject
Plan: <title>, bodyRefs #<n>. - Ask how to build: directly in this session, or in forked agents for independent steps, each brief naming the plan's path, its step and the files it may touch. This session stays the plan's anchor either way.
Done means
- The issue exists, unless the change is a typo or comment fix.
- A change that needs a plan has one, reviewed, approved, and committed first on its branch.
- The branch exists from
origin/main, and how to build is chosen.
Never
- Write code before the plan is approved, or on
main. - Plan from memory of the code or of an API instead of reading it.
- Keep a plan only in the session, an issue comment or a PR body: the plan is a file.
- Post an issue or a comment with tool attribution in it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

