Software development as a state machine.

Feed it requirements. Forge them autonomously. Finish with a single confirm.

Get started
phases.ts
ticket.log
export const phases = {
feed: {
states: ['draft', 'staged'],
},
forge: {
states: ['building', 'reviewing', 'testing'],
},
finish: {
states: ['validated', 'shipped'],
},
}

Introduction

Getting started

Feed, Forge, Finish

Software development as a state machine. Feed it. Forge it. Finish it.

FFF (Feed, Forge, Finish) is a pull-based project management methodology that treats your delivery pipeline as a deterministic state machine rather than a calendar-driven ceremony. You measure Cycle Time - the elapsed time from trigger to delivery - not velocity. Work does not start until you explicitly trigger it, and it does not ship until you explicitly confirm it.

The three phases are simple: Feed a requirement into the system. Let agents Forge it in an autonomous loop. Finish by auditing the Validation Package and pressing confirm.

Where to start

  • Core philosophy - understand the state-machine framing and why Cycle Time replaces velocity.
  • Phase A - Feed - how a raw requirement becomes a staged, ready-to-trigger ticket.
  • Phase B - Forge - the autonomous build-review-test loop you barely need to watch.
  • Phase C - Finish - the Validation Package, audit, and the one command that ships.