npx claudepluginhub zate/cc-plugins --plugin devloopThis skill is limited to using the following tools:
Save the current devloop plan state for resuming after a context reset. **You do the work directly.**
Saves Plan-Build-Run session state to .continue-here.md for resumption, capturing current phase, plan progress, git status, and blockers from .planning files.
Creates .continue-here.md handoff files in .planning phases to capture current phase, tasks completed/remaining, decisions, blockers, and next actions for pausing and resuming work sessions.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Save the current devloop plan state for resuming after a context reset. You do the work directly.
Use the Read tool to read .devloop/plan.md.
If no plan exists, tell user to run /devloop first.
Identify the next pending task (first - [ ] in the plan).
Write to .devloop/next-action.json:
{
"task": "Task X.Y: Description",
"phase": "Current Phase Name",
"notes": "Any context about work in progress",
"saved_at": "YYYY-MM-DD HH:MM"
}
Tell user:
State saved to .devloop/next-action.json
Next steps:
1. Run /clear to reset context
2. Run /devloop:run to resume work
Tip: Before doing a full /devloop:fresh + /clear, try pressing Esc+Esc first. This triggers partial summarization which compresses your context without losing state — often enough to keep working without a restart.
Note: The next-action.json file is consumed (deleted) when /devloop:run runs.