Course overview

Choose how to start

Start with the result you want. Choose how much preparation you need to review the scope and checks.

Choose the useful amount of preparation
ApproachUseful whenWhat you review
Goal-driven developmentThe outcome is small and bounded, and the affected files and checks can be made clear in a short request.The goal, scope, constraints, success criteria and proposed plan.
Spec-driven developmentSeveral workflows, dependencies, consequential choices or competing requirements need to be settled before implementation.A specification with requirements, exclusions, acceptance examples, dependencies and unresolved decisions.

Start from a bounded goal

A short prompt is enough for this reporting exercise. The input, expected totals and files that may change are easy to review together.

Example prompt

Plan a readable HTML report of time by project and category from this synthetic CSV. Keep the sample data and acceptance checks unchanged. Show me the plan and expected totals for my review and approval, then stop and wait for my decision.

  1. Open Turn an idea into a useful result to define the outcome and checks.
  2. Open Build your first report to preview the plan, approve its scope and authorize the build separately.

For your own project, read the goal-driven development guide.

Develop requirements before implementation

Use a specification when decisions about requirements, dependencies or failures need to hold across several workflows. For example, a shared reporting product may need rules for input formats, saved reports and access.

Example prompt

Help me draft a spec for shared activity reporting. List the user workflows, data and access rules, dependencies, acceptance examples and open decisions. Show me the draft for review and wait for my approval before starting implementation or model consultations.

  1. Review the requirements, exclusions and acceptance examples. Resolve open decisions with your assistant.
  2. Ask the assistant to turn the reviewed spec into a supported Harness plan. Review and accept the plan before authorizing the build.

Read the spec-driven development guide and plan import instructions.

Optional reference for spec authoring

Spec Ladders is the Attune AI host workflow invoked with /spec. It organizes requirements, design and a sequence of tasks with approval points. This course uses the Harness plan and build commands, which the course checks exercised with Harness 1.7.0 and 1.8.0.

Choose a prompt format

Use plain language for a short request. Use XML tags when headings such as context, instructions and expected result make a longer prompt easier to read. See Harness authoring forms.

Keep the same review points

Revisit the requirements and plan when the work changes.

Start the first lesson