First task set

Before you press Start, make the first task set boring in the best way: small, grounded, framed, and easy to verify.

Start with three to five tasks

That is enough to prove sequencing and inspection without burying a bad assumption inside a huge queue.

Good first tasks:

• fix one known failure
• implement one narrow behavior
• update one doc for a clear audience
• add one test surface for code that already exists
• write one policy or spec before asking Guildhall to apply it everywhere

Weak first tasks:

• "Build the whole product."
• "Clean up everything."
• "Make the UI better."
• "Review all code."
• "Set the policy" when you have not said whether you want a spec, a parent feature, or implementation now.

Give each task a blueprint

Each runnable task answers:

• What changes?
• What is out of scope?
• Where is the likely work area?
• How can the work be checked?
• What would make the reviewer reject it?

If those answers are missing, leave the item as a draft or answer the question in Thread.

Do not over-specify routine mechanics. If a decision is conventional and the repo gives enough evidence, Guildhall can recommend the default and keep moving. Save your attention for product intent, audience, flow, content, constraints, and the finish line.

If a task contains several pieces that need to fit together, let Guildhall keep them linked without making them one task. A policy decision, a written spec, the product changes that apply it, and the checks that prove it can be four related tasks under one parent goal.

Treat drafts as a holding area

A draft means "maybe work, not framed yet." It does not auto-run just because Guildhall found it in a file.

Approve the draft when it has enough evidence to become a blueprint. Keep it as a draft when it needs your decision, release planning, or a clearer success signal.

Start when the queue is honest

Before starting, check that at least one task is ready, no task is waiting for your answer, and blockers are visible where you can act on them.

Once started, Guildhall keeps showing motion: live events, transcript movement, worktree/bootstrap status, verification output, reviewer decisions, change orders, and blockers.