day-reconstructor — Claude Code skill: what it does, how to install
day-reconstructor turns Littlebird MCP activity into a record of a work session. Produces a dev log entry or a rundown of what shipped.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install littlebird-toolkit@wasp-nestWhat day-reconstructor does
The skill pulls session data through Littlebird MCP calls: search_user_context locates session boundaries and activity, LB_INTERNAL_LIST_MEETINGS and LB_INTERNAL_GET_MEETING bring in calls and their recorded decisions, and LB_INTERNAL_GET_ROUTINE_REPORTS pulls up its earlier write-ups first, so a project spanning several days reads as one continuous thread rather than disconnected notes. After that it sorts and deduplicates entries, runs a redaction pass over sensitive values, and sorts findings into confidence tiers: confirmed, strong, weak, or not evidence at all.
It refuses to run without a connected Littlebird MCP on a Power or Pro plan, stopping outright if the required tools aren't present in the session. Git access is optional — without it, file-level claims stay at a lower confidence tier instead of being confirmed.
The daily routine is scheduled around the end of the user's own session plus roughly an hour, not midnight, since the target workflow runs overnight and crosses the date boundary.
What it helps with
- log a work session from actual activity instead of commit history
- recover decisions and problems raised during calls
- merge scattered session notes into one thread-by-thread report
- draft a standup update from what actually happened
- carry context forward across a multi-day project
Example prompts for the agent
- Reconstruct what I worked on today and write the dev log
- Draft a changelog entry for this session
- Put together my standup from last night's work
How to install day-reconstructor
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install littlebird-toolkit@wasp-nestThis installs the whole littlebird-toolkit plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill day-reconstructor -a claude-code3Manually: put the files in place
~/.claude/skills/day-reconstructor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/day-reconstructor/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill day-reconstructor -a codex2Manually: put the files in place
.agents/skills/day-reconstructor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill day-reconstructor -a cursor2Manually: put the files in place
.cursor/skills/day-reconstructor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/littlebird-toolkit/skills/day-reconstructor2Manually: put the files in place
.github/skills/day-reconstructor/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill day-reconstructor -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/littlebird-toolkit/skills/day-reconstructorManually: put the files in place
.devin/skills/day-reconstructor/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about day-reconstructor
How do I install day-reconstructor in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install littlebird-toolkit@wasp-nest.
What does day-reconstructor do?
It pulls a user's tracked activity from Littlebird MCP and turns it into a session log covering what was done, which problems came up, and what got decided. Without commits to go by, this is what captures the steps that happen in between them.
What does day-reconstructor need to run?
It needs a connected Littlebird MCP on a Power or Pro plan, and stops instead of working from memory if that's missing. Git access is optional but sharpens how confidently findings get tied to specific files.