Creation
What this stage is
Creation is where the spec becomes real. You build from the tracks and phase specs Workstreams shaped, steward the work as it runs, and ship it. This stage does the creation.
The skills that run it: execute + finalize
executeruns the deliverables phase by phase: it plans the phase, then runs it as stewarded execution - you stay in the loop at the gates ("is it ready?", and session history carries your decisions forward) - and writes an audit report that updates the phase specs, so the spec sharpens as you build. Surfaces asfai:workstreams_execute.finalizeis the quality gate: validate the execution, capture any deferred work, and confirm it's truly done. Surfaces asfai:workstreams_finalize. (reviewandtestare the QA siblings.)
A note on naming
execute and finalize share the workstreams_ prefix with create and iterate - they're all the workstream lifecycle. In the loop, Create/Iterate shape the spec (Workstreams stage); Execute/Finalize do the creation (this stage).
What emerges re-enters the loop
What Creation produces - working code, content (blog, social, whitepaper, video, research reports), and patterns that crystallize into reusable workbenches - becomes new Intake. That's the compounding: the loop's output is the next loop's input.
Back to the loop →.