dynamo-submission
Skill1 starsChanged 35 days agoNo licenceView on GitHub
Write the Submission Form Pack for a finished Dynamo task, as a file, answering the platform form's four numbered proposal questions plus the artifact-type and task-objective checkboxes. Use this after a valid failure when the deliverables are due, when the user asks for the submission form, the form pack, the proposal, the artifact type or the task objective, when a proposal came back REVISE from the automated reviewer, or when the taxonomy fields or the pass bar changed and the pack needs regenerating. It answers each question in two or three specific sentences rather than a long essay, because the two criteria that have failed real reviews fail on vagueness, not on length.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-reconcileSkill
- change-scoperSkill
- codebase-cartographerSkill
- commit-conventionsSkill
- debuggerSkill
- dynamo-bootstrapSkill
- dynamo-bootstrapSkill
- dynamo-designSkill
- dynamo-designSkill
- dynamo-probeSkill
- dynamo-probeSkill
- dynamo-rebuildSkill
- dynamo-rebuildSkill
- dynamo-repairSkill
- dynamo-repairSkill
- dynamo-reworkSkill
- dynamo-submissionSkill
- dynamo-verifySkill
- dynamo-verifySkill
- feature-grafterSkill
- feature-integratorSkill
- grillingSkill
- intake-triageSkill
- phase-executorSkill
- pr-descriptionSkill
- product-architectSkill
- product-guideSkill
- product-state-initSkill
- quality-gateSkill
- refactor-stewardSkill
- regression-guardSkill
- root-cause-investigatorSkill
- safety-net-builderSkill
- surgical-fixerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.