generic-artifact-paths

Standardizing artifact paths involves auditing references across docs/, specs/, and docs/plans/ directories to ensure consistency. This process validates path references to prevent broken links and enables portable, reusable path usage across multiple workflow contexts.

Documentation links break when artifact paths lack portability across different contexts. Applying a standardized path-resolution approach to docs, specs, and plans ensures references remain valid, reducing broken references and content duplication when artifacts are reused.

The best way to resolve artifact path references is to run a path-resolution audit across your repository directories. This audit standardizes access to generic artifact paths, verifying that references to docs and specs are unambiguous and correctly linked.

No external dependencies are required to manage artifact paths for documentation tasks. The path-resolution process requires no external runtime beyond the repository's own guidance, allowing you to validate references directly within your existing environment.

You should audit artifact path references when drafting specs, proposals, or plans to ensure locations are referenced unambiguously. Auditing prevents broken links and ensures path consistency before artifacts are reused across multiple workflows.