Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/davidbuenov/dbv-specs-ops/llms.txt

Use this file to discover all available pages before exploring further.

As the dbv-specs-ops framework evolves, new phases, agents, and configuration fields are added to the prompt files. The UPGRADE_PROMPT.md agent automates the entire upgrade process: it detects your current framework version, calculates exactly which files need to change, downloads or lists the updates, and applies them — all without touching a single file that belongs to your project. Your specifications, architecture decisions, backlog, and source code are guaranteed to remain exactly as you left them.
The following files are permanently protected and will never be modified by the upgrade agent under any circumstances. They belong to your project, not to the framework:
FileWhy it is protected
docs/SPECIFICATIONS.mdYour project requirements
docs/ARCHITECTURE.mdYour technical decisions
task.mdYour backlog and project state
CHANGELOG.mdYour project version history
README.mdYour project documentation
walkthrough.mdYour delivery history
implementation_plan.mdYour in-progress technical plans
All source codeYour application

​
How to trigger an upgrade

Tell your AI assistant: 
Read docs/UPGRADE_PROMPT.md and update my project.
The agent will execute all five phases automatically and show you a summary when done.

​
The 5-Phase Upgrade Process

1

Phase 1 — Version detection

The agent reads project.config.md and looks for the **Framework Version:** field.
  • If the field exists → its value is used as the current version.
  • If the field is missing → the agent asks you to identify your version manually. You can check by looking at what platform files exist in your project: .windsurfrules was added in v1.1.0, and project.config.md itself was added in v1.2.0.
The current latest version of the framework is v2.1.0. If your project is already on v2.1.0, the agent reports that everything is up to date and stops.
2

Phase 2 — Change manifest

Based on the detected version, the agent calculates every file that needs to be added or updated to reach v2.1.0. The full version-to-version delta is:
VersionKey additions
v1.1.0ANTIGRAVITY.md, .windsurfrules, docs/ADOPTION_PROMPT.md, docs/README.md
v1.2.0project.config.md (new fields), updated platform adapters
v1.2.1README.template.md, bootstrap language question
v1.3.0docs/DESIGN.md, docs/UPGRADE_PROMPT.md, framework_version field in project.config.md
v1.4.0memory.md, Architect Review in /plan, XML-structured prompts
v1.5.0Enforcement Layer, Phase Gates, Memory Gate, Adversarial Review
v1.5.1Fixed English documentation inconsistencies in README.md
v1.5.2Trust boundary in MASTER_PROMPT.md, granular Memory Triggers
v2.0.0docs/AGENTIC_ENGINEERING.md, Conductor/Orchestrator modes, Evals in /test, Security Review in /code-simplify, Agent Harness in ARCHITECTURE.md, Model Routing Guidelines
v2.1.0Agent Readiness in /spec, /build, /ship; agent.json/mcp.json cards; Agent Readiness (Web) field in project.config.md
Only the delta from your current version to v2.1.0 is applied — files already present from earlier versions are not re-downloaded unnecessarily.
3

Phase 3 — Apply changes

The agent applies updates using one of two options depending on network availability:Option A — Automatic download (with network access)For each file marked as NEW or MODIFIED, the agent downloads the latest version from:
https://raw.githubusercontent.com/davidbuenov/dbv-specs-ops/main/<filepath>
Files updated this way include GEMINI.md, CLAUDE.md, ANTIGRAVITY.md, .windsurfrules, .github/copilot-instructions.md, README.template.md, and all docs/ prompt files. If any download fails, the agent shows you the direct link so you can save it manually.Option B — Manual download (without network access)If the agent cannot reach the internet, it shows you this message:
“I don’t have internet access right now. Please download the following files manually from GitHub and copy them to the indicated paths in your project.”
It then lists every file that needs updating with its exact target path, and links to github.com/davidbuenov/dbv-specs-ops for the Raw download.
4

Phase 4 — Surgical changes

Some upgrades require adding a single field or line to a file rather than replacing it entirely. The agent makes only the minimum necessary change:project.config.md — add Framework Version fieldIf the Framework Version field does not already exist, one line is appended to the ## Project Identity section:
- **Framework Version:** 1.4.0
The rest of project.config.md (your project name, author, license, headers) is never overwritten.docs/SPECIFICATIONS.md — add DESIGN.md referenceIf the reference to docs/DESIGN.md is missing from section 4, one line is appended:
- **Design System:** If the project has a user interface, see `docs/DESIGN.md` for color tokens, typography and components.
docs/DESIGN.md — create only if absent and project has UIIf your project has a user interface and docs/DESIGN.md does not exist, the agent creates it from the framework template and informs you to fill it in with your actual design tokens.
5

Phase 5 — Close

Once all changes are applied:
  1. The Framework Version field in project.config.md is updated to 2.1.0.
  2. The agent prints a clear summary:
✅ Framework updated from vX.X.X → v2.1.0

Files updated:
  • [list of modified/added files]

Project files not modified (protected):
  • docs/SPECIFICATIONS.md ✓
  • docs/ARCHITECTURE.md ✓
  • task.md ✓
  • CHANGELOG.md ✓
  • README.md ✓

Next steps:
  [If DESIGN.md was created] → Fill in docs/DESIGN.md with your project's design tokens.
  [If AGENTIC_ENGINEERING.md was added] → Read docs/AGENTIC_ENGINEERING.md to understand the v2.0.0 methodology.
  → Continue with your project normally. The framework is now up to date.

​
Version history at a glance

VersionDateHeadline change
v2.1.02026-06-17Agent Readiness integration across /spec, /build, /ship
v2.0.02026-06-15Agentic Engineering: Conductor/Orchestrator modes, Evals, Security Review, Agent Harness
v1.5.22026-05-12Trust boundary, granular Memory Triggers, anti-boilerplate Adversarial Review
v1.5.12026-05-12Fixed English documentation inconsistencies
v1.5.02026-05-12Enforcement Layer: Phase Gates, Memory Gate, Adversarial Review
v1.4.02026-05-12memory.md, Architect Review, XML-structured prompts
v1.3.02026-05-05docs/DESIGN.md, UPGRADE_PROMPT.md, framework_version field
v1.2.12026-04-30README.template.md, bootstrap language question
v1.2.02026-04-30project.config.md, file headers, Git integration, CHANGELOG auto-management
v1.1.02026-04-26Bilingual README, ANTIGRAVITY.md, Windsurf support, ADOPTION_PROMPT.md
v1.0.02026-04-15Initial public release

Build docs developers (and LLMs) love

Get started for freeTalk to us