definition-of-done plugins

by Ravindra Kumar

Outcome-named autonomous fleets for the Orca runtime: each mission is one outcome with its own state machine and an evidence-backed definition of done. Missions compose best-of-breed worker recipes (mattpocock, gstack, addyosmani) over Orca — one router per worker. No vendor-named fleets. MIT.

by zot24

Run a control tower over a fleet of herdr agents — delegate every project task to a pane, dispatch from a spec file, watch a completion marker, staff only the required seats, and verify through acceptance gates so 'done' is an exit code, not a claim.

by MotionComplex

Specification & development toolkit built on the FZAG DXP Definition of Ready/Done. Three skills sharing one source-of-truth checklist file: spec (author a story/bug/feature spec to the relevant DoR as tool-agnostic markdown), check (audit any artifact against the matching DoR/DoD and report gaps), and promote (publish a markdown draft to an Azure DevOps work item or a Confluence spec page). Works without MCP (markdown in/out) and uses Atlassian/Azure DevOps MCP when present.

by Thong Phan

Turn committed, project-sized outcomes into evidence-backed rolling-wave plans after an explicit five-question intake.

by Luiz Tadeu Mendonça

The knowledge layer of a public agent-harness reference: 15 dense, opinionated engineering skills covering AWS infrastructure, React/Vite frontends, BFF-on-Lambda backends, CI/CD, the development loop and its quality gates. Written project-agnostically with <project> / <apex-domain> placeholders. This Power ships skills only — the harness's personas, permission hooks and merge gates are deliberately not exported.