boyle

Use before any creative work, when the user says "let's brainstorm", wants to think through options, describes a vague or ambitious feature request, asks what to build, presents a problem with multiple valid solutions, or seems unsure about scope or direction. Triggers: brainstorm, 头脑风暴, 设计讨论, think through, explore idea.

CE workflow retrospective with six-dimension analysis. Use when reviewing a completed or partially completed /run-ce-workflow task for dispatch accuracy, workflow friction, and skill/agent effectiveness. Triggers: /ce-session-retro, session retro, CE 复盘, 工作流复盘, workflow retro.

Enhance an existing plan with parallel research and review agents to add depth, best practices, and implementation details. Use when a plan needs more detail, when audit finds plan insufficiency, or when the user says "deepen plan", "enhance plan", 深化计划, 增强计划, 补全计划.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Triggers: parallel agents, dispatch subagents, independent failures, multiple test files, 并行任务, 分派子代理.

Review requirements or plan documents for quality, coherence, and completeness. Use when a requirements document or plan document exists and the user wants to improve it. Triggers: review doc, requirements review, plan review, 文档审查, brainstorm review.

Use when an implementation plan exists, task status is execute, or the user says execute plan, run tasks, or 执行计划. Triggers: execute plan, run tasks, 执行计划, 开始实现.

Use when implementation is complete and all tests pass. Triggers: "ship it", "发布", "merge branch", "open PR", "discard branch", Stage 9.

Grounded improvement idea generation for the current project. Use when asking what to improve, requesting idea generation, exploring surprising improvements, or wanting proactive project direction suggestions. Triggers: 'what should I improve', 'give me ideas', 'ideate on this project', 'surprise me', 'what would you change', 改进建议, 想法生成.

Use when reviewing code changes before creating a PR. Triggers: code review, 代码审查, review my code, review this branch, review this PR.

Structured engineering workflow orchestration. Use when starting or resuming a development task via the stage-based workflow. Triggers: /run-ce-workflow, task YAML, 开始任务, 恢复任务.

Use when starting the compound engineering workflow for the first time or reconfiguring review agent selection. Triggers: first setup, reconfigure agents, compound-engineering.local.md.

Use when executing implementation plans with independent tasks in the current session. Triggers: multi-task impl plan, independent tasks, same session, parallel implementation, 子代理开发, subagent development.

Use when encountering any bug, test failure, build failure, or unexpected behavior. Triggers: error, crash, test failure, build failure, unexpected output.

Use when implementing any feature, fixing any bug, or when the task file status is tdd. Triggers: new feature, bug fix, TDD stage, test-first.

Use when task status is verify (Stage 10) or when explicit verification is needed after code changes. Triggers: post-ship, verify stage, evidence collection.

Use when the user says "plan this", "create a plan", "write a tech plan", "how should we build", or when a brainstorm or design doc is ready for technical planning. Triggers: plan this, create a plan, write a tech plan, 架构规划, arch plan, 技术方案.

Use when the user says "plan the implementation", "write impl plan", "break this down into tasks", or when an architecture plan is ready for implementation planning. Triggers: plan the implementation, write impl plan, break this down, 实现计划, 拆分任务, impl_plan.

Address PR review comments via gh CLI. Use when your human partner says "处理评论", "fix PR comments", "回复review", "address review feedback", or explicitly references @address-pr-comments or /address-pr-comments.

Resolve git rebase conflicts through deep analysis, commit history tracing, and merge recommendations. Use when your human partner says "解决冲突", "rebase 冲突", "fix conflict", or explicitly references @fixing-rebase-conflict or /fixing-rebase-conflict.

Commit local changes and publish as a GitHub PR with automated interaction handling. Use when your human partner says "发PR", "提交并发布", "publish PR", or explicitly references @publishing-pr or /publishing-pr.

Request PR reviewers based on personal config. Use when the user says "拉人review", "request reviewers", "加reviewer", or explicitly references @request-reviewers or /request-reviewers.

Split large PRs into smaller, focused PRs and publish each independently. Use when your human partner says "拆分PR", "split PR", "PR太大", or explicitly references @splitting-pr or /splitting-pr.

Create isolated git worktrees for parallel development. Use when starting feature work, splitting PRs, working on a hotfix, 创建工作树, 隔离工作区, git worktree, isolated workspace, or before executing implementation plans.

the project Cursor SKILLS Best Practice. Use when writing or reviewing a SKILL.md file in Cursor, designing skill structure, choosing Rules vs Skills, writing description fields, avoiding anti-patterns. Triggers: write skill, review skill, SKILL.md, skill description, 反模式, skills best practice, skills vs rules.