hivemind-plugin
Copilot instructions51 starsChanged 7 months agoMITView on GitHub
- Use the get-shit-done skill when the user asks for GSD or uses a gsd-* command. - Treat /gsd-... or gsd-... as command invocations and load the matching file from .github/skills/gsd-*. - When a command says to spawn a subagent, prefer a matching custom agent from .github/agents. - Do not apply GSD workflows unless the user explicitly asks for them. - After completing any gsd-* command (or any deliverable it triggers: feature, bug fix, tests, docs, etc.), ALWAYS: (1) offer…
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,349 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository17 other files it gives its agents.
- .github/get-shit-done/templates/copilot-instructions.mdCopilot instructions
- context-first-gatekeepingSkill
- debug-orchestrationSkill
- delegation-intelligenceSkill
- hivefiver-bilingual-tutorSkill
- hivefiver-domain-pack-routerSkill
- hivefiver-gsd-compatSkill
- hivefiver-mcp-research-loopSkill
- hivefiver-persona-routingSkill
- hivefiver-ralph-taskingSkill
- hivefiver-skill-auditorSkill
- hivefiver-spec-distillationSkill
- hivemind-architect-strategistSkill
- hivemind-governanceSkill
- parallel-debugging-hivemindSkill
- sequential-orchestrationSkill
- systematic-debugging-hivemindSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 4
Use the get-shit-done skill when the user asks for GSD or uses a gsd-* command.
- Very specific: line 5
Treat /gsd-... or gsd-... as command invocations and load the matching file from .github/skills/gsd-*.
- Very specific: line 6
When a command says to spawn a subagent, prefer a matching custom agent from .github/agents.
- Distinctive: line 7
Do not apply GSD workflows unless the user explicitly asks for them.
- Very specific: line 8
After completing any gsd-* command (or any deliverable it triggers: feature, bug fix, tests, docs, etc.), ALWAYS: (1) offer the user the …
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
<!-- GSD Configuration — managed by get-shit-done installer -->Instructions for GSD
- Use the get-shit-done skill when the user asks for GSD or uses a
gsd-*command. - Treat
/gsd-...orgsd-...as command invocations and load the matching file from.github/skills/gsd-*. - When a command says to spawn a subagent, prefer a matching custom agent from
.github/agents. - Do not apply GSD workflows unless the user explicitly asks for them.
- After completing any
gsd-*command (or any deliverable it triggers: feature, bug fix, tests, docs, etc.), ALWAYS: (1) offer the user the next step by prompting viaask_user; repeat this feedback loop until the user explicitly indicates they are done.
<!-- /GSD Configuration -->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.