Locate and read project specification files to extract invariants before structural changes.
npx skills add https://github.com/v0lka/skills --skill vibespec-consult
Please help me install this Agent Skill. Skill: vibespec-consult Source: https://github.com/v0lka/skills/tree/main/development/sdd/vibespec-consult Command: npx skills add https://github.com/v0lka/skills --skill vibespec-consult
Proactively consult project specifications before making any structural changes to ensure invariants are preserved and architectural integrity is maintained.
Follow the SPEC CONSULT procedure to locate the spec system, identify relevant specs, read in order, and extract constraints before implementing changes.
High-intent search queries and answers about installing and using this skill.
To check project specs before making structural changes, locate the spec root and read specs/INDEX.md to surface relevant domain constraints. This ensures architectural invariants are preserved when modifying interfaces, adding components, or altering architectural boundaries.
The best way to identify invariants and extension points is to read domain READMEs and detail contract specs in order. This extracts anti-patterns and breaking-change checklists to inform interface modifications and maintain architectural integrity.
You need to consult a spec system for change management whenever modifying interfaces, adding components, altering architectural boundaries, or changing configuration schemas across domains. This prevents breaking invariants and maintains architectural integrity during structural modifications.
To extract breaking-change checklists from project specifications, locate specs/INDEX.md and read the relevant domain READMEs alongside detail contract specs. This surfaces explicit constraints, anti-patterns, and extension points required to evaluate the impact of structural changes.
Reading specs/INDEX.md and META.md helps preserve architectural invariants by surfacing relevant constraints before implementing changes. This disciplined workflow ensures you review domain boundaries and contract specifications prior to altering structural components or schemas.
Relying only on READMEs for change management may miss detailed contract specs and specific breaking-change checklists. A complete approach requires locating the spec root, reading META.md, and extracting invariants from detail contracts to ensure architectural integrity.
v0lkaAnalyze a codebase and generate an initial specification suite with domain docs and ADR templates.
azat-ioRestructure code in small steps while preserving external behavior with tests.
AnvinX1Run linting and static analysis on Python and Node.js projects.
garrardkitchenDocument architecture decisions in MADR format with risk analysis and diagrams.
