synthesis_checkpoint
Save progress after completing meaningful work.
When to Call
Call checkpoint after any significant task:
- Bug fix completed
- Feature implemented
- Refactor done
- Decision made
- Test run completed
Input Schema
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | Project ID from synthesis_start |
summary | string | Yes | Brief summary of what was accomplished |
files_changed | string[] | No | List of files modified |
completed_steps | number[] | No | 1-based indices of Next Steps to mark complete |
add_next_step | string | No | New step to add if discovered |
details | string | No | Longer description for work log |
Example Request
{
"project_id": "my-api-project",
"summary": "Implemented JWT authentication",
"files_changed": ["src/auth/jwt.js", "src/routes/login.js"],
"completed_steps": [2],
"add_next_step": "Add refresh token rotation"
}
Response
{
"success": true,
"project_id": "my-api-project",
"summary": "Implemented JWT authentication",
"actions": [
"updated context",
"completed step 2",
"added next step",
"created work-log entry"
]
}
What Gets Updated
- Project context - Updates current state with new progress
- Next Steps - Marks specified steps as completed
- Work log - Creates a timestamped entry of what was accomplished
Lesson Hints
If the summary contains keywords like "fix", "bug", "error", the response includes a hint:
"lesson_hint": {
"should_create_lesson": true,
"type": "incident",
"reason": "This work involved fixing issues."
}