bmad-taskmaster-mcp-bootstrap_skill

Overview

This skill bootstraps a TaskMaster MCP server and aligns it with BMAD Skills + Hooks so the project uses TaskMaster's task engine instead of a Markdown-only flow. It provisions the server, guides configuration of secrets and persistence, verifies health, and produces hand-off artifacts and next steps.

How this skill works

The skill checks environment readiness (Node.js, npm, git, permissions) and chooses an install mode (npx vs managed clone). It runs deterministic provisioning steps or instructs the operator to run the provided bootstrap script, collects configuration inputs (API keys, persistence paths, tool subsets), writes minimal config scaffolding (.env / mcp.json), and validates the running MCP with status and health commands. Finally, it documents Hook integration points so BMAD session load/save operations call the MCP endpoints and shared tasks.md files.

When to use it

• When you want Claude-driven TaskMaster MCP instead of the built-in Markdown-only workflow.
• When you need a managed TaskMaster environment that BMAD Skills can call.
• When configuring API keys, persistence, or automation for TaskMaster.
• When installing, upgrading, or re-provisioning the TaskMaster MCP server.
• When preparing hand-off artifacts and operational runbooks for operators.

Best practices

• Verify Node.js, npm, git, and workspace permissions before starting; stop and escalate if missing.
• Use the provided deterministic bootstrap script for repetitive shell work instead of ad-hoc commands.
• Never paste private API keys into shared responses; require the operator to supply them interactively.
• Keep .env and mcp.json templates minimal with clear placeholder tokens for secrets.
• Record installation logs and any deviations from the standard workflow for future resume.

Example use cases

• Provision a new TaskMaster MCP for a repo so BMAD Skills can create and manage tasks via the task engine.
• Switch an existing project from Markdown-only task tracking to TaskMaster MCP and align Hooks.
• Upgrade TaskMaster to a new release and verify tool exposure and tasks.md read/write.
• Prepare operator hand-off with commands to start/stop the server, health checks, and backup recommendations.