The optional workflow bundle for awow: design and planning, meetings and retros, digests, strategy and OKRs, knowledge capture, and styled documents. Installs beside awow; self-contained, and expects a repo configured by awow's /setup-awow.
Plugin awow-workflows from marketplace awow in CauchyIO/awow. Commands read from the repo's manifest — 17 days ago.
bet-refinement-coachUse 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-targetUse 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-checkinUse 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.
department-coachThe 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
knowledge-source-routingUse 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.
process-transcriptUse 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-planUse 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.
workitem-writeUse 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.
/awow-workflows:artifactUse 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.
/awow-workflows:board-lifecycleUse 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
/awow-workflows:daily-checkinUse 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.
/awow-workflows:daily-digestUse 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.
/awow-workflows:design-systemUse 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.
/awow-workflows:handoverUse 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.
/awow-workflows:kb-mineUse 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.
/awow-workflows:kb-synthesizeUse 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.
/awow-workflows:okr-cascadeUse 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.
/awow-workflows:process-retroUse 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.
/awow-workflows:process-transcriptUse 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.
/awow-workflows:project-planUse 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.
/awow-workflows:refinement-prepUse 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.
/awow-workflows:setup-departmentUse 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.
/awow-workflows:solution-design-flowUse 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.
/awow-workflows:strategy-flowUse 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.
/awow-workflows:team-workshopUse 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.
Bring the Agentic Way of Working to any repo. /setup-awow walks you through connecting your issue board and your team's conventions, and the delivery commands then keep the board current as a byproduct of the work — without changing anything you've already built.
6 skills · 5 commands · hooks
The evidence layer for awow. Export your agent sessions, build a visual timeline of how a project actually got built, score prompt craft, and coach a team or an individual off what the sessions show. Installs beside awow; neither requires the other.
5 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.