ce:resume

Summarizes recent git history, pending ideas, and active plans to orient returning developers.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-resume-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce:resume
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/ce-resume
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-resume-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to a project after time away, developers waste time reconstructing context: what was last done, what ideas are waiting, and which plans are still in progress. This Skill reads three project sources and produces a concise status summary with a recommended next step. ## Core Features & Use Cases - Parallel context gathering: Reads the last 10 git commits, scans IDEAS.md for unchecked items, and inspects docs/plans/*.md frontmatter for active plans. - Three-part status summary: Outputs what was last done, what is waiting (ideas and active plans), and a suggested next action based on available data. - Interactive handoff: Asks the user where to start and routes directly into ce-work, ce-ideas, or ce-ideate based on the selection. - Use Case: You open a side project after two weeks away. Run the resume command to see your last functional commit, three pending ideas, and your active plan, then jump straight back into work. ## Quick Start Ask the assistant to resume the project and summarize recent git activity, pending ideas, and active plans.

Frequently Asked Questions about ce:resume

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I quickly catch up on a project after time away?▼

Run the resume command, which reads your last 10 git commits, scans IDEAS.md for unchecked items, and lists active plans from docs/plans. It outputs a three-part summary and suggests the next step.

What data sources does the resume workflow read?▼

It reads three sources in parallel: git log for recent commits, the IDEAS.md file for unexecuted ideas, and Markdown files in docs/plans with status active in their YAML frontmatter.

What happens if the project is not a git repository?▼

The git source is marked unavailable and the summary notes that git history could not be read. The other two sources, IDEAS.md and active plans, are still collected and reported normally.

Does the resume command work without an IDEAS.md file?▼

Yes. If IDEAS.md is missing, the summary notes its absence and suggests creating one. The recommendation logic then falls back to active plans or suggests starting fresh ideation.

How does the resume skill decide the recommended next step?▼

If an active plan exists, it recommends continuing the most recent one. If only ideas exist, it suggests picking one from IDEAS.md. If both are empty, it suggests starting fresh ideation.