tech-rewrite

Extract facts into a structured register and validate via quality gates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill tech-rewrite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-rewrite
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/skills/tech-rewrite
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill tech-rewrite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform existing technical material into high-quality technical documentation. This tool enforces an extraction-before-composition firewall to prevent contamination from source material, enabling clean, publish-ready results.

Core Features & Use Cases

  • Phase-based workflow: extraction, anchor-definition, drafting, and validation to ensure high quality.
  • Fact Register lifecycle: KEPT/DISCARDED/MISSING/AMBIGUOUS with contamination-risk assessment.
  • Anchor Sheet-driven drafting: central argument, reader, and document type defined before writing.
  • Quality gates: shared quality standards plus rewrite-specific gates to catch structural mirroring, hedges, and missing information.
  • Real-world use: convert rough notes, meeting minutes, or legacy docs into polished engineering documentation.

Quick Start

Provide your source notes and I will extract a Fact Register, then draft from the Phase 2 Anchor Sheet.

Frequently Asked Questions about tech-rewrite

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

FAQPage Schema
How do I turn rough meeting notes into publication-ready technical documentation?

To turn rough notes into publication-ready technical documentation, the tool extracts concrete facts into a Fact Register, defines the target document via an Anchor Sheet, and validates drafts through quality gates to prevent structural mirroring.

What is the extraction-before-writing firewall in technical rewriting?

The extraction-before-writing firewall is a process that isolates fact extraction from drafting. It prevents structural mirroring and contamination from source material by enforcing an evidence-based drafting workflow using a structured Fact Register.

How do I prevent structural mirroring when rewriting legacy engineering documents?

To prevent structural mirroring when rewriting legacy documents, the workflow uses an Anchor Sheet to define the central argument and reader before drafting, then applies rewrite-specific quality gates to catch mirrored structures and hedges.

Can I convert rough technical notes into polished docs without losing factual accuracy?

Yes, you can convert rough notes into polished docs by tracking every extracted fact through a lifecycle of KEPT, DISCARDED, MISSING, or AMBIGUOUS. This lifecycle includes contamination-risk assessment to maintain factual accuracy during drafting.

What are the limitations of using an Anchor Sheet for technical document drafting?

Using an Anchor Sheet requires you to define the document type, central argument, and target reader before drafting begins. This means you cannot start writing until Phase 2 definition and Phase 1 fact extraction are fully completed.

Does the tech-rewrite workflow support validating missing information in technical drafts?

Yes, the tech-rewrite workflow validates missing information by applying Phase 4 quality gates. These gates check against shared quality standards and the Fact Register to identify missing facts, structural mirroring, and unsupported hedges.