Seeding Playbooks

Coordinate bulk creation or enrichment of playbook agent notes across many orgs using parallel sub-agents.

What a playbook is

A playbook is a per-org skill for fetching that org's releases. Same mental model as the global skills in this corpus (parsing-changelogs, managing-sources, etc.) — but scoped to one organization. It tells a future agent (managed or local) how to pull updates from this org: extraction quirks, naming conventions, which sources are canonical, what to skip, where rollups hide.

Global skills teach general patterns; per-source parseInstructions teach source-specific hints; the playbook is the org-level layer between them. When agents fetch any of an org's sources, they should load that org's playbook into context alongside the global skills — the playbook overrides general rules with specific org behavior.

Write notes as instructions to an LLM, not as human documentation. Imperative voice ("Set version=null", "Parse <h2> as version boundaries"), concrete examples from real data, and only observations that change future fetch behavior.

A local-Claude-Code skill. The dispatch pattern below uses Claude Code's Agent tool, run locally — there is no remote managed-agent fleet in this repo to deploy it to. Onboarding and fetch dispatch for orgs/sources goes through the local-ingest skill or releases admin org|source create instead.

When to Use

• Batch-populating playbooks for orgs that have sources but no notes
• Re-running the verified workflow on existing playbooks to enrich them with data-grounded observations
• After a wave of new orgs are onboarded and need initial playbook scaffolding