build
SolidExecutes the tracks of a work file (docs/work/*.md) — in this session or through parallel coder agents when file sets are disjoint — checking every return with a diff and a re-run, a checkpoint per track and a full gate every third. Use after /plan, "build it", "implement the tracks", "continue the work file".
Install
Quality Score: 85/100
Skill Content
Details
- Author
- assaio
- Repository
- assaio/assaio
- Created
- 2 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
auto
Autonomous, non-interactive run of the whole chain — work → plan → build → gate → review → ship up to the PR — for a task or B-id, without questions. Takes the most reversible decision when unsure and records it in the work file as "decided alone … reverse by …". Stops only at hard lines (merge, tag, push to main, money, protected contracts). Exits cleanly when nothing is left to do.
start-work
Pick up the project's pending work and do it — settle the open decisions first, select a batch from the backlog, partition it into lanes that cannot collide, and run those lanes in parallel. SHORTHAND: `--start`. Also trigger on "carry on with what's pending", "pick up the next thing", "keep going with the backlog".
buildwork
Run a repository's open issues as parallel agents, one per issue, each in its own worktree and its own pull request, then check them and propose a merge order. Works through Paseo tabs or the host's own subagents. Trigger on phrases like "buildwork", "run the roadmap", "work through the backlog", "fan these out", "run these issues in parallel", "spin up agents for these", "what are my agents doing", "what are my agents running", "which order do I merge these", "collect the wave".