The 26 Packs at a glance
The full DOS Pack catalog organized by intent: Knowledge, Make, Sell, Build, and Operate.
A Pack is a capability bundle DOS invokes by name. Skill("Research", "extensive research on vertical SaaS for law firms") — one shape, 26 Packs, every one routed by the phrasing of your request.
Packs are curated and shipped by the DOS team. You do not build them yourself. If a capability you want does not exist in the catalog, file a Feature Request and it enters the queue.
The catalog is organized around the intent behind your request — not the tool that fulfills it. Five groups, 26 Packs.
The five intent groups
Knowledge (4)
Remember, retrieve, research. MemPalace, Telos, Research, ContextSearch.
Make (5)
Produce visual, written, branded artifacts. Media, WriteStory, CinematicLanding, DesignSystem, Brand.
Sell (5)
Win a customer or prepare for one. Sales, BDR, ChiefOfStaff, StartupInvestorDocs, SocialMedia.
Build (6)
Design, decide, ship code. Sentinel, FeatureDelivery, Agents, DreamTeam, Thinking, Compliance.
Operate (6)
Investigate, scrape, run ops. Utilities, Investigation, Security, Scraping, USMetrics, ContentAnalysis.
How invocation works
Every Pack uses the same shape. The Pack's SKILL.md reads your phrasing and dispatches to the right sub-workflow — you never pick a workflow by hand.
A request like "extensive research on vertical SaaS for law firms" lands in Research, selects the 12-agent extensive mode, verifies every URL, and returns a sourced brief. The same Pack handles "quick research on X" by routing to a single-agent quick mode instead. One entry point, different destinations, all determined by the words you used.
How the groups relate
Packs compose. Brand produces tokens that DesignSystem pins and CinematicLanding consumes. Research produces findings that Sales uses in a pre-call brief. MemPalace stores the outcome of every session and feeds it back into the next one through hooks. You rarely invoke one Pack in isolation — a single morning might pull ChiefOfStaff for the brief, Sales for the 2pm call prep, and BDR for the afternoon sequencing pass, all reading from the same MemPalace wing.
User overrides
Every Pack checks ~/.claude/DOS/USER/SKILLCUSTOMIZATIONS/{PackName}/ at the start of every run. Drop a PREFERENCES.md there and it loads before the default behavior — your tone on BDR sequences, your default depth on Research, your color palette on DesignSystem.
Missing a Pack?
If you find yourself wanting a capability that isn't in the catalog, file a Feature Request. Packs ship from the DOS team — Feature Requests are how the catalog grows.
Was this page helpful?