andreifinogeev/weft-tasks

Turn a vague request into a task someone can actually finish and verify, put it on the user's Weft board (letsweft.com), and close it with proof. Use whenever work is being captured or planned — "add a task", "put this on my board", "plan this", "break this down", a pasted list of work to import — or when the ask is a wish with no defined finished state, like "I need a landing page", "write the investor update", "redo pricing", "find a contractor". Use again when finishing a task the board is tracking, so it closes on a named artifact instead of a claim. Runs a one-turn interview of at most three questions, often none, then writes a Done-when acceptance checklist instead of a paragraph, picks the single executor, and sizes or splits the work. Covers non-code work — marketing, sales, hiring, finance, personal — as much as code. Works with the Weft MCP server connected, and degrades to a copy-pasteable brief when it is not.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/andreifinogeev/weft-tasks

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.