okhp3-handoff-packaging
Skill3 starsChanged 2 months agoMITView on GitHub
Assemble all validated BP-SKILL process artifacts into a publication-ready bundle with a manifest, approvals record, and completeness check. Use this skill when the user is ready to publish or hand off a complete process documentation set; when they ask to package the process docs, create a handoff bundle, publish the process artifacts, or generate a release package. Requires a passing validation report (Band A or B) before bundling. Produces a MANIFEST.yaml, APPROVALS.yaml, and a ZIP-ready directory structure.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decision-recordsSkill
- catalog-integritySkill
- frontend-designSkill
- okhp3-artifact-validationSkill
- okhp3-as-is-process-captureSkill
- okhp3-brand-style-registrySkill
- okhp3-capture-intakeSkill
- okhp3-chatgpt-project-migrationSkill
- okhp3-custom-gpt-builderSkill
- okhp3-custom-gpt-readinessSkill
- okhp3-decision-model-authoringSkill
- okhp3-elicitation-interviewsSkill
- okhp3-equilibrium-reviewSkill
- okhp3-evidence-standardSkill
- okhp3-future-state-strategySkill
- okhp3-gpt-skill-conversion-planSkill
- okhp3-graduation-gateSkill
- okhp3-notion-capture-routerSkill
- okhp3-outcome-modeling-coreSkill
- okhp3-overkill-hill-brandSkill
- okhp3-process-captureSkill
- okhp3-process-gap-analysisSkill
- okhp3-process-intake-and-scopeSkill
- okhp3-project-promotionSkill
- okhp3-replit-build-in-publicSkill
- okhp3-replit-canvas-boardSkill
- okhp3-replit-design-pipelineSkill
- okhp3-replit-free-mode-autonomySkill
- okhp3-replit-github-syncSkill
- okhp3-replit-multi-artifactSkill
- okhp3-replit-repl-janitorSkill
- okhp3-replit-repository-janitorSkill
- okhp3-replit-task-executorSkill
- okhp3-repository-janitorSkill
- okhp3-repository-organizerSkill
- okhp3-session-handoffSkill
- okhp3-skill-catalogerSkill
- okhp3-skill-discoverySkill
- okhp3-skill-foundrySkill
- okhp3-source-backed-researchSkill
- okhp3-thread-context-extractionSkill
- okhp3-thread-extract-chatgptSkill
- okhp3-thread-extract-claudeSkill
- okhp3-triage-and-fileSkill
- okhp3-vite-github-pagesSkill
- production-build-verificationSkill
- published-keyboard-recovery-checkSkill
- publish-health-checkSkill
- publishing-trigger-checkSkill
- static-route-validationSkill
- validation-smokeSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- okhp3-skill-promotionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Only a subset of artifacts is ready — wait until all required artifacts pass validation
- Very specific: line 134
Read validation-report.yaml — abort if ready_for_publication: false
- Distinctive: line 136
Check required artifacts are present
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
okhp3-handoff-packaging
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Purpose
Assemble all validated process artifacts into a publication-ready bundle. The bundle includes a machine-readable manifest, an approvals record for ISO 9001 §7.5.3 document control, and a structured directory suitable for archiving, sharing, or committing to a repository.
When to use this skill
validation-report.yamlexists withready_for_publication: true(Band A or B)- User is ready to hand off the process documentation to stakeholders or a document management system
- User wants to create a release package for audit, certification, or onboarding
When NOT to use this skill
- Validation report is missing or
ready_for_publication: false— runprocess-validation-and-quality-scoringfirst - Only a subset of artifacts is ready — wait until all required artifacts pass validation
Required Bundle Contents
The following artifacts must be present and validated before bundling:
| Artifact | Source skill | Required |
pir.yaml | process-intake-and-scope | yes |
pns.yaml | process-narrative-authoring | yes |
bpmn-beta.mmd | visual-process-modeling | yes |
sop.md | sop-and-work-instruction-generation | yes |
validation-report.yaml | process-validation-and-quality-scoring | yes |
stakeholder-register.yaml | stakeholder-and-role-mapping | recommended |
raci.md | raci-and-governance-matrix-generation | recommended |
sipoc.md | sipoc-generation | recommended |
decision-model.yaml | decision-model-authoring | if ≥3 gateways |
work-instructions.md | sop-and-work-instruction-generation | recommended |
gap-analysis.yaml | process-gap-and-exception-analysis | if redesign |
measures-register.yaml | process-measures-and-controls-definition | if governance extended |
Bundle Directory Structure
process-artifacts/<process-id>/
├── MANIFEST.yaml
├── APPROVALS.yaml
├── pir.yaml
├── pns.yaml
├── pns.md
├── bpmn-beta.mmd
├── sop.md
├── work-instructions.md (optional)
├── stakeholder-register.yaml (recommended)
├── raci.md (recommended)
├── sipoc.md (recommended)
├── validation-report.yaml
├── decision-model.yaml (if ≥3 gateways)
├── gap-analysis.yaml (if redesign)
└── measures-register.yaml (if governance extended)MANIFEST.yaml Schema
manifest_version: "0.1"process_id— from PIRprocess_name— from PNSbundle_date— ISO 8601 datebundle_version—"v1.0"for initial releasequality_band— from validation reportcomposite_score— from validation reportartifacts[]— each withfilename,source_skill,status(present|missing|optional),sha256missing_required[]— artifacts that are required but absent (must be empty for release)missing_recommended[]— artifacts that are recommended but absent
APPROVALS.yaml Schema
For ISO 9001 §7.5.3 document control:
process_id,process_name,bundle_versionapprovals[]— each withrole,approval_date,status(pending|approved|rejected),commentseffective_date— date the bundle becomes activereview_date— scheduled review datedistribution[]— list of roles who should receive this bundle
Bundle Assembly Workflow
scripts/build-publication-bundle.mjs executes:
- Read
validation-report.yaml— abort ifready_for_publication: false - Inventory all artifacts in
process-artifacts/<process-id>/ - Check required artifacts are present
- Compute SHA256 hashes for all present files
- Generate
MANIFEST.yamlwith artifact inventory and quality metadata - Generate
APPROVALS.yamlstub withstatus: pendingfor each required approver - Report
missing_required[]— must be empty for release - Return
{ valid, errors, warnings, manifest_path, approvals_path }
Publication Gate
Release is blocked if:
validation-report.yamlis missing orready_for_publication: false- Any
missing_required[]artifact is present in MANIFEST - APPROVALS has any entry with
status: rejected
Handoff Instruction
Once the bundle is assembled and all approvals collected, archive the process-artifacts/<process-id>/ directory and distribute per APPROVALS.yaml distribution[]. Tag the version in your document management system.
References
Load on demand:
references/publication-checklist.md— required artifact list, bundle directory structure, MANIFEST schema, and ISO 9001 §7.5.3 document control requirements
Scripts
scripts/build-publication-bundle.mjs— assembles MANIFEST.yaml + APPROVALS.yaml stub and validates bundle completeness
Assets
assets/fixtures/handoff-manifest-example.yaml— canonical MANIFEST.yaml for a complete purchase-approval bundle
About
Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
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.

