shared-docs-paths

Project documentation structure maps hierarchical paths and purposes for files like changelogs, dev plans, guides, architecture, briefs, and reports. This ensures documents are referenced and maintained in correct locations, streamlining project understanding and collaboration.

Mapping a knowledge base hierarchy involves defining clear hierarchical paths for development plans, bug reports, briefs, and PRDs. This structure ensures contextual relevance so documents are loaded and referenced at appropriate stages of the project lifecycle.

Load architecture and dev-plan documents before implementation to ensure development aligns with project goals. Enforcing critical rules for document loading before access guarantees the AI agent locates and understands relevant briefs and plans at the correct project stage.

This approach manages project documentation paths by defining specific hierarchical locations for changelogs and test reports. It enforces critical rules for document loading before access, ensuring files are referenced at appropriate stages like after testing or during status updates.

Yes, you can use this documentation structure for PRDs, personas, and use cases across project stages. It defines hierarchical paths and purposes for these documents, ensuring they are loaded and referenced at appropriate lifecycle stages for contextual relevance.