skills.rest
marktoda
marktodaCOMMUNITY
Explore all skills by this author →
𝕏@MarkTodaGitHub

validate-rewrite

Validate rewritten codebase specs and design documents for coherence and completeness.

Updated May 7, 2026
Search Tags:#design review#spec validation#implementation gate#fresh-eyes review#cohesion check#rewrite validation
One-click install
npx skills add https://github.com/marktoda/cohesive --skill validate-rewrite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-rewrite
Source: https://github.com/marktoda/cohesive/tree/main/skills/validate-rewrite
Command: npx skills add https://github.com/marktoda/cohesive --skill validate-rewrite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of implementing flawed rewritten specs by running an independent, context-free review of design changes before development starts, catching coherence gaps, missing invariants, and misalignment with system direction that the original design team overlooked.

Core Features & Use Cases

  • Independent Fresh-Eyes Review: Dispatches an isolated spec-cohesion-reviewer agent with no inherited design context to catch blind spots the original team missed.
  • Automated Repair Loop: Automatically drives the rewrite-specs skill to fix Issues Found findings, re-reviewing each pass until the design is approved, incoherent, or hits the max pass limit.
  • Use Case: After rewriting specs for a new authentication flow on a design/auth-v2 branch, run this skill to confirm the rewrite is coherent and aligned with system invariants before starting implementation.

Quick Start

Use the validate-rewrite skill to review the rewritten specs on your active design branch to confirm they are ready for implementation.

Frequently Asked Questions about validate-rewrite

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

FAQPage Schema
How do I validate rewritten specs before implementation to catch design blind spots?▼

Validating rewritten specs requires an independent, context-free review gate that checks design documents for coherence, completeness, and alignment with system direction to catch blind spots the original design team overlooked.

What is a fresh-eyes review for spec rewrites and how does it prevent rework?▼

A fresh-eyes review dispatches an isolated reviewer with no inherited design context to evaluate rewritten specs, identifying coherence gaps and missing invariants that prevent costly rework from flawed implementations.

How do I check if my rewritten design docs align with system invariants before coding?▼

Checking design doc alignment involves validating that rewritten specs maintain system invariants, behavior matrix adjustments, and coherence with the overall system direction before development begins on your design branch.

Can I automatically fix spec cohesion issues found during a design review?▼

Automated repair loops can drive spec rewrites to fix issues found during validation, re-reviewing each pass automatically until the design is approved, deemed incoherent, or hits the maximum pass limit.

When do I need to run a spec validation gate on my design branch?▼

You need a spec validation gate after rewriting specs on a design branch but before implementation begins, ensuring post-rewrite changes like design doc revisions and invariant updates are coherent and ready for development.

Related Skills

Explore More Software Engineering Skills→
marktodamarktoda

brainstorm-design

Generate codebase-grounded design options and pressure-test them with 25 questions.

Community
Advanced
s0613s0613
1

sj-spec

Generate structured specification documents from vague product requirements.

Community
Advanced
rafifosrafifos
6

subagent-driven-development

Dispatch fresh subagents for isolated tasks with two-stage reviews.

Community
Intermediate
kk20300113-pngkk20300113-png

autoplan

Automates sequential CEO, design, engineering, and developer experience plan reviews.

Community
Advanced