Agent
Decides and acts, within the frame you define.
Craft · Frameworks
Agents, skills, loops, workflows, composed correctly.
Using the frameworks well means composing agents, skills, loops and workflows so the system does the heavy, repetitive work, deterministically where it must. Humans keep the two ends: the requirements and the quality gate.
§01 Craft
Building blocks, not buzzwords.
An agent decides and acts; a skill is a reusable capability; a loop repeats a step until a condition holds; a workflow chains it all in a fixed order. Composed correctly, the system takes on the repetitive heavy lifting, you do not orchestrate every step by hand. The craft is not in the single prompt, but in making these blocks mesh cleanly.
Skill
A reusable capability, built once, usable everywhere.
Loop
Repeats a step until the condition holds.
Workflow
Chains it all in a fixed, traceable order.
§02 Craft
Software example: you write the requirement, not the code.
You state what the software has to do and define the test that proves it. The framework runs the loop: the agent writes code, runs the test suite, reads the errors, fixes, and repeats, until the loop terminates cleanly. You implement nothing by hand; you define what “done” means, and the system works its way there. The same pattern carries from software to any other use case.
- 01 Define requirement & test
- 02 Write code
- 03 Run the test suite
- 04 Read errors, fix
- 05 Loop until green
- 06 Quality gate & sign-off
Human AI Algorithm
§03 Craft
Human at the start, human at the end, algorithm in between.
As in any serious software project (ISO, arc42), the result is proven, not trusted. A human-defined metric and a deterministic quality gate decide pass or fail, an algorithm checks, not the model grading itself. The middle may be stochastic; the gate never is. Afterwards everything is documented and structured, ready for the next change.
The middle may be stochastic. The gate never is.
§04 In practice
How it runs in practice
Example: software. The same model fits any use case.
Human-owned
Define
You and AI define the requirements together.
AI + framework
Build
The framework runs the loops and implements, no manual coding.
Human-owned
Verify
A deterministic quality gate (arc42) proves the requirements are met.
The start and the end stay human-owned; the quality gate is deterministic. Everything stays documented and retrievable for the next change.
§05 Read on
More on frameworks
How agents, skills, loops and workflows compose cleanly, with a human at the start and a deterministic gate at the end, we show in the blog and in mema's code.