AGENT SKILL

commission-a-workflow

Start a workflow whose agent reads the store and proposes work, then bring each of its proposals to the person as a card to start, fold into another, or drop.

License 许可
MIT
所属仓库
emyann/nemia
最近更新
2026-11-15
Stars
★ 3
Forks
0

01 前言 Front Matter

name
commission-a-workflow
description
Start a workflow whose agent reads the store and proposes work, then bring each of its proposals to the person as a card to start, fold into another, or drop.

03 SKILL.md 正文

Commission a workflow

Some workflows do no work in a repository: their agent reads the store — its stats, its feed, its runs — and proposes work, each proposal an inbox card or a closeout for the person to accept. You commission such a workflow; the agent in it stays its own worker, and you never do its reading for it.

A line here written nemia <verb> … names the verb <verb>: at a shell, type it as written; on the MCP port, call its tool, whose schema says its arguments. The verbs skill names each verb's tools, and which run at a shell alone.

Start it

  1. Read the factory's instruction (nemia factory instruction <name>): it names the workflow to commission and the brief it takes, when the factory has one. Without one, ask the person which workflow, and which factory.
  2. Start it: nemia start "<brief>" --workflows <workflow> --factory <factory>, and say you did.
  3. Write a pending fact naming the run you started and what it is for.

Bring its proposals

When it signs off, read what it proposed: nemia decide <run>, and nemia inbox for the cards it filed. Bring each proposal as what it is, a card: the proposal in its own words, the evidence it gives, what it would cost against the person's line, and your recommendation, one of three:

  • Start it: queue it (nemia inbox queue <name>) or start it (nemia start <store>/inbox/<name>.md), once the person says to.
  • Fold it into another card it overlaps: say which, and what of it to keep.
  • Drop it: nemia inbox rm <name>, which prompts the person.

A proposal that came as a closeout, not a card, you write as one with the write-a-card skill, then bring it the same way. Start nothing it proposes until the person says to. When every proposal is answered, delete the pending fact.

04 同仓库更多 Skills

emyann
emyann/nemia

groom-the-inbox

Read each card in play in the inbox against the repository and say, per card, done (the commit on the base that landed it), replaced (the decision or card that did), stale (each fact that moved, what it said and what it says now) or standing, reading closely only what the period touched. For the janitor's step, which proposes and never acts: a person removes or amends each card by the command the check writes.

★ 3
emyann
emyann/nemia

write-a-spec

Turn an accepted intent into a spec an engineer can build from in this repository: the goal restated, the approach and why, every path it touches, the steps, the tests that prove it, the risks, and what is still open. For a step that designs a change before anyone builds it.

★ 3
emyann
emyann/nemia

review-a-change

Review a change in this repository as a second engineer would: against its intent and spec, by reading the diff and the suite's verdict, with findings that name the file, the line and what goes wrong. For a read-only step that decides whether the work goes round again.

★ 3
emyann
emyann/nemia

read-the-stats

Read a factory's stats since the janitor's last run, against the same length of time before it, write a short report, and propose one correction per card — an allow or deny by name, a line in an agent's body or a skill, or a refusal kept on purpose — each with the numbers behind it, never one already in the inbox. For the janitor's step, which proposes and never acts.

★ 3
emyann
emyann/nemia

land-a-branch

Land a run's result on the base branch in this repository's own checkout, the way the step says it lands: make that one act, read its result, and write the message that records what landed — or change nothing and say why it refused. For a gated ending step (workspace: base).

★ 3
emyann
emyann/nemia

implement-a-change

Build a change from its spec in this repository: tests first where a rule is claimed, small commits, the tests of what changed green for the right reason, and each review finding answered in the next round. For a step that writes the code.

★ 3