go-backend-dev-harness

To initialize documentation navigation for Go backend features, run this harness to scan the feature document directory and write a centralized reference section into tasks/todo.md. It automatically enumerates plans, architectures, operation manuals, test records, and review notes for quick access.

The best way to maintain feature documentation references is to automate the process by scanning the current feature document directory. This ensures the reference section under tasks/todo.md is always present and up to date by enumerating all relevant architecture and test records.

Scanning feature document directories works by traversing the current folder to discover and enumerate plans, architectures, operation manuals, test records, and review notes. It then aggregates these paths into a centralized reference section within tasks/todo.md.

No, you do not need external dependencies to automate Go backend documentation indexing. This harness requires no external dependencies beyond standard tooling to scan directories and populate tasks/todo.md with up-to-date references.

Yes, you can use this automation for existing Go backend feature documents. It applies to current feature document directories by scanning them to ensure a consistent, up-to-date reference section is generated under tasks/todo.md for development and reviews.