reassess-spec

Name: reassess-spec
Availability: InStock
Author: joeloverbeck

Reassess roadmap-gate specs against the codebase and FOUNDATIONS, then update them after approval.

Updated Jun 5, 2026

Search Tags:#documentation #codebase #audit #spec #gate #foundations #reassess

Ready to run

npx skills add https://github.com/joeloverbeck/rulepath --skill reassess-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reassess-spec
Source: https://github.com/joeloverbeck/rulepath/tree/main/.claude/skills/reassess-spec
Command: npx skills add https://github.com/joeloverbeck/rulepath --skill reassess-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reassesses a Rulepath roadmap-gate spec against the codebase (docs/, .claude/skills/, existing specs) and docs/FOUNDATIONS.md; identifies issues/improvements/additions, presents findings for approval, then writes the updated spec.

Core Features & Use Cases

Validate a gate spec against the current repository to surface compatibility gaps with the FOUNDATION rules.
Generate a findings report (issues, improvements, additions) and present it for user decision-making.
Apply approved changes by writing the updated spec back to the target file, ensuring traceability and FOUNDATIONS alignment.

Quick Start

Begin by specifying a target spec path, e.g., specs/gate-0-repository-skeleton.md, and run the reassess-spec workflow to generate findings and an updated spec after approval.

Frequently Asked Questions about reassess-spec

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

FAQPage Schema

How do I audit a spec file against my codebase and foundations document?▼

To audit a spec file, you can run a reassessment workflow that validates the spec against your codebase and FOUNDATIONS.md. This process identifies compatibility gaps, generates a findings report for approval, and writes the updated spec back to the target file.

What is spec governance and when do I need to validate roadmap-gate specs?▼

Spec governance is the process of ensuring roadmap-gate specs align with repository rules and foundation documents. You need to validate specs when you want to surface compatibility gaps, enforce deterministic validation rules, and maintain traceability across your documentation.

Can I automatically update documentation specs under the docs/ and specs/ directories?▼

Yes, you can automatically update documentation specs located under specs/, docs/, and .claude/skills/. The workflow presents identified issues and improvements for your decision-making, then applies approved changes by writing the updated spec back to the target file.

How do I ensure codebase alignment before applying spec updates?▼

You ensure codebase alignment by running a pre-apply verification workflow that enforces deterministic validation rules and FOUNDATIONS conformance. This generates a findings report detailing issues, improvements, and additions before you approve any updates.

What is the best way to enforce deterministic validation rules on repository specs?▼

The best way to enforce deterministic validation rules is to reassess the specs against the current repository and docs/FOUNDATIONS.md. This identifies misalignments and produces an updated spec file only after user approval, ensuring strict conformance and traceability.

Do I need a FOUNDATIONS.md document to perform a spec audit?▼

Yes, a docs/FOUNDATIONS.md document is required to perform a spec audit. The reassessment process relies on checking specs against these foundation rules to identify compatibility gaps, enforce conformance, and generate accurate findings for user approval.