dbs-restore

Restore saved business diagnosis session snapshots to resume interrupted workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zhongjjm-design/claude-skills --skill dbs-restore-zhongjjm-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbs-restore
Source: https://github.com/zhongjjm-design/claude-skills/tree/main/dbs-restore
Command: npx skills add https://github.com/zhongjjm-design/claude-skills --skill dbs-restore-zhongjjm-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users often interrupt ongoing business diagnosis sessions due to conversation timeouts, topic switches, or breaks, losing all prior context, conclusions, and next steps, and are forced to restart the entire diagnosis process from scratch.

Core Features & Use Cases

  • Snapshot Restoration: Retrieves the full content of the most recent saved diagnosis snapshot, including user complaints, validated conclusions, rejected options, pending hypotheses, and recommended next steps.
  • Multi-Project Support: Allows switching between different business projects to access their respective diagnosis histories, with project names automatically derived from the current working directory.
  • Edge Case Handling: Gracefully handles scenarios like missing snapshots, empty project directories, or invalid snapshot indices by listing recent active projects or guiding users to run a diagnosis first.
  • Use Case: If you were halfway through a business model diagnosis for your new SaaS product when the conversation ended, you can use this skill to pull up all your previous findings and continue exactly where you left off without re-explaining your business context.

Quick Start

Use the dbs-restore skill to pull up your most recent diagnosis snapshot for your current project and continue your analysis from where you left off.

Frequently Asked Questions about dbs-restore

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

FAQPage Schema
How do I resume an interrupted business diagnosis session without losing context?

To resume an interrupted business diagnosis session without losing context, restore a previously saved snapshot to retrieve validated conclusions, rejected options, pending hypotheses, and recommended next steps. This eliminates the need to re-enter historical context or re-analyze prior business problems.

Can I restore business diagnosis history for multiple different projects?

Yes, you can restore business diagnosis history for multiple projects. The skill supports multi-project state organization, automatically deriving the project name from the current working directory to switch between different diagnosis histories.

What happens when trying to restore a business diagnosis snapshot that is missing or corrupted?

When a business diagnosis snapshot is missing or corrupted, the system applies graceful error handling by listing recent active projects or guiding you to run a diagnosis first, ensuring reliable state recovery without crashing.

How do I retrieve the most recent business model diagnosis findings after a conversation timeout?

To retrieve the most recent business model diagnosis findings after a timeout, use timestamp-based snapshot sorting to pull up the full content of your latest saved session. You can then continue your analysis exactly where you left off without re-explaining your business context.

Does retrieving a session snapshot restore the entire content of a prior business diagnosis?

Yes, retrieving a session snapshot restores the entire content of a prior business diagnosis, including user complaints, validated conclusions, rejected options, pending hypotheses, and recommended next steps for complete work continuity.