hostplanSign in

Runnable example

Split a large implementation into an ordered plan stack

Chain schema, API, UI, and rollout plans so each coding-agent session receives one actionable step with explicit dependencies.

Maintained by the Hostplan projectView source

Scenario

A feature is too large for one safe implementation turn and later phases must not begin before foundational work is complete.

Workflow

  1. 1

    Start in the intended repository

    Project and branch context come from Git, so check the working directory before adding plans.

  2. 2

    Run the commands in order

    Keep the returned plan ids; placeholder ids below stand for the ids printed by your own store.

  3. 3

    Inspect each transition

    Use JSON output for automation and the browser viewer when a human needs to review the artifact.

  4. 4

    Verify the outcome

    `hsp next` returns only the first unblocked plan, and marking one step done prints which dependent step becomes actionable.

hsp stack 01-schema.md 02-api.md 03-ui.md 04-rollout.md
hsp stack <first-id>
hsp next
hsp status <first-id> done
hsp next

What this example proves

`hsp next` returns only the first unblocked plan, and marking one step done prints which dependent step becomes actionable.

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.