← ClaudeAtlas

intuitive-doclisted

Create and maintain an intuitive human documentation surface for AI-agent-developed repos. Use when humans should only need README.md, ARCHITECTURE.md, STATUS.md, and docs/human/** while planning logs, generated docs, retrospectives, ADR detail, and implementation evidence stay in AI-agent-only folders.
MiaoDX/intuitive-flow · ★ 41 · AI & Automation · score 84
Install: claude install-skill MiaoDX/intuitive-flow
# Intuitive Doc Maintain a small human-facing documentation surface and keep it aligned with code. ## Human/Agent Surface Rule The default human-facing source of truth is intentionally small: - `README.md` - `ARCHITECTURE.md` - `STATUS.md` - `docs/human/**` `AGENTS.md` and `CLAUDE.md` are agent-operational docs. Use them for startup rules, local hazards, command pointers, and skill routing, but do not treat them as human-authoritative project truth by default. Agent planning, generated evidence, history, and working notes belong in explicit agent/process surfaces such as `.planning/**`, `docs/plans/**`, `docs/retrospectives/**`, `docs/status/active/**`, and `output/**` unless a human doc intentionally promotes a specific artifact into current truth. AI coding docs are agent/process-facing docs that help future coding agents but do not need to be human project truth. Prefer `docs/agents/**` for durable agent runbooks, repo-specific coding procedures, tool quirks, and long harness notes. Prefer `.planning/**`, `docs/plans/**`, `docs/retrospectives/**`, `docs/status/active/**`, and `output/**` for execution state, plans, retrospectives, generated evidence, and proof artifacts. When any default human surface is missing, `$intuitive-doc` should make the next action obvious. In audit/guard output, report the missing file or folder and give the smallest generation hint that would restore the default surface. Do not silently create files in audit mode. Default generation hin