---
id: "action-extract-context"
type: "action-item"
source_timestamps: ["19:50:00", "20:40:00"]
tags: ["data-extraction", "prompt-engineering"]
related: ["concept-implicit-context", "framework-four-layers-context", "action-deploy-mcp-server"]
action: "Run a structured extraction prompt against your primary AI to articulate your implicit workflow and behavioral preferences."
outcome: "A structured markdown file or dataset containing your professional AI context, ready for export."
speakers: ["Nate B. Jones"]
sources: ["s18-anthropic-openai-memory"]
sourceVaultSlug: "s18-anthropic-openai-memory"
originDay: 18
---
# Action: Extract Context via Structured Prompts

## The Action

Run a structured extraction prompt against your primary AI to articulate your implicit workflow and behavioral preferences.

## Expected Outcome

A structured markdown file or dataset containing your professional AI context, ready for export.

## Why It Works

To escape the context trap, professionals must actively extract their implicit working intelligence from siloed AI platforms. The crucial insight is this: **the AI already possesses a rich, implicit model of how the user works** ([[concept-implicit-context]]). The user can therefore prompt the AI to articulate this model explicitly — sidestepping the impossibility of writing it from memory.

## Prompt Strategy

[[entity-nate-b-jones]] advises running a structured extraction prompt against the primary AI assistant, asking it to detail the user's:
- **Domain context** → corresponds to [[concept-domain-encoding]]
- **Communication preferences and workflow patterns** → corresponds to [[concept-workflow-calibration]]
- **Recurring project types**
- **Observed behavioral tendencies** → corresponds to [[concept-behavioral-relationship]]

This forces the AI to translate years of implicit "compound interest" into explicit, structured data that maps cleanly onto the [[framework-four-layers-context]].

## Curation Step

The user should then **review, edit, and refine** this output to ensure it accurately reflects their professional identity **without including proprietary company secrets**. This curated profile becomes the foundational data feeding [[action-deploy-mcp-server]].

## Sequence

1. (this action) Extract → produces curated context document
2. [[action-deploy-mcp-server]] → wraps it as a portable, read-write backend

Together they operationalize ownership of [[concept-professional-capital]].