codex-skill-foundry-minimal

name	codex-skill-foundry-minimal
description	Use for low-complexity Codex work that needs concise responses, dependency-correct sequencing, and safe deterministic command execution without heavier governance.

Codex Minimal

Operating Rule

Use the smallest process that can produce a correct result.

Default sequence:

1. understand the request
2. inspect current state when local context matters
3. sequence dependent steps safely
4. make the smallest coherent change or run the smallest command set
5. validate the direct result
6. report what changed, what was checked, and what remains uncertain

Keep answers concise. Do not add ceremony when it does not change correctness, safety, evidence, or maintainability.

When To Use

Use this tier for:

1. answer-only requests
2. one-off local commands
3. tiny isolated text edits
4. small low-risk code edits
5. quick repo inspection or status checks

Move to a heavier tier when work affects releases, policy, multiple coupled files, user-facing workflows, production systems, data, auth, payment, or long-lived documentation.

Sequencing

Instruction order is not automatically execution order.

Before acting:

1. identify prerequisites
2. do reads before writes
3. do low-risk checks before expensive checks
4. avoid destructive actions unless explicitly requested or confirmed
5. validate before final reporting

Parallelize only independent reads or inspections. Do not parallelize writes or commands that share mutable state.

Command Safety

For shell work:

1. verify the working directory
2. prefer idempotent, non-interactive commands
3. keep side effects scoped to the project
4. capture only the output needed for the final answer
5. retry only after reading the error and changing something meaningful
6. stop if repeated failures suggest missing permissions, missing dependencies, or data-loss risk

Do not deploy, publish, release, charge money, rotate secrets, or mutate production unless explicitly requested.

Editing

For file edits:

1. inspect the relevant file first
2. preserve unrelated user changes
3. keep the edit narrow
4. avoid unrelated refactors
5. run the fastest useful validation

If validation is unavailable or blocked, report the blocker and residual risk.

Final Response

When complete:

1. state the result first
2. mention files changed when useful
3. state validation performed
4. state blockers or uncertainty
5. keep the response short