Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

docs(skills): agents read and record line settings [I11,O5]

Corey Olsonfabf47d35435
diff --git a/skills/pullboard-run/SKILL.md b/skills/pullboard-run/SKILL.md
index f7c0f7de..b80fba9e 100644
--- a/skills/pullboard-run/SKILL.md
+++ b/skills/pullboard-run/SKILL.md
@@ -142,6 +142,7 @@ At the start of every coordinator cycle, check the flow from the `flow:` line in
- When you need to see who works for whom, run `pullboard agents`: each agent with its seats and the helpers it opened, and what each holds.
- When you need current syntax, run `pullboard help` or `pullboard help <command>`; check the installed release with `pullboard version`. Use `pullboard tour` to walk a person through the scripted example in a throwaway repo.
- When checking machine gate capacity, run `pullboard resources`; change the configured slot count with `pullboard settings gateSlots <n>`, `pullboard settings browserSlots <n>` or `pullboard settings gate.shortSlots <n>` only when the team has agreed to that machine-wide setting.
+- Read the board's line settings with `pullboard settings line`. The coordinator changes one with `pullboard settings line <name> <value> --reason "why" --window <json>`, where the value is on, off or a number in that setting's range; each change is a recorded move with its reason and window numbers, all are off by default, and a value outside the range is refused.
- When an item needs its frozen check, run `pullboard check <id>`; use `pullboard claim <id>` to take or renew a specific lease and `pullboard release <id>` when you cannot continue. `pullboard done <id>` is the submit alias.
- When coordinating a pause or correction, use `pullboard hold` for a lane or item, `pullboard reopen` to return a submission for criterion correction, and `pullboard withdraw` only when nobody should build the item.
- When answering a decision addressed to the coordinator, run `pullboard answer <id>`; when it belongs to the person, use `pullboard pass <id>` to forward it rather than answering for them.