agentleFS
OKHP3OKHP3/skillz/.agents/skills/okhp3-handoff-packaging/SKILL.md

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.

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
  1. Distinctive:

    Only a subset of artifacts is ready — wait until all required artifacts pass validation

    line 56
  2. Very specific:

    Read validation-report.yaml — abort if ready_for_publication: false

    line 134
  3. Distinctive:

    Check required artifacts are present

    line 136

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.yaml exists with ready_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 — run process-validation-and-quality-scoring first
  • 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:

ArtifactSource skillRequired
pir.yamlprocess-intake-and-scopeyes
pns.yamlprocess-narrative-authoringyes
bpmn-beta.mmdvisual-process-modelingyes
sop.mdsop-and-work-instruction-generationyes
validation-report.yamlprocess-validation-and-quality-scoringyes
stakeholder-register.yamlstakeholder-and-role-mappingrecommended
raci.mdraci-and-governance-matrix-generationrecommended
sipoc.mdsipoc-generationrecommended
decision-model.yamldecision-model-authoringif ≥3 gateways
work-instructions.mdsop-and-work-instruction-generationrecommended
gap-analysis.yamlprocess-gap-and-exception-analysisif redesign
measures-register.yamlprocess-measures-and-controls-definitionif 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 PIR
  • process_name — from PNS
  • bundle_date — ISO 8601 date
  • bundle_version — "v1.0" for initial release
  • quality_band — from validation report
  • composite_score — from validation report
  • artifacts[] — each with filename, source_skill, status (present|missing|optional), sha256
  • missing_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_version
  • approvals[] — each with role, approval_date, status (pending|approved|rejected), comments
  • effective_date — date the bundle becomes active
  • review_date — scheduled review date
  • distribution[] — list of roles who should receive this bundle

Bundle Assembly Workflow

scripts/build-publication-bundle.mjs executes:

  1. Read validation-report.yaml — abort if ready_for_publication: false
  2. Inventory all artifacts in process-artifacts/<process-id>/
  3. Check required artifacts are present
  4. Compute SHA256 hashes for all present files
  5. Generate MANIFEST.yaml with artifact inventory and quality metadata
  6. Generate APPROVALS.yaml stub with status: pending for each required approver
  7. Report missing_required[] — must be empty for release
  8. Return { valid, errors, warnings, manifest_path, approvals_path }

Publication Gate

Release is blocked if:

  • validation-report.yaml is missing or ready_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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.