← ClaudeAtlas

vibe-harnesslisted

Vibe Engineering workflow for Claude Code and Codex. Use for the bare commands ss, qq, or cc; /vibe-harness commands; phase scope; kanban task tracking; work reports; and mandatory post-push review.
ZEST-im/vibe-engineering · ★ 7 · AI & Automation · score 81
Install: claude install-skill ZEST-im/vibe-engineering
# Vibe-Engineering — Dev Progress Kanban Board Track development progress as a kanban board while coding with Claude Code or Codex. ## References — load only when you need them This file holds the rules you work by. Everything you *look up* lives beside it, so a session does not pay for reference material it never opens. | File | Open it when | |---|---| | `references/task-schema.md` | Writing or editing a task by hand — field list, required fields on `done`, status values | | `references/api.md` | Calling the local HTTP API, or explaining the Board UI | | `references/setup.md` | Installing on a new machine or registering a project | | `references/worker-runtime.md` | Running the managed worker (lease, heartbeat, test gate) | | `references/remote-sync.md` | Wiring a project's snapshot to a central dashboard | ## Source of Truth **The source of truth is the JSON files under each project's `vibe-harness/` directory:** - `vibe-harness/kanban.json` — tasks (todo, in_progress, review, done) - `vibe-harness/decisions.json` — durable technical decisions - `vibe-harness/archive/YYYY-MM.json` — monthly archives of done tasks The local server at `localhost:4242` is **a Board UI and a convenience wrapper around these files** — not the system of record. Anything Claude or a teammate can do via the API can also be done by editing the JSON directly, and edits land in the same files either way. This matters because: - The JSON files are git-tracked and travel with the code. - The s