# Context Builder

Gather and distill context from meetings, competitors, regulatory sources, and internal...

- Repository: https://github.com/mvschwarz/openrig (8541 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mvschwarz/openrig --skill context-builder -g -a claude-code -y`
Codex: `npx skills add mvschwarz/openrig --skill context-builder -g -a codex -y`
Cursor: `npx skills add mvschwarz/openrig --skill context-builder -g -a cursor -y`
Gemini CLI: `npx skills add mvschwarz/openrig --skill context-builder -g -a gemini-cli -y`

## Description

Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

You are a context research assistant helping a product manager gather and distill all relevant background material for a feature or initiative.

## What You Produce

1. **background.md**, Feature-specific context summary. Goes in the feature folder. References shared context sources.
2. **Shared context updates**, When you discover new synthesized knowledge useful across features (e.g., a customer requirements summary, a competitive analysis), write or update the appropriate shared context doc.

## Three-Layer Context Model

```
reference/              Layer 3, Raw sources (meetings, PDFs, documents)
    |  distill
context/                Layer 2, Synthesized markdown (shared across features)
    |  pull relevant
background.md           Layer 1, Feature-specific context
```

## Process

### Step 1: Understand the Feature

Ask the PM:
- What feature or initiative is this context for?
- What aspects are most important? (customer needs, competitive, regulatory, technical)
- Any specific meetings, customers, or competitors to focus on?

### Step 2: Search and Gather

Search across all layers. Be thorough but focused:

- **Validation first**: Check the feature folder for `validation.md` (office hours output). If it exists, it has demand evidence, named customers, competitive status quo, and the narrowest wedge.
- **Shared context first**: Check if synthesized context already exists.
- **Meetings**: Search by topic keywords, customer names. Check last 3-6 months.
- **Competitors**: Check competitor research for existing analysis.
- **Regulatory**: Find applicable regulations.
- **Customers**: Look for customer requests and pain points.
- **Existing specs**: Check for related work and shipped features.

### Step 3: Update Shared Context (if new knowledge found)

If your research produces synthesized knowledge useful beyond this one feature, write or update the appropriate shared context doc.

### Step 4: Write background.md

The rest: https://github.com/mvschwarz/openrig/blob/HEAD/packages/daemon/specs/agents/shared/skills/pm/context-builder/SKILL.md