l3io-execute

Files (24)

• SKILL.md
• customize.toml
• payload-manifest.json
• ac-dimensions.md · references/
• auto-remediation.md · references/
• calibration-model.md · references/
• config-resolution.md · references/
• metrics-contract.md · references/
• status-files.md · references/
• spec-align.py · scripts/
• epic-closure.md · steps/closure/
• sprint-closure.md · steps/closure/
• step-02-scope-resolve.md · steps/execute/
• step-03-load-plan.md · steps/execute/
• step-04-arch-gate.md · steps/execute/
• step-05-epic-loop.md · steps/execute/
• step-06-epic-closure.md · steps/execute/
• step-00-activate.md · steps/shared/
• step-00-digest.md · steps/shared/
• step-01-classify-work.md · steps/shared/
• step-estimate.md · steps/shared/
• step-02-story-prep.md · steps/sprint/
• step-03-dev-loop.md · steps/sprint/
• step-04-sprint-closure.md · steps/sprint/

SKILL.md (first lines)

# l3io-execute

Communicate all responses in `{communication_language}`.

## Conventions

- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}`-prefixed paths resolve from the project working directory.
- Bare paths (e.g. `steps/shared/step-00-activate.md`) resolve from `{skill-root}`.
- `{spec_align}` = `uv run {skill-root}/scripts/spec-align.py --project-root {project-root} --planning-root {planning_artifacts} --impl-root {implementation_artifacts} --state-root {implementation_artifacts}/state --pm-status {project-root}/_bmad/scripts/pm-status/__main__.py --spec-paths '{spec_paths}'` — the spec-alignment helper; it never calls a model. `{spec_paths}` is `customize.toml`'s list rendered as JSON (`[]` by default). Step files run it only where `{spec_alignment}` is `true`, except `disposition`, `check-dispositions` and `adrs`, which run either way. Headless sprint subagents receive both bindings in their context block (`steps/execute/step-05-epic-loop.md` §5a).

## On Activation

Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`

If the script fails, resolve the `workflow` block by reading `{skill-root}/customize.toml`, then
`{project-root}/_bmad/custom/l3io-execute.toml` (team), then
`{project-root}/_bmad/custom/l3io-execute.user.toml` (personal) in order. Scalars override, arrays append.

`setup`, `configure`, and `install` are not recognized arguments here — `/l3io-setup` is
the module's setup entry point. Config itself is resolved in step-00-activate per
`{skill-root}/references/config-resolution.md`; an absent `modules.l3io-pm` section means the
module has no overrides, not that it needs setup.

## Execution

**Headless mode** — when `headless: true` is present in the injected context block, do not run
activation: the orchestrator already did, and its context block carries the bindings (pm_status
path, state dirs, session id). Load the digest, then the sprint steps. Activation is not loaded
because its in-run records (`{layouts_reconciled}`, `{layout_migrated}`, `{state_repointed}`) are
orchestrator memory and a subagent has none.
step-01-classify-work is skipped because `{work_type}` is already injected in the context block.
No setup pointer here: this is a dispatched sprint subagent, not the entry a user is starting
work from, and the orchestrator that dispatched it already had its own chance to print it —
the pointer fires at most once ever per project regardless of which invocation gets there
first.

```
{skill-root}/steps/shared/step-00-digest.md
{skill-root}/steps/sprint/step-02-story-prep.md
{skill-root}/steps/sprint/step-03-dev-loop.md
{skill-root}/steps/sprint/step-04-sprint-closure.md
```

**Normal mode** — no `headless: true` in context. Load shared steps, then execute steps in order:

```
{skill-root}/steps/shared/step-00-activate.md
```

Before reading any further state, apply the once-per-project setup pointer
(`{skill-root}/references/config-resolution.md` §5) — this skill is one of the two skills the
pointer is wired into. It fires only when `{l3io_pm_section_absent}` (bound in step-00-activate
§1, from config already resolved there) is `true` — a configured project gets no pointer at
all:

```bash
if [ "{l3io_pm_section_absent}" = "true" ]; then
  uv run {pm_status} notice --state-root {pm_state_root} --key setup-pointer && \
    echo "l3io-pm currently has no project-level configuration. /l3io-setup configures it if you want to."
fi
```

`notice` is keyed on `--key` alone, not a session — there is no cross-invocation session
identifier available (`{session_id}` is bound fresh per invocation), so this fires **at most
once ever** for this project, not once per invocation. Exit 1 means this key was already
recorded — print nothing further, permanently, for this key. Exit 2 means recording it
actually failed (never conflated with exit 1). Never halt on any branch, and never treat this
as a setup trigger.

```
{skill-root}/steps/shared/step-01-classify-work.md
{skill-root}/steps/execute/step-02-scope-resolve.md
{skill-root}/steps/execute/step-03-load-plan.md
{skill-root}/steps/execute/step-04-arch-gate.md
{skill-root}/steps/execute/step-05-epic-loop.md
{skill-root}/steps/execute/step-06-epic-closure.md
```

From ravensorb/bmad-extensions, MIT.

More from ravensorb/bmad-extensions