No longer maintained; use kc-dev-flow-2. Profile-native POC, Pilot, and Production delivery routes that load one minimal authority core plus only the selected stage contract in Claude Code or Codex
3 on GitHubby Kent Chenv4.6.0MITupdated 2 days ago
/
Plugin kc-dev-flow from marketplace kc-claude-plugins in iamcxa/kc-claude-plugins. Commands read from the repo's manifest — 2 days ago.
What it installs
Skills (6)
adopt-dev-flow
Audit, adopt, or upgrade profile-native kc-dev-flow in a brownfield repository while preserving any existing 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.
Subagents (2)
chief-engineer
Use when a kc-dev-flow route is unclear, blocked, drifting, or approaching a material transition and the Captain wants the next smallest integrated delivery step. Not a stage review and not an assurance gate.
science-officer
Use when the Captain or First Officer needs independent technical assurance on a contested, high-risk, hard-to-reverse, or low-confidence engineering claim in kc-dev-flow work. Not a mandatory stage gate; routine delivery advice belongs to chief-engineer.
Team operations pipeline — EM triage with strategic lens (depth-adaptive routing, team context cache), project pulse updates, codebase exploration, issue decomposition, structured Linear management, EM plan/project review (keystone verification + cross-model pressure-test), and on-demand cross-model second opinion via Google's agy / Antigravity CLI (/gemini review|challenge|consult)
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
Cedar policy enforcement + Ed25519 signed receipts for every Claude Code tool call. First cryptographic governance plugin — decisions are policy-gated before they run and every decision produces a tamper-evident receipt verifiable offline.
Evidence-backed BioPharma research workflows over Maven Bio's drug, trial, company, and deal knowledge graph. Skills for competitive pipelines, indication landscapes, asset profiles, deal and financing activity, and evidence synthesis grounded in FDA, SEC, clinical, and press sources. Requires a Maven Bio account.
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, live Q&A and polls, and more.
18 skills · 11 commands
phuryn/pm-skills 27,939
Maintain kc-dev-flow?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.