Hotseat

hotseat — Claude Code plugin

Ships the plan-feature and build-feature skills (FSM-gated feature planning and builds driven by the structured wiki) plus the wiki MCP server config they depend on, so installing this plugin gives any repo all of it in one step. /plan-feature produces a grounded, reviewed, build-ready plan and stops; /build-feature takes a brief the rest of the way to a human sign-off gate. The skills are namespaced hotseat:plan-feature / hotseat:build-feature; invoke them as /plan-feature / /build-feature (or the hotseat:-prefixed form if another skill shadows the short name).

Install

The hotseat-web repo is its own marketplace (.claude-plugin/marketplace.json at the repo root). From any Claude Code session:

/plugin marketplace add Goldenmule-Media/hotseat-web     # or a local path to a checkout
/plugin install hotseat@hotseat

To test changes before pushing: /plugin marketplace add /path/to/hotseat-web, then install, then /plugin marketplace update hotseat after edits.

Discovery: the feature model bundle declares this plugin (a skills export in wiki-models/src/feature/index.ts), so a running server reports the skill and the exact install commands above — the listModelSkills MCP tool, or GET :4438/_server/models.

Prerequisites (per machine)

The skill talks to a running wiki-server; the plugin only carries the client wiring.

1. A wiki-server running with the feature model loaded — from a hotseat-web checkout: npm start (or npm run start -w wiki-server -- --models wiki-models/feature).
2. The MCP endpoint defaults to http://127.0.0.1:4439/mcp; override with the WIKI_MCP_URL env var if your server lives elsewhere.
3. If the target repo should mirror wiki Markdown to disk, run the wiki-mirror process with the workspace mapped to a root in ~/.wiki/wiki-mirror.config.json — the plugin does not do this for you.
4. A hotseat.config.json at the repo root binding the repo to its workspace ({ "workspaceId": "ws:..." }), so /build-feature resolves the workspace without an argument. Commit it so it travels with every clone/worktree. Skip it and the skill falls back to listWorkspaces + a prompt (and offers to write it for you).

Contents

• skills/plan-feature/ — the planning skill (spine + workflows/ fan-out templates): grounds, authors, and reviews a plan, then stops build-ready. See its README.
• skills/build-feature/ — the build skill (spine + workflows/ fan-out templates). See its README for design and usage.
• .mcp.json — the wiki MCP server entry (HTTP, WIKI_MCP_URL-overridable).

Source of truth

The canonical copies of the skills live here. hotseat-web's own .claude/skills/plan-feature/ and .claude/skills/build-feature/ are the same skills loaded as project skills for work inside this repo — keep each pair in sync when editing (or delete the project copies and install the plugin here too).