一键导入
designing-and-implementing
Use when receiving feature requests, architectural discussions, or multi-step implementation needs that require design before coding.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when receiving feature requests, architectural discussions, or multi-step implementation needs that require design before coding.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manages task lifecycle transitions including starting, completing, and blocking tasks with enforcement gates and Trello synchronization.
Manages feature planning workflow with provider-agnostic PM operations. Detects active provider and adapts commands accordingly.
Manages feature planning workflow including budget validation, task creation, and Trello synchronization.
Orchestrates the full branch-to-merge pipeline. Runs code review, surgical fixes, architecture simplification, test verification, security audit, PR submission, CI monitoring, and automated failure remediation in a single invocation. Integrates reviewing-code, implementing-with-tdd, architecting-modules, and finishing-branches skills into a nine-phase pipeline with a circuit-breaker-guarded CI remediation loop. Produces a green, merge-ready PR or a structured failure report.
Analyzes bpsai-pair review branch output by cross-referencing findings against actual code and task state. Classifies each finding as real blocker, bookkeeping-only, already resolved, or defer-to-next-sprint. Outputs a filtered report that becomes input to /draft-backlog, breaking the review-loop pattern.
Transforms a rough idea into a sprint-level structured brief for /draft-backlog. Operates only at sprint scope — cross-task dependencies, file collisions, Cx budget, priority ordering, and AC templates — never per-task implementation detail, which is /pc-plan's responsibility during engage. Uses bpsai-pair validate, budget, arch, and query tools at wider scope than /pc-plan uses them.
| 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"] |
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.
Present 2–3 options with pros/cons and recommend one.
bpsai-pair plan new <slug> --type feature --title "Title"
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)
bpsai-pair plan sync-trello <plan-id> --target-list "Planned/Ready"
bpsai-pair task update TASK-XXX --status in_progress.paircoder/plans/.paircoder/tasks/.paircoder/context/state.md.paircoder/context/project.mdbpsai-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