Codex

execution-mode

Set or report the reproducibility mode governing how AIWG workflows execute, from standard to fully auditable

104 stars

Best use case

execution-mode is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

It is a strong fit for teams already working in Codex.

Set or report the reproducibility mode governing how AIWG workflows execute, from standard to fully auditable

Teams using execution-mode should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/execution-mode/SKILL.md --create-dirs "https://raw.githubusercontent.com/jmagly/aiwg/main/.agents/skills/execution-mode/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/execution-mode/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How execution-mode Compares

Feature / Agentexecution-modeStandard Approach
Platform SupportCodexLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Set or report the reproducibility mode governing how AIWG workflows execute, from standard to fully auditable

Which AI agents support this skill?

This skill is designed for Codex.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Execution Mode

You set or report the reproducibility mode that governs how AIWG workflows execute, controlling determinism constraints from none (standard) to fully auditable (audit).

## Triggers

Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):

- "make runs deterministic" → set strict mode
- "pin the seed" → set seeded mode with provided seed value
- "what mode are we in" → report current execution mode
- "reset to default" → set standard mode
- "enable audit logging" → set audit mode

## Trigger Patterns Reference

| Pattern | Example | Action |
|---------|---------|--------|
| Set standard | "use default execution mode" | Run `aiwg execution-mode standard` |
| Set seeded | "use a fixed seed for this run" | Run `aiwg execution-mode seeded --seed <value>` |
| Set strict | "make execution deterministic" | Run `aiwg execution-mode strict --seed <value>` |
| Set audit | "enable audit mode" | Run `aiwg execution-mode audit --seed <value>` |
| Status check | "what execution mode is active?" | Run `aiwg execution-mode` (no args) |
| Seed only | "set seed to 42" | Run `aiwg execution-mode seeded --seed 42` |

## Behavior

When triggered:

1. **Extract intent**:
   - Is this a status check or a mode change?
   - Which mode is requested: `standard`, `seeded`, `strict`, or `audit`?
   - Is a `--seed` value provided or should one be generated?

2. **Run the appropriate command**:

   ```bash
   # Report current mode (no args)
   aiwg execution-mode

   # Standard — no reproducibility constraints
   aiwg execution-mode standard

   # Seeded — fixed random seed for all operations
   aiwg execution-mode seeded --seed 42

   # Strict — seeded + no external calls + pinned versions
   aiwg execution-mode strict --seed 42

   # Audit — strict + decision logging for replay
   aiwg execution-mode audit --seed 42
   ```

3. **Mode summary**:

   | Mode | Seed | External calls | Pinned versions | Decision log |
   |------|------|----------------|-----------------|--------------|
   | `standard` | No | Allowed | No | No |
   | `seeded` | Yes | Allowed | No | No |
   | `strict` | Yes | Blocked | Yes | No |
   | `audit` | Yes | Blocked | Yes | Yes |

4. **Persistence**: Mode is written to `.aiwg/execution-mode.json` and persists across sessions until explicitly changed.

5. **Report the result** — confirm the mode that is now active and note any implications (e.g., external calls will be blocked in strict/audit mode).

## Examples

### Example 1: Status check

**User**: "What execution mode are we in?"

**Extraction**: Status check, no change requested

**Action**:
```bash
aiwg execution-mode
```

**Response**: "Current execution mode: `seeded` (seed: 1234). External calls are allowed and versions are not pinned. To increase determinism, switch to `strict` or `audit` mode."

### Example 2: Enable strict mode

**User**: "Make the workflow fully deterministic with seed 42"

**Extraction**: Strict mode requested, seed 42 provided

**Action**:
```bash
aiwg execution-mode strict --seed 42
```

**Response**: "Execution mode set to `strict` with seed 42. External network calls are blocked and dependency versions are pinned. Mode saved to `.aiwg/execution-mode.json`."

### Example 3: Enable audit mode for compliance

**User**: "Enable audit mode so we can replay every decision"

**Extraction**: Audit mode requested, no seed provided — generate one

**Action**:
```bash
aiwg execution-mode audit --seed 7391
```

**Response**: "Execution mode set to `audit` with seed 7391. All decisions will be logged for replay. Seed chosen automatically — note it if you need to reproduce this run exactly."

### Example 4: Reset to default

**User**: "Reset execution mode back to default"

**Extraction**: Reset to standard mode

**Action**:
```bash
aiwg execution-mode standard
```

**Response**: "Execution mode reset to `standard`. No reproducibility constraints are active."

## Clarification Prompts

If the user's intent is ambiguous:

- "Should I generate a random seed or would you like to specify one?"
- "Which mode would you like? `seeded` (fixed seed only), `strict` (seed + pinned versions + no external calls), or `audit` (strict + decision logging)?"

## References

- @$AIWG_ROOT/src/cli/handlers/subcommands.ts — Execution mode command handler
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/schemas/reproducibility/ — Reproducibility schemas

Related Skills

dev-mode-init

104
from jmagly/aiwg

Switch AIWG CLI to dev mode (local repo source), rebuild, deploy dev tools, and run a health check — all via the Steward agent

uat-mode

104
from jmagly/aiwg

Detect requests for UAT generation, execution, or reporting and invoke the appropriate UAT command

Codex

rlm-mode

104
from jmagly/aiwg

Detect requests for recursive decomposition and large-scale operations that benefit from RLM processing

Codex

flow-test-strategy-execution

104
from jmagly/aiwg

Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis

Codex

auto-test-execution

104
from jmagly/aiwg

Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern

Codex

aiwg-orchestrate

104
from jmagly/aiwg

Route structured artifact work to AIWG workflows via MCP with zero parent context cost

venv-manager

104
from jmagly/aiwg

Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.

pytest-runner

104
from jmagly/aiwg

Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.

vitest-runner

104
from jmagly/aiwg

Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.

eslint-checker

104
from jmagly/aiwg

Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.

repo-analyzer

104
from jmagly/aiwg

Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.

pr-reviewer

104
from jmagly/aiwg

Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows.