---
title: "feature-workflow"
description: "功能開發工作流: 以.spec/ 做本地規劃，涵蓋需求、DB、架構、實作、驗證、審查與結案。"
canonical: https://agentpluginsdirectory.com/plugins/feature-workflow
last-updated: 2026-10-05
---

# feature-workflow
功能開發工作流: 以.spec/ 做本地規劃，涵蓋需求、DB、架構、實作、驗證、審查與結案。
- Slug: feature-workflow
- Publisher: Cheng
- Repository: https://github.com/mark22013333/crew
- Manifest: plugins/feature-workflow/plugin.json
- Version: 5.0.5
- License: MIT
- Category (editorial): other
- Skills: 17 (plan-browse, plan-build, plan-close, plan-demo, plan-deploy-confirm, plan-drift, plan-explore, plan-next, plan-review, plan-security, plan-setup, plan-stack, plan-start, plan-status, plan-sync, plan-verify, plan)
- MCP servers: 0
- Stars: 9
- Repository created: 2026-03-11
- Repository last pushed: 2026-10-04
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/feature-workflow
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What feature-workflow does, in the publisher's words

跨 Host 的 Feature lifecycle：本地.spec/ 規劃、Human approval gates、正式實作、安全/驗證/review、Human UAT 與結案同步。核心 contract 不依賴單一 Host 的 team、subagent 或 provider model 名稱。

首次使用執行 /plan-setup；若 Bug workflow 也安裝，建議先跑 /bug-setup，Feature setup 可重用共用 Notion metadata。

若同時安裝 bug-workflow，可直接用統一入口：

- Intake Refiner：回答「使用者到底想做什麼？」；不產 AC、不做 DB/API/架構設計。
- Human：確認 refined intent；沉默不算核准。
- persistence 前若疑似含 credential，先要求 Human 提供 redacted 版本；不把 secret 寫進 cache / Notion / plan.md / state。
- Git repo 內建立 cache/state 前先確認.spec/ 已被.gitignore 保護。
- feature-spec-analyst：task 建立後才把 confirmed brief 工程化成 Goal / AC / Decisions / Risks。
- Notion「📋 需求描述」永久保存 raw original + confirmed refined brief；plan.md 只保留 refined brief。

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/mark22013333/crew/HEAD/plugins/feature-workflow/README.md