Docs human

Skill dustinkeeton/wafflestack/.claude/skills/docs-human

🧇 One batter, every repo — reusable AI agent & skill definitions rendered into harness-native files (.claude/, .codex/, .agents/)

Install

npx -y skills add dustinkeeton/wafflestack --skill docs-human

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Human-readable documentation standard — scannable, plain-language docs derived from the agent docs but formatted for human consumption. Defines the project's human-doc file set and format rules. Use when creating or updating documentation intended for human stakeholders.

SKILL.md

2.3 KB, as published. Nobody here has run it

Human Documentation

Purpose

Produce documentation that humans can quickly scan to understand the project. The human docs for this project are DECISIONS.md, STATUS.md, and ARCHITECTURE.md at the repo root. Derive from the machine docs and the codebase, but reformat for human readers — plain language, headings, and bullets over walls of prose.

Prioritize:

Decision log — what was decided, why, and what alternatives were considered
Status visibility — what's done, what's in progress, what's blocked
Change history — what changed and why, in reverse chronological order (newest on top)
Plain language — avoid jargon where possible, explain technical terms

Documentation Files

`DECISIONS.md` (root)

Decision log in reverse chronological order:

## YYYY-MM-DD: Decision Title

**Context**: What situation prompted this decision
**Decision**: What was decided
**Alternatives considered**: What else was evaluated
**Rationale**: Why this option was chosen
**Impact**: What this affects

`STATUS.md` (root)

Current project status:

Feature completion matrix (feature × status)
Current sprint/focus area
Known issues and blockers
Dependency status (external tools, APIs)

`ARCHITECTURE.md` (root)

High-level architecture overview for humans:

System diagram (ASCII or Mermaid)
Feature descriptions in plain language
How features interact
Configuration overview
Getting started for new contributors

Format Rules

Use headings liberally for scannability
Lead with the most important information
Use bullet points over paragraphs
Include dates on all log entries
Keep STATUS.md under 100 lines — it's a snapshot, not a history

Owner-voiced docs — do not rewrite

README.md, schema/FORMAT.md, and schema/SETUP.md are owner-voiced canonical documents (the schema files ship to consumers via npx). Never rewrite them in a docs pass — if they have drifted from reality, flag the drift in your report instead.