Runnable example
Run a plan through draft, approval, execution, and completion
Use explicit status transitions and addressable tasks so a coding-agent plan cannot silently move from proposal to implementation.
Scenario
A human asks for a repository change, reviews the implementation plan, approves it, and resumes the work in another coding-agent session.
Workflow
- 1
Start in the intended repository
Project and branch context come from Git, so check the working directory before adding plans.
- 2
Run the commands in order
Keep the returned plan ids; placeholder ids below stand for the ids printed by your own store.
- 3
Inspect each transition
Use JSON output for automation and the browser viewer when a human needs to review the artifact.
- 4
Verify the outcome
`hsp status <id>` returns done, every required checkbox is complete, and the implementation checks named in the plan have passed.
hsp add PLAN.md
hsp status <id> approved
hsp status <id> in-progress
hsp tasks <id>
hsp check <id> 1 2
hsp status <id> doneWhat this example proves
`hsp status <id>` returns done, every required checkbox is complete, and the implementation checks named in the plan have passed.
The example uses no customer data and does not require a hosted account. Add--local when you want to guarantee that a sample remains only on the current machine.