project-documentation

Project Context

• CLAUDE.md exists: !find . -maxdepth 1 -name "CLAUDE.md" -type f
• project-discovery.md: !find . -maxdepth 3 -name "project-discovery.md" -type f
• personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"
• project .han/config.md: !cat .han/config.md 2>/dev/null || echo ""

As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md probe supplies content, apply it per config-rule.md, which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

Project Documentation

Readability. As you write the documentation, source the standard by invoking han-communication:readability-guidance and apply it. The output is a committed file, so the standard applies at generation time. Hold a named audience above the default: a technically-literate reader who needs to understand the feature's behavior before reading or modifying its code. Scope that frame per section so the technical specifics the reader needs are not simplified away.

Step 1: Evaluate and Gather Context

Guard check: If the request is about an architectural decision, suggest architectural-decision-record instead. If it's about a coding convention, suggest coding-standard instead. Proceed only after confirming this is project documentation.

Docs directory: Resolve project config: read CLAUDE.md's ## Project Discovery section for docs directory and language; fall back to project-discovery.md; fall back to Glob default (docs/). Use the found docs directory with Glob to enumerate existing .md files. If no docs directory was found, create docs/. The found language informs code fence language identifiers in Step 3.