designing-and-implementing

BPSAI's avatarfrom BPSAI

Use when receiving feature requests, architectural discussions, or multi-step implementation needs that require design before coding.

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025

When & Why to Use This Skill

This Claude skill facilitates a structured 'Design → Plan → Implement' workflow for complex software engineering tasks. It bridges the gap between high-level feature requests and actual coding by enforcing a rigorous architectural discussion and planning phase. By utilizing systematic task breakdowns and project management integration, it ensures that multi-step implementations are well-architected, documented, and executed with clear acceptance criteria.

Use Cases

  • Complex Feature Development: Transforming ambiguous user requirements into a concrete technical design and a prioritized list of actionable tasks.
  • Architectural Refactoring: Evaluating multiple technical approaches for system changes, comparing pros and cons, and planning the migration steps before writing code.
  • Multi-step Implementation Management: Breaking down large-scale coding projects into granular sub-tasks with defined dependencies and complexity scores to maintain development momentum.
  • Project Management Synchronization: Automatically syncing local development plans and task statuses with external tools like Trello to keep stakeholders informed and maintain a single source of truth.
namedesigning-and-implementing
descriptionUse when receiving feature requests, architectural discussions, or multi-step implementation needs that require design before coding.

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

Task format in .paircoder/tasks/:

---
id: TASK-XXX
title: Task title
status: pending
priority: P0  # P0=must, P1=should, P2=nice
complexity: 30  # 10-100 scale
---

## Objective
- What this accomplishes.

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Tests pass

## Dependencies
- Requires TASK-YYY (if any)

5. Sync to Trello

bpsai-pair plan sync-trello <plan-id> --target-list "Planned/Ready"

6. Implement Each Task

  1. bpsai-pair task update TASK-XXX --status in_progress
  2. Write tests first (see implementing-with-tdd skill)
  3. Implement feature
  4. 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              # List plans
bpsai-pair plan show <id>         # Show plan details
bpsai-pair task list --plan <id>  # Tasks in plan
bpsai-pair task next              # Next task to work on