---
title: "kc-dev-flow"
description: "Profile-native POC, Pilot, and Production delivery routes with a minimal shared authority core."
canonical: https://agentpluginsdirectory.com/plugins/kc-dev-flow
last-updated: 2026-10-21
---

# kc-dev-flow
Profile-native POC, Pilot, and Production delivery routes with a minimal shared authority core.
- Slug: kc-dev-flow
- Publisher: Kent Chen
- Repository: https://github.com/iamcxa/kc-claude-plugins
- Manifest: kc-dev-flow/plugin.json
- Version: 4.6.0
- License: MIT
- Category (editorial): productivity
- Skills: 6 (adopt-dev-flow, chief-engineer, choose-work-profile, continue-dev-flow, science-officer-em, science-officer)
- MCP servers: 0
- Stars: 3
- Repository created: 2026-03-09
- Repository last pushed: 2026-10-21
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/kc-dev-flow
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What kc-dev-flow does, in the publisher's words

Load development constraints in proportion to work risk, so agent behavior is just sufficient without losing verification or authority boundaries.

KC Dev Flow supplies one minimal authority core and three profile-native delivery routes. A repository may bind a planning provider, while its workflow runtime and delivery provider remain local. The design rationale records the observed pain, trade-offs, directional evidence, and conditions that would falsify this direction.

An item leaves backlog only after its required brief is admitted. Scheduling metadata is optional; it activates provider reconciliation when present.

- Development Brief: required for Pilot and Production; contains the problem, accepted outcome, complete non-goal list, route-back conditions, and one canonical ## Acceptance criteria section with concrete, unique, ascending AC-N bullets for new admission. Already-admitted prose is not migrated or rewritten.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/iamcxa/kc-claude-plugins/HEAD/kc-dev-flow/README.md

## Skills

- adopt-dev-flow: Audit, adopt, or upgrade profile-native kc-dev-flow in a brownfield repository while preserving any existing planning provider, local execution grouping, workflow runtime, and delivery provider.
- chief-engineer: Advise the next smallest integrated delivery step when an approved development route is unclear, blocked, drifting, or approaching a material transition. Use for normal delivery guidance; do not use as a mandatory stage review or independent assurance gate.
- choose-work-profile: Recommend and ask the Captain to choose POC, Pilot, or Production before a work item enters its first working stage, or when an observed promotion trigger makes the committed profile stale.
- continue-dev-flow: Resume an adopted repository's approved work through its selected POC, Pilot, or Production route while loading only the shared core and selected profile-stage contract.
- science-officer-em: Compatibility alias for callers that explicitly request the legacy science-officer-em report envelope. New delivery guidance uses chief-engineer; new independent technical assurance uses science-officer.
- science-officer: Provide independent technical assurance for a contested, high-risk, hard-to-reverse, or low-confidence engineering claim. Use when the Captain or First Officer needs an evidence-bound second judgment; do not use for routine delivery guidance or as a mandatory stage gate.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.