OpenCode — Plan, Talk, Execute
Break development into an understandable plan. Give a coding assistant a bounded task, inspect changes and test the result instead of asking for an entire system at once.
Why this matters
Websites, internal trackers and practical portfolio projects. A useful learning task gives you a reason to use the tool and a way to judge the result. Instead of collecting generated answers, learn to identify what the task requires and what still needs checking.
The worked task
Your practice brief
A beginner wants to build an enquiry tracker without understanding its components.
Use fictional or approved information. Before starting, say what a useful output would look like and which claims or actions need review.
- Write the user problem and a minimum useful feature list.
- Ask for a plan, identify files and agree one small implementation step.
- Review the change and test the stated behaviour.
- Document the next improvement and what you still do not understand.
What you can show
Small working prototype, change notes and tested acceptance checks.
Keep the original attempt and the improved version when appropriate. Explain which parts AI helped with, what you changed yourself and why the final output is more useful.
Review before calling it complete
- Does the result answer the actual brief?
- Which facts, calculations or behaviours did you verify?
- What is still uncertain or incomplete?
- Can you explain the important decisions without relying on the generated answer?
Connect the next skill
Add persistence, permissions and deployment only after the basic workflow works.
Practice presenting the result or handling the conversation around it. A well-made output and a clear explanation are different skills; both deserve an attempt and feedback.
Explore the learning platform: Foundation curriculum. Examples here explain possible learning applications; they are not promises of individual results.
Explore the demo before choosing your next step.
From repeated problem to a tested prototype
A team repeatedly answers the same service questions and wants an AI assistant.
Research → design → build → testFollow the example →
Test the problem before building the app
A founder has an exciting app idea but has not checked whether people face the problem often enough.
Customer discovery + prototype thinkingFollow the example →Questions to connect this topic with real situations
These related, illustrative practice guides can help you rehearse the conversation or task around your learning. Choose a suitable level; they do not replace the actual lesson brief or specialist review.
All topic questions and scenarios · Choose a practice format