From bdk
Save current work progress to .bdk/save-progress/ for resuming in a future session. Use when context is large, work is in progress, and you want to stop and continue later.
npx claudepluginhub broneq/bdk --plugin bdkThis skill uses the workspace's default tool permissions.
> Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference.
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.
Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference.
Capture work state to .bdk/save-progress/$ARGUMENTS.md for future resume.
Announce: "Saving progress to .bdk/save-progress/$ARGUMENTS.md"
$ARGUMENTS empty: say "Usage: /bdk:save-progress " and stop.bdk/save-progress/$ARGUMENTS.mdCollect in parallel:
git branch --show-currentgit diff --name-only HEAD~3..HEAD 2>/dev/nullTaskList has tasks:
AskUserQuestion: "Want to add notes or adjust statuses before saving?"No tasks:
AskUserQuestion:
From history, identify every BDK skill invoked. For each:
Ask user:
Write to .bdk/save-progress/$ARGUMENTS.md:
# Progress: {name}
**Branch:** {current branch}
**Saved:** {YYYY-MM-DD}
**Status:** In Progress
---
## Used Skills
- `/bdk:skill-name` — Brief description | **Reuse: Yes/No** (reason)
## Reference Files
- `{path/to/plan.md}` — Description
## Tasks
| # | Task | Status | Notes |
|---|------|--------|-------|
| 1 | {task description} | done | |
| 2 | {task description} | in_progress | |
| 3 | {task description} | todo | |
## Important Notes
- {note 1}
[save-progress] Saved to .bdk/save-progress/$ARGUMENTS.md
Tasks: {N done} / {N in_progress} / {N todo}
References: {N files}
Skills: {N skills used}
Notes: {N notes}
Resume with: /bdk:restore-progress $ARGUMENTS
done, in_progress, todo, skipped, blocked