mcp-server-trello

Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo. Use when cutting a release, bumping the version, tagging, or publishing to npm / the MCP registry — triggers: "cut a release", "release 1.x.y", "ship a new version", "bump the version", "publish to npm", "publish to the MCP registry", "tag the release", "how do I release this". Codifies the FOUR version-bearing literals that must move in lockstep (package.json, server.json ×2, src/index.ts McpServer info) plus CHANGELOG, and the exact GitHub-Actions triggers that make merging a PR the publish event. Do NOT use for generic changelog prose (docs-changelog), cross-repo semver task scaffolding (mise-versioning), or non-release tagging.

Trello MCP Server skill for board discovery, card workflows, checklist management, comments, attachments, labels, members, board/workspace selection, and health monitoring through the bundled @delorenj/mcp-server-trello server.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.

System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer.

Autopilot orchestrator who runs target BMAD workflows unattended, delegates to workers, and answers HITL questions per a policy file. Use when the user asks to talk to Otto, says "run X on autopilot", or invokes /bmad-bmp-agent-otto.

Hand a target BMAD workflow to Otto for unattended execution. Otto plans, delegates to workers, answers HITL questions per a policy file, and pauses cleanly when confidence dips below floor or category is in always_pause. Use when the user says "run X on autopilot", "do this unattended", or invokes /bmad-bmp-autopilot.

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".

LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow'.

Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

Lossless LLM-optimized compression of source documents. Use when the user requests to 'distill documents' or 'create a distillate'.

Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"

Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry

Edit an existing PRD. Use when the user says "edit this PRD".

Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"

Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.

Conduct market research on competition and customers. Use when the user says they need market research

Orchestrates group discussions between installed BMAD agents, enabling natural multi-agent conversations where each agent is a real subagent with independent thinking. Use when user requests party mode, wants multiple agent perspectives, group discussion, roundtable, or multi-agent conversation about their project.

Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.

Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.

Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"

Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"