product-context-aggregator

To consolidate external product docs, you provide absolute paths to existing directories containing specs, Swagger, diagrams, and wikis. The tool links these directories via symlinks, reads common file formats, and generates a unified contexto-consolidado.md file summarizing the verified product context.

When consolidating product documentation artifacts, the tool reads and classifies common file formats including markdown, JSON, YAML, Swagger, and protocol buffer files. It analyzes these formats to identify complements, confirmations, and inconsistencies relative to your initial product context.

Symlink creation works by validating the absolute paths you provide for external documentation directories, then safely creating symlinks under /documentacao/{titulo}/extra/. It uses the last path segment as the link name and automatically resolves any naming conflicts.

Yes, you can detect inconsistencies between API definitions and interview notes. After linking external directories, the artifact analysis phase reads files like Swagger and markdown, identifies complements and confirmations, and flags inconsistencies against the Phase 1 interview context for resolution.

You should use product context aggregation immediately after an initial product interview but before generating final documentation. It enriches product knowledge by verifying scattered reference artifacts, ensuring your documentation reflects verified sources rather than ad-hoc claims.

If a provided path for external documentation does not exist, the filesystem validation step will detect the missing directory. The tool prompts users for absolute paths to existing documentation directories and validates their existence before proceeding with artifact analysis and symlink creation.