— The Claude Playbook · OutSystems

Don't browse. Plan.

Five minutes in. A real adoption plan out. Three questions about where you are in the 5 layers of your Personal OS, and you walk away with a Phase 1–4 ramp aligned to the training's 30-day plan — starting exactly where you are.

Step 1 of 7 — your role

What's your role and which team do you lead?

This helps us frame the plan around your specific position and responsibilities.

What you get from the diagnostic

Four phases. Five layers. A ramp that mirrors the training's 30-day plan and starts where you are right now.

Phase 1

Context

Finish your CLAUDE.md. Verify Claude reads it every session.

Phase 2

Connectors

Wire one connector — Gmail or Slack — so Claude reads your real data.

Phase 3

Skills · Agents

Save the first prompt you reach for every week. Schedule the one that should run without you.

Phase 4

Memory

A team-context Project that compounds — answers “where are we with X?” without re-explaining.

The Context layer

Every playbook, every prompt, every agent rests on your CLAUDE.md. This is Layer 1.

CLAUDE.md is a plain-text file Claude reads at the start of every Project session. Your role. Your V2MOM. Your manager's priorities. Your working style. Without it, you re-explain your context every time. With it, every playbook in this library becomes ten times more specific.

The generator on the next page takes 20 minutes and uses the OutSystems Leadership MCP to pull your orgchart and V2MOM automatically. You paste the result into Claude. Done.

CLAUDE.md — five sections

## WHO I AM
[Name], VP of Engineering at OutSystems Platform Group.
Manager: [Manager]. Team: 8 direct reports.

## MY V2MOM
Vision: A platform team other teams trust completely.
Methods, obstacles, measures: …

## MY MANAGER
Top 3 priorities and how my work connects.

## MY TEAM
Direct reports + cross-functional partners.

## HOW I WORK
Lead with the conclusion. Bullets over prose. Push back if I bury the lead.