Build Your First Useful Tool with Plain-Language Prompts

Build stage · Module 8 of 15

Outcome for this lesson

Use the brief and prompt to build one narrow working slice, test it, and save a recoverable version.

Bring forward: Bring the build brief, prompt package, and acceptance tests from Modules 6–7.

Produce: A working thin slice with a version label, test record, known-limit note, and screenshot or demonstration.

0 of 15 core modules complete

Progress is saved on this browser. Create a free membership to sync across devices.

Recommended prerequisite: complete Module 7, “Convert the Brief into a Testable Build Prompt,” and bring its artifact. You may still use this page as a reference.

Build stage

Build the next result

Planning becomes useful only when it produces a verified result. Build the smallest end-to-end journey, inspect what changed, and preserve a version you can recover.

Your result for this module

A working thin slice with a version label, test record, known-limit note, and screenshot or demonstration.

Continuous case study

Worked example: Tracker version 0.1

Version 0.1 only adds an inquiry and displays it after refresh. Editing, reminders, analytics, and automation remain out of scope. The test record covers a normal entry, blank name, invalid date, duplicate entry, keyboard flow, refresh, and small screen.

Do the work

Build one vertical slice
Choose the smallest journey that crosses the interface, rules, storage, and visible result.
Inspect before expanding
Review changed files, data storage, external calls, permissions, assumptions, and deviations from the brief.
Run the acceptance tests
Record the input, expected result, observed result, environment, and evidence for ordinary and edge paths.
Save the working version
Use a named version or dated recoverable copy. Record known limits before the next change.

Copy-and-complete template

Create your module artifact

Version or dated copy:

Journey demonstrated:

Changed files or components:

Tests and results:

Evidence reference:

Known limits:

Rollback location:

Keep sensitive information, passwords, API keys, payment data, and private customer details out of course notes and AI prompts.

Quality gate

Check the result before the quiz

One useful journey works end to end.
The build matches the brief’s boundary.
Test results are recorded, not merely claimed.
A known working version can be restored.

How this moves the project forward

Module 9 applies accessibility tests to this working slice while changes are still inexpensive.

Evidence checkpoint and lesson summary

Confirm the artifact, then answer the key questions

The questions cover a core idea, a realistic decision, and evidence from the lesson. Incorrect answers identify concepts to review; they are not a complete measure of your experience or ability.

Artifact checkpoint I created the module artifact, checked it against the quality gate, and recorded any remaining limitation.

This is an honest self-check. Do not enter private data here; keep the artifact in your own approved workspace.

1. Which slice should be built first for the course example? Implement the entire roadmap so the database is designed once, using the same rule throughout the first release Capture and display one inquiry before adding automation and analytics Finish branding and animation before testing saved information

2. What evidence should accompany an AI-generated change? A statement that the implementation follows current best practices, followed by a review at the next project checkpoint A polished screenshot and a summary of intended benefits Changed files, important decisions, test steps, risks, and known limits

3. Which build record is sufficient for this module? Version v0.1 saves and reloads an inquiry; six tests passed; duplicate handling remains a known limit The interface looks complete and the model reports no remaining issues, with that decision recorded in the project evidence Most planned features exist, but no stable version or test record was saved

Confirm the artifact and answer all three questions correctly to unlock the recommended next step.

Build and Verify the First Useful Slice

Outcome for this lesson

Build the next result

Your result for this module

Worked example: Tracker version 0.1

Do the work

Build one vertical slice

Inspect before expanding

Run the acceptance tests

Save the working version

Create your module artifact

Check the result before the quiz

How this moves the project forward

Confirm the artifact, then answer the key questions

About the author

Outcome for this lesson

Build the next result

Your result for this module

Worked example: Tracker version 0.1

Do the work

Build one vertical slice

Inspect before expanding

Run the acceptance tests

Save the working version

Create your module artifact

Check the result before the quiz

How this moves the project forward

Confirm the artifact, then answer the key questions

About the author

Continue with related field notes

Turn the Validated Idea into a One-Page Build Brief

Convert the Brief into a Testable Build Prompt