Learning Reviews
Turn completed or postponed work into reusable learning.
A Learning Review is a generated read-only review of one or more tasks or goals. It uses the targets, related tasks or goals, logs, and source packs to explain what was learned and what follow-up action may be useful.
Reviews do not save anything. They do not create packs, update packs, or create suggestions. They return stats and, for detailed reviews, Markdown content so a person or agent can decide whether to call existing pack or suggestion operations.
When reviews appear
Epismo may return a lightweight learningReview when a track reaches a reviewable outcome:
| Track type | Trigger status | Why it matters |
|---|---|---|
task |
done |
The task is complete enough to extract local execution notes. |
goal |
completed |
The outcome succeeded and may contain reusable process. |
goal |
postponed |
The work stopped or changed direction, which can reveal missing prerequisites, risks, or pack warnings. |
The lightweight review is included in the update response only. It returns stats that help the UI suggest inspecting the learning; it is not a persisted artifact.
Detailed reviews
Run a detailed review when you want a Markdown review that can be read directly or passed to an agent:
epismo track review <track-reference>
epismo track review <track-reference> <another-track-reference>The same operation is available through MCP as epismo_track_review with a references array and through the HTTP API as POST /v1/tracks/review with targetIds.
Detailed reviews collect:
- the target task(s) or goal(s)
- linked goal context for a task
- linked tasks for a goal
- parent, dependency, and child tasks for a task
- logs on the relevant records
- source workflow/context packs referenced by
sources
The generated review follows the primary language of the seed knowledge base content and logs. If seeds mix languages, it prefers the language of the target tasks or goals.
Recommendations
Recommended actions are suggestions, not writes:
| Recommendation type | Typical next step |
|---|---|
| Create a pack | Use epismo pack create when the work produced a new reusable pattern. |
| Update a pack | Use epismo pack update when you own the relevant source pack. |
| Suggest a change | Use epismo suggestion create when the source pack belongs to someone else. |
| No action | Keep the learning as review output when it is not reusable enough yet. |
Use review output as evidence, then choose the normal pack or suggestion command yourself.
Relationship to logs
Logs are durable timeline entries attached to a track. Reviews read logs as input, but review output is not automatically written back as a log. If the review contains a decision or result that should remain on the track, append it explicitly with a review log.