writing-pack
claudeFour skills for writing that people and agents can use: plain-language user copy, architecture decision records, developer guides, and clarifying questions before work starts
4 skills
The /flow workflow engine: a PM-agnostic, dual-mode (manual and autonomous) system that carries product work from capture to done across one stage spine, with a runnable-TypeScript engine and a pluggable tracker adapter.
Plugin flow from marketplace dorkos in dork-labs/marketplace. Commands read from the repo's manifest — 2 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
fake-adapterThe fake tracker flow's self-test runs against. An in-memory tracker in a JSON file, behind the code adapter contract. It reaches no real tracker.
linear-composio-adapterReference tracker adapter for /flow - Linear reached over the Composio CLI. A concrete, forkable realization of the adapter contract (../../SPEC.md) built on `composio execute LINEAR_*` calls. Implements all 16 required capability verbs plus the optional completeProject, and normalizes Linear into t
linear-mcp-adapterReference tracker adapter for /flow - Linear reached over an in-session MCP server. A concrete, forkable realization of the adapter contract (../../SPEC.md) built on the Linear MCP tools (the mcp__linear__* / mcp__plugin_linear_linear__* family). Implements all 16 required capability verbs plus the
building-adaptersGuided procedure for generating and verifying a concrete /flow tracker adapter that conforms to the adapter contract. Use when building, porting, or scaffolding a tracker adapter for a new tracker (Jira, GitHub Issues, or another), or when /flow:init must produce one for an adopter. Teaches the gene
capturing-workThe /flow engine's CAPTURE stage — quick, low-commitment intake of a new piece of work into the tracker as an idea, without doing full triage or evaluation. Use when the goal is to get a thought captured cleanly so it survives, not to assess, classify deeply, or plan it. Generalizes the legacy /line
closing-workThe /flow engine's DONE stage — report completion on a work item, move it to Done with the agent/completed label, create any follow-up work, run a project pulse check for the next loop action, and clean up the worktree. Use when running /flow:done or advancing an approved work item into the DONE sta
decomposing-workThe /flow engine's DECOMPOSE stage — break a validated specification into actionable tasks in 03-tasks.json, mirror the active phase into the tracker as a plan checklist, project the stage/decompose label, then hand the item on at stage/execute. Use when running /flow:decompose or advancing a work i
executing-specsOrchestrates parallel implementation of decomposed specifications with incremental progress tracking. Use when running the /flow:execute stage (the EXECUTE stage of the /flow engine).
flow-drainClaim the top-ranked eligible issue and carry it to its review gate.
flow-groomScheduled read-only backlog health check — run the groom oracles and report, never write.
flow-retroScheduled weekly retro — measure how flow's own runs went and file up to five concrete fixes to flow, never ready.
flow-triageScheduled daily triage — ready or park every untriaged item, and release claims nobody has touched for a week.
grooming-backlogThe /flow engine's backlog GROOM — a whole-backlog corrective sweep that makes the configured team's backlog honestly dispatchable. Audits every open item against the fifteen groom invariants, closes shipped/duplicate/junk work with cited evidence, reconciles projects with the repo's real programme
ideating-featuresTurns a feature brief, rough notes, or an existing partial design into a structured ideation artifact and next-step plan. Use when the user wants to explore a feature or shape rough requirements into a structured ideation artifact.
initializing-flowFirst-run setup for the /flow engine in a new repo - detect or reconfigure an existing install, gather setup choices (tracker + connection, identity mode, project routing, adversarial review, model tiers) via the calibration ladder, generate and verify the concrete tracker adapter, scaffold the comm
linear-adapterThe /flow engine's tracker adapter — the single skill that owns EVERY Linear MCP / Composio call and normalizes Linear into the generic WorkItem shape. Use whenever a /flow stage skill or the loop engine needs to read or write the tracker (claim, transition, comment, inbox, relations, evidence, sub-
specifying-workThe /flow engine's SPECIFY stage — turns a validated ideation artifact into an implementation-ready specification, resolves its open decisions, and seeds draft ADRs. Use when work is ready to move from IDEATE to a frozen spec. PM-agnostic; all tracker I/O routes through the adapter skill.
tending-trackerThe /flow engine's agent-as-team-member loop — the agent participates in a shared tracker like a teammate. Each tick it polls its inbox, decides respond/act/ignore per the five comment-response rules, claims work with durable agent/* labels, asks the human via comment+assign when genuinely stuck (so
triaging-workThe /flow engine's TRIAGE stage — classify and route incoming work. Classifies a freeform brief/idea/bug/question into the right work-item type, or evaluates an already-captured item (accept/reject/needs-research/needs-refinement) and routes it simple-vs-complex (stay-in-tracker task vs escalate to
verifying-workThe /flow engine's VERIFY stage — trace recent work for correctness, run the verification gate, put the branch through an independent adversarial review before any PR opens, gather proof-of-completion scaled to the change, attach it to the work item under a deliberately chosen closing or non-closing
/flow:captureCapture a thought as a low-commitment work item (the /flow CAPTURE stage)
/flow:decomposeRun the DECOMPOSE stage — break a validated spec into tasks and mirror them into the tracker
/flow:doneRun the DONE stage — report completion, close the work item, and check project follow-ups
/flow:executeRun the EXECUTE stage — implement a validated spec by orchestrating concurrent agents
/flow:flowThe /flow engine — route stages, advance work or drain the ready queue.
/flow:groomGroom the whole backlog — audit, correct, and verify it against the dispatch contract (check = read-only report)
/flow:ideate/flow IDEATE stage — shape a brief into a structured ideation artifact
/flow:initFirst-run setup for /flow - pick your tracker, generate its adapter, and scaffold config
/flow:pauseHalt every autonomous /flow mode from one place (drain sentinel + pause flag)
/flow:resumeRestore autonomous /flow operation that /flow:pause halted
/flow:self-testCheck this flow install, its prose and how its commands behave, and report what is broken
/flow:specify/flow SPECIFY stage — turn an ideation artifact into a validated specification
/flow:statusShow every in-flight item, parked question and drift across the /flow loop, plus this project's flow schedules
/flow:triageClassify and route incoming work, simple-vs-complex (the /flow TRIAGE stage)
/flow:verifyRun the VERIFY stage — verify recent work, gather proof, and hand off to the review gate
cd "$(git rev-parse --show-toplevel)" && node "${CLAUDE_PLUGIN_ROOT}/hooks/flow-loop.mjs"
node --experimental-strip-types "${CLAUDE_PLUGIN_ROOT}/scripts/flow.ts" limit-check --hook
Four skills for writing that people and agents can use: plain-language user copy, architecture decision records, developer guides, and clarifying questions before work starts
4 skills
Label throwaway containers, VMs and sandboxes, and sweep them from the next run: exit handlers do not survive a kill
1 skill
Guides AI agents through developing, validating, and publishing DorkOS marketplace packages
1 skill
Three guards that stop an agent's shell commands from destroying work: no stash or discarding checkout, no killing processes by name, and no reading or writing files your settings deny
hooks
Your agent shows you screens, mockups and clickable prototypes beside the chat. Pin a note on the exact spot you want changed, press Send, and it gets to work. It runs on this computer only, with no share or guest links. Any page this renders can message the agent that owns it. Don't open pages you don't trust.
1 skill
Your Linear issues on the dashboard. After you approve its schedule, the agent checks your Linear inbox every 15 minutes.
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.
12 skills · 1 MCP server · hooks
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
AI-supervised issue tracker for coding workflows
1 skill · 1 agent · hooks
PRD generation and conversion skills for the Ralph autonomous agent loop
2 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.