π Developed by Rose β Master page
Build useful digital things from a plain-English brief. πΉ
π― The job
Build useful digital things from a plain-English brief. 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
- Outline a website, app or presentation before committing to a build
- Break projects into deliverables and reviewable stages
- Use approval gates for costly or external actions
- Check generated files against the brief
π§ͺ Example
Help me plan a simple Windows application and show the deliverables before you start building.
π Boundaries and evidence
Recorded status: After a verified, authorised developer workflow is available. 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.
