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.
Use when planning features, organizing sprints, or syncing work with Trello boards.
Teams using planning-with-trello should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
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
sprint-planning-helper
Sprint Planning Helper - Auto-activating skill for Enterprise Workflows. Triggers on: sprint planning helper, sprint planning helper Part of the Enterprise Workflows skill category.
planning-disaster-recovery
Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".
analyzing-capacity-planning
This skill enables Claude to analyze capacity requirements and plan for future growth. It uses the capacity-planning-analyzer plugin to assess current utilization, forecast growth trends, and recommend scaling strategies. Use this skill when the user asks to "analyze capacity", "plan for growth", "forecast infrastructure needs", or requests a "capacity roadmap". It is also useful when the user mentions specific capacity metrics like CPU usage, memory, database storage, network bandwidth, or connection pool saturation. This skill is ideal for proactive infrastructure planning and preventing performance bottlenecks.
planning-oracle-to-postgres-migration-integration-testing
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.
gtm-enterprise-account-planning
Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
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.
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必须决定是否修复飞船返回地球,还是留在盖亚,这是艰难的抉择