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.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
docs(skills): the run skill names each slot setting
Corey Olson3e47a73594c8
diff --git a/skills/pullboard-run/SKILL.md b/skills/pullboard-run/SKILL.mdindex 4e413243..5ff9fa9d 100644--- a/skills/pullboard-run/SKILL.md+++ b/skills/pullboard-run/SKILL.md@@ -125,7 +125,7 @@ At the start of every coordinator cycle, check the flow from the `flow:` line in- When registering the main checkout as coordinator, run `pullboard join coordinator --model <name>`; when joining a lane, run `pullboard join <lane> --model <name>`. After the same agent starts a new session, run `pullboard takeover`; confirm the active identity with `pullboard whoami`.- 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` only when the team has agreed to that machine-wide setting.+- 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.- 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.