wrapup
npx machina-cli add skill eidetics/claude-eidetic/wrapup --openclaw/wrapup
Step 1: Detect Project
PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$PROJECT_ROOT" ]; then
PROJECT_NAME=$(basename "$PROJECT_ROOT")
NOTES_DIR="$HOME/.eidetic/notes/$PROJECT_NAME"
echo "PROJECT_NAME=$PROJECT_NAME"
echo "NOTES_DIR=$NOTES_DIR"
else
echo "NO_GIT_REPO"
fi
- Argument overrides PROJECT_NAME (e.g.
/wrapup myproject). - If NO_GIT_REPO and no argument, ask for project name.
Step 2: Extract Facts
From the conversation, extract:
- Decisions (choice, rationale, alternatives rejected)
- Changes (exact file paths, what changed)
- Numbers (metrics, costs, counts)
- Open questions (mark OPEN or ASSUMED)
- Next actions (specific, actionable)
- Blockers
If nothing meaningful to persist, inform user and stop.
Step 3: Write Note
mkdir -p "$NOTES_DIR"
Filename: $NOTES_DIR/<YYYY-MM-DD>-<topic-slug>.md (kebab-case, max 3 words, today's date).
---
project: <PROJECT_NAME>
date: <YYYY-MM-DD>
branch: <current git branch>
---
# <PROJECT_NAME> — <YYYY-MM-DD>: <Topic Title>
**Date:** <YYYY-MM-DD>
**Project:** <PROJECT_NAME>
## Decisions
- **[Title]**: [Choice]. Rationale: [why]. Rejected: [alternatives].
## Changes
- `path/to/file.ts`: [what changed and why]
## Numbers
- [measurements, counts, costs]
## Open Questions
- **OPEN**: [needs decision]
- **ASSUMED**: [assumption, needs validation]
## Next Actions
1. [specific action]
---
*<PROJECT_NAME> session recorded <YYYY-MM-DD>*
Date and project appear 4 times for search reliability — keep all occurrences.
Step 4: Index
index_codebase(path="<NOTES_DIR>")
Do not use force: true.
Step 5: Confirm
Report: file path saved, count of decisions/changes/open questions, index updated.
Source
git clone https://github.com/eidetics/claude-eidetic/blob/main/plugin/plugins/claude-eidetic/skills/wrapup/SKILL.mdView on GitHub Overview
Wrapup captures decisions, changes, metrics, questions, and next actions from a project session and saves them as a structured markdown note in a per-project notes folder. It then indexes the codebase for quick recovery and confirms what was saved.
How This Skill Works
The workflow detects the git project root to determine PROJECT_NAME and NOTES_DIR. It extracts Decisions, Changes, Numbers, Open Questions, Next Actions, and Blockers from the conversation, writes a markdown note named with the date and a topic slug, and finally runs an index_codebase call before reporting success.
When to Use It
- After finishing a coding sprint to lock decisions and next steps
- When a feature is paused or blocked and you need a formal record
- During code reviews to capture design choices and rationale
- When handing a project off to a new teammate for continuity
- When you want metrics, costs, and counts captured for future reference
Quick Start
- Step 1: Detect the project and set NOTES_DIR using the wrapup workflow
- Step 2: From the session, extract Decisions, Changes, Numbers, Open Questions, Next Actions, and Blockers
- Step 3: Write the markdown note to NOTES_DIR, index the codebase, and confirm the saved artifacts
Best Practices
- Ensure you run inside a git repo so PROJECT_ROOT is detected
- Use a concise topic slug (max 3 words) for the filename
- Explicitly record Decisions, Changes, Numbers, Open Questions, and Next Actions
- Make Next Actions concrete and assignable
- Run the indexing step and verify the confirmation output
Example Use Cases
- Post-sprint wrapup for a new feature: captured decisions, file changes, and estimated costs
- Bug fix session: documented root cause, changes, and open questions
- API design review: recorded decisions, rationale, and alternatives rejected
- Codebase handoff: notes prepared for a new team member with next actions
- Performance optimization pass: metrics collected and follow-up actions listed
