Codex
Claude
GeminiWhat you do
- State the question or decision the memory review should support.
- Confirm the project scope and desired persistence level.
- Review the recommendation before starting any follow-up workflow.
Any team resuming or orienting complex project work / core
Project Memory Review
A bounded memory review that explains what the project knows, what remains uncertain, and the best next action.
From request to resultA complete plan you can follow.
Visible planThe problem
Projects accumulate runs, decisions, evidence, and unfinished work faster than an agent can safely reconstruct from chat.
AI can connect evidence across several project records while keeping source refs and uncertainty visible.
What the agent does
- Check active tracker and run-plan state first so the review does not ignore or duplicate current work.
- Query only the relevant project sources and preserve their refs.
- Separate facts, decisions, stale assumptions, contradictions, and gaps.
- Return a recommendation or a concrete run-plan proposal without executing it implicitly.
When this workflow helps
A reusable method, adapted to the request.
- The agent needs to understand recent project history before planning work.
- A workflow should start from prior runs, learnings, experiments, and decisions.
Before it starts
Ready with project context
- A clear question or decision
- An existing StackOS project with relevant stored context
What proves it worked
Evidence, not a success claim.
- Source-linked memory summary
- Explicit gaps and conflicts
- Recommended next action with rationale
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Clarify Goal And Scope
Restate the goal, assumptions, constraints, and missing inputs.
- 02Passes to next stage
Retrieve Bounded Context
Query only the declared fields and limits before reasoning.
- 03Verified outcome
Propose Next Plan
Draft an agent-authored plan, explicit open questions, and any approval needs.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop after the recommendation unless the operator explicitly starts follow-up work.
- If the project scope or source authority is unclear, stop with a bounded clarification.
- If records conflict, present both and name the decision needed.
Specialists inside this workflow