eawf — Eä Workflow

State-first, agent-driven development framework. Parallel waves, strict schema, Claude Code adapter.

Install

git clone <repo> && cd eawf && uv sync
# or, install as a tool from the local checkout:
uv tool install --from . eawf
# on Windows, pull the named-pipe daemon transport:
uv tool install --from . "eawf[windows]"

Quickstart (new project)

cd /path/to/your/repo
eawf init                            # interactive wizard
eawf plugin install claude           # render local .claude/ skills/agents/hooks
eawf phase open --auto --title "Bootstrap"

Workflow

research → plan → execute (parallel waves) → cherry-pick → ship phase

Use slash commands /research, /prep, /audit, /ship, /review, /polish, or /flow to drive the lifecycle.

Contributing

See CONTRIBUTING.md for local development setup, harness plugin setup, and verification commands.

What gets committed

• .ea/state.json — canonical project ledger. The eawfd daemon is the sole canonical mutator; the eawf state CLI proxies mutations to it over JSON-RPC and falls back to a direct portalocker write only when the daemon is unavailable (CI / one-shot / recovery). Read access is free.
• AGENTS.md — agent contract (regenerated by eawf sync; user region preserved on re-render).

The Claude Code plugin tree (.claude/ + CLAUDE.md) and any user-local files (.claude/settings.local.json) stay gitignored — they are machine-specific renders, not committed assets. Re-render anytime via eawf plugin install claude.

Docs

See docs/ — architecture, CLI surface, schemas, policy. Start with the source map for a one-line-per-package index of src/eawf/, then the architecture overview.

License

MIT — see LICENSE.