Communitygithub.com

Dev Cycle Orchestrator

编排完整的 GitHub Issues 驱动的开发生命周期。7 阶段流水线,从头脑风暴到 PR,带有状态跟踪和跨对话恢复能力。当用户提及“dev cycle”、“development workflow”、“full development pipeline”或调用 /dev-cycle 时使用。

Dev Cycle Orchestrator 是什么?

Dev Cycle Orchestrator 是一个端到端的开发生命周期管理技能,专为 AI 辅助开发环境设计(如 Claude Code、Cursor 等)。它通过一个强制性的 7 阶段流水线(头脑风暴→计划→CEO 审查→Issue→实现→代码审查→PR)来指导用户,确保每个步骤都不可跳过,并通过状态文件实现跨对话恢复。该技能集成 GitHub CLI 和 Issues,自动创建分支、管理 PR,并在实现阶段使用子代理和 TDD 模式。它还支持失败恢复、回退过渡(如从实现返回计划)以及完成后的归档。对于需要管理复杂、结构化开发工作流的团队或个人开发者来说,这是一个强大的工具。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cdcoonce/Portfolio_Website/tree/HEAD/.claude/skills/dev-cycle

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

Dev Cycle Orchestrator 是做什么的?

编排完整的开发生命周期:头脑风暴 → 计划 → 审查 → Issue → 实现 → 代码审查 → PR。

消歧义: 如果用户只需要 PRD,请路由到 /write-a-prd。如果只需要计划,请路由到 /prd-to-plan。此技能适用于完整的端到端生命周期。

7 阶段流水线

每个阶段都是强制性的。不得跳过任何阶段。

#阶段委托给门控条件
1头脑风暴write-a-prd记录 Issue URL
2计划prd-to-plan计划文件存在于 docs/plans/
3CEO 审查plan-ceo-review (建议 HOLD SCOPE)审查完成,用户批准
4IssueOrchestrator (计划切片 → GitHub Issues)记录所有 Issue URL
5实现Orchestrator (每个 Issue 使用 tdd,subagent-development)所有 Issue 解决,测试通过
6代码审查daa-code-review审查干净
7PRcommit + github-cli记录 PR URL

重新进入逻辑

每次调用时:

无参数 (/dev-cycle)

  1. 扫描 docs/dev-cycle/ 中所有 status: in_progress 的 *.state.md 文件
  2. 如果找到一个 → 询问:“是否恢复 {feature} ({branch})?当前位于 {phase}。”
  3. 如果找到多个 → 列出分支名,询问恢复哪个
  4. 如果没有 → 询问:“您正在开发什么功能?” → 启动阶段 1

带参数 (/dev-cycle {slug})

  1. 查找 docs/dev-cycle/{slug}.state.md
  2. 找到 → 在 current_phase 处恢复
  3. 未找到 → 创建状态文件,启动阶段 1

Slug 冲突

创建新状态文件时,检查 docs/dev-cycle/ 中是否已有该 slug。如果 slug 已存在(已放弃或已完成),则添加后缀 -2、-3 等。

恢复时的上下文加载

继续之前,加载所有引用的产物:

  • 头脑风暴: gh issue view 查看 PRD Issue
  • 计划: 从磁盘读取计划文件
  • CEO 审查: 读取计划文件(包含审查修改)
  • Issue: gh issue view 查看每个实现 Issue
  • 实现: 检查功能分支上的 git 状态,审查关闭的 Issue

呈现摘要:“正在恢复 {feature} 位于 {phase}。以下是上次中断的位置:...”

阶段执行

阶段 1:头脑风暴

调用 write-a-prd。信任该技能的内部流程(访谈 → PRD → GitHub Issue)。将 Issue URL 记录在状态文件中。

阶段 2:计划

将 PRD Issue URL 传递给 prd-to-plan。记录计划文件路径(位于 docs/plans/{feature}.md)。

阶段 3:CEO 审查

将计划文件路径传递给 plan-ceo-review。建议 HOLD SCOPE 模式,但让技能自己的模式选择(步骤 0F)运行。记录审查完成且用户批准的状态。

阶段 4:Issue

由编排器拥有。 读取计划的垂直切片。对于每个切片,使用 gh issue create 创建一个 GitHub Issue:

  • 引用 PRD Issue
  • 包含计划中的验收标准
  • 按依赖顺序创建

创建后立即将每个 Issue URL 记录在 Issues 表中。关于部分完成恢复,请参见 references/phase-transitions.md。

阶段 5:实现

由编排器拥有。 创建功能分支 feat/{feature-slug}(有关分支处理,请参见 references/phase-transitions.md)。

按照 subagent-development 方法,为每个 GitHub Issue 分派一个子代理:

  • 每个子代理调用 tdd 技能
  • 每次子代理分派之间运行代码审查
  • 每个子代理完成后更新状态文件(不批量)

记录每个子代理的事件:

  • “子代理 #N 已启动:{title}”
  • “子代理 #N 已完成:{pass/fail}”
  • “#N Issue 后的代码审查:{clean/blocking issues found}”

阶段 6:代码审查

对功能分支上所有更改的文件调用 daa-code-review。如果发现阻塞问题 → 修复,重新运行。循环直至干净。

如果架构问题需要重新制定计划 → 触发向后过渡至阶段 2。

阶段 7:PR

首先检查与默认分支的冲突。调用 commit 进行常规提交,然后调用 github-cli 提交 PR。记录 PR URL,设置 status: completed。然后运行归档步骤(参见下面的归档)。

状态文件

每个功能在 docs/dev-cycle/{feature-slug}.state.md 中追踪。有关完整格式、字段定义和过渡规则,请参见 references/state-file-schema.md。

失败与恢复

有关以下内容,请参见 references/phase-transitions.md:

  • 阶段重试逻辑(阻塞 → 下次调用重试)
  • 向后过渡(实现/代码审查 → 计划)
  • 功能放弃。归档的文件移至 docs/archive/。

分支管理

  • 阶段 1–4: 在当前分支上运行(仅文档)
  • 阶段 5: 创建 feat/{feature-slug} 分支
  • 阶段 7: 向默认分支提交 PR(通过 gh repo view --json defaultBranchRef 检测)
  • 在阶段 5+ 处恢复: 如果尚未在功能分支上,则切换过去

归档

当功能达到终止状态(completed 或 abandoned)时,归档其产物:

  1. 创建归档目录:mkdir -p docs/archive/dev-cycle docs/archive/plans
  2. 移动状态文件:git mv docs/dev-cycle/{slug}.state.md docs/archive/dev-cycle/
  3. 移动计划文件:从产物表读取计划路径,然后 git mv {plan_path} docs/archive/plans/
  4. 提交移动,使用消息:chore(dev-cycle): archive {slug}

归档自动运行:

  • 在阶段 7 结束时(记录 PR URL 并将状态设置为 completed 后)
  • 功能放弃时(将状态设置为 abandoned 后)

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

cdcoonce/Portfolio_Website

Git commit workflow with enforced conventional commit style. Use when Claude needs to stage and commit changes, craft commit messages, or the user asks to commit, make a commit, or save their work. Ensures consistent commit message format, proper scoping, and atomic commits across the project.

cdcoonce/Portfolio_Website

AI-powered code quality analysis for Python, Markdown, and Mermaid diagrams. Use this skill when: (1) reviewing code for quality issues, (2) checking Python files for PEP8 violations, unused code, missing type hints, docstring problems, complexity issues, or potential runtime errors, (3) validating Markdown documentation for broken links, heading structure, or formatting issues, (4) validating Mermaid diagram syntax, (5) the user asks for a "code review" or "quality check", (6) analyzing code snippets pasted in conversation, or (7) suggesting and applying fixes for code quality issues.

cdcoonce/Portfolio_Website

Deploy the portfolio chat agent Lambda function to AWS. Use when the user asks to deploy, redeploy, push to Lambda, update the chat agent, or after updating context files or lambda_function.py. Rebuilds the knowledge base, packages dependencies, and deploys to AWS Lambda.

cdcoonce/Portfolio_Website

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

cdcoonce/Portfolio_Website

Production Python coding standards with automatic version detection (3.10-3.13). Use when writing, reviewing, or refactoring Python to ensure adherence to modern type syntax, LBYL exception handling, pathlib operations, ABC-based interfaces, and production-tested patterns. Not Dagster-specific - applies to any Python project.

cdcoonce/Portfolio_Website

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

cdcoonce/Portfolio_Website

GitHub CLI (gh) integration for managing issues, pull requests, branches,

cdcoonce/Portfolio_Website

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

cdcoonce/Portfolio_Website

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

cdcoonce/Portfolio_Website

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when the user asks for a plan review, CEO review, mega review, or wants a plan challenged/stress-tested before implementation.

cdcoonce/Portfolio_Website

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

cdcoonce/Portfolio_Website

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in docs/plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

cdcoonce/Portfolio_Website

Generate or update the `.claude/docs/project.md` file that gives Claude project-specific context. Use this skill when the user asks to create, update, regenerate, or refresh project context, or says things like "update project.md", "generate project context", "this repo needs a project.md", or "Claude doesn't know about this project". Also trigger when onboarding Claude to a new repository for the first time.

cdcoonce/Portfolio_Website

Generate comprehensive, high-quality README.md files for code repositories. Use this skill whenever the user asks to create, write, generate, update, or improve a README for any project or repository. Also trigger when the user says things like "document this project", "write docs for this repo", "this repo needs a README", "help me onboard developers to this codebase", or asks for project documentation in markdown. Even if the user just says "README" or "readme" in the context of a codebase, use this skill.

cdcoonce/Portfolio_Website

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

cdcoonce/Portfolio_Website

Set up pre-commit hooks for the current repo. Use when user wants to add pre-commit hooks, configure commit-time linting, formatting, type checking, or testing. Triggers on "pre-commit", "git hooks", "linting hooks", or /setup-pre-commit.

cdcoonce/Portfolio_Website

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

cdcoonce/Portfolio_Website

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

cdcoonce/Portfolio_Website

Rewrites the prose sections of wiki pages in-place. Reads source files to understand current context, then updates only the content inside <!-- claude:prose --> ... <!-- claude:prose:end --> markers. Never touches <!-- generated:start --> ... <!-- generated:end --> blocks. Supports targeting a single page with /update-wiki {PageName}.

cdcoonce/Portfolio_Website

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

相关技能