speckit-brownfield-validate

Validate spec-kit brownfield bootstrap artifacts against actual repository structure and conventions.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-validate-numu-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-brownfield-validate
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-brownfield-validate
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-validate-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks whether a spec-kit brownfield bootstrap accurately reflects the real repository, helping teams catch mismatched structure, conventions, and ownership rules before they cause confusion.

Core Features & Use Cases

  • Constitution Validation: Compares documented languages, directories, frameworks, naming rules, tests, and branch patterns against the actual codebase.
  • Template Review: Verifies custom spec, plan, and tasks templates still point to real modules, commands, and project-specific workflows.
  • AGENTS.md Audit: Confirms directory ownership is complete, non-overlapping, and aligned with the repository layout.
  • Drift Detection: Flags new modules, changed dependencies, or outdated bootstrap assumptions with actionable correction guidance.
  • Use Case: Use this Skill after a repository evolves to determine whether its bootstrap artifacts and agent instructions still match the current project reality.

Quick Start

Ask the skill to validate the repository’s spec-kit brownfield bootstrap against the current project structure and report any drift with fixes.

Frequently Asked Questions about speckit-brownfield-validate

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

FAQPage Schema
How do I detect bootstrap drift in a brownfield repository?▼

To detect bootstrap drift in a brownfield repository, validate spec-kit artifacts against the actual project structure by inspecting constitution rules, templates, and directory coverage to report actionable mismatches.

What does spec-kit constitution validation check for?▼

Constitution validation checks whether documented languages, directories, frameworks, naming rules, tests, and branch patterns accurately match the actual codebase and conventions within the repository.

How do I audit AGENTS.md ownership mappings for directory coverage?▼

Audit AGENTS.md ownership mappings by confirming directory ownership is complete, non-overlapping, and aligned with the repository layout to prevent agent instruction conflicts during drift audits.

Can I validate custom spec and task templates against current project modules?▼

Yes, you can validate custom spec, plan, and task templates by reviewing them to verify they still point to real modules, commands, and project-specific workflows within the current repository structure.

Does the bootstrap validation process respect .gitignore rules?▼

Yes, the bootstrap validation process respects .gitignore rules during evidence-based inspection of the constitution, templates, branch patterns, and directory coverage to ensure accurate drift reporting.