---
schema_version: 1
revision: "22ce5d34dbcb5a78"
id: "codex-context-packing-practice"
title: "Context packing with Oracle and PackX: practice drills"
---

# Context packing with Oracle and PackX: practice drills

These exercises practice asking for the `oracle-packx` skill clearly. They do not require team members to memorize PackX or Oracle command syntax.

## Exercise 1: Write A Skill Invocation

Pick a real software project, feature, or bug.

Write a prompt that starts with:

```text
Use the oracle-packx skill.
```

Include:

- desired software outcome
- feature/module/subsystem in scope
- source paths that probably matter
- tests or logs that probably matter
- docs or provider references that probably matter
- files or areas to exclude
- how you will know the answer is useful

Template:

```text
Use the oracle-packx skill.

I want to:

Relevant code is probably in:

Relevant tests/logs/docs are probably:

Exclude:

Ask Oracle for:

I will know this worked if:
```

## Exercise 2: Identify Evidence

For the same project, list what should go into the context packet.

```markdown
# Evidence Map

## Source

- path:
- why it matters:

## Tests

- path:
- why it matters:

## Logs Or Failures

- path:
- why it matters:

## Docs Or External Contracts

- path or URL:
- why it matters:

## Out Of Scope

- path/topic:
- why excluded:
```

## Exercise 3: Decide What Should Be Compact Evidence

Some material is useful but should not be packed raw.

Mark each item as `pack raw`, `summarize`, or `exclude`:

```markdown
# Compact Evidence Decisions

- 30,000-line CI log:
- screenshot of broken UI:
- `.env.local`:
- payment provider API docs:
- one failing test output:
- previous Oracle output:
- entire session history:
- generated build directory:
```

## Exercise 4: Review A Bad Prompt

Bad:

```text
Use Oracle to review my repo and tell me what to do.
```

Rewrite it so the `oracle-packx` skill has enough direction:

```text
Use the oracle-packx skill.

...
```

Make sure your rewrite includes:

- exact project area
- expected outcome
- likely evidence
- exclusions
- what Oracle should return
- how local work will be confirmed

## Exercise 5: Plan A Follow-Up Oracle Call

A second Oracle call should not repeat the same broad question.

Fill this out before asking again:

```text
Prior-State Ledger:
- prior_oracle_session:
- last_oracle_recommendation:
- implemented_since_prior_oracle:
- verified_since_prior_oracle:
- failed_proof_or_blocker:
- narrowing_decision:
- files_functions_now_in_scope:
- files_functions_out_of_scope:
- next_falsifiable_verification:
- forward_progress_index:
```

Decide which condition is true:

```text
implemented:
verified:
blocked:
narrowed:
```

If none are true, do local work before another Oracle run.

## Exercise 6: Inspect The Skill

Open:

```text
skills/oracle-packx/SKILL.md
```

Find the sections that define:

- runtime mode
- PackX pipeline
- compact evidence
- `output.log`
- follow-up call requirements
- completion checklist

Write one sentence about what each section protects you from.

## Related resources

- [Companion reference](https://lapis-fossil-vsbc.here.now/downloads/codex-power-user-workshop-2026-06-27.bundle)
- [Resource directory and portable download](/topics/codex-resources/)

## Original references

- [Portable Codex workflow resources](https://lapis-fossil-vsbc.here.now/downloads/codex-power-user-workshop-2026-06-27.bundle)
