project-workflow
Skill11 starsChanged 3 months agoMITView on GitHub
Use when the user wants the full package on a repo, says run my project workflow, project check-in, or is overwhelmed opening an old or new folder. Runs the project onboarding checklist—explain-new-project, project-worth-my-time, and project-catch-up—in order or on demand.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- zhucl1006/skillstheir own version, first seen Nov 8, 2026
- waynesutton/builder-skillstheir own version, first seen Sep 28, 2026
- waynesutton/convexskillstheir own version, first seen Sep 28, 2026
- woduseh/RisuTokitheir own version, first seen Sep 27, 2026
- tikhomirovv/agents-knowledgetheir own version, first seen Aug 1, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- waynesutton/convexskills★ 405same name
- waynesutton/builder-skills★ 404same name
- tikhomirovv/agents-knowledge★ 2same name
- woduseh/RisuToki★ 2same name
- zhucl1006/skills★ 1same name
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 repository39 other files it gives its agents.
- agent-starter-packSkill
- agent-state-machineSkill
- local-ai-ollamaSkill
- apple-hig-command-paletteSkill
- apple-hig-empty-statesSkill
- apple-hig-feedback-statusSkill
- apple-hig-inspectorsSkill
- apple-hig-macos-window-layoutSkill
- apple-hig-search-filteringSkill
- apple-hig-settingsSkill
- apple-hig-sf-symbolsSkill
- apple-hig-sidebarsSkill
- apple-hig-toolbarsSkill
- apple-hig-typographySkill
- blog-post-publishingSkill
- social-post-kitSkill
- color-principlesSkill
- kika-design-systemSkill
- emergency-switch-appSkill
- product-hunt-polish-reviewSkill
- docs-updateSkill
- project-folder-cleanupSkill
- between-runs-auditSkill
- explain-new-projectSkill
- new-project-gateSkill
- old-project-auditSkill
- project-catch-upSkill
- project-worth-my-timeSkill
- butterfly-effectSkill
- spreadSkill
- tilSkill
- apple-app-intentsSkill
- macos-app-distribution-dmgSkill
- macos-clipboard-pasteboardSkill
- macos-global-shortcutsSkill
- macos-launch-at-loginSkill
- macos-menubar-swiftuiSkill
- macos-notificationsSkill
- macos-permissions-privacySkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Do not ask permission to save files—sub-skills always save.
- Distinctive: line 64
Use this checklist in the reply:
- Distinctive: line 75
If a step was skipped, say which and why.
- Distinctive: line 87
Do not inline the full text of the three skills—delegate to them.
- Distinctive: line 88
Do not run step 2 or 3 without project context (guide or quick explore per sub-skill).
- Distinctive: line 89
Do not add a fourth combined markdown file.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Project Workflow
One sentence
One ask → the right steps in order → three files on disk + a short chat summary.
Pick a path first (routing)
| User means… | Run |
| New folder / “what is this?” / guide only | Step 1 only → explain-new-project |
| “Worth my time?” / build vs buy | Step 2 → project-worth-my-time (read PROJECT_GUIDE.md first if it exists) |
| “I’m back after a while” / what’s new | Step 3 → project-catch-up |
| “Full workflow” / “check-in” / “do everything” | Steps 1 → 2 → 3 in order (unless skip rules below) |
| Unclear | Default: full (1 → 2 → 3) |
Same audience as the other skills: self-taught, plain language, Learn: for jargon.
What each step saves
| Step | Skill | File |
| 1 | explain-new-project | PROJECT_GUIDE.md |
| 2 | project-worth-my-time | PROJECT_VERDICT.md |
| 3 | project-catch-up | PROJECT_CATCH_UP.md |
Before you start
- Confirm project root (workspace folder or path user names).
- Glance at which
PROJECT_*.mdfiles already exist—report in chat, then follow skip rules or user request.
Execute
For each step you run: read that skill’s SKILL.md and follow it completely (do not shorten sub-skills).
- Step 2 uses Pieces MCP (
user-pieces:get_user_persona,ask_pieces_ltm) when available. - Step 3 uses web search when available.
Do not ask permission to save files—sub-skills always save.
Skip rules
| User says | Skip |
| guide only / step 1 only | 2 and 3 |
| no verdict / no worth | 2 |
| no catch-up | 3 |
| verdict only | 1 if PROJECT_GUIDE.md exists and is usable; else run 1 first |
| catch-up only | 1 if guide missing; else skip 1 and 2 |
| File already exists | Default |
| All three fresh enough | Ask once: Re-run all three or only what’s missing? If user said full workflow, re-run all (overwrite). |
| User said full workflow | Overwrite all three |
After you finish — chat reply (keep short)
Use this checklist in the reply:
Done:
- [ ] PROJECT_GUIDE.md — paste "In one minute" + "How you run it"
- [ ] PROJECT_VERDICT.md — paste Quick verdict + What I'd do (if ran step 2)
- [ ] PROJECT_CATCH_UP.md — paste Headline + Do these first (if ran step 3)
Files saved at: [project root path]If a step was skipped, say which and why.
Prerequisites
| Need | For |
| Write access to project root | All steps |
PiecesOS + the pieces MCP server configured in your agent | Step 2 (ok to skip Pieces if down—say so) |
| Web search | Step 3 |
What not to do
- Do not inline the full text of the three skills—delegate to them.
- Do not run step 2 or 3 without project context (guide or quick explore per sub-skill).
- Do not add a fourth combined markdown file.
Related
- The Pieces MCP server name can differ between agents (often
piecesoruser-pieces). Use whichever name your coding agent exposes; the flow is identical.
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.