pipemason start

Start a single-story run from a feature description. One story becomes one branch and, optionally, one PR.

Usage

pipemason start "<feature description or Jira/Figma URL>" [flags]

The argument can be plain text describing a feature, a Jira ticket URL, or a Figma URL. Run the command from inside the target git repository.

Examples

# Plain-text feature
pipemason start "add a /healthz endpoint that returns 200 ok"

# Open a PR at finalize, against a non-default base branch
pipemason start "add a /version endpoint" --pr --base develop

# Auto-stash a dirty working tree before starting
pipemason start "fix flaky retry logic" --stash

# Run only through the architect phase, then stop
pipemason start "design the billing module" --scope architect --stop-after architect

Flags

Flag	Meaning
`--base <branch>`	Override base branch detection.
`--pr`	Open a PR at finalize (implies push). Uses your connected GitHub token.
`--push`	Push the branch at finalize without opening a PR.
`--stash`	Auto-stash a dirty working tree before starting.
`--skip-gate <name>`	Skip a named verify gate for this run.
`--scope <analyze\|architect\|tdd\|red-green\|iterate\|full>`	Limit the run to a scope of pipeline work (default: full).
`--stop-after <phase>`	Stop the run after the named phase completes.
`--no-cloud`	Run without streaming metadata to the cloud control plane.
`--use-api-key`	Use a configured API key instead of the paired account credentials.
`--max-tier <haiku\|sonnet\|opus\|fable>`	Global flag: set the most expensive model tier this run may use.

What it writes

Scaffolds .pipeline/ in the repository if it does not already exist.
Registers the run with the cloud control plane (unless --no-cloud) and prints the run id.
Creates a working branch for the story and records progress in .pipeline/STATE.md.
At finalize, always pushes when --push or --pr is set, and opens a PR when --pr is set.

Use pipemason status to inspect the current state, and pipemason resume to continue after an escalation.