agent-workflow-enginelisted

# agent-workflow-engine The **canonical source of truth** for the `agent-workflow` planning methodology. It is a **published, installable npm package** (`capability.json` → `available:true`): it holds the methodology text and **provides** it, but it ships no runtime and mutates no files. The kit reads **this canon live from the installed engine** (resolved via the family `detect.installed` pattern) and injects the bounded slot fragment from it — **one source of truth, no bundled mirror**. `npx @sabaiway/agent-workflow-kit@latest init` installs the engine as a core part of the kit; when a slot fill is needed but the engine is absent, the kit's reconcile **fails loudly** (never silently). ## What it provides (`provides: ["plan"]`) - [`references/planning.md`](references/planning.md) — the **full methodology**: the Plan→Phase→Step→Substep vocabulary, plan-file lifecycle (`docs/plans/*.md`, gitignored, never committed), the `queue.md` series index, the mandatory final **Phase: Cleanup**, the plan-then-execute split, and the session-continuity heuristic. - [`references/methodology-slot.md`](references/methodology-slot.md) — the **bounded** fragment the composition root injects into a deployed project's `AGENTS.md`, between the `<!-- workflow:methodology:start -->` / `<!-- workflow:methodology:end -->` markers. A short summary + pointer, not the full reference, so the entry point stays under its line cap. - [`references/orchestration.md`](references/orchestration.md)