devbooks-brownfield-bootstrap

Generate project profile, glossary, SSOT skeleton, and baseline specs for empty truth directories.

84|6|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-brownfield-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devbooks-brownfield-bootstrap
Source: https://github.com/Darkbluelr/dev-playbooks-cn/tree/main/skills/devbooks-brownfield-bootstrap
Command: npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-brownfield-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Brownfield projects often lack a stable, auditable starting point for governance. This Skill bootstraps a complete truth foundation by generating a project portrait, glossary, SSOT skeleton, baseline specs, and minimal verification anchors when the truth directory is empty.

Core Features & Use Cases

  • Auto-create project constitution, project context, truth assets, and initial SSOT when starting from an empty truth directory.
  • Produce a measurable baseline to prevent "changing specs while implementing" by establishing aded delta specs and verification anchors.
  • Enable a deterministic onboarding path for legacy projects and new teams to align on shared vocabulary and governance.

Quick Start

Initialize a brownfield bootstrap for the current repository to generate project profile, glossary, SSOT skeleton, and baseline specs.

Frequently Asked Questions about devbooks-brownfield-bootstrap

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

FAQPage Schema
How do I bootstrap a legacy brownfield codebase to create a baseline and SSOT?

To bootstrap legacy projects, this Skill generates a deterministic truth foundation comprising a project-profile, glossary, SSOT skeleton, and baseline specs when the truth directory is empty. It establishes a stable, auditable starting point for future changes and verification.

What is a project glossary and SSOT skeleton used for in legacy project governance?

A project glossary and SSOT skeleton provide a shared vocabulary and single source of truth for legacy project governance. They enable a deterministic onboarding path for new teams to align on context and establish a measurable baseline for future audits.

How do I prevent changing specs while implementing features in an existing codebase?

Preventing changing specs during implementation requires establishing a measurable baseline with dedicated delta specs and verification anchors. This creates a stable, auditable truth foundation that keeps future changes traceable and prevents mid-implementation spec drift.

Can I generate baseline specs and verification anchors for legacy projects with an empty truth directory?

Yes, you can generate baseline specs and minimal verification anchors for legacy projects starting from an empty truth directory. The generated artifacts are deterministic, traceable, and ready for insertion into the current truth source via the standard delta spec workflow.

When do I need to generate a project-profile and truth assets for a growing codebase?

You need to generate a project-profile and truth assets when a growing codebase lacks a stable, auditable starting point for governance. This auto-creates the project constitution, context, and initial SSOT to establish a measurable baseline for future verification.