developer-handoff
Skill0 starsChanged 2 months agoMITView on GitHub
Package accepted product work for Development Team continuation.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- github/replicatheir own version, first seen Nov 1, 2026
- BojanKocijan/design-forgetheir own version, first seen Oct 19, 2026
- BojanKocijan/bk-charterlinetheir own version, first seen Oct 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- github/replica★ 230same name
- BojanKocijan/bk-charterline★ 4same name
- BojanKocijan/design-forge★ 4same 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- react-fsd-pocSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- project-analysisSkill
- user-storySkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
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 10
Use when the task matches: developer-handoff, DEV_READY, handoff.
- Distinctive: line 25
Document FSD structure, changed files, and run setup.
- Distinctive: line 27
Do not grant production release permission.
- Distinctive: line 41
Keep Product validation and engineering verification distinct.
- Distinctive: line 42
Do not claim completion without evidence.
- Distinctive: line 46
Do not rewrite the app during handoff.
- Distinctive: line 47
Do not omit mocks as if they were real integrations.
- Very specific: line 48
Do not treat DEV_READY as production authorization.
“Common” is measured: kept by at least 6 in 10 of the 3 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
developer-handoff
When to use
Use when the task matches: developer-handoff, DEV_READY, handoff.
Purpose
Give developers intent, structure, limitations, and next production steps.
Inputs
- Validated definition and UX
- POC and verification evidence
- Architecture decision
Process
- Summarize product intent in Product language.
- Document FSD structure, changed files, and run setup.
- List known limitations and owners for deferred work.
- Do not grant production release permission.
Outputs
- Product intent
- Implemented features
- FSD structure
- Changed files
- Known limitations
- Production next steps
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not rewrite the app during handoff.
- Do not omit mocks as if they were real integrations.
- Do not treat DEV_READY as production authorization.
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.