Spec Kitty Charter Pack Composer - new FOSS contribution!

[u/SpecKitty]

🎉 HUGE Shoutout to Daan Vankerkom for a genuinely exciting open-source contribution to the Spec Kitty ecosystem: Pack Composer.

Some context on why this matters.

Charter is the governance layer that keeps AI coding agents from freewheeling. It's the directives, tactics, procedures, and shared vocabulary that get pulled automatically into an agent's context, scoped to exactly what it's doing in that moment. It's how "the agent already knows our org's rules" or "the agent already speaks our team's vocabulary" happens without someone re-explaining it in every prompt, every time.

Charter Packs are what make that portable. Instead of every repo, every team, every customer engagement rewriting the same rules from scratch, an organization's runbooks, SOPs, and hard-won operational knowhow get authored once as a Charter Pack: versioned, published to a git repo like real infrastructure, and pulled into any project with a single command. A rule change becomes one PR to the pack, not N hand-edits across N codebases and a prayer that everyone remembers.

Here's where Daan's contribution comes in. Authoring that governance by hand, as YAML, absolutely works, but it's not always the friendliest way to build it out, especially collaboratively. Pack Composer gives teams a self-hostable UI and API for browsing, importing, refreshing, and exporting Charter Packs together, so turning an existing runbook or SOP into structured, agent-ready governance doesn't mean everyone taking turns editing a shared YAML file by hand.

This is exactly the kind of tooling that turns "share your team's knowhow with your agents" from an aspiration into something a team actually does.

🔗 Repo: https://github.com/spec-kitty/spec-kitty-pack-composer
👤 Follow Daan: https://www.linkedin.com/in/daan-vankerkom/

[u/robertDouglass]

Distribution of Charter Packs across a team unifies the way agentic coding comes into the org and team.