Agent Plugins Marketplace
← All plugins

dev-flow

一般程式語言專案的需求導向開發（TypeScript / JavaScript、Python、Go、Rust）：需求（必須達成，各有一句驗收）先講好，spike-impl 先用實作貫通一條垂直切片，scope-laws 對著跑得通的東西與開發者談 Law（不得違反），整個專案都該守的由 global-laws 經開發者批准抽成全域 Law（領域不變量、層、對外 I/O），build 帶 qa 與 refactor 兩個互不可見的角色讓每條 law 都有一條會失敗而現在通過的測試守著，integrate 是唯一發 PR 的出口；合進主線之後，上線與否從 git tag 推，線上壞了由 incident 在使用者手上的那一版重現、歸因到一條 law 再交棒。文檔住 .design/:system.md、requirements/、features/；進度一律由 CLI devflow 從程式碼與測試推導（status、release、lint、claim、brief、migrate）。skills:kickoff、require-design、global-laws、spike-impl、scope-laws、scope-revise、build、qa、refactor、integrate、incident、status、audit、study。

Claude Code14 Skills

By utomore0 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes
Claude Code
Parsed components
14 skill or MCP entries
Source updated
Sep 24, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install dev-flow for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev-flow-3@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/utomore/uto-skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/dev-flow/.

Plugin files

plugins/dev-flow/
├── .claude-plugin/plugin.json
├── skills/audit/SKILL.md
├── skills/build/SKILL.md
├── skills/global-laws/SKILL.md
├── skills/incident/SKILL.md
├── skills/integrate/SKILL.md
├── skills/kickoff/SKILL.md
├── skills/qa/SKILL.md
├── skills/refactor/SKILL.md
├── skills/require-design/SKILL.md
├── skills/scope-laws/SKILL.md
├── skills/scope-revise/SKILL.md
├── skills/spike-impl/SKILL.md
├── skills/status/SKILL.md
└── skills/study/SKILL.md

Included Skills14

auditskills/audit/SKILL.md

dev-flow(有 .design/ 的專案)的稽核:lint 與 status 的紅逐條分類(文檔錯還是程式碼錯)、需求與里程碑是否貼合、穩定度、安全度,產出「哪裡、什麼事、怎麼辦」表,不直接改契約。觸發詞:稽核、audit、健檢、對帳、文檔與程式碼對不上、安全檢查。Use when checking that .design and the code still agree and how healthy the project is.

buildskills/build/SKILL.md

dev-flow(有 .design/ 的專案)的建構指揮(conductor):對 ready 的文檔派 qa 寫測試、驗首跑、派 refactor 調整實作、仲裁紅燈,每條 law 成立才改 verified;目標也可以是 R-n 或 INV-n(只補那一條驗收測試)。觸發詞:build、建構、開工、跑這條里程碑、跑 feature、補驗收測試、委派開發。Use when ready documents should be turned into tests and law-abiding code, or an acceptance test is missing.

global-lawsskills/global-laws/SKILL.md

dev-flow(有 .design/ 的專案)全域 Law 落筆的地方。全域 Law 是從做出來的切片裡抽上去的:scope-laws 列的候選或開發者點名的一條既有 law,攤影響範圍、開發者明確批准才寫進 system.md「全域 Law」區,抽上去的 law 從原文檔搬走;之後的修改、放寬、替換、刪除同樣要批准、也只在這裡。觸發詞:全域 Law、抽上去、領域不變量、invariant、定層、對外 I/O、放寬全域 Law。Use when a Law from a finished slice should become a global Law, or a global Law must be changed, relaxed or removed.

incidentskills/incident/SKILL.md

dev-flow(有 .design/ 的專案)的事故入口:線上壞了、使用者回報了一件事,把現象整理成一組輸入與輸出,在使用者手上的那一版(devflow release 讀它上線在哪個 tag)重現,歸因到哪份 feature 的哪個 step 與哪條 law,照分流交給 scope-revise、scope-laws、global-laws 或 require-design;不寫測試、不改程式碼、不改文檔。觸發詞:事故、incident、線上壞了、使用者回報、bug report、production 出錯、重現、復現。Use when something broke for users and it must be reproduced, attributed to a law and handed to the skill that fixes it.

integrateskills/integrate/SKILL.md

dev-flow(有 .design/ 的專案)的整合,唯一發 PR 的出口:把達成的 build 分支合成一條,整套綠、每條 law 仍成立才發 PR;兩條線的 law 互斥時向開發者仲裁、寫 ADR;全域 Law 只提變更建議。觸發詞:發 PR、pull request、整合、integrate、合併分支、merge、仲裁、ADR。Use when finished branches should be merged, verified together and sent as a pull request.

kickoffskills/kickoff/SKILL.md

dev-flow 的立案,專案的第一個命令(還沒有 .design/ 的專案從這裡開始):建立 .design/ 的樹,與開發者訂願景、名詞表、Constraint(硬性限制,語言與版本、編譯器與執行環境、套件、環境、命名與寫法)、Constraint(三道指令)、模組表的骨架;Constraint 之後要補、要改也回這裡;不談需求也不談全域 Law,收尾自動接上 require-design。觸發詞:開新專案、立案、kickoff、建立 .design、專案願景、技術選型、限制、constraint、命名規範、寫法規範、模組表、補名詞表。Use when starting a new dev-flow project and creating its .design tree, vision, language, tooling and module table.

qaskills/qa/SKILL.md

dev-flow(有 .design/ 的專案)的 qa 角色,只由 build 的 conductor 委派(開發者要補測試走 build):只讀文檔與宣告,每條 law 一條 property test、每個 example 一條 example test,或一條需求驗收、領域不變量的測試;不讀實作本體。觸發詞:寫測試、qa、property test、性質測試、驗收測試。Use when translating laws and examples into tests without reading any implementation.

refactorskills/refactor/SKILL.md

dev-flow(有 .design/ 的專案)的 refactor 角色,只由 build 的 conductor 委派(開發者說測試紅了、要調實作,走 build 的仲裁,不直接用這一份):依文檔與紅燈歸因調整或重寫實作,直到每條 law 成立,假的換成真的;不碰測試與宣告。觸發詞:調整實作、重寫實作、refactor、讓 law 成立、把假的換成真的。Use when code must be adjusted or rewritten until a document's laws hold, without touching tests or declarations.

require-designskills/require-design/SKILL.md

dev-flow(有 .design/ 的專案)的需求設計:與開發者一次一條談需求(一句話、驗收、優先 1 到 4;用到的領域名詞先講定、寫進名詞表),當場切成有順序的里程碑 M-n-<slug>,每條是使用者看得到、展示得出來的階段,把既有的東西改快改好也是一條里程碑(綁既有的 feature,靠修訂達成);之後加需求、改驗收、重排、加里程碑也走這裡。觸發詞:需求、requirement、驗收、里程碑、milestone、優先、名詞的定義、這個功能為什麼做。Use when adding or reshaping requirements, their acceptance, priorities and milestones.

scope-lawsskills/scope-laws/SKILL.md

dev-flow(有 .design/ 的專案)談與調整 Scope Law 的地方。切片做完後根據決策紀錄把約束逐條談成 law,並列出該抽成全域 Law 的候選;既有的 law 要修改、放寬、替換、刪除只在這裡,一手做到 verified,含刪 step、重複的 step 改成引用、文檔退役。觸發詞:談約束、談 Law、切片做完、寫功能文檔、改既有的 law、放寬 law、刪 law、刪 step、文檔退役。Use when a finished slice needs its laws discussed, an existing law must be changed or removed, or a document is retired.

scope-reviseskills/scope-revise/SKILL.md

dev-flow(有 .design/ 的專案)的文檔修訂,既有的 law 一條都不動。改 verified 文檔的簽名、型別、模組與層,或做一條靠修訂這份文檔達成的里程碑(效能、大小這類實作品質,或新的承諾);可以新增 law,改完原有的每條 law 仍然綠、文檔仍是 verified;非調整既有的 law 不可就放棄,整件交給 scope-laws。觸發詞:改簽名、改介面、改型別、搬模組、效能調整、靠修訂達成的里程碑、重構已驗證的文檔、補保護用的 law。Use when a verified document's signatures, types, modules or implementation must change while every existing law stays unchanged.

spike-implskills/spike-impl/SKILL.md

dev-flow(有 .design/ 的專案)的切片:拿一條里程碑,在 build/M-n-<slug> 工作樹上用實作從入口貫通到出口,做出跑得通的垂直切片並留下決策紀錄;同時是可行性驗證,走不通也是答案。觸發詞:切片、spike、先做出來、貫通、做這條里程碑、可行性、試一下、PoC、prototype、原型。Use when a milestone should first be made to work end to end in code, before any feature document or law is written.

statusskills/status/SKILL.md

dev-flow(有 .design/ 的專案)的派工報告:跑 devflow status,用人話講每條需求達成了沒與它的里程碑走到哪、全域 Law 有沒有被踩到、今天能開幾條線、每條分支走到哪一步、卡住的與建議路線;可畫成看板。觸發詞:進度、狀態、status、今天做什麼、派工、還差什麼、哪些卡住、看板。Use when the developer asks where the project stands or what to do next.

studyskills/study/SKILL.md

dev-flow 的專案導讀:帶開發者由上而下讀懂一個專案,六層縮放(全景 → 架構 → 理念 → 資料結構 → trace → 細讀),每個結論附 檔案:行號 的原文,一次一課。觸發詞:study、理解專案、導讀、帶我看 code、trace code、熟悉專案、onboarding。Use when guiding a developer through an existing codebase top-down with code evidence.

Plugin manifests1

plugins/dev-flow/.claude-plugin/plugin.json
{
  "name": "dev-flow",
  "description": "一般程式語言專案的需求導向開發（TypeScript / JavaScript、Python、Go、Rust）：需求（必須達成，各有一句驗收）先講好，spike-impl 先用實作貫通一條垂直切片，scope-laws 對著跑得通的東西與開發者談 Law（不得違反），整個專案都該守的由 global-laws 經開發者批准抽成全域 Law（領域不變量、層、對外 I/O），build 帶 qa 與 refactor 兩個互不可見的角色讓每條 law 都有一條會失敗而現在通過的測試守著，integrate 是唯一發 PR 的出口；合進主線之後，上線與否從 git tag 推，線上壞了由 incident 在使用者手上的那一版重現、歸因到一條 law 再交棒。文檔住 .design/:system.md、requirements/、features/；進度一律由 CLI devflow 從程式碼與測試推導（status、release、lint、claim、brief、migrate）。skills:kickoff、require-design、global-laws、spike-impl、scope-laws、scope-revise、build、qa、refactor、integrate、incident、status、audit、study。",
  "author": {
    "name": "utomore"
  },
  "homepage": "https://github.com/utomore/uto-skills"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[dev-flow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev-flow-3)