doc-writing

Separate human-authored judgments from AI-generated content using HWPR and AWOR markers.

42|7|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/addxai/enterprise-harness-engineering --skill doc-writing-addxai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-writing
Source: https://github.com/addxai/enterprise-harness-engineering/tree/main/skills/doc-writing
Command: npx skills add https://github.com/addxai/enterprise-harness-engineering --skill doc-writing-addxai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When AI generates or expands business documents, critical human value judgments—such as key decisions, trade-offs, and unique context—often get buried in lengthy, generic content, making it hard for readers (both human and AI) to locate the most important human input.

Core Features & Use Cases

  • Structured Document Markers: Uses standardized [HWPR] (Human Wrote, Please Read) and [AWOR] (AI Wrote, Optional Read) markers to clearly separate short human-authored judgment content from freely modifiable AI-expanded details.
  • Multi-Mode Workflows: Supports writing new documents from scratch, restructuring existing documents to add the marker framework, and reviewing documents for correct formatting and compliance with established rules.
  • Use Case: Product teams drafting PRDs can use this skill to ensure core product decisions, trade-offs, and success criteria are prominently highlighted instead of being lost in AI-generated feature descriptions.

Quick Start

Use the doc-writing skill to draft a new project proposal with clear HWPR sections for your core judgments and AWOR sections for expanded supporting details.

Frequently Asked Questions about doc-writing

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

FAQPage Schema
How do I keep human value judgments visible in AI-generated business documents?

To keep human value judgments visible in AI-generated business documents, use a structured marker framework that separates short, immutable human-authored content from freely editable AI-expanded details using standardized formatting rules.

What is the best way to structure product requirements documents so key decisions are not buried?

The best way to structure product requirements documents is to apply standardized markers that strictly separate short human-authored judgment content, such as trade-offs and success criteria, from freely modifiable AI-generated feature descriptions.

How do I format AI-assisted documents to distinguish human input from AI expansions?

You format AI-assisted documents by enforcing strict separation using standardized markers, designating short human-authored judgment content as immutable and AI-expanded details as freely editable within the document structure.

Can I review existing documents to check if human context is properly highlighted?

Yes, you can review existing documents by using a multi-mode workflow that checks for correct formatting and compliance with established rules, ensuring human value judgments are prominently highlighted rather than lost in generic content.

Does this document structuring approach work for internal reports and proposals?

Yes, this document structuring approach works for internal reports and proposals, supporting drafting, restructuring, and review workflows across product requirements, proposals, and other enterprise documentation.

When should I not use AI to expand my enterprise documentation?

You should avoid using AI to expand enterprise documentation without a marker framework when critical human value judgments, such as key decisions and unique context, need to be quickly located by readers without being buried in lengthy content.