Guides

Use this catalogue to add repeatable, supervised ways of working to your agent. Start with the outcome you need; the linked pack guides explain what to install, what to ask for, what the agent produces, and where a human decides.

Follow a path

A path is an ordered set of guides that ends at a handoff, not at a document. Each names what you must already have and roughly what it costs. Start at the front door and work down; the two tables after this one are alternate ways in once you know the shape.

P1 · Adopt the catalogue — ~1 hour

Prerequisite: none. For: anyone, first session.

1. Choose an install route
2. Install the whole lifecycle
3. Adapt an existing repo — or start a new project
4. Orient at session start

First value: workspace status answers what to work on next. Ends at: a repository whose queues you can read.

P2 · Shape what to build — ~3 hours

Prerequisite: P1. For: product manager, product engineer, strategist.

The light path is the default: frame an intent, test its riskiest assumption, break it down. Reach past it to the robust path — situation, opportunities, options, bet, capability map — only when the problem itself is unclear or the bet is large enough to need a recorded rationale. The intent tree explains the choice.

1. Gather evidence when the answer is not already known
2. Shape a feature intent — frame-intent
3. De-risk it and break it down — de-risk-intent, then decompose-intent
4. Shape the architecture concept against it
5. Hand the intent to the build loop

On the robust path, frame the situation first, then identify opportunities, generate options, and place a bet before step 4.

First value: one written intent naming an outcome and the bet behind it. Ends at: Core intake, which selects the route from the content — a spec, a delivery brief, or a minimum repository intent.

P3 · Build it — ~2 hours

Prerequisite: P2, or an existing spec. For: engineer, agent.

1. Orient at session start
2. Plan and execute non-trivial work
3. Review someone else’s PR
4. Close and disposition the work

First value: a spec and plan you approved before any code was written. Ends at: a merged change, and the decision to merge is yours.

P4 · Decide together — ~1.5 hours

Prerequisite: P1. For: tech lead, architect.

1. The governance index — which of RFC, ADR, or spec you need
2. Propose an RFC
3. Record an ADR

P4 draws on P2’s artifacts: an intent, a decision brief, a research survey, or an architecture concept is what an RFC or ADR is written from.

First value: a circulated proposal with its alternatives written down. Ends at: an accepted decision that outlives the people who made it.

P5 · Ship and report — ~2 hours

Prerequisite: P3. For: delivery lead, SRE.

1. The release loop
2. Run a release
3. Project slices out to a tracker — or intake from one
4. Measure flow and DORA metrics

First value: a deployed artifact validated in an environment like production. Ends at: a human ratifying the production ship.

P6 · Extend the catalogue — ~3 hours

Prerequisite: P1 and P3. For: AI enablement, catalogue owner.

1. Why catalogue curation
2. Your first skill
3. Build an org stack pack
4. Create a catalogue

First value: one skill of your own that your agent can run. Ends at: a catalogue your organisation owns.

Choose what you want to achieve

I need to…	Start with	Continue with
Decide what to build	product-strategy for strategic choices	desk-research for evidence, then product-engineering to shape a build-ready bet
Design the product and system	experience-design for journeys and surfaces	architect, contracts, and frontend-engineering for the system, interfaces, and implementation
Build and review software	core to route work into a durable artifact and supervised loop	governance-extras for durable decisions and monorepo-extras for package scaffolding
Provision and release safely	iac-terraform for reviewable infrastructure plans	release-engineering for deployed validation and the human production gate, supervised by core
Work with team systems and evidence	atlassian, github, linear, or figma	converters for source material and credential-brokers for credential-safe access
Document what ships	product-documentation	converters and the guide for the pack whose behavior you are documenting
Build and govern a catalogue	catalogue-curation	governance-extras, product-documentation, and the catalogue authoring standards

The core build loop is the catalogue’s flagship and its strongest standalone product: a spec-driven implementation loop with mechanical gates, cold independent review, stasis detection, and a human merge decision. Start there when you want the most rigorous coding-agent workflow; the rest of the catalogue applies the same supervised-work principle to other jobs.

Choose by role

• Product manager or strategist: decide what to build, gather evidence, then shape the bet.
• Platform, infrastructure, or SRE team: design the system, author its contracts, plan infrastructure, and validate the release.
• Software engineer: start with the core work loop, then add the design, contract, frontend, infrastructure, or governance pack your change needs.
• Designer or UX practitioner: start with experience-design and connect the result to product-engineering or frontend-engineering.
• Researcher or analyst: start with desk-research and add the relevant team-system or conversion pack.
• AI enablement or catalogue owner: start with the pack catalogue, then use catalogue-curation to evolve your organization-owned collection.

Shared and pack-specific guidance

Pack directories contain task guidance for that pack. _shared/ contains cross-catalogue guidance that applies regardless of which packs you install:

• Start, remember, inspect, or refresh repository work, then use the routing and lifecycle reference when you need the exact boundary.

• Get from zero to the three-loop operating model.

• Understand packs, profiles, adapters, composition, and catalogue ownership.

• Choose an install route and check adapter support.

• Install a curated profile, preview a change, or upgrade safely.

• Create your own catalogue and apply its portable authoring standards.

Claude users can add this catalogue as a plugin marketplace and install user-scope packs directly. Repo-scoped packs such as core still install with agentbundle so their workflow belongs to the project and team.

The public documentation site generates the complete pack and guide navigation from this tree. Browse the complete generated pack reference; this page stays a route map rather than duplicating that inventory by hand.

Writing a guide

Use the author-product-docs workflow. It selects the right page contract and destination; the catalogue authoring standards define the portable rules.