← ClaudeAtlas

speckit-brownfield-validatelisted

Verify bootstrap output matches actual project structure and conventions
mhabedank/lernkarten · ★ 1 · Testing & QA · score 70
Install: claude install-skill mhabedank/lernkarten
# Validate Bootstrap Verify that the spec-kit configuration generated by `/speckit.brownfield.bootstrap` accurately reflects the actual project structure, conventions, and architecture. Reports mismatches and suggests corrections. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). The user may specify a focus area (e.g., "only constitution", "only templates") or request verbose output. ## Prerequisites 1. Verify a spec-kit project exists by checking for `.specify/` directory 2. Verify git is available and the project is a git repository 3. Verify at least one bootstrap artifact exists (constitution, customized templates, or AGENTS.md) ## Outline 1. **Validate constitution**: Check `.specify/memory/constitution.md` against the actual codebase: | Check | How | |-------|-----| | **Language references** | Verify mentioned languages actually exist in the codebase | | **Directory references** | Verify all referenced paths (`client/`, `server/`, etc.) exist | | **Framework references** | Verify mentioned frameworks are in dependency files | | **Naming conventions** | Sample 20 files and check if naming rules match reality | | **Test location** | Verify test directories mentioned in constitution exist | | **Branch pattern** | Check if branch naming rules match actual branches in `git branch -a` | 2. **Validate templates**: Check customized spec/plan/tasks templates: | Check | How | |----