AIPOM Context Package Builder
What Is It
Build the smallest inspectable context package that enables a specific human-AI workflow or decision. Include purpose, trusted sources, constraints, definitions, decisions, examples, exclusions, conflicts, ownership, and refresh rules.
Why Use It
More context is not automatically better. Stuffed, stale, conflicting, or unowned context increases error and hides provenance. A bounded package makes context a maintained product input rather than an accidental prompt dump.
When to Use It
Use for recurring workflows, agent handoffs, evaluations, or decisions that require stable organizational context. Diagnose source readiness first when ownership or trust is broadly unclear.
What It Produces
- Purpose and decision contract
- Authoritative source inventory and conflict rules
- Constraints, glossary, decisions, examples, and exclusions
- Access, refresh, expiry, version, and owner metadata
- Gaps and next maintenance action
Who Should Participate
Include the workflow owner, source owners, intended users, technical implementer, and privacy, security, legal, records, or domain specialists as needed.
Evidence to Bring
Bring the real source files, dates, owners, prior decisions, examples, access rules, user evidence, and known conflicts. Links without owners or freshness signals are leads, not authoritative context.
How to Do It
- State the workflow, decision, audience, and failure consequence.
- Define what the package must enable and must not be used for.
- Inventory sources; name owner, authority, audience, access, and freshness.
- Resolve or preserve conflicts with an explicit precedence rule.
- Extract only necessary constraints, definitions, decisions, and examples.
- Add exclusions: sensitive, irrelevant, expired, speculative, or unlicensed material.
- Define retrieval cues, version, refresh, expiry, and change notification.
- Test the package on representative and failure cases.
- Assign stewardship and record unresolved gaps.
Key Concepts
- Purpose-bounded context: relevance depends on the decision.
- Authority and provenance: users can trace why a source is trusted.
- Exclusion is design: what stays out is as important as what enters.
- Lifecycle: context decays and must be refreshed or retired.
Organizational Applications
Use for product strategy, customer synthesis, portfolio reviews, support, evaluation, governance evidence, and reusable skills.
Common Pitfalls
- Copying everything into one file
- Treating recency as authority
- Hiding conflicting decisions
- Including sensitive material without a purpose or permission
- Omitting expiry and ownership
- Testing retrieval without testing decision quality
Combine With
Use authoritative-source-map for wider source systems, aipom-context-readiness-advisor for diagnosis, and aipom-context-lifecycle-designer for persistence and refresh controls.
Assets and Templates
- Context package template
- Synthetic worked example
- Weak example
Sources
This skill is an original AIPOM synthesis of context-engineering and organizational knowledge practices.
1---2name: aipom-context-package-builder3description: Assemble a bounded, reusable context package with purpose, authoritative sources, constraints, decisions, examples, exclusions, and refresh rules. Use for recurring AI-assisted work.4---56# AIPOM Context Package Builder78## What Is It910Build the smallest inspectable context package that enables a specific human-AI workflow or decision. Include purpose, trusted sources, constraints, definitions, decisions, examples, exclusions, conflicts, ownership, and refresh rules.1112## Why Use It1314More context is not automatically better. Stuffed, stale, conflicting, or unowned context increases error and hides provenance. A bounded package makes context a maintained product input rather than an accidental prompt dump.1516## When to Use It1718Use for recurring workflows, agent handoffs, evaluations, or decisions that require stable organizational context. Diagnose source readiness first when ownership or trust is broadly unclear.1920## What It Produces2122- Purpose and decision contract23- Authoritative source inventory and conflict rules24- Constraints, glossary, decisions, examples, and exclusions25- Access, refresh, expiry, version, and owner metadata26- Gaps and next maintenance action2728## Who Should Participate2930Include the workflow owner, source owners, intended users, technical implementer, and privacy, security, legal, records, or domain specialists as needed.3132## Evidence to Bring3334Bring the real source files, dates, owners, prior decisions, examples, access rules, user evidence, and known conflicts. Links without owners or freshness signals are leads, not authoritative context.3536## How to Do It37381. State the workflow, decision, audience, and failure consequence.392. Define what the package must enable and must not be used for.403. Inventory sources; name owner, authority, audience, access, and freshness.414. Resolve or preserve conflicts with an explicit precedence rule.425. Extract only necessary constraints, definitions, decisions, and examples.436. Add exclusions: sensitive, irrelevant, expired, speculative, or unlicensed material.447. Define retrieval cues, version, refresh, expiry, and change notification.458. Test the package on representative and failure cases.469. Assign stewardship and record unresolved gaps.4748## Key Concepts4950- **Purpose-bounded context:** relevance depends on the decision.51- **Authority and provenance:** users can trace why a source is trusted.52- **Exclusion is design:** what stays out is as important as what enters.53- **Lifecycle:** context decays and must be refreshed or retired.5455## Organizational Applications5657Use for product strategy, customer synthesis, portfolio reviews, support, evaluation, governance evidence, and reusable skills.5859## Common Pitfalls6061- Copying everything into one file62- Treating recency as authority63- Hiding conflicting decisions64- Including sensitive material without a purpose or permission65- Omitting expiry and ownership66- Testing retrieval without testing decision quality6768## Combine With6970Use `authoritative-source-map` for wider source systems, `aipom-context-readiness-advisor` for diagnosis, and `aipom-context-lifecycle-designer` for persistence and refresh controls.7172## Assets and Templates7374- [Context package template](template.md)75- [Synthetic worked example](examples/worked-example.md)76- [Weak example](examples/weak-example.md)7778## Sources7980This skill is an original AIPOM synthesis of context-engineering and organizational knowledge practices.
Dean Peters