📚 OpenCode by Rose — Master page
Bring authorised coding workers into one coordinated view. 🌹
🎯 The job
Bring authorised coding workers into one coordinated view. The aim: less faff, more progress. The boss fight is still checking the result.
⚙️ How the approach works
Start with your goal, follow the documented steps, then inspect the result. You keep the final say on anything consequential.
✨ Product-specific scope
- Use existing OpenCode worker lanes, not a duplicate dispatcher
- Track claimed tasks and verified changes
- Read worker results and actionable failures
- Preserve permission and scope boundaries
🧪 Example
Show which coding jobs are ready and which ones need an approval.
🛑 Boundaries and evidence
Recorded status: Development / integration concept. Availability labels describe the project record; they do not promise a public release.
Page art is illustration, not proof of a working interface.
✅ How to judge a good result
A good run gets you closer to the goal and changes nothing you did not approve. If the screen disagrees with this guide, stop and check the version.
🌹 Page art is decorative; it does not show the product UI.