Communitygithub.com

cdcoonce/Portfolio_Website

編排完整的 GitHub issues 驅動開發生命週期。從腦力激盪到 PR 的七階段管道,包含狀態追蹤與跨對話恢復。當使用者說「開發週期」、「開發工作流程」、「完整開發管道」或輸入 /dev-cycle 時使用。

Portfolio_Website 是什麼?

Dev Cycle Orchestrator 是一個完整的七階段開發生命週期協調技能,專為 AI 代理(如 Claude Code、Cursor、Codex)設計。它從腦力激盪階段開始,依次經歷規劃、CEO 審查、問題建立、實現、程式碼審查,最後到 PR 建立,所有階段均為強制性且不可跳過。此技能支援透過狀態檔案進行跨對話恢復,並可處理部分完成的情境,例如在實現過程中中斷後,下次啟動時能自動掃描 `docs/dev-cycle/` 目錄中的 `*.state.md` 檔案,判斷應從哪個階段繼續。此外,它還整合了 `write-a-prd`、`prd-to-plan`、`plan-ceo-review`、`tdd`、`subagent-development`、`daa-code-review` 等子技能,實現問題驅動的開發流程,並在每個階段記錄狀態,確保開發過程的可追溯性與可靠性。

相容平台~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

編排完整的開發生命週期:腦力激盪 → 規劃 → 審查 → 問題 → 實現 → 程式碼審查 → PR。

區別說明: 如果使用者只想要 PRD,請導向 /write-a-prd。如果只想要計畫,請導向 /prd-to-plan。此技能適用於完整的端到端生命週期。

七階段管道

每個階段都是強制性的。不得跳過任何階段。

#階段委派給閘門條件
1腦力激盪write-a-prdIssue URL 已記錄
2規劃prd-to-plan計畫檔案存在於 docs/plans/ 下
3CEO 審查plan-ceo-review (建議 HOLD SCOPE)審查完成,使用者批准
4問題Orchestrator (計畫切片 → GitHub issues)所有 Issue URL 已記錄
5實現Orchestrator (每個 issue 執行 tdd、subagent-development)所有 issue 已解決,測試通過
6程式碼審查daa-code-review乾淨審查
7PRcommit + github-cliPR 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 審查: 讀取計畫檔案(包含審查修訂版本)
  • 問題: 使用 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 階段:問題

由 orchestrator 擁有。 讀取計畫的垂直切片。為每個切片使用 gh issue create 建立 GitHub issue,該 issue 需要:

  • 引用 PRD issue
  • 包含計畫中的驗收標準
  • 按依賴順序建立

在建立後立即在 Issues 表格中記錄每個 issue URL。請參閱 references/phase-transitions.md 了解部分完成的恢復方法。

第 5 階段:實現

由 orchestrator 擁有。 建立功能分支 feat/{feature-slug}(請參閱 references/phase-transitions.md 中的分支處理)。

按照 subagent-development 方法為每個 GitHub issue 派遣一個子代理:

  • 每個子代理調用 tdd 技能
  • 程式碼審查在每次子代理派遣之間執行
  • 狀態檔案在每個子代理完成後更新(非批量)

記錄每個子代理的事件:

  • "為 Issue #N 啟動子代理:{title}"
  • "Issue #N 的子代理已完成:{pass/fail}"
  • "Issue #N 後的程式碼審查:{clean/blocking issues found}"

第 6 階段:程式碼審查

對功能分支上所有變更的檔案調用 daa-code-review。如果發現阻礙性問題 → 修正後重新執行。迴圈直到審查乾淨。

如果出現需要重新規劃的架構問題 → 觸發向後轉換至第 2 階段。

第 7 階段:PR

首先檢查與預設分支的衝突。調用 commit 進行 conventional 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.

相關技能