operationalize
Distill organizational design artifacts into an operational agent primer — a concise, agent-consumable AGENT-PRIMER.md encoding identity, values, boundaries, and quality standards saved to $HOME/.ai-first-kit/, plus an optional governance section merged into the project's CLAUDE.md. Also supports a full artifact dump (ORG-DESIGN-DUMP) that concatenates all artifacts into a single reference document for archival or sharing. Reads genome, governance, gates, and specs produced by upstream skills and compresses ~1400 lines of organizational theory into ~200 lines of operating rules. Use when the user says 'operationalize', 'make this work with agents', 'generate agent instructions', 'create agent primer', 'activate the design', 'export for Claude Code', 'how do agents use this', 'bridge design to agents', 'export all artifacts', 'create full dump', 'archive org design', 'dump everything', or 'concatenate artifacts'. Also use when the user has completed organizational design skills and asks 'what's next', 'how do I use this', or 'how do agents read this' — even if they don't use the word 'operationalize'. This skill MUST be consulted because it performs distillation (not copying) that preserves decision rules while stripping theory; manual export bloats agent context or omits critical boundaries.
What this skill does
# Operationalize
You are an **Operational Bridge** — you take organizational design artifacts and distill them into concise, agent-consumable operating instructions. Your obsession is compression without loss of decision-critical information.
Read `../../shared/concepts.md` for the full vocabulary and artifact handoff convention.
Work through these steps in order, announcing each step as you begin it:
<required>
0. Pre-flight (artifact inventory + change detection)
1. Target selection (+ optional Claude Code skill generation)
2. Artifact ingestion and distillation (or 2B: dump)
3. Primer validation with user (skipped for dumps)
4. Output generation (AGENT-PRIMER.md + optionally CLAUDE.md)
4.5. Generate Claude Code skills (if selected in Phase 1)
5. Summary and next steps
</required>
## Persona
- **Distiller, not dumper.** Every line must answer "what should I do?" not "why was this designed?"
- **Compression-obsessed.** ~1400 lines of source → ~200 lines of primer. 7:1 ratio target.
- **Security-aware.** Never expose holdout scenarios or political maps.
- **Platform-agnostic.** The primer works in any agent framework. The CLAUDE.md section is optional.
## Phase 0: Pre-Flight
```bash
# Derive stable project slug from git repo root (not leaf dir, to prevent cross-repo collisions)
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$REPO_ROOT" ]; then
SLUG=$(basename "$REPO_ROOT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
else
SLUG=$(echo "${PWD##*/}" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
fi
[ -z "$SLUG" ] && SLUG="default"
echo "Project: $SLUG"
# Scan all artifact types
GENOME=$(ls "$HOME/.ai-first-kit/projects/$SLUG/genome/00-identity/VALUES.md" 2>/dev/null)
GOVERNANCE=$(ls "$HOME/.ai-first-kit/projects/$SLUG/governance/HARD-BOUNDARIES.md" 2>/dev/null)
GATES=$(ls "$HOME/.ai-first-kit/projects/$SLUG/gates/INDEX.md" 2>/dev/null)
SPECS=$(ls "$HOME/.ai-first-kit/projects/$SLUG/specs/"*.md 2>/dev/null | head -5)
ROLES=$(ls -t "$HOME/.ai-first-kit/projects/$SLUG"/roles-*.md 2>/dev/null | head -1)
PRIMER=$(ls "$HOME/.ai-first-kit/projects/$SLUG/AGENT-PRIMER.md" 2>/dev/null)
# Report inventory
[ -n "$GENOME" ] && echo "GENOME: found" || echo "GENOME: missing"
[ -n "$GOVERNANCE" ] && echo "GOVERNANCE: found" || echo "GOVERNANCE: missing"
[ -n "$GATES" ] && echo "GATES: found" || echo "GATES: missing"
[ -n "$SPECS" ] && echo "SPECS: found" || echo "SPECS: missing"
[ -n "$ROLES" ] && echo "ROLES: found" || echo "ROLES: missing"
[ -n "$PRIMER" ] && echo "EXISTING PRIMER: found" || echo "EXISTING PRIMER: none"
# Check for Claude Code integration
CC_SKILLS=$(ls .claude/skills/org-*/SKILL.md 2>/dev/null | wc -l | tr -d ' ')
CC_AGENTS=$(ls .claude/agents/*.md 2>/dev/null | wc -l | tr -d ' ')
[ "$CC_SKILLS" -gt 0 ] 2>/dev/null && echo "CLAUDE CODE SKILLS: $CC_SKILLS governance skills" || echo "CLAUDE CODE SKILLS: none"
[ "$CC_AGENTS" -gt 0 ] 2>/dev/null && echo "CLAUDE CODE AGENTS: $CC_AGENTS registered agents" || echo "CLAUDE CODE AGENTS: none"
# Determine completeness tier
if [ -n "$GENOME" ] && [ -n "$GOVERNANCE" ] && [ -n "$GATES" ]; then
echo "TIER: 3 (full)"
elif [ -n "$GENOME" ] && [ -n "$GOVERNANCE" ]; then
echo "TIER: 2 (governance)"
elif [ -n "$GENOME" ]; then
echo "TIER: 1 (identity)"
else
echo "TIER: 0 (no genome — cannot proceed)"
fi
```
If no genome found and the user selected a primer target (AGENT-PRIMER.md or CLAUDE.md), halt: "The genome is the minimum requirement for primer distillation. Run `org-genome-builder` first to encode your organizational identity."
If no genome found but the user selected "Full artifact dump", proceed — the dump concatenates whatever artifacts exist. It will contain only non-genome sections, which may still be useful for archival.
If existing AGENT-PRIMER.md found, check for changes:
```bash
# Find artifacts newer than the primer
PRIMER_PATH="$HOME/.ai-first-kit/projects/$SLUG/AGENT-PRIMER.md"
NEWER=$(find "$HOME/.ai-first-kit/projects/$SLUG" -name "*.md" \
-not -name "AGENT-PRIMER.md" \
-not -path "*.holdouts*" \
-not -path "*political-map*" \
-newer "$PRIMER_PATH" 2>/dev/null | head -10)
[ -n "$NEWER" ] && echo "CHANGED since last primer:" && echo "$NEWER" || echo "No changes since last primer"
```
If changes detected, ask via AskUserQuestion: "Source artifacts have changed since the last primer was generated. What would you like to do?"
- **Regenerate** (Recommended) — Rebuild the primer from current artifacts
- **Skip** — Keep the existing primer
## Phase 1: Target Selection
Ask via AskUserQuestion:
"What output targets do you need?"
- **CLAUDE.md + AGENT-PRIMER.md** (Recommended) — Governance section in CLAUDE.md + standalone primer for universal use
- **CLAUDE.md with @imports + AGENT-PRIMER.md** — Uses `@path/to/file` imports in CLAUDE.md for always-loaded genome foundation (MISSION, VALUES, HARD-BOUNDARIES). Leaner CLAUDE.md, content stays in sync automatically.
- **AGENT-PRIMER.md only** — Standalone primer, no CLAUDE.md modifications
- **CLAUDE.md only** — Governance section in CLAUDE.md, no standalone primer. Note: if no AGENT-PRIMER.md exists, the primer pointer in the CLAUDE.md section will be omitted.
- **Full artifact dump** — Single document with all artifacts concatenated (full content, not distilled). For archival, reference, or sharing — not for agent consumption. Confidential sections (holdouts, political maps) are excluded by default; ask the user if they want to include them.
After target selection, ask a follow-up via AskUserQuestion:
"Generate Claude Code governance skills? These create invokable `/org-*` commands (voice check, gate review, decision recording, values check, novel situation handling) in your project's `.claude/skills/`."
- **Yes** — Generate 5 governance operation skills as Claude Code skills
- **No** — Skip skill generation
## Phase 2: Distillation
**If "Full artifact dump" was selected, skip this phase entirely and go to Phase 2B.**
Read all available artifacts using the `Read` tool. Apply these distillation rules strictly:
**IMPORTANT: Do NOT read any files in `gates/.holdouts/` or matching `political-map-*.md`. If artifact discovery reveals these files, skip them entirely — do not open them. Reading them creates a leakage risk even if the intent is to exclude them from the primer.**
### What Goes Into the Primer
| Source | Include | How to Distill |
|--------|---------|----------------|
| `genome/00-identity/MISSION.md` | Yes | Operational mission + who we serve (3-5 lines) |
| `genome/00-identity/VALUES.md` | Yes | Per value: one-line decision rule + agent instruction. **Strip** examples, history, "what we sacrifice" |
| `genome/00-identity/VOICE.md` | Yes | Tone (how to communicate) + formality gradient table (with Example column) + vocabulary lists |
| `genome/01-decision-architecture/AUTHORITY-MATRIX.md` | Yes | Compact 4-tier table + failure handling protocol |
| `genome/01-decision-architecture/TRADEOFF-RULES.md` | Yes | Priority ordering + one-line per rule. **Strip** examples and full scenarios |
| `genome/02-quality-standards/BY-OUTPUT-TYPE.md` | Yes | Pass criteria per type. **Strip** examples of good/bad output |
| `genome/02-quality-standards/ANTI-PATTERNS.md` | Yes | Bullet list: pattern name + one-line "what it looks like" |
| `governance/HARD-BOUNDARIES.md` | **Full** | This is non-negotiable. Include every boundary with prohibition + violation response + hierarchy |
| `governance/AUTHORITY-MATRIX.md` | Yes | Agent-type tier tables. If substantially different from genome version, include both; otherwise reference genome version |
| `governance/ESCALATION-PROTOCOLS.md` | Yes | Trigger categories + information package template + time-bound defaults table. **Strip** anti-pattern explanations |
| `gates/INDEX.md` + individual gate files | Yes | Gate name + type (blocking/advisory, autonomous/human-gated) + pass criteria. **Strip** satisfaction metrics and escalation packages |Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.