원클릭으로
review-progress
Use when user wants to assess progress toward an open-ended goal by reading and summarizing all iteration journals
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when user wants to assess progress toward an open-ended goal by reading and summarizing all iteration journals
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | review-progress |
| description | Use when user wants to assess progress toward an open-ended goal by reading and summarizing all iteration journals |
| user-invocable | true |
Assess progress toward an open-ended goal by reading iteration journals, summarizing achievements, identifying patterns, and suggesting next steps.
Core principle: Regular review reveals trends, validates strategy, and informs future direction.
Use this skill when:
/review-progress commandCan be used:
| Step | Action | Tool/Agent |
|---|---|---|
| 1. Locate goal | Find autonomy directory | Glob |
| 2. Load summary | Read summary.md if exists | Read |
| 3. Load recent iterations | Get last 3-5 iterations | Task (journal-reader) |
| 4. Analyze progress | Identify trends, metrics, patterns | Manual analysis |
| 5. Present report | Structured progress summary | Direct output |
Find the goal directory:
# Use Glob to find goal
pattern: "autonomy/*/goal.md"
If multiple goals found:
If no goal found:
"No autonomy goal found in this project. Use `/start-iteration` to begin tracking an open-ended goal."
Check for summary.md:
# Use Read to load summary
file: "autonomy/[goal-name]/summary.md"
If summary exists:
If summary doesn't exist:
Dispatch journal-reader to load recent context:
Task tool with subagent_type: "autonomy:journal-reader"
Prompt: "Read all iteration files for goal '[goal-name]' (or last 5-10 if many exist).
Extract:
- Progress timeline
- Completed work by iteration
- Persistent blockers
- Metric trends
- Skills most frequently used
- Strategic pivots"
Model: haiku
Wait for agent response with structured findings.
Synthesize information from summary and journal-reader:
Calculate metrics:
Identify patterns:
Assess trajectory:
Flag concerns:
Generate comprehensive progress report:
# Progress Report: [Goal Name]
**Report Date:** [Today's date]
**Goal Status:** Active
**Iterations Completed:** [N]
**Time Elapsed:** [First date] - [Latest date] ([X days/weeks/months])
---
## Goal Statement
[From goal.md]
---
## Progress Overview
### Key Metrics
| Metric | Starting | Current | Change |
|--------|----------|---------|--------|
| [Metric 1] | [Value] | [Value] | [+X% or -Y%] |
| [Metric 2] | [Value] | [Value] | [+X% or -Y%] |
### Timeline of Major Work
- **Iteration 1:** [Summary of work]
- **Iteration 2:** [Summary of work]
- **Iteration N:** [Summary of work]
### Completed Initiatives
✅ [Initiative 1]: [Outcome]
✅ [Initiative 2]: [Outcome]
### In Progress
🚧 [Initiative 3]: [Current state]
---
## Current State
### What's Working Well
- [Positive pattern 1]
- [Positive pattern 2]
### Current Blockers
- **[Blocker 1]:** [First appeared iteration X, still unresolved]
- **[Blocker 2]:** [Description and impact]
### Open Questions
- [Question 1]
- [Question 2]
---
## Analysis
### Strategic Evolution
[How has the approach changed over time?]
- Iteration 1-3: [Initial strategy]
- Iteration 4-6: [Pivot or continuation]
- Current: [Where we are now]
### Skills & Methods Most Used
- **[Skill/workflow]:** Used in [X] iterations for [purpose]
- **[Skill/workflow]:** Used in [Y] iterations for [purpose]
### Effectiveness Assessment
[Is the current approach working?]
- **Strengths:** [What's effective]
- **Weaknesses:** [What's not working]
- **Opportunities:** [What could be explored next]
---
## Recommendations
### Immediate Next Steps
1. [Specific action based on current state]
2. [Specific action based on blockers]
### Strategic Considerations
- [Consider pivot if X]
- [Double down on Y because Z]
- [Investigate new approach for A]
### Health Check
[Overall assessment: Is goal on track? Should strategy change? Is this goal still valuable?]
---
**This is an open-ended goal - continuous iteration and optimization expected.**
If reviewing during active iteration:
If no iteration active:
Suggest reviewing progress:
Be honest:
Constructive:
| Mistake | Reality |
|---|---|
| "Progress looks good" without data | NO. Use specific metrics and evidence. |
| "I'll review just the last iteration" | NO. Look at full history for patterns. |
| "No need to flag concerns" | NO. Honest assessment helps course-correct. |
| "I'll skip analysis and just list work done" | NO. Synthesis and insights are the value. |
| "Goal is open-ended so no progress metrics" | NO. Even open goals have measurable indicators. |
Once review is complete:
Use when working in a project that has a `.agents/` directory or when the user asks about Conway Architecture, the conway-architecture plugin, domain agents, owned_paths enforcement, or how to coordinate a persistent subagent team that shadows the application's architecture
Use when reading or writing OST (Outcome / Strategy / Tactic) graph data in the `agents` TypeDB database - covers the falsifiability rubric, the three-layer discipline, ID conventions, lifecycle transitions, and the structured Task fields that replace generic descriptions
Use when interacting with a TypeDB 3.x database via the typedb MCP tools (typedb-query, typedb-database_schema, etc.) - covers schema-first workflow, transaction types, TypeQL 3.x syntax (which differs materially from 2.x), and the most common failure modes
Use when analyzing another branch's iteration journals to extract findings, decisions, and insights from divergent work
Use when user wants detailed status report for single autonomy branch including iteration timeline and metrics progression
Use when saving current iteration progress mid-conversation, before context compaction, or at interim pause points