awow-workflows

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

Skills (22)

• artifact

  Use when the user asks for a deck, slides, a blog post, one-pager, or report as HTML or PDF — any styled document that should follow the team's house style instead of hand-written CSS.

• bet-refinement-coach

  Use for a live board session working one strategic bet through the full refinement arc — ground in the session record → ratify numbers → red-pen bars → battery-challenge changes → decide open calls one-by-one → log every decision → handover. Also the translate round: coaching the board block-by-bloc

• board-lifecycle

  Use when the board's project layer needs governing — projects without owners or end conditions piling up, nobody sure which containers are alive, or a planning round that needs a trustworthy project overview first. Declares shapes and horizons, sweeps the estate, and turns expiry into a visible exce

• 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.

• daily-checkin

  Use when the user recounts their day, points at a check-in note or voice memo, or wants the board to reflect today's work — end-of-day logging, standup prep, catching untracked work.

• daily-digest

  Use when the user asks what the team shipped today or this week, wants a daily or weekly digest written up and raised as a PR, or says they have no idea what other people are working on.

• department-coach

  The single home of the KR challenge battery — loaded by /okr-cascade (Refine, Review), /strategy-flow (Gate 2), and the bet-refinement-coach skill. Per-KR tests (outcome-not-output through gameability), objective-level tests (leading/lagging balance, commercial face), the admin-burden test for track

• design-system

  Use when the user wants one house style for the HTML they generate — asks to stand up or adopt a design system, points at a site or brand to derive tokens from, or says every deck looks different.

• handover

  Use when a session's work must survive it — the user asks for a handover, a resume prompt or a brief for another agent, says they are signing off, switching sessions, running out of context, or wants to pick this up tomorrow.

• kb-mine

  Use when the user asks what's worth writing down from a day's work, wants to backfill knowledge-base candidates for a past day, or says hard-won insight is evaporating unrecorded.

• kb-synthesize

  Use when mined knowledge candidates are piling up unpromoted, or the user asks to drain the KB inbox, review staged candidates, or fold recent learnings into the durable knowledge base.

• 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.

• okr-cascade

  Use when a department's quarterly OKR cascade needs attention — starting the quarter's objectives, refining key results, translating objectives into team PI-plan proposals, or reviewing drift and KR movement partway through the quarter.

• process-retro

  Use when the user points at or pastes a retrospective transcript or recording notes, or asks to turn a retro into named anti-patterns, owned actions, and diffs to their agent instructions.

• process-transcript

  Use when the user hands over a meeting transcript or recording notes (.vtt, .srt, pasted text), or asks to turn a meeting, standup, refinement, or stakeholder interview into board items.

• project-plan

  Use when a design is locked and decomposed but nothing says what blocks what — the user asks for build order, sequencing, a delivery plan, or a critical path, or just finished /solution-design-flow.

• refinement-prep

  Use when the user has a feature brief, quarterly slidedeck, or board issue and wants it broken into right-sized stories before a refinement session, or asks to prep work for the next refinement.

• setup-department

  Use when a department repo has no identity or OKR surface yet, or the user asks to stand up a department, register a team submodule, or scaffold the department's quarterly OKR doc.

• solution-design-flow

  Use when the user is weighing architectural or solution options, is about to lock a design decision, or points at a transcript of a design discussion — before the decision only exists in chat.

• strategy-flow

  Use when a team or department has a vision but no measurable goals yet — the user wants to name strategic bets and refine each into committed and aspirational KRs with baselines and dated targets, landed as a draft OKR set. Start-of-quarter, or whenever the strategy layer above the board is missing.

• team-workshop

  Use when a team wants to talk its way of working through and needs a meeting brief, or has the workshop transcript back to turn into team context proposals.

• 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