- Waykit
- Product guide
- Getting started
Getting started
Four steps to Waykit on a repo. macOS and Linux; needs git and Node 22+. No API key.
- Install Waykit (~2 min) — Links
~/.agentsand putswkon your PATH via~/.local/bin(kitremains an alias). - Bootstrap this checkout (~2 min) —
wk init . --mcp default --hookwrites the thin handshake, IDE pointers, and a default MCP profile. Already in this repo?./install.shis enough. - Open the lifecycle (~3 min) — Feature work routes grill → spec → TDD + XFN → audit → release. Read the feature lifecycle.
- Optional: prove a tool call (~3 min) —
wk eval run --suite evals/edd/demo.yaml --model scripted, thenwk eval ci --suite evals/edd/demo.yaml --threshold-routing 95 --out out/reports.
Install Waykit
If wk is missing after install, add ~/.local/bin to PATH.
curl -fsSL https://raw.githubusercontent.com/mzworthington/waykit/main/install.sh | sh
wk init . --mcp default --hook
Run an eval locally (optional)
wk eval run --suite evals/edd/demo.yaml --model scripted
wk eval ci --suite evals/edd/demo.yaml --threshold-routing 95 --out out/reports
wk eval report --format md --out out/reports
The scripted driver works offline. A provider key is only for optional live-model evals.
Next
- Jobs for today if you already know the failure in front of you
- Feature lifecycle for grill → spec → TDD → ship
- EDD guide for suites, CI, and production misses
- What Waykit gives you for context budget, the live kit graph, and MCP profiles
- Waykit map is that graph in the browser; author it after you change skills or SOPs
- Common questions