autonomous-workflow

# Autonomous Workflow Phase-based autonomous feature development. Each phase has a gate that must pass before continuing. Phases optionally invoke companion skills based on the task — companions skip silently if not installed. > **Source of truth.** This `SKILL.md` is a thin index. Detailed procedures > live in `rules/*.md` and load on demand. Companion-skill triggers and > disable instructions live in [`rules/companion-skills.md`](./rules/companion-skills.md). --- ## Self-Improvement The workflow improves across runs through a **two-tier loop** (full contract in [`rules/self-improvement-loop.md`](./rules/self-improvement-loop.md)): **Fast tier — episodic lessons (LoreKit `memory.*` tools, optional companion).** The workflow reads accumulated `loop::aw-lessons` lessons before planning (Phase 1) and writes new ones when it gets stuck (Phase 4) or finishes (Phase 7), mapping universal lessons to LoreKit's `global` scope and repo-bound lessons to `repo::{owner}/{repo}`. Lessons are **advisory** — they bias the plan, never silently change a gate. Skips silently when LoreKit's `memory.*` tools are not connected. **When invoked through the `aw` dispatcher, the read/write is hoisted to the dispatcher** (intake + exit) so **every tier** — Micro, Lite, and Full — both benefits from and contributes lessons; the phase-level reads/writes are the Full-tier specialization. This is how self-improvement stays universal without forcing planning on simple tasks. **Slow tier — retrospect...