DBS

Coordinate end-to-end change management across the DBS pipeline with structured state tracking.

18|2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/MetalLegBob/solana-vibes-kit --skill dbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: DBS
Source: https://github.com/MetalLegBob/solana-vibes-kit/tree/main/dont-break-shit
Command: npx skills add https://github.com/MetalLegBob/solana-vibes-kit --skill dbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DBS provides a disciplined framework to manage large-scope codebase changes, ensuring changes are deliberate, auditable, and testable.

Core Features & Use Cases

  • End-to-end change management across the full pipeline (brief, interview, analyze, map, discuss, plan, execute) for complex projects.
  • Structured state tracking and artifact generation (.dbs/*) to support audits, reviews, and rollback.
  • GSD-backed execution phases with validation gates and cross-phase consistency checks.

Quick Start

Start a DBS session by running /DBS:brief to begin.

Frequently Asked Questions about DBS

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

FAQPage Schema
How do I manage large-scale codebase changes without losing track of progress?

Managing large-scale codebase changes requires a structured framework that tracks progress through a state file like .dbs/STATE.json. This ensures modifications remain deliberate, auditable, and testable across all project phases.

What is the best way to structure complex code modifications across multiple phases?

Structuring complex code modifications is best handled through a full pipeline: brief, interview, analyze, map, discuss, plan, and execute. Each phase builds upon validated artifacts to guide decisions and maintain cross-phase consistency.

How do I start a structured change management session for a complex project?

To start a structured change management session, initiate the pipeline with a brief phase to define the project scope. This kickoff generates the initial artifacts and state tracking files needed to guide subsequent analysis and execution phases.

Do I need GSD to execute structured codebase modifications?

Yes, GSD is required for the execution phases of this change management pipeline. It provides the validation gates and cross-phase consistency checks necessary to safely apply and verify the planned codebase modifications.

Can I audit and rollback code changes tracked in .dbs state files?

Yes, the .dbs directory generates structured state and artifacts specifically to support audits, reviews, and rollback. This artifact generation ensures every modification is deliberate and traceable throughout the end-to-end pipeline.