Let the builder organize the team Illustrative terminal demo. Same dialogue as the series clip. 0s — You — human Now I want people to create their own themes, share them, and sync them across devices. 5.3s — dev-build@starter — speech I’ll use the Software Factory recipe to split this larger project into manageable slices. 10s — dev-build@starter — command rig context get skills/core/openrig-software-factory/SKILL.md 10.7s — dev-build@starter — result Recipe excerpt Separate coordination, implementation, QA and code review as the work grows. 15s — dev-build@starter — speech I’ll coordinate. A designer can build the theme editor, a QA seat can try the user paths, and dev-review keeps examining the code independently. 21s — dev-build@starter — command rig grow starter design qa --pod dev --runtime codex 21.7s — dev-build@starter — result Added dev-design@starter 23.3s — dev-build@starter — result Added dev-qa@starter 25s — dev-build@starter — command rig send dev-design@starter "Own the theme-editor slices. Design and build each one against its spec." 27s — dev-design@starter — peer From: dev-build@starter To: dev-design@starter Own the theme-editor slices. Design and build each one against its spec. 30s — dev-design@starter — speech I’ll design and build each assigned slice against its spec. 31s — dev-build@starter — command rig send dev-qa@starter "Own QA for the new slices. Try the user paths against each spec." 33s — dev-qa@starter — peer From: dev-build@starter To: dev-qa@starter Own QA for the new slices. Try the user paths against each spec. 36s — dev-qa@starter — speech I’ll check the user paths against each spec, separately from code review. 37s — dev-build@starter — command rig send dev-review@starter "Keep what you learned from the dark-mode check. Keep reviewing the code independently." 39s — dev-review@starter — peer From: dev-build@starter To: dev-review@starter Keep what you learned from the dark-mode check. Keep reviewing the code independently. 43s — dev-review@starter — speech I’ll use what we learned to examine the implementation.