planning-with-trello
Use when planning features, organizing sprints, or syncing work with Trello boards.
Best use case
planning-with-trello is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Use when planning features, organizing sprints, or syncing work with Trello boards.
Use when planning features, organizing sprints, or syncing work with Trello boards.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "planning-with-trello" skill to help with this workflow task. Context: Use when planning features, organizing sprints, or syncing work with Trello boards.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/planning-with-trello/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How planning-with-trello Compares
| Feature / Agent | planning-with-trello | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when planning features, organizing sprints, or syncing work with Trello boards.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Trello-Aware Planning ## Board Structure (7 Lists Max) 1. **Intake/Backlog** - New ideas, not selected for work 2. **Planned/Ready** - Selected for upcoming work 3. **In Progress** - Active development 4. **Review/Testing** - Under review 5. **Deployed/Done** - Completed 6. **Issues/Tech Debt** - Bugs, improvements 7. **Notes/Ops Log** - Decisions, notes ## Card Title Format ``` [Stack] Task Name ``` Examples: `[CLI] Add MCP server`, `[Docs] Update README` ## Effort Labels | Size | Description | Complexity | |------|-------------|------------| | S | Few hours | 0-25 | | M | Half-full day | 26-50 | | L | Multiple days | 51+ | ## Stack Labels | Label | Use For | |-------|---------| | Frontend (green) | React, UI | | Backend (blue) | Flask, API | | Worker (purple) | Background jobs | | Bug/Issue (orange) | Bugs | | AI/ML (black) | Models, LLM | ## Workflow ### 1. Create Plan ```bash bpsai-pair plan new <slug> --type feature --title "Title" ``` ### 2. Add Tasks Break into 1-2 day units with acceptance criteria. ### 3. Sync to Trello ```bash # Preview bpsai-pair plan sync-trello <plan-id> --dry-run # Sync to Planned/Ready (recommended for sprints) bpsai-pair plan sync-trello <plan-id> --target-list "Planned/Ready" ``` ### 4. Execute Tasks Follow managing-task-lifecycle skill for starting/completing. ## Commands ```bash bpsai-pair plan list # List plans bpsai-pair plan status <plan-id> # Plan status bpsai-pair plan sync-trello <plan-id> # Sync to Trello bpsai-pair task list --plan <plan-id> # Tasks in plan ```
Related Skills
task-planning
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.
trello-automation
Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
planning
Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
research-driven-planning
Loop 1 of the Three-Loop Integrated Development System. Research-driven requirements analysis with iterative risk mitigation through 5x pre-mortem cycles using multi-agent consensus. Feeds validated, risk-mitigated plans to parallel-swarm-implementation. Use when starting new features or projects requiring comprehensive planning with <3% failure confidence and evidence-based technology selection.
planning-workflow
Jeffrey Emanuel's comprehensive markdown planning methodology for software projects. The 85%+ time-on-planning approach that makes agentic coding work at scale. Includes exact prompts used.
planning-the-escape
逃离计划 - 最终章,Stella必须决定是否修复飞船返回地球,还是留在盖亚,这是艰难的抉择
planning-sprints
Automatically activated when user mentions sprint planning, backlog refinement, iteration planning, sprint goals, capacity planning, velocity tracking, or asks to plan/start/close a sprint. Provides comprehensive sprint planning expertise using agile best practices.
project-planning
Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs/planning/ contains placeholder files, or when user requests project planning document generation.
planning-action
Use when the user asks for a roadmap, timeline, phased plan, or execution sequence.
roadmap-planning-expert
When the user asks about roadmap planning, sprint planning, milestone estimation, or capacity planning