Let the owner 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-owner@first-project — speech I’ll use the Software Factory recipe to split this larger project into manageable slices. 10s — dev-owner@first-project — command rig context get skills/core/openrig-software-factory/SKILL.md 10.7s — dev-owner@first-project — result Recipe excerpt Separate coordination, implementation, QA and code review as the work grows. 15s — dev-owner@first-project — speech I’ll coordinate. A builder can implement, our checker can handle QA, and a reviewer can examine the code independently. 21s — dev-owner@first-project — command rig grow first-project builder review --pod dev --runtime codex 21.7s — dev-owner@first-project — result Added dev-builder@first-project 23.3s — dev-owner@first-project — result Added dev-review@first-project 25s — dev-owner@first-project — command rig send dev-builder@first-project "Own implementation. Use the slice spec as your target." 27s — dev-builder@first-project — peer From: dev-owner@first-project To: dev-builder@first-project Own implementation. Use the slice spec as your target. 30s — dev-builder@first-project — speech I’ll build each assigned slice against its spec. 31s — dev-owner@first-project — command rig send dev-review@first-project "Review the code independently against each slice spec." 33s — dev-review@first-project — peer From: dev-owner@first-project To: dev-review@first-project Review the code independently against each slice spec. 36s — dev-review@first-project — speech I’ll examine the implementation, separately from QA. 37s — dev-owner@first-project — command rig send dev-check@first-project "Keep your testing knowledge. Own QA for the new slices." 39s — dev-check@first-project — peer From: dev-owner@first-project To: dev-check@first-project Keep your testing knowledge. Own QA for the new slices. 43s — dev-check@first-project — speech I’ll use what we learned to check the user paths.