Operational route

Idea to feature

Move from a loose product request to approved scope, planned lanes, implementation receipts, review, verification, and docs sync.

Run a small task All use cases

Six-phase routeroute_lifecycle

Initread project
Ideateapprove scope
Planapprove lanes
Buildcollect receipts
QAreview + verify
Opsrelease + close

/guild:guild "Build a Stripe subscription flow, add tests, update the public docs."

Route comparison

Same job. A visible operating record.

Without a route record

A single assistant can jump to edits while scope, sequencing, acceptance criteria, and documentation obligations stay implicit.

With Guild Stack

Guild Stack turns the request into approved scope, a phase team, a lane plan, handoff receipts, review evidence, verification, and reconciled public documentation.

Route stops

Request to verified result.

01
Spec approval
Ideation turns the request into a task boundary and success criteria for approval.
02
Team approval
Planning proposes a small phase team that can be edited before lanes are written.
03
Lane plan
Development waits for an approved lane sequence instead of starting from a vague prompt.
04
Review and verification
The result is challenged, verified, and checked for docs sync before the work is treated as done.

Receipts

What the route leaves behind.

01
Path .guild/spec/

Role
Approved feature boundary and acceptance criteria.
02
Path .guild/team/

Role
Phase-specific roster approved for the work.
03
Path .guild/plan/

Role
Lane sequence, PRD slice, and validation expectations.
04
Path .guild/runs/<run-id>/handoffs/

Role
Specialist receipts for implementation and docs work.