القائمة
The probabilistic satisfaction metric. Not pass/fail — a judgment about the fraction of users who would be satisfied with this output.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Complete reference for the factory CLI — all commands, arguments, options, and usage. Use when an agent needs to invoke factory commands, check correct syntax, or understand available options.
When and how to write a human-action-needed entry to memory/{agent}/needs.md. Agents write these entries when they hit blockers that only a human can resolve.
When you encounter a failure, correction, or new pattern, write a learning and optionally propose a skill.
How the factory workspace is organized and what each directory means.
What to examine during a reflection pass and how to write observations to memory/{agent}/needs.md.
When and how to write scenario holdouts for factory verification.
| name | satisfaction-scoring |
| description | The probabilistic satisfaction metric. Not pass/fail — a judgment about the fraction of users who would be satisfied with this output. |
The satisfaction score answers this question:
"Of a population of users who wanted what the spec describes, what fraction would be satisfied with this output?"
Express as N/10. This is a judgment about fitness for purpose, calibrated against the spec's stated intent — not a code quality score, completeness checklist, or binary pass/fail.
9-10/10 — All verification criteria satisfied, no unexpected behaviors. 7-8/10 — Core behavior correct. Minor gaps most users wouldn't encounter. 5-6/10 — Core behavior partially correct. Missing behaviors a meaningful fraction needs. 3-4/10 — Key requirements not met. 1-2/10 — Fundamental misalignment with the spec.
Always accompany the score with:
A score of 8/10 or higher moves to tasks/verified/.
A score of 7/10 or below moves to tasks/failed/ with a full failure report.
