Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

meganemura

@meganemura source repo

4 published skills

  1. ▌
    Workflow · meganemura
    Drive a headsign phase-gate workflow. Use when the repository has a .headsign/ directory holding one or more workflow files — workflow.yaml, or named ones like fitness.yaml run with `headsign start fitness` — and the user asks to start, continue, or resume a run, or when .headsign/state.json shows a run in progress (e.g. when recovering after compaction). Do not use in repositories that have no .headsign directory.
    0
    installs
  2. ▌
    Design Workflow · meganemura bundle
    Design and write a headsign workflow file — the YAML that names a repository's phases and holds the shell checks that gate them. Use when the user asks to create a workflow for this repository, to add another one alongside ones already there, or to change how an existing one's phases, gates, routes, or limits are shaped. This skill authors the file and stops at it; starting, continuing, or resuming a run is the `workflow` skill's job instead. The two divide by what is being asked for — writing the graph versus walking it — not by what is on disk, so this one applies whether or not the repository already has a .headsign/ directory.
    0
    installs
  3. ▌
    Migration · meganemura
    Use when moving an existing test suite onto nukadoko, whether from cucumber-js (typically driving Playwright), from a Playwright Test suite with no cucumber and no Gherkin, or from another DSL already shaped as typed steps. Covers the two-stage discipline that keeps every failure traceable to one change, the `nukadoko/compat` door, sharing an implementation with a Playwright Test suite, and promoting steps to typed `defineStep`s at your own pace.
    0
    installs
  4. ▌
    Acceptance · meganemura bundle
    Use when turning a requirement into a signed-off Gherkin scenario, starting from whatever is on hand, whether that is raw prose with no stated acceptance criteria yet (a ticket, a request, a conversation), acceptance criteria that still need concrete scenarios, a scenario ready to write, or a path already explored one `nuka do` call at a time and now worth fixing in a scenario.
    0
    installs