Help Center

Course overview

Turn an idea into a useful result

Choose a result you can explain and a first version you can check.

This full-text reading copy does not save answers. Open the interactive lesson for saved browser notes.

See where the work went

Six activity entries can answer a useful question: how much time went to each project and category?

Click Open formatted report. Find the total, one project and one category. A readable report lets you explain where the time went without adding every row again.

The target result from the six supplied rows
Entries6
Total270 minutes, or 4 hours 30 minutes
ProjectsOrion 180 minutes; Lumen 90 minutes
CategoriesDevelopment 150; Documentation 75; Testing 45 minutes

In this course, you direct the outcome and decisions. Your assistant helps inspect the project and prepare the work. Harness retains the agreed request, checks and execution evidence for supported workflows.

Start by defining what would make the report useful. You do not need to design its code. Opening the supplied report does not mean that you have built a new one.

Check the six entries

The projects and activity are synthetic. The small input makes the target result easy to check yourself.

The supplied activity data
ProjectCategoryMinutes
OrionDevelopment90
OrionTesting30
OrionDocumentation45
LumenDevelopment60
LumenDocumentation30
OrionTesting15

Read the actual activity CSV, which also includes the dates. Add Orion's rows: 90 + 30 + 45 + 15 = 180 minutes. Lumen has 60 + 30 = 90 minutes. Together they account for 270 minutes, or 4 hours 30 minutes.

Pick a category and add its rows before looking at the report. Development should total 150 minutes, Documentation 75 and Testing 45. These expected answers come from the input, not from trusting the reporting code.

Describe what the person needs

State what the reader needs from the report. Let the assistant propose how to build it.

Use the sample CSV to describe the result you want and the checks that would show it works. Decide what the reader needs to see before you review the scope.

For a project with several workflows or unresolved requirements, compare the goal-driven and spec-driven approaches.

goal prompt

Help me plan a readable HTML report of time by project and category from the supplied synthetic activity CSV. Include the entry count and total minutes so the reader can see where the time went. Inspect the CSV and sample report. Draft the goal, the files that may change and the checks that will show the totals are correct. Show me the draft for review and approval, then stop and wait for my decision.

Keep one complete useful journey

Agree on the report you will build and the files that may change.

In your own project, inspect the proposed file list before approving it. Consider filtering, remote services, new dependencies and deployment as separate decisions.

Say how you will recognize success

Use concrete examples and a failure case. A polished appearance alone cannot establish that the totals are right.

Match each criterion to a check you can verify. You can add one total by hand now. In lesson 2, you will inspect the recorded test results.

Review the draft before you approve its scope. Authorize the build separately.

Which success criterion is useful before the reporting work starts?

The six supplied entries total 270 minutes, and project totals account for that same total. This is observable and can be checked independently from the source rows.

The report looks professional, so its totals can be assumed correct. Appearance can help the reader, but the totals still need independent checks against the input.

Change the reader, then explain the consequence

Suppose a colleague only wants to compare the two projects. Does that require a new feature?

The existing project table already supplies that comparison. A useful next step might be clearer instructions about where to look, rather than adding a filter or rewriting the tool.

Now consider a different request: “Show only Orion's activity.” That changes selection behavior. Keep it as a proposed later change until its goal, permitted files and checks are reviewed.

Your reader and first-version decision

Write your answer in your own notes, or use the interactive lesson.

This lesson saves your note in this browser when storage is available. Paste any wording you want to reuse into your project brief.

Explain why your chosen scope completes a useful journey. If the existing report already answers the question, keeping the scope unchanged is a valid decision.

Prepare a brief you can review

You are ready for planning when you can explain the goal, the boundary and what would establish success.

Proposed project brief

Reader and benefit
A person reviewing activity wants to explain where the time went.
Input and result
Read the supplied synthetic CSV and produce an HTML report of time by project and category.
Success
Six entries; 270 minutes; correct project and category totals; clear bad-input behavior; preserved inputs and checks.
Boundary
A local reporting task. Filtering, remote services and deployment need separate decisions.
Status
Draft brief for review.

Ask your assistant to turn the brief into a draft request. Review the proposed files and checks before making a decision.

brief handoff prompt

Use my reviewed reporting brief to draft the Harness request. Preserve my wording and existing work. Show me the goal, the files that may change, the protected inputs and the checks. Flag any decision I still need to make. Present the draft for my review and approval, then stop.

Next: Open Build your first report to follow planning, scope approval, separately authorized execution and evidence inspection.

Practice runtime and verification

Follow the course setup instructions to use a tested Harness release. Read the original 1.7.0 check summary for the supplied example's actual local results and limits. Software checks do not measure a learner's independence or establish model quality.

Read the working guide or read the course guide.