Index listing of all 18 items tagged with #workflow.
A practical architecture for running AI agents reliably using instruction contracts, handoff memory, and measurable quality gates.
A practical explanation of the difference between autonomous-seeming agents and controlled workflows, and why the distinction matters in production systems.
A case study in using Flowright WebsiteOps to prepare, verify, review, and hand off website content without autonomous publishing.
How to design AI skills with clear boundaries, input and output contracts, tool limits, side-effect controls, and escalation paths.
Why evaluation should live inside the operating loop of an AI system instead of being treated as an occasional review ritual.
A practical case study showing how structured instructions, handoff memory, and quality gates improved consistency and coverage in this repository.
How to design robust handoff protocols and shared memory blackboards to preserve state continuity across multi-agent boundaries.
How to define expected behavior, detect regressions, version skill changes safely, and decide when rollback is the right move.
A prompt is one instruction, a skill is a reusable capability, an agent decides what to do next. Here is where each belongs and how to tell which you need.
A practical definition of skills as reusable execution units that sit between prompts and workflows in modern AI systems.
A launcher flow that hands a local Ollama model to Codex or OpenCode. Setup walkthrough, the two gates it checks, failure modes and what fixed them.
A weekly pass format for keeping note structures coherent, linked, and retrieval-ready.
A compact weekly review format for tracing decisions, evidence, and outcomes in AI workflows.
One file per day, minimal structure, and a quick export habit.
Short markdown logs + ripgrep to keep the archive searchable.
Three compact templates for defining, reviewing, and composing AI skills as reusable execution units.
A control-plane framing where policy, infrastructure, workflows, and quality checks become versioned artifacts.
The simplest way to keep experiments honest and reversible.