What Is the "Draft the Rewrite" Step in Humanizer? A Technical Guide

The "draft the rewrite" step is the second phase of Humanizer's workflow where the tool generates an intermediate revision that preserves every factual claim from the source text while eliminating AI-style artifacts, without introducing new information.

The blader/humanizer repository implements a structured four-step workflow for converting AI-generated content into human-sounding prose. According to the project's SKILL.md, the draft phase serves as a critical bridge between identifying AI tells and producing the final polished output.

Where "Draft the Rewrite" Fits in the Humanizer Workflow

Humanizer processes text through a strict sequential pipeline defined in the repository's documentation. Understanding the draft step requires context about what precedes and follows it.

Step 1: Mark the Tells

Before drafting begins, Humanizer performs an initial pass to identify "tells"—linguistic patterns typical of AI-generated text. These include not-X-but-Y contrasts, one-line closers, and other stylistic markers that signal synthetic writing.

Step 2: Draft the Rewrite

This is the core transformation phase. As specified in SKILL.md (lines 35-37), the system creates an intermediate version that:

• Preserves every supported factual claim—no new names, dates, numbers, quotes, or citations are introduced unless they exist in the source or are supplied by the user
• Restructures for readability—paragraphs may be shortened, merged, split, or rearranged to improve flow
• Eliminates fabrication—sentences lacking required facts are either simplified or flagged for user input rather than inventing details
• Permits limited voice adaptation—opinion or reaction is allowed when the original text's voice calls for it, provided no factual claims are fabricated

Step 3: Check the Draft

Following the draft, Humanizer reviews the intermediate text to ensure no AI-style artifacts remain and that no facts were added or dropped during restructuring.

Core Constraints of the Draft Phase

The draft step operates under strict fact-preservation rules that distinguish it from standard paraphrasing tools. According to the Humanizer source code, the implementation enforces these constraints:

No Fact Addition Rule
The system must never add a fact, name, number, date, quote, or citation unless it originates from the source material or explicit user input. This prevents hallucination during the humanization process.

Information Integrity
While the draft may "shorten dull parts" and change structural organization, the underlying information content must remain identical to the source.

Missing Data Handling
When encountering sentences requiring unavailable factual support, Humanizer either queries the user for the missing information or rewrites the sentence in a simpler form that removes the unsupported claim.

Example: From AI Text to Draft Rewrite

Below is a practical demonstration showing how the draft step transforms AI-generated content while preserving factual accuracy:

**Original AI-Generated Text**  
"The new feature was released in March 2024. It dramatically improves performance, 
and it eliminates the need for manual configuration. In fact, the update is a 
game-changer for developers."

**Step 1: Mark the Tells**  
- Not-X-but-Y contrast  
- One-line closer ("In fact...")

**Step 2: Draft the Rewrite**  
"The feature released in March 2024 improves performance and removes the need 
for manual configuration."

**Step 3: Check the Draft**  
Verification: No AI-style artifacts remain; all factual claims preserved.

**Step 4: Final Rewrite**  
"The March 2024 release boosts performance and eliminates manual configuration."

In this example, the draft (step 2) demonstrates the key principle: the March 2024 date and performance claims are preserved, while the subjective "game-changer" language and AI-tell patterns are removed. No new facts enter the text during drafting.

Integration with README.md

The README.md in blader/humanizer references this workflow as part of the overall Humanizer skill definition. While SKILL.md contains the granular specification of the draft step's constraints, the README provides high-level context about how this intermediate phase enables safe editing before final output generation.

Summary

• The "draft the rewrite" step is step 2 of Humanizer's four-step workflow, positioned between identifying AI tells and final verification.
• The draft serves as an intermediate, fact-preserving version that can be freely edited without risking information loss.
• Strict constraints prohibit adding new facts, names, dates, quotes, or citations not present in the source or provided by the user.
• The implementation allows structural reorganization—merging, splitting, or reordering paragraphs—to improve readability while maintaining information integrity.
• Source documentation in SKILL.md (lines 35-37) explicitly defines these boundaries to prevent hallucination during the humanization process.

Frequently Asked Questions

What happens if the source text contains factual errors during the draft step?

Humanizer preserves the factual claims as presented in the source material. The draft step does not fact-check or correct information; it only restructures and removes AI stylistic patterns. If the source contains errors, those errors remain in the draft unless the user explicitly provides corrections as additional input.

Can the draft step add examples or citations to support weak claims?

No. According to the SKILL.md specification, the draft cannot add citations, quotes, dates, numbers, or names unless they already exist in the source text or are explicitly supplied by the user. If a claim lacks support, Humanizer either asks the user for the missing information or simplifies the sentence to remove the unsupported assertion.

How does "draft the rewrite" differ from the final rewrite step?

The draft produces a working intermediate version focused on fact preservation and AI-tell removal, while the final rewrite (step 4) applies additional stylistic polishing and voice adaptation. The draft must maintain strict information fidelity, whereas the final version may incorporate more significant stylistic changes once facts are verified as preserved.

Is user input required during the draft phase?

User input is optional but supported. If the system encounters sentences requiring factual support that doesn't exist in the source, it can either query the user for the missing information or automatically rewrite the sentence in a simpler form. This design prevents the AI from hallucinating details while allowing the workflow to continue uninterrupted if the user isn't available.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}