In practice

Daily workflow

Overview

The FFF daily workflow is designed to fit into the gaps of your day, not consume it. There is no fixed time of day when you must attend to the system. Instead, there are a small number of lightweight touchpoints that recur whenever the system needs your attention.

Morning - check for interruptions

The first thing to do each morning is check whether any in-progress tickets have raised an interruption request overnight.

Interruptions are rare. A well-specified ticket should produce zero interruptions. But when they occur, they are blocking - the Forge loop for that ticket is paused waiting for your answer.

For each interruption:

  1. Read the question (it will be specific and offer concrete options)
  2. Respond with the answer
  3. The Forge loop resumes automatically

Total time: 0-10 minutes, depending on the number of interruptions.

Morning - review the backlog

Scan the staged tickets. Ask yourself:

  • Are there any tickets that are ready to trigger today?
  • Are there any new requirements I need to drop into the Inlet?
  • Is the priority order still correct, or has something changed?

This is not a planning session. It is a 5-minute orientation. You are not estimating effort, assigning developers, or writing sprint goals. You are simply deciding whether to push any of the green buttons in front of you.

Throughout the day - feed new requirements

Any time you encounter a new requirement - a user complaint, a feature idea, a bug report, a strategic decision - drop it into the Inlet immediately. Do not accumulate requirements in a notes app or a mental queue. Get them into the system.

The PM and Analytic agents will pick them up and refine them into staged tickets asynchronously. By tomorrow, a fresh requirement is typically staged and ready to trigger.

When ready - trigger 1-2 tickets

The key question before triggering a ticket: will you have 10-15 minutes later today or tomorrow to review the Validation Package?

If yes, trigger the ticket. If not, wait. A Validation Package sitting unreviewed is a mild form of waste - the ephemeral environment is idling and the ticket is in a limbo state.

A sustainable rhythm for a solo Orchestrator is 1-3 tickets per day depending on ticket complexity. This translates to a constant stream of small, reviewed, confirmed deliveries rather than infrequent large batches.

When the Validation Package arrives - review and confirm

When a Validation Package lands, treat it as a scheduled meeting with yourself. Reserve a block:

  1. Read the summary (2 minutes)
  2. Review screenshots or screen recording (3 minutes)
  3. Check the test report - look for unexpected skips or low coverage (3 minutes)
  4. Scan the diff summary for anything surprising (2-3 minutes)
  5. Make your decision: confirm, reject, or defer

If you confirm: issue the confirm command and the deployment runs automatically.

If you reject: write a specific note describing what is missing or wrong, and return the ticket to Forge. Avoid vague rejections like "this doesn't feel right" - the agents cannot act on that.

If you defer: leave the ticket in Validating. It will be there when you are ready.

End of day - optional glance

Before finishing, take 60 seconds to look at the pipeline state. How many tickets are in Forge? How many are staged? Is anything stalled?

This is not a review. It is a pulse check. If something looks odd - a ticket has been In Progress for much longer than similar tickets - make a note to investigate tomorrow.

The rhythm in practice

Morning      5-10 min    Clear interruptions, scan backlog
Throughout   0-5 min     Drop new requirements into Inlet
Midday       15 min      Review + confirm Validation Package(s)
Afternoon    2-5 min     Trigger 1-2 staged tickets
End of day   1 min       Pulse check on pipeline state

Total active time: 25-35 minutes per day for a team of 6-8 agents running 2-4 concurrent tickets.