Every pack.
Your way.
Start with the work you need to accomplish, then choose the packs that produce it. The complete 22-pack inventory stays below for readers who already know what they need.
What do you need to change?
Packs are the stable installation layer. These paths are curated views over that inventory, so the same pack can support more than one outcome.
Decide what to build
Turn strategy, evidence, and an uncertain idea into a bounded decision a delivery team can act on.
Design the product and system
Connect customer intent to the experience, architecture, interfaces, and implementable surface.
Build and review software
Move a brief or spec through implementation, mechanical gates, independent review, and a human merge decision.
Provision and release safely
Produce reviewable infrastructure and release evidence while stopping before apply and production.
Work with team systems and evidence
Bring trackers, documents, designs, and credentials into agent work with provenance and mutation boundaries intact.
Document what ships
Create, restructure, audit, and verify product documentation against canonical behavior.
Build and govern a catalogue
Curate organization-owned packs and profiles, validate their contracts, and distribute one governed system.
Or start with your role
- Product manager or strategistDecide what to build →
- Platform, infrastructure, or SREProvision and release safely →
- Software engineerBuild and review software →
- Designer or architectDesign the product and system →
- Researcher or analystWork with team systems and evidence →
- AI enablement or catalogue ownerBuild and govern a catalogue →
Browse every pack
Pack detail pages carry the exact scope, dependencies, install routes, shipped primitives, journey, and guides.
Core
repoThe agentic build loop that cannot self-certify.
Product Strategy
userAnswer the committed strategic questions upstream of every initiative.
Desk Research
userEvidence-grounded research — portable across every repo.
Product Engineering
userRaw idea → build-ready decision brief.
Experience Design
userThe design/UX seat for product teams.
Architect
userAssess what exists, decide what to do next, design, diagram, and review.
Contracts
userOpenAPI 3.1 and AsyncAPI — API-first design.
Frontend Engineering
userThe implementation layer for product web surfaces.
IaC (Terraform)
repoIntent → governed Terraform. Stops at plan.
Release Engineering
repoDeploy. Verify. Converge. Then ship.
Governance Extras
repoDecision trail — RFCs, ADRs, and conventions for long-lived repos.
Product Documentation
repoCreate, revise, audit, and verify catalogue-facing documentation.
Converters
userDocument conversion — between every format your team uses.
Monorepo Extras
repoPackage scaffolding for monorepos.
Catalogue Curation
repoGrow the catalogue — assimilate, survey, propose.
Credential Brokers
userCredential resolution — env → OS keyring → dotfile. Never cleartext.
Atlassian
userRun Jira and Confluence from a conversation
Figma
userRead and render Figma designs — files, frames, variables.
GitHub
userTurn a GitHub Milestone into a product brief
Linear
userTurn a Linear Issue into a product brief and keep it in sync
User Guide (Diátaxis) — Deprecated
repoSuperseded by product-documentation.
Agent Skill Engineering
userFrame, create, update, review, and optimize portable agent skills.