claude-slack-bridge

One-time per-repo configuration for the /process workflow. Delegates verification that mcp__claude-slack-bridge is installed (via the verify-bridge skill), task-manager setup end-to-end (via the build-task-manager skill, which generates `.claude/skills/claude-slack-bridge_list-tasks/SKILL.md`), and the three workflow phases — design, plan, and run-plan — each via its own leaf skill (`build-design-workflow`, `build-plan-workflow`, `build-run-plan-flow`) spawned directly so AskUserQuestion is never nested more than one level deep. Use when the user runs /process-setup or asks to set up / re-configure the /process workflow for this repository.

Generate the `/process` orchestrator command for this repo. Writes `.claude/commands/process.md` — the local entry point that reads `.claude/process-template.json` and walks through the configured workflow steps in order, dispatching to each step's slash command and routing to `/required-fixes` when a `/review` step surfaces reviewer comments. Returns a status of `configured` (with the path written) or `skipped` (when the file already exists and the user opts not to overwrite). Use as the process-command phase of /process-setup.

Configure the plan phase of the /process workflow. Asks whether the user wants a plan step at all (skip-able), then asks whether they already have a planning process (e.g. an existing /plan command or skill). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets added. If they don't, asks what kind of plan doc the step should produce and bakes that prompt directly into the wrapper. The ONLY file this skill writes is `.claude/skills/claude-slack-bridge_plan/SKILL.md` — a wrapper skill that runs the user's plan flow (`<@ref-plan-flow>`) or an inline plan prompt when none exists, saves the output to the fixed path `.roadmap_features/<branch>/plan/feature_plan.md` (creating the folder if missing), commits and pushes if the inner flow didn't, opens a GitHub PR, and sends a response back to the caller. Never scaffolds a separate `/plan` slash command. Returns a status of `configured` (with the captured reference) or `skipped` (with the literal label `plan-workflow:

Configure the design phase of the /process workflow. Asks whether the user wants a design step at all (skip-able), then asks whether they already have a design process (e.g. an existing /design command or skill). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets added. If they don't, asks what kind of design doc the step should produce and bakes that prompt directly into the wrapper. The ONLY file this skill writes is `.claude/skills/claude-slack-bridge_design/SKILL.md` — a wrapper skill that runs the user's design flow (`<@ref-design-flow>`) or an inline design prompt when none exists, saves the output to `.roadmap_features/<feature>/design/feature_design.md` (creating the folder if missing), commits and pushes if the inner flow didn't, opens a GitHub PR, and sends a response back to the caller. Never scaffolds a separate `/design` slash command. Returns a status of `configured` (with the captured reference) or `skipped` (with the literal label `design-w

Configure the run-plan (implementation) phase of the /process workflow. Asks whether the user wants a run-plan step at all (skip-able), then asks whether they already have a run-plan process (e.g. an existing /run-plan command or skill that takes a plan doc and implements it). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets added. If they don't, bakes a simple inline implementation prompt directly into the wrapper. The ONLY file this skill writes is `.claude/skills/claude-slack-bridge_run-plan/SKILL.md` — a wrapper skill that runs the user's run-plan flow (`<@ref-run-plan-flow>`) or an inline implementation prompt when none exists, commits and pushes if the inner flow didn't, opens a GitHub PR, and sends a response back to the caller. Never scaffolds a separate `/run-plan` slash command. Returns a status of `configured` (with the captured reference) or `skipped` (with the literal label `run-plan-flow: skip`). Use as the run-plan-flow phase of /process-s

Set up the task manager for this repo end-to-end: pick a manager (Linear / Jira / GitHub Issues / Notion / None), pick an integration method (MCP / CLI / plugin / API), verify the chosen integration is installed (offering to help install, wait for the user, or skip), ask the user how to fetch their tasks and try it (suggesting likely configuration issues on failure), then write `.claude/skills/claude-slack-bridge_list-tasks/SKILL.md` and verify it runs end-to-end. Returns a status of `configured` (with task_manager_label, task_manager_slug, integration_method) or `skipped`. Use as the task-manager phase of /process-setup.

Precondition check that mcp__claude-slack-bridge is installed in the current repo. Reads cwd/.mcp.json and verifies a `claude-slack-bridge` entry exists under `mcpServers`. Exits non-zero with a fix-it message if the entry is missing. Use as a standalone precondition for /process-setup, /process, or any flow that depends on the Slack bridge MCP being declared. Does not check whether the bridge container is running — only that the repo declares the server.