read-docs

Reading project documentation with access logging records each file you open alongside a helpfulness score, tracking usage transparency and surfacing valuable resources. This approach logs interactions via a helper script with UTC timestamps to guide documentation quality improvements.

Finding missing or outdated docs involves checking the ./docs folder and automatically appending documentation requests to a tracking file. When existing files are insufficient to answer questions, a request entry is created in ./docs/documentation-requests.md with a UTC timestamp to track coverage gaps.

Logging documentation access uses an atomic append workflow via a helper script, safely recording interactions without altering your original project files. This method adds entries to a dedicated log and appends new requests to ./docs/documentation-requests.md, keeping source documents untouched.

Requesting new documentation happens automatically when current files fail to answer architecture or component questions. The workflow appends a new entry to ./docs/documentation-requests.md with a UTC timestamp, creating a transparent record of needed updates for your team.

This documentation workflow requires no external dependencies to read files and log access. It operates entirely within your project environment using a helper script to manage the atomic append process and record helpfulness scores with UTC timestamps.