/yaawn-prepare-plan
Get a new idea or an existing issue ready for planning. Asks
which work item you have — story, refactor, spike, bug report,
prototype, or other change — or infers it from the issue's
labels, routes it to the matching writer, grills it with the
type's dedicated grill, and saves it to GitHub after your
approval. Every story gets a split assessment.
Refinement
/yaawn-create-plan
Turn a GitHub issue into a grilled implementation plan: discuss
the design first, explore the codebase when needed, choose the
rollout strategy — branch by abstraction with a feature flag, a
feature flag only, or shipping directly — and record every
decision.
Planning
/yaawn-save-plan
Write the plan into the issue: implementation steps, design
decisions, open questions with owners, and a concise
plain-language summary with a high-level diagram per visible
structure. Offers to answer the open questions with you first.
Marks the issue ready for implementation.
Planning
/yaawn-implement-plan
Execute the plan unattended, overnight — one issue or several in
parallel, each in its own git worktree inside the project folder
(yaawn-<issue>-<slug>, next to
main/). Runs on the coding agent picked for the
sessions during setup. Never commits or pushes.
Overnight
/yaawn-verify-executed-plan
The final gate: check every Definition of Done step from your
project's shared checklist, run your verification commands, walk
the manual checks with you, then open the pull request — when
setup enabled it.
Verification
/yaawn-write-user-story
Write and refine user stories: persona, Given/When/Then
acceptance criteria, INVEST validation, and a value type.
Produces words only — never code — and saves to GitHub after
your approval.
Backlog
/yaawn-write-refactor
Write a refactor issue — goal, why now, what done means, and a
value type — for a change users do not see. No persona, no
Given/When/Then, and never code.
Backlog
/yaawn-write-spike
Write a spike — one sharp question, why it blocks, a timebox,
and exit criteria. After the save, a human answers it; the
overnight run never picks it up.
Backlog
/yaawn-write-bug-report
Write a bug report — summary, steps to reproduce in words,
current and expected behavior, and environment. Describes the
problem, never the solution.
Backlog
/yaawn-write-prototype
Write a prototype — a throwaway build of a feature idea to test
with customers: goal, success criteria, and what will be built.
It runs on a prototype/ branch that is never
merged.
Backlog
/yaawn-write-other
Write an other change — work that matches none of the other
types — with goal, why now, and what done means. Never code.
Backlog
/yaawn-grill-story
Stress-test a story — persona, acceptance criteria, INVEST, and
value — in rounds of questions and push-back that come mainly
from the persona's point of view, until you and the agent share
an understanding and no assumption stays unstated.
Refinement
/yaawn-grill-refactor
Stress-test a refactor — goal, why now, what done means, and
value — in rounds of questions, until you and the agent share an
understanding of what improves and why now.
Refinement
/yaawn-grill-spike
Stress-test a spike — the question, why it blocks, the timebox,
and exit criteria — until it is clear what must be found out and
when the spike is done. Never answers the question itself.
Refinement
/yaawn-grill-bug-report
Stress-test a bug report — summary, steps to reproduce, current
and expected behavior, and environment — until it is clear what
goes wrong and how to reproduce it.
Refinement
/yaawn-grill-prototype
Stress-test a prototype — goal, success criteria, and what will
be built — until it is clear what the experiment should teach
and how its result is judged.
Refinement
/yaawn-grill-other
Stress-test an other change — goal, why now, and what done means
— in rounds of questions, until no assumption stays unstated.
Refinement
/yaawn-grill-design
Stress-test the implementation design — architecture, data flow,
interfaces, edge cases, security, and testing — logging every
decision and adding settled terms to the project glossary.
Proposes an ADR for each decision that is hard to reverse and
writes it only after you confirm.
Planning
/yaawn-split-story
Split oversized stories into vertical, independently deployable
slices with the SPIDER technique — created as standalone issues
once you approve, linked with **Depends on:**
where one slice needs another.
Refinement
/yaawn-owasp-security
A background security lens based on the OWASP Top 10:2025 — read
silently when proposing designs, plans, or code, baking
mitigations in autonomously and escalating only the risks it
cannot resolve on its own.
Security
/yaawn-clean-code
Deep Clean Code rules from Robert C. Martin — naming, functions,
classes, tests, SOLID — complementing the always-on
instructions.
Code review
yaawn-developer.md
The default: delivers working, tested code in small, surgical
changes, with security baked in and the definition of done in
mind.
Everything else
yaawn-reviewer.md
Reviews like a staff engineer: flags only what matters, names
file and line, proposes a concrete fix, and ranks findings by
severity.
Reviews & audits
yaawn-product-owner.md
Starts from user value: prepares stories, bugs, refactors,
spikes, and prototypes for your product's user roles, holds them
to INVEST, and keeps code out of them.
Story work
yaawn-clean-code.typescript.instructions.md
Clean Code principles for the codebase, applied to every
TypeScript file — the lightweight summary the /yaawn-clean-code
skill expands into its full reference.
Always-on instruction
yaawn-function-coupling.typescript.instructions.md
Keep methods independent: orchestrate every step of a flow from
one method, so each step can change without touching the others.
Call the steps in parallel, and reduce repeated arguments by
passing shared data through the constructor or class members.
Always-on instruction
yaawn-declarative.instructions.md
Write code that states the desired outcome — the what — instead
of narrating every step — the how: array methods over loops,
SQL, JSX. Keeps step-by-step logic where it is clearer, and code
review checks for it too.
Always-on instruction
yaawn-semantic-html.html.instructions.md
Always use semantic HTML elements — header, nav, main, section,
button, label — instead of meaningless div and span wrappers.
Accessibility, SEO, and resilience by default.
Always-on instruction
yaawn-html-css-js.html.instructions.md
Build new UI features in priority order: native HTML first, then
HTML + CSS, and only then JavaScript/TypeScript. The simplest
technology that solves the problem wins.
Always-on instruction
yaawn-vanilla-css.css.instructions.md
Hand-written vanilla CSS only — no preprocessors, no utility
frameworks, no CSS-in-JS — with class names following the OOCSS
or BEM pattern. Predictable, reusable, collision-free styles.
Always-on instruction
yaawn-accessibility.html.instructions.md
Accessible markup, area by area along the A11Y Project checklist
— alternative text, one top-level heading, table header cells,
labelled form inputs, captions, and a page language.
Always-on instruction
yaawn-accessibility.css.instructions.md
Accessible presentation along the A11Y Project checklist —
sufficient color contrast, visible focus styles, reduced-motion
support, reflow and zoom, and touch targets large enough to hit.
Always-on instruction
yaawn-accessibility.javascript.instructions.md
Accessible behavior along the A11Y Project checklist —
keyboard-operable custom controls, focus management, accessible
media controls, reduced motion, and safely rendered content.
TypeScript projects get it too.
Always-on instruction
yaawn-open-source-first.instructions.md
Research whether a well-maintained open-source package already
provides the feature before writing it from scratch. Reuse
first, write second.
Always-on instruction
yaawn-personas.instructions.md
Picks the agent persona for every task under the hood — Reviewer
for reviews, Product Owner for story work, Developer for
everything else. You never have to choose.
Always-on instruction
yaawn-instructions
The Vibe bridge skill: Vibe never reads instruction files, so
this skill makes it read yaawn's and the project's instructions
and follow each one whose applyTo matches. Every
other agent ignores it.
Vibe only
yaawn-eli5.instructions.md
The plain-language output style: short sentences, everyday
words, no jargon. Plans and overnight summaries are written in
it so anyone on the team can understand them.
Output style
yaawn-grilling.md
How every grill skill runs a session: an open grill that
questions everything first, then a focused grill over the
skill's checklist. Asks in rounds over the open frontier, looks
up facts itself, leaves decisions to you, and ends only when no
assumption stays unstated. Shared by all seven grill skills so
they behave the same way. Reads the domain's ADRs before round
one, and concept grills mark ADR-worthy decisions with
[ADR].
Grilling
yaawn-adr.md
How grill sessions use Architecture Decision Records in
.yaawn/adr/<domain>/: cite a settled decision
instead of asking again, and ask whether to reverse it when an
answer contradicts it — the record is updated in place, and its
earlier wording stays in git history. Only
/yaawn-grill-design writes ADRs, after you confirm.
Without ADRs, grills run as before.
Grilling
yaawn-issue-writing.md
How every writer skill refines an existing issue and saves it:
your approval first, the grill's decisions and open questions in
the same save, the template's labels, and the body passed as a
file. Shared by all six writer skills, so each keeps only its
own fields.
Refinement
yaawn-worktrees.md
How overnight skills lay out git worktrees: a bare repository at
the project root, the main copy at main/, and one
worktree per issue inside the project folder — never next to it.
Pre-flight refuses to launch until the project uses this layout.
Overnight
yaawn-glossary.md
yaawn's own glossary, shipped in .yaawn/ and
overwritten on install — the vocabulary of the workflow itself
(grill, ADR, slice, lane). Never holds project terms.
Shared
yaawn-project-glossary.md
Your project's domain vocabulary in
.yaawn/ — every term that settles during a design
grill is added here, in alphabetical order. Grill skills keep it
current automatically.
Shared
yaawn-definition-of-done.md
Your project's shared checklist that
/yaawn-verify-executed-plan walks through before
opening a pull request. Edit it to match how your team defines
done — every item must be checkable by a human or a command.
Verification
yaawn-verification-commands.md
The commands /yaawn-verify-executed-plan runs from
the repo root, in order, stopping at the first failure. List the
cheap checks first — lint, typecheck, unit tests — and e2e last.
Verification
roles/*.role.md
Your product's user roles in .yaawn/roles/, one
file per role — the personas that story work starts from. Each
file holds the role's name as its heading, a description, and
its goals. /yaawn-write-user-story,
/yaawn-grill-story, and
/yaawn-split-story read every role file to keep
personas consistent across issues; with no role files, stories
are written for the Developer.
Backlog