kc-dev-flow-2

Plugin kc-dev-flow-2 from marketplace kc-claude-plugins in iamcxa/kc-claude-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (12)

• 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.

• design-director

  Run the design review of one ui task's pictures, rule on each decline the author or validator proposes, rule on a release walk's merged complaints, and read the product's accepted design rulings first. Use at ideation and validation of a task whose Surfaces include ui, and on a release walk; advises

• dev

  Start or resume kc-dev-flow-2 work by resolving the project, task, approved profile and scope, then handing orchestration to Spacedock First Officer.

• engineering-reviewer

  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.

• evaluate-learning

  Evaluate explicitly supplied closed-task evidence for conditional project learning; record local add, no-change or remove proposals without activating rules or changing workflow state.

• ideation

  Author a profile-routed design definition for a dispatched kc-dev-flow-2 ideation stage; POC explicitly skips this stage.

• implementation

  Implement the accepted outcome for a dispatched kc-dev-flow-2 task using its recorded profile and stage references.

• learn

  Complete a named task's learning loop, by hand or at archive through the learn extension, from verified SD closure and original merged PR through independent evaluation, optional reviewed learning.md Draft PR, and durable local notices.

• maintain-flow

  Maintain the kc-dev-flow-2 static stage skills, profile references and the adopted workflow template (references/sd/workflow.md), keep them from only growing, and check declared routing without executing a development workflow.

• observer

  Independently read what the First Officer wrote into one task's state against the workflow rules it owns, and report each finding with the quoted rule and quoted evidence. Use at task archive through the learn extension, or when a maintainer reads an adopter's first task after a release; not a stage

• read-adr

  Use before you decide anything an earlier ruling (an ADR) may govern, when a task or message cites a ruling by repository, path, commit and digest, and before you write down something a person told you (a decision, limit, preference or deferred idea). Teaches reading an ADR at an exact commit with g

• validation

  Validate a dispatched kc-dev-flow-2 outcome against its recorded profile, exact artifact and accepted evidence boundary.

Subagents (4)

• chief-engineer

  Use when a kc-dev-flow-2 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.

• design-director

  Use when a kc-dev-flow-2 ui task needs its design review run, its proposed declines ruled on, or the screenshots of its built screen reviewed, or when a release walk's complaints need ruling. Advises and holds no gate; not a stage review of code.

• engineering-reviewer

  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-2 work. Not a mandatory stage gate; routine delivery advice belongs to chief-engineer.

• observer

  Use when a kc-dev-flow-2 task is archived (learn extension) or a maintainer reads an adopter's first task after a release, to check what the First Officer wrote into task state against the workflow rules. Read-only; not a stage review and not a repair.

Similar plugins