task-funnel

Plugin task-funnel from marketplace task-funnel in gabrielbsandim/claude-kit. Commands read from the repo's manifest — 27 days ago.

Skills (5)

• backlog

  Grooms an open backlog before the next task is picked: finds issues that are the same work, adopts orphans into the epic they belong to, and proposes what can ship in one pull request. Read-only until the user approves each move. Use when the board feels like it only grows, before planning a sprint

• investigate

  Investigation flow. Takes a question about the system (why does X happen, where does Y live, is Z feasible, what broke) and returns a verified written answer with evidence. Read-only end to end, no branch, no code change, no pull request. Use when asked to investigate, diagnose, explain behaviour or

• note

  Writes one durable fact into a markdown knowledge vault, with the frontmatter and the provenance that keep it checkable, then reindexes so search can find it. Use when something learned in a session has to outlive it, or on /note <the fact>, and not for what the repo already records.

• ship

  Takes work that is already implemented and committed on a branch and ships it: runs the repo's ship gates off receipts, pushes, opens a draft pull request, moves the board to in review, and removes the worktree. Use when the code exists and the task is to get it reviewable, or on /ship, and not when

• task

  Delivery funnel for one repository task: a feature, bug fix, refactor or chore. Takes a task description or issue number and runs triage and spec, implementation, tests and a scoped adversarial review, ending in a pushed branch and a draft pull request with the board moved. Every path, gate command

Slash commands (2)

• /task-funnel:backlog

  Groom the open backlog: what is the same work, what is an orphan, and what can ship in one pull request

• /task-funnel:setup

  One-time setup for task-funnel in this environment, then a per-repo config check

Subagents (5)

• funnel-implementer

  Stage 2 of the task funnel. Writes the change inside an existing worktree against a spec it must not renegotiate, runs the repo's own gates through kit, and commits. Invoked by the task skill, not directly.

• funnel-reviewer

  Stage 4 of the task funnel. Reviews one already-written diff slice against a numbered multi-part contract, one part per lens, and returns findings graded Critical, Important or Minor with CONFIRMED or PLAUSIBLE. Reads the diff file it is given and does not run git. Invoked by the task skill, not dir

• funnel-screen-lens

  Stage 4 of the task funnel, browser half. Opens the screens a change touched in a real browser and answers two numbered parts from one visit: whether the feature works, and whether the interface can be used. Returns findings graded Critical, Important or Minor. Reads the route list it is given and n

• funnel-test-writer

  Stage 3 of the task funnel. Writes tests for a change it did not implement, from the spec and the list of files that changed, then runs the repo's test gate through kit and commits. Invoked by the task skill, not directly.

• funnel-triage

  Stage 1 of the task funnel. Read-only. Judges whether a task is real, then writes the dispatch spec for it in the same pass. Returns a structured verdict, effort level, file scope, acceptance criteria and invariants. Invoked by the task skill, not directly.

Hooks (2)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/guards.py"

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/guards.py"

Similar plugins