The Official Home of the Framework

RICOF
-STEC

Role · Instruction · Context · Output Format  —  Style · Tone · Examples · Constraints

RICOF-STEC™ is an eight-component system for engineering prompts. Four components build the instruction. Four shape the result. Together they turn a request into a specification.

1-1

What it is

1-1.a

Most prompts fail for the same reason: they describe a wish instead of a job. The model is left to guess who it is, what standard applies, what the reader needs, and what the finished thing should look like. It guesses plausibly, and the output is plausible — and wrong.

RICOF-STEC removes the guessing. Every component answers a question the model would otherwise answer for you.

1-1.b

The framework runs in two engines. The Core Engine (RICOF) is mandatory — omit any part of it and the model fills the gap with an assumption. The Sub-Engine (STEC) is corrective: it is what you reach for when the output is structurally right but tonally, stylistically, or dimensionally wrong.

1-1.c

It is model-agnostic and medium-agnostic. The same eight components govern a text prompt, an image prompt, a video shot list, a voice script, a code specification, and an agent's operating instructions. Only the vocabulary inside each component changes.

The Eight Components

Core Engine + Sub-Engine
Core Engine — RICOF — required
RRole

Who the model is, and by whose standard the work will be judged. Sets the expertise it draws on.

IInstruction

The task, stated as one action verb. What is actually being asked for — not the topic, the job.

CContext

The situation, the audience, and the source material. Everything the model can't infer but needs.

OFOutput Format

The shape of the deliverable — structure, sections, length, medium, file type.

Sub-Engine — STEC — corrective
SStyle

The register and conventions of the craft. How a professional in this field writes, shoots, or builds.

TTone

The emotional temperature. How the finished work should land on the person receiving it.

EExamples

A sample of the target. The single fastest correction available when an output comes back wrong.

CConstraints

The hard limits. What to never do, never exceed, never include. Failure conditions, stated up front.

1-2

All eight, in one prompt

1-2.a

Every component below is labelled. In practice they are written as continuous prose — the labels are here only to show the seams.

You are a clinical pharmacist writing for patients, not for colleagues.R Write a one-page handout explaining how to take a new medication safely.I The readers were diagnosed last week, read at roughly a sixth-grade level, and are seen at a county clinic with no follow-up scheduled.C Return a titled handout with four short sections and a closing bulleted list headed "Call your doctor if."OF Use plain declarative sentences; define any clinical term in parentheses the first time it appears.S Reassuring and matter-of-fact — never alarming.T Match the structure and voice of the handout pasted below.E Do not exceed 400 words. Do not state specific doses.C
1-2.b

Strip the last four and the model still produces a handout — just not one you'd hand to a patient. That is the division of labour between the engines: RICOF decides whether you get the right artifact, STEC decides whether it's usable.

1-3

Origin & citation

1-3.a

RICOF-STEC™ was developed by Ben F. Fominyam and published by Operation Digital Alchemy in The Prompt Engineering Field Manual: RICOF-STEC — A Complete System for Multimodal AI, Creative Media, Code, and Autonomous Workflows. This page is the framework's canonical reference and the authoritative source for its definition.

Canonical URL
https://operationdigitalalchemy.com/ricof-stec
How to cite
Fominyam, B. F. (2026). The RICOF-STEC™ Framework. Operation Digital Alchemy. https://operationdigitalalchemy.com/ricof-stec
Correct usage of the mark
Write it as RICOF-STEC™ — all capitals, hyphenated, with the symbol on first use in any document. Not "Ricof-Stec," not "RICOF STEC."