decision-package
Skill2 starsChanged 17 days agoGPL-3.0View on GitHub
Produce the Decision Package — the paid keystone deliverable of a semantic/data consulting engagement's Proof of Value. Use to write the recommendation, the in/out scope, the sequenced (pilot → scale) roadmap, the buy/build/defer decisions, and the ready-to-contract execution brief that hands off to the build/architecture tier. The unit of value is decision-readiness; the artefact sits ABOVE architecture (it justifies and scopes the build before a repo exists). Triggers — "produce a decision package", "write the recommendation / scope / roadmap / buy-build-defer", "decision-readiness deliverable", "execution brief for the build", "scope this engagement", "Semantic Readiness & Direction / Decision Foundation deliverable". This skill PRODUCES the artefact; it does NOT coach the engagement design or hold the free→paid line (that is semantic-consulting-coach — "produce" vs "coach"). Not for free presale, not for delivery artefacts (an ontology, a mapping), not for code architecture.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/vault-setup/assets/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectureSkill
- bdd-gherkinSkill
- ci-cd-deliverySkill
- clarity-gateSkill
- conceptual-modellingSkill
- cosmic-pythonSkill
- epic-deliverySkill
- epic-planningSkill
- estimationSkill
- executive-communicationSkill
- explanatory-writingSkill
- formal-reasoningSkill
- guardrailsSkill
- infrastructure-operationsSkill
- infrastructure-securitySkill
- linkml-engineeringSkill
- meaningfy-code-reviewSkill
- meaningfy-git-workflowSkill
- meaningfy-releaseSkill
- meaningfy-voiceSkill
- modelling-conventionsSkill
- project-setupSkill
- proposal-writingSkill
- rulebookSkill
- rule-learnerSkill
- rule-stewardSkill
- sales-accountsSkill
- sales-conversationsSkill
- sales-operationsSkill
- sales-pipeline-custodySkill
- sales-qualificationSkill
- semantic-consulting-coachSkill
- service-reliabilitySkill
- skillery-feedbackSkill
- spec-stewardshipSkill
- stack-operationsSkill
- technical-writingSkill
- vault-captureSkill
- vault-conventionsSkill
- vault-dailySkill
- vault-planningSkill
- vault-projectSkill
- vault-promoteSkill
- vault-resumeSkill
- vault-setupSkill
- vault-tidySkill
- writing-antipatternsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — 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.