Trello Card Creator

Overview

This skill provides a standardized workflow for expanding high-level sprint structures into testable, developer-ready Trello cards using the context_todo_board MCP server tools. It acts as an "Experienced Senior Full Stack Developer," breaking down features into clear Acceptance Criteria (AC) and highly prescriptive QA validation procedures.

Workflow

When the user asks to generate Trello cards or detail the tasks for a sprint, follow these exact steps:

1. Information Gathering

Before detailing any tasks, you MUST ensure you have the necessary context. Instead of asking the user directly, leverage the MCP tools to pull this information:

1. Identify the Target Trello Board & List: Find out where these cards should be created. Use mcp_context_todo_board_list_boards or mcp_context_todo_board_get_active_board_info to identify the correct board. You'll also need the target list using mcp_context_todo_board_get_lists.
2. Fetch Project Context: Use mcp_context_todo_board_get_business_context and pass the target board's ID to automatically retrieve the MLP/MVP Definition, User Journey Flow, and any Integrations or overall context stored with the board.
3. Sprint Structure: Obtain the high-level sprint plan. If it's not stored in the board or previously provided by the user, DO NOT ask the user for it. Instead, use the gathered Business Context (MVP Definition, User Journey, etc.) to proactively generate a proposed sprint structure (including task IDs, titles, descriptions, and dependencies) for the user to review.

Only ask the user to provide pieces of information if they cannot be retrieved from the MCP tools or logically inferred from the available context.

2. Prepare Task Details (Definitions, AC, and QA Steps)

For each task in the sprint structure, formulate its contents with Extreme Specificity. If the user hasn't provided fully fleshed-out task titles and descriptions, refine or create them based on the following task definition standards before moving to Acceptance Criteria and QA Steps. Remember the project context (Next.js, React, Node.js, PostgreSQL, Storybook, etc.) and the rule against writing test files.

Task Definition Standards:

• Task Titles: Must be concise (≤ 60 characters), action-oriented (start with a verb), user-facing, and free of technical jargon. (e.g., "Build User Preferences API", not "POST /api/user/preferences").
• Task Descriptions: Must be 3-5 sentences explaining What needs to be built (including technical details like endpoints/paths), Why it brings user value or technical necessity, and How the technical approach works.
• Task Granularity: Aim for no more than 1 story point per task. Tasks should be thin vertical slices completable within a sprint.
• Dependencies: Ensure logical sequencing (Database schema → API endpoints → Frontend components). Reference dependencies by their full task name.

Standard Tasks MUST include:

• Acceptance Criteria (4-6 items): Specific, testable, technical criteria covering core functionality, UI/UX (responsive, dark mode), and edge cases.
• QA Steps (5-8 items): Step-by-step procedures that a junior developer with zero project context could run. Include:
• Exact commands (e.g., pnpm dev, curl -X POST ...)
• Exact file paths or URLs (e.g., http://localhost:3000/dashboard)
• Exact tools to check (e.g., "Open TablePlus and verify 1 row", "Check Chrome DevTools > Network tab")
• Storybook states or specific UI elements to click.
• Exact expected results (e.g., '200 OK', specific error messages).

Manual Integration Tasks MUST include (if title ends with `[Manual]`):

• Instructions: Actionable setup steps (e.g., "Create OpenAI account", "Generate API key", "Add to .env.local"). Determine one explicit task per integration, and ensure the title appends [Manual].
• Notes (optional): Non-actionable guidance like cost estimates.
• Verification: 2-3 specific checks confirming setup success.

3. Create Cards via MCP Tools

Once the details are prepared or approved by the user, automate the creation of the cards physically on Trello using the context_todo_board MCP tools:

1. Create the Base Card:

• Use mcp_context_todo_board_add_card_to_list.
• Set the name to [Task ID] Title.
• Set the description to the verbatim sprint task description, appended with the Dependencies and Sprint Goal (if any).

1. Add Acceptance Criteria:

• Use mcp_context_todo_board_create_checklist (or the equivalent checklist tool) to add an "Acceptance Criteria" checklist to the card.
• Use mcp_context_todo_board_add_checklist_item to add each AC as a separate item.

1. Add QA Steps:

• Create a "QA Steps" (or "Instructions" & "Verification" for manual tasks) checklist.
• Use mcp_context_todo_board_add_checklist_item for every specific prescriptive testing instruction.

CRITICAL: Respect the original Sprint Assignment, Ordering, and Dependencies. Do not reorganize the sprint.

4. Verify and Confirm

After all task cards have been fully provisioned, provide the user with a summary of the created cards. Verify that all components (AC, QA steps, Descriptions) were attached successfully to each Trello card.