researching-tech-stack-best-practices

To generate best-practices documentation, provide a populated stack-definition.md file and run the skill to output deterministic Markdown files per technology under docs/stack-best-practices.

A stack-definition.md enumerates your declared technologies. You need it as the required input to normalize technology names and produce standardized best-practices documentation.

MCP research applies by connecting to official docs and production patterns across each technology, applying automated research to generate dedicated best-practices Markdown files.

Yes, you can generate a cross-stack overview for holistic governance. The skill automatically produces this overview document alongside dedicated per-technology best-practices files.

Yes, the documentation generation process removes duplicates. It normalizes technology names from the stack-definition.md before researching and outputting separate Markdown files.

Automated tech stack documentation requires a valid stack-definition.md and relies on MCP-based research, meaning outputs are deterministic and constrained by available official documentation patterns.