mill
Use this skill whenever you are writing or reviewing a mill-based orchestration program (including pi-mill extension flows).
Core rules
-
Keep systemPrompt (WHO/how) separate from prompt (WHAT/task).
-
Use await for sequential steps and Promise.all for independent parallel work.
-
Always pass an explicit model in provider/model-id format.
-
Check exitCode , stopReason , and errorMessage before trusting results.
-
Use mill.observe.log(...) for progress and diagnostics.
Available patterns
-
General orchestration patterns: ./references/patterns.md
-
Iterative Ralph Loop pattern: ./references/ralph-loop.md
-
Worktree-isolated parallel development: ./references/worktree.md
Prefer these patterns before inventing new orchestration scaffolding.