hivefiver-ralph-tasking
Skill51 starsChanged 7 months agoMITView on GitHub
Convert HiveFiver plans and TODO state into Ralph PRD JSON and beads graphs with enriched related entities and anti-pattern validation.
In this repository17 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- .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-skill-auditorSkill
- hivefiver-spec-distillationSkill
- hivemind-architect-strategistSkill
- hivemind-governanceSkill
- parallel-debugging-hivemindSkill
- sequential-orchestrationSkill
- systematic-debugging-hivemindSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when output must be executable by Ralph tooling.
≈ “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
HiveFiver Ralph Tasking
Use this skill when output must be executable by Ralph tooling.
Workflow
- Build PRD user stories from distilled spec.
- Merge TODO/task nodes into story traceability map.
- Export flat-root
tasks/prd.json. - Build beads dependency mapping.
- Validate anti-patterns and dependency integrity.
Loop Integrations
ralph-tui-prdralph-tui-create-jsonralph-tui-create-beads- optional iterative
ralph-loopvalidation
Validation Rules
- root must include
name+userStories - reject wrapper roots (
prd) - reject legacy root key (
tasks) - require deterministic user story IDs/order
- preserve related entity links:
workflow_idrequirement_node_idmcp_provider_idexport_id
References
references/prd-json-rules.md
Template
templates/prd-json-flat.md
Scripts
scripts/validate-prd-json.mjsscripts/todo-to-prd-json.mjs
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.

