Menu
The reviewer agent's structured process for identifying factory improvement opportunities and generating evidence-backed intents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | review-protocol |
| description | The reviewer agent's structured process for identifying factory improvement opportunities and generating evidence-backed intents. |
Generate well-formed intent files for the human to curate. Your job is observation and identification — not execution. The human decides what gets built.
Before identifying anything, read:
specs/inbox/ — pending intents awaiting specspecs/drafting/ — intents being speccedspecs/ready/ — specced and awaiting builderspecs/archive/ — completed specs (reference)Note what topics are already addressed. Do not generate competing or duplicate intents. If an existing intent partially addresses a concern, note it in your daily log but do not generate a competing intent.
Read memory/*/needs.md across all agent directories.
For any entry where status: open and the created timestamp is more than 2× your heartbeat interval in the past, note it in your review output as an escalated item. Format:
Escalated need: {id} [{agent}, created {timestamp}]
{blocked field}
This is informational — you cannot resolve needs entries. The human runs factory needs to see the full list and factory needs --resolve {id} after acting.
Do not generate a competing intent if the blocker is already captured in a needs entry.
Work through these categories. Stop at 3 high-quality intents — do not exhaust all categories if you've already found 3 worth generating.
Read learnings/failures/. Look for:
{date}-{project}-{summary}.md)Intent candidate: recurring theme with 2+ entries, no existing fix in skills/ or specs.
Read universe/values.md. For each value:
Intent candidate: value that has no structural support and no existing spec addressing it.
Read universe/synthesis/factory-blueprint.md. Check:
Intent candidate: described capability with no evidence of implementation or planned work.
Scan skills/{agent}/ directories. For each agent in agents.yaml with available skills listed:
skills/{agent}/{skill-name}/SKILL.md exist with content?.gitkeep (i.e., listed but unbuilt)?Also check: which agents have daily logs (memory/daily/{agent}/) but have only the shared skill set?
Intent candidate: skill listed in agents.yaml but with no SKILL.md content. Cite the specific agent and skill name.
Read specs/archive/ and tasks/verified/. Look for:
Intent candidate: explicit follow-up mention in verified work with no existing spec.
Read memory/shared/KNOWLEDGE.md and memory/shared/PROJECTS.md. Look for:
Intent candidate: concrete inconsistency or stale entry.
Rank by impact:
Generate the top 3. Log the rest in your daily log for next run.
For each intent to generate:
{topic}-{aspect}.md (e.g., missing-verifier-skills.md, value-transparency-gap.md)specs/inbox/{slug}.md:<!-- generated by: reviewer | run: {YYYY-MM-DD}T{HH:MM} | evidence: {brief citation} -->
# {working-title}
## What I'm Seeing
[Concrete observations with file/directory references — be specific]
## What I Want to See
[Desired end state — describe the outcome, not the implementation]
Write to memory/daily/reviewer/{YYYY-MM-DD}.md:
## {HH:MM} — Review Run
**Categories reviewed**: [list all reviewed]
**Candidates identified**: [count]
**Intents generated**: [list slugs]
**Deferred**: [list topics not generated, with reason]
**Skipped (duplicate)**: [list topics already addressed]
If NO_REPLY: note what was reviewed and why nothing was generated.
Every "What I'm Seeing" section must reference:
skills/verifier/scenario-evaluation/ contains only .gitkeep)Generic observations ("the factory lacks X") without file/directory evidence are not acceptable.