hai-rewrite-doc

Verify document claims against evidence and rewrite unsupported content.

278|15|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/hylarucoder/hai-stack --skill hai-rewrite-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hai-rewrite-doc
Source: https://github.com/hylarucoder/hai-stack/tree/main/skills/hai-rewrite-doc
Command: npx skills add https://github.com/hylarucoder/hai-stack --skill hai-rewrite-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of unreliable documents that have drifted through repeated edits by verifying claims against current conclusions and removing unsupported content instead of patching it.

Core Features & Use Cases

  • Block-by-block verification: Checks document sections, claims, metadata, and lists against available evidence before deciding what survives.
  • Evidence-based rewriting: Preserves verified wording, removes failed claims, and produces a clean rewritten document with traceable decisions.
  • Use Case: When a technical design document no longer matches the latest discussions and code reality, use this Skill to verify each section, remove stale assumptions, and rebuild the document around confirmed facts.

Quick Start

Ask the AI to verify this document against the latest conclusions, remove incorrect sections, and rewrite it based on the evidence.

Frequently Asked Questions about hai-rewrite-doc

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

FAQPage Schema
How do I rewrite technical documents to remove outdated decisions and unsupported claims?

Block-level verification checks document sections, claims, and metadata against available evidence before deciding what survives. It removes unsupported content and preserves verified wording, ensuring specifications match confirmed facts.

How do I fix a drifted technical design document that no longer matches code reality?

Fix drifted documents by verifying each section against current conclusions. The process removes stale assumptions, preserves verified wording, and rebuilds the artifact around confirmed facts with traceable disposition tracking.

Can I verify collaborative writing artifacts that have accumulated inconsistent edits?

Yes, collaborative writing artifacts with inconsistent edits are supported. The process applies block-level verification and anchor-based rewriting to remove unsupported content while producing traceable decisions for every changed block.

What happens to unresolved questions during evidence-based document rewriting?

Unresolved questions receive explicit handling during evidence-based rewriting. Block-level disposition tracking ensures unverified claims are removed while open questions are explicitly documented rather than silently discarded in the rewritten output.

Does document rewrite verification require manual review of every removed claim?

Document rewrite verification automates checking claims against available evidence, but disposition tracking provides traceable decisions for every removed block. You can review the traceable dispositions to understand why specific content failed verification.