| name | designing-and-implementing |
| description | Use when receiving feature requests, architectural discussions, or multi-step implementation needs that require design before coding. |
| skills | ["designing-and-implementing"] |
| agent-roles | ["navigator","driver"] |
Design → Plan → Implement
When to Use This Skill
Check if planning is needed:
bpsai-pair intent should-plan "user's request here"
Use this skill for: features, refactors, multistep work.
Skip planning for: typo fixes, small bugs, documentation tweaks.
Workflow
1. Clarify Requirements
- Restate the goal in 1–3 sentences
- Identify affected components
- Ask clarifying questions if ambiguous
- Research existing code patterns
2. Propose Approaches
Present 2–3 options with pros/cons and recommend one.
3. Create Plan
bpsai-pair plan new <slug> --type feature --title "Title"
4. Add Tasks
Resolve the per-task model before writing the file (MR3.2 — single-source
doctrine, calibration-aware):
bpsai-pair calibration recommend-model --task-type <type> --complexity <n> [--cross-module]
Task format in .paircoder/tasks/:
---
id: TASK-XXX
title: Task title
status: pending
priority: P0
complexity: 30
model: claude-sonnet-5
---
- What this accomplishes.
- [ ] Criterion 1
- [ ] Tests pass
- Requires TASK-YYY (if any)
5. Sync to Trello
bpsai-pair plan sync-trello <plan-id> --target-list "Planned/Ready"
6. Implement Each Task
bpsai-pair task update TASK-XXX --status in_progress- Write tests first (see implementing-with-tdd skill)
- Implement feature
- Complete via managing-task-lifecycle skill
Key Files
- Plans:
.paircoder/plans/
- Tasks:
.paircoder/tasks/
- State:
.paircoder/context/state.md
- Project context:
.paircoder/context/project.md
Commands
bpsai-pair plan list
bpsai-pair plan show <id>
bpsai-pair task list --plan <id>
bpsai-pair task next
