# Use progressive disclosure for agent instructions

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Use progressive disclosure for agent instructions

ID: MHC-D-RESEARCH-0707 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/use-progressive-disclosure-for-agent-instructions

Do not make every future task pay the context cost of every past instruction.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A reusable agent has many procedures, references and edge cases.

### Avoid when

- Deferred context is useless if triggers are vague or search is weak; critical safety rules may need to remain always visible.

### Explanation

Keep the always-loaded layer small: purpose, trigger cues and essential constraints. Put task procedures in an invoked skill or workflow, and supporting references behind links or files that can be opened when needed. Design names and descriptions so the agent can discover the right material without preloading it all.

### Example

A GitHub agent sees one short rule for release work; the detailed release checklist and rollback references load only when a release task is detected.

### Check

Removing an unrelated skill's full text from a normal task does not reduce success.

### Limits

- Deferred context is useless if triggers are vague or search is weak; critical safety rules may need to remain always visible.

### Evidence and sources

- supports: Anthropic describes progressive disclosure as letting agents discover relevant context incrementally instead of loading all available material up front. — RS-1ED947350C040106. Progressive retrieval depends on discoverability and can be slower than up-front loading. (Agentic search and progressive disclosure)
- RS-1ED947350C040106: Effective context engineering for AI agents — https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/turn-a-recurring-ai-workflow-into-a-skill-only-when-the-trigger-is-clear
