Documentation artifact package
Skill jukrap/ai-agent-playbook/skills/project/documentation-artifact-package
Use when bundling docs, runbooks, reports, evidence, or handoffs into a documentation package.From its SKILL.md
npx -y skills add jukrap/ai-agent-playbook --skill documentation-artifact-packageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 207 tokens by cl100k_base, as published. Nobody here has run it
Documentation Artifact Package
Package reviewed documentation into a bounded reader-facing deliverable with source evidence and maintenance rules.
Workflow
- Identify the package type: stakeholder brief, developer handoff, knowledge base entry, runbook bundle, report pack, or archive.
- Define audience, purpose, owner, freshness date, update cadence, sensitivity boundary, and archive path.
- Separate durable docs, generated runtime evidence, raw notes, and local-only sources before assembling the package.
- Build a manifest of included artifacts, source evidence, caveats, decisions, open questions, and verification.
- Keep generated reports under runtime until reviewed and explicitly promoted.
- Add maintenance and stale-content rules so the package does not become hidden active policy.
Reference
Read references/artifact-package-manifest.md when defining package contents, evidence, caveats, and boundaries.
Read references/reader-handoff-and-maintenance.md when tailoring the package to a reader and assigning update or archive responsibilities.
What ships with it: 2 files
3.4 KB alongside SKILL.md