kf

Plugin kf from marketplace kanban-flow in phuthuycoding/kanban-flow. Commands read from the repo's manifest — 2 days ago.

Skills (10)

• archive

  Close a PASS-reviewed feature or bug: kf status / kf sync close it once its PR is merged, kf archive is the explicit idempotent form. Features require a completion report (written at review PASS); living docs under docs/specs/ are edited in review and the close copies nothing under docs/. Use at rev

• brainstorm

  Kanban Phase 1 — brainstorm the feature requirement with the user, create the feature via `kf new`, and author phase-1-spec-requirement.md with FR-### anchors. Use when a kanban feature is at the brainstorm stage, or right after "kanban {context} {feature}" starts a brand-new feature.

• bug

  Kanban bug workflow — triage and document a defect with reproduction, expected/actual result, severity, root cause and regression coverage before handing off to kf:plan. Use when a work item has kind: bug.

• docs

  Consolidate a project's legacy docs snapshots (docs/requirement, docs/use-cases, docs/testplan) into the living docs under docs/specs, one context per run. Use when kf doctor lists "Legacy docs not consolidated" or the user asks to migrate or consolidate the docs.

• flow

  Drive a kanban feature or bug through brainstorm, planning approval, implementation, testing, review (PR + CI) and the close on merge using the kf CLI — one command, every gate, each delegated step leaving a named line. Use when the user requests the kanban workflow or resumes a work item managed in

• implement

  Implement an approved kanban feature or bug: run the subagent-driven task loop — per task a test-writer, a developer and an independent code-reviewer, a bounded fix loop and a ledger — then verify the build. Use in implementation — after `kf approve` started the item, an explicit start from backlog,

• plan

  Plan and obtain human approval for a kanban feature contract or lightweight bug triage contract; the approval starts the item, or parks it in backlog when the reply defers. Use when a work item is in planning.

• review

  Review a kanban feature or bug against its approved scope, current testing evidence and layered review rules: establish the facts mechanically, pick the review tier from the diff, dispatch independent code-reviewer agents, verify their evidence, and write PASS/FAIL/REQUIREMENT_BUG for the current ex

• spike

  Answer a question instead of changing the code, with no work item. Use for "can we…", "how long would…", "what does X return today" questions, for probing an API, a library or a setting, and for one-shot operations that land no code. Reports a recommendation, the sources and the exact commands run.

• travel

  Run the day as the controller of kanban-flow items: a morning plan from yesterday''s carry-over and kf status, each line T-shirt sized against a daily budget, human approval, then this session runs the phase skills of up to N started items, each in its own worktree, dispatching their seats in the ba