awow — Agentic Way of Working

Plugin awow in CauchyIO/awow-dist. Commands read from the repo's manifest — 17 days ago.

Skills (9)

• awow-help

  Use when the user asks what awow can do here, what a command does, what to run next, or has just installed the plugin and does not know where to start.

• board-target

  Use before any board read or write, or whenever a command names the board, to settle which awow installation and which board you are acting on — including when board.md is missing or names several boards.

• knowledge-source-routing

  Use when a task reads shared ANCHOR context, mentions another repository or external knowledge system, or may capture durable knowledge whose canonical source could be elsewhere.

• my-work

  Use when the user asks what they should work on, what is pending or waiting on them, or says they have lost track of the board and want to get oriented before starting a block of work.

• process-workitem

  Use when the user points at a board item — a ticket ID, issue link, or “let's pick up X” — and wants it explained, refined, planned, or carried through a code change to an opened PR.

• setup-awow

  Use when a repo needs awow set up or repaired: connect its board, anchor it to a team's shared repo, join a configured repo on a new machine, or check what is wired.

• update-context

  Use when a session is wrapping up — a commit, a PR, a sign-off — and the user stated a durable rule about how the team works, so it lands in the context tree.

• using-awow

  The awow operating reflex, injected at session start: board-first discipline, the approval gates, and the route from each work moment to its awow command. Read it to recall how awow expects an agent to work.

• workitem-write

  Use for any board item create or update — an ad-hoc make-a-ticket request or a flow's write step. The one convention-wired path: resolve the target, look first, cite conventions, shape, gate, write, report.

Similar plugins