tick-steplisted
Install: claude install-skill the-cloud-clockwork/agentihooks
# Tick step
A tick step is five artefacts: the registered step in a `scripts/tick/steps/<module>.py`
module, its floor row in `scripts/tick/steps/budgets.py`, its feature test in
`tests/tick/steps/test_<name>.py`, its row in `tests/swarm/tick_scenarios/steps.json`
and its `feature-map.json` entry. Code writes all five; you write only the body.
## 1. Scaffold
From the worktree root:
```bash
python -m scripts.tick.new_step <name> --group <group> --lane tick|slow \
--interval 60|120|600 --effects <port,port> --feature <feature id> --module <steps module>
python -m scripts.tick.new_step --check <name>
```
- The task spec names the step, group, lane, effects and feature. Take them from it;
an effect is a field name of `scripts.tick.ports.tools.Tools`.
- A module the steps package lacks is created and joins `MODULES`.
- The command refuses a name any artefact already holds. A changed step keeps
its artefacts: edit them, then run `--check`.
- `--check` must report all five `true`.
## 2. Fill the body
- The stub is a `CallStep`: a function of the tick module and a pass state
reader, `(tick, get)`, returning the step's action lines. Fill its `needs`,
`reads` and `writes` with what the body uses.
- A step written as a `WriteStep` or a `Step` dataclass acts only through
`ctx.tools`, the view of the ports it declares in `effects`, reads the pass
view with `ctx.view.read(domain, key)`, never `ledger.state`, finishes under
`ctx.deadline` and returns `Result(writes)`