Request

Harness should support manual steps that wait for a user to sign off, so a full process can be built out in Harness before every step is automated.

Background

braintree/runbook has been used to automate large deployment processes incrementally. Runbook is a DSL for defining a procedure as an ordered set of steps, where manual and automated steps live in the same document. With it, all steps were put in place, documented, and partially automated, then automated in pieces until the process was complete.

Core need

A tool like this should not require 100% automation to be useful. Even at a fraction of full automation, having the non-automated steps documented in one place with correct dependency ordering helps with:

Standing up new environments, where the full sequence (manual and automated) is visible and ordered

Incrementally automating the manual steps, since each one is already defined and sequenced and can be replaced over time

Example flow

Define the full process in Harness, with every step in order.

Steps that can be automated today run automatically.

Remaining steps pause and wait for a person to complete the work and sign off.

Over time, replace each manual step with an automated one.

Gap

Manual Approval works as an approve/reject gate rather than a documented unit of work. What it and other existing steps cover today should be confirmed.

Suggested scope

Markdown instructions per step

Assignee or group, with notifications

Sign-off audit trail (who, when, optional comment)

Works with existing stage ordering and conditions

Optional timeout

Outputs that downstream steps can use

Ability to swap a manual step for an automated one without restructuring the pipeline