ak-mioflow

---
name: ak-mioflow
description: >-
  Run the full bundled MioFlow validate-first workflow from Agent Kit. Use only
  when the user invokes ak:mioflow or explicitly asks to enter MioFlow mode.
---

# AK MioFlow

`ak:mioflow` is an Agent Kit entrypoint that activates the bundled MioFlow workflow without changing the default AK routes.

## Activation Contract

Use this skill only when the user explicitly invokes `ak:mioflow` or asks to use MioFlow. Do not route ordinary `ak:plan`, `ak:cook`, `ak:debug`, `ak:review`, or `ak:test` requests here.

`ak:mioflow` is an intent router, not a shell command.

## Bundled Skill Root

The complete MioFlow skill set is vendored under:

```text
skills/ak-mioflow/mioflow-skills/
```

Load bundled skills from that directory. Preserve MioFlow semantics, phase gates, handoffs, and support skills.

## Required Startup

1. Read `mioflow-skills/using-mioflow/SKILL.md` first.
2. Follow its routing summary and gates.
3. If the user is starting a new feature and no downstream state exists, begin with `mioflow-skills/exploring/SKILL.md`.
4. If resuming, inspect `.mioflow/HANDOFF.json`, `.mioflow/state.json`, and any referenced `history/<feature>/CONTEXT.md` when present.

## Main MioFlow Chain

```text
using-mioflow
  -> exploring
  -> planning
  -> validating
  -> swarming
  -> executing
  -> reviewing
  -> compounding
```

## Support Skills

Use the bundled support skills only when MioFlow itself routes to them:

- `mioflow-skills/debugging/SKILL.md`
- `mioflow-skills/dream/SKILL.md`
- `mioflow-skills/gkg/SKILL.md`
- `mioflow-skills/writing-mioflow-skills/SKILL.md`
- `mioflow-skills/bootstrap-project-context/SKILL.md`
- `mioflow-skills/refresh-project-docs/SKILL.md`
- `mioflow-skills/prompt-leverage/SKILL.md`
- `mioflow-skills/xia/SKILL.md`
- `mioflow-skills/agent-creator/SKILL.md`
- `mioflow-skills/animated-landing-pages/SKILL.md`
- `mioflow-skills/book-sft-pipeline/SKILL.md`

## Isolation Rules

- Keep normal Agent Kit routes unchanged outside `ak:mioflow` mode.
- Do not expose bundled MioFlow subskills as top-level AK aliases unless the user explicitly asks for that later.
- Do not run `ak:mioflow` in a shell.
- Do not create commits or push changes. The user must explicitly handle git commits.

## MioFlow Gates

Never skip these gates inside MioFlow mode:

1. Approve locked `CONTEXT.md` after exploring.
2. Approve work shape after planning.
3. Approve feasibility-validated execution after validating.
4. Resolve or acknowledge P1 review findings before completion.

## Runtime Notes

MioFlow may use these runtime artifacts when present:

```text
.mioflow/onboarding.json
.mioflow/state.json
.mioflow/HANDOFF.json
.mioflow/reservations.json
.codex/mioflow_status.mjs
.codex/mioflow_reservations.mjs
```

If required tools such as `br`, `bv`, `gkg`, `cass`, or `cm` are unavailable, report the degraded mode and follow MioFlow's documented fallback behavior.