MCP Playbook Server

Provides an instruction to the LLM about the purpose of the mcp-playbook server, which is to facilitate local project documentation and enable partial replication of documentation and chat logs for an AI-powered playbook.

Creates or overwrites a new specification file (e.g., PRD, RFC, architectural planning) in the docs/specs/ directory of the target project. Specification files will be named following a `spec-name.md` convention. For small feature changes, a simple markdown outline is sufficient. For larger or more complex changes, format the content as a formal PRD or RFC.

Creates or overwrites a new Architectural Decision Record (ADR) file in the docs/adr/ directory of the target project. ADR files will be named following an `adr-name.md` convention.

Creates a new, detailed, and user-facing changelog entry file in the docs/changelog/ directory of the target project. Each changelog entry will be a separate file named following a `changelog-entry.md` convention. Entries should provide comprehensive information about changes, including how to use new features or any impact on existing functionality, rather than being brief summaries.

Captures the current conversation history, saves it as a markdown file in the .chat/ directory of the target project, and uploads it to the dwarvesf/prompt-log GitHub repository. Requires a user ID to organize logs by user.

Fuzzy search for keywords in the dwarvesf/runbook GitHub repository.

Fuzzy search for keywords in the dwarvesf/prompt-db GitHub repository (excluding the synced_prompts/ folder).

Creates or updates a Pull Request in the dwarvesf/runbook repository with a new runbook entry.

Syncs an LLM prompt to the dwarvesf/prompt-db GitHub repository in YAML format.

Use the tool to think about something. It will not obtain new information or make any changes to the repository, but just log the thought. Use it when complex reasoning or brainstorming is needed. For example, if you explore the repo and discover the source of a bug, call this tool to brainstorm several unique ways of fixing the bug, and assess which change(s) are likely to be simplest and most effective. Alternatively, if you receive some test results, call this tool to brainstorm ways to fix the failing tests.

Use this tool to append content to the central 'Project Runbook' file located at `docs/runbook.md` within the `target_project_dir`. **Before calling this tool, you MUST:** 1. Thoroughly analyze all relevant project documents (ADRs, specs, changelogs, code, etc.) within the `target_project_dir`. 2. If `docs/runbook.md` already exists, **you MUST review its current content** as part of your analysis to avoid duplicating information. 3. Synthesize all gathered information into new, additive content for the Project Runbook. This runbook serves as the primary, evolving knowledge base for understanding feature flows, key components, interactions, and operational procedures. 4. The `content` you provide to this tool **must be new content to be appended** to the existing `docs/runbook.md` file. **IMPORTANT:** This tool *only appends* content. If you need to perform significant rewrites, corrections, or manual edits to the `docs/runbook.md` file, you should use `commander-edit_block` for surgical changes or `commander-write_file` with `mode: 'rewrite'` if a complete overhaul is necessary. The frontmatter of the runbook will be automatically updated with the current date and any source references you provide.