The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Withvibe Roadmap listing page.
A per-env implementation roadmap board for WithVibe — Postgres-backed, with an MCP server the AI orchestrator drives directly.
Multi-phase features drift. Plans change mid-flight. After a few sessions you lose track of what shipped, what's pending, and which step you're actually on. This plugin gives the AI a structured place to keep that state — and the user a live view of it.
pending / in_progress / done / blocked / deferred / canceled statuses.ai or user) and an optional reason. The trail makes drift visible.propose_plan, set_active_task, complete_task, add_note, update_task, log_change, …shared-postgres plugin storage, so state survives container restarts.env — one container per (env, plugin). Each env gets its own roadmap, its own Postgres schema, its own port.shared-postgres — the platform provisions a dedicated role + schema in the withvibe_plugins database and injects DATABASE_URL + PGSCHEMA at spawn. The plugin role can't reach the main withvibe DB.plan (singleton), phase, task, plan_event (change log).All tools return the full updated plan in the trailing text so the AI never holds stale state.
| Tool | Purpose |
|---|---|
get_plan | Read the full roadmap + active marker + last 20 events. |
propose_plan | Replace the whole roadmap (initial planning or a major re-plan). |
add_phase / add_task | Append work mid-flight; reason recorded. |
set_active_task | Mark the "you are here" anchor before starting work. |
complete_task | Mark done with a 1-line outcome; auto-closes the phase if every task is done. |
update_task / update_phase | Edit title/description/status (blocked, deferred, canceled) with reason. |
add_note | Append a markdown note — decisions, things tried, references. |
log_change | Narrate a plan-level decision without mutating data. |
See mcp.js for the full schemas.
The image is multi-arch-friendly via Node 20 Alpine, ~150 MB, no native build steps.
To update after rebuilding the image, hit Update on the plugin row in the admin list — running instances are stopped so the next env start picks up the new image.
The manifest is the entire install input. The fields that matter for this plugin:
When developing against a real WithVibe install, hit Update in the admin Plugins page after each rebuild — that stops running instances so the next env start picks up the new image.
Issues and PRs welcome. Keep changes focused and document the why in commits.
Apache License 2.0. See NOTICE for attribution.