team-implement
Skill11 starsChanged 3 months agoMITView on GitHub
Use for executing implementation plans only on explicit request. Never infer from a ready plan.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rafaelgarrafiel/team_skillstheir own version, first seen Oct 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rafaelgarrafiel/team_skills★ 2same 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-team-skillSkill
- version-bumpSkill
- team-code-reviewSkill
- team-designSkill
- team-fixSkill
- team-migrateSkill
- team-planSkill
- team-prSkill
- team-questionSkill
- team-researchSkill
- team-security-reviewSkill
- teamSkill
- team-structureSkill
- team-updateSkill
- team-worktreeSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Before each dispatch or retry, read host dispatch and supply its resolved installed paths.
- Distinctive: line 11
Before artifact work, read artifact schema.
- Distinctive: line 12
Before each consuming step, read its linked shared rules from this installed skill directory.
- Distinctive: line 13
If a required read fails, stop that step with the exact path.
- Distinctive: line 14
Before finalizing prose you author, read the writing standards.
- Very specific: line 20
After the implementer returns DONE with its completion report, print "Next: run /team-code-review docs/plans/<id>/" in every mode.
- Distinctive: line 24
Read each reference completely when reaching it, in order.
- Distinctive: line 32
Read and apply: execution rules.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Team Implement
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading. Before finalizing prose you author, read the writing standards.
Core contracts
- Require
7-structure.md,8-plan.md, and a non-default-branch worktree. UseAskUserQuestiononly for missing standalone setup. - With
4-repos.md, multi-repo work requires worktrees; refuse in-place execution. - After the implementer returns
DONEwith its completion report, print "Next: run/team-code-review docs/plans/<id>/" in every mode. Never loadteam-code-revieworteam-pr.
Procedure references
Read each reference completely when reaching it, in order.
- Input
- Worktree Check
- Execution
Applied principles
Read and apply: execution rules.
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.