audit-stack

To audit tech stack choices, compare your preferences.md file against problem domain documents in docs/input/ to verify orthodoxy, idiomaticity, right-sizing, and compatibility. This generates a structured audit report highlighting mismatches early without automatically altering your preferences.

Tech stack right-sizing evaluates whether your selected stack's complexity matches the inferred project quality tier, categorized as shed, house, or skyscraper. It ensures your architecture fit and component interoperability align with the actual scale described in your input documents.

Checking technology selection idiomaticity involves reviewing your language, frameworks, and conventions to flag deviations from standard boring choices. It verifies that tooling, testing, and deployment conventions align with established community norms for the selected stack.

Yes, a stack audit validates client-mandated technology constraints by reviewing deploy target compatibility and architecture fit. It assesses whether the required components have integration library support and verifies interoperability against the problem domain.

No, auditing preferences.md does not automatically change your configuration files. It performs a read-only review of your stack choices and returns a structured audit report flagging mismatches, ensuring you retain full control over any subsequent updates.

You should run a stack audit during new project bootstrap or post-distillation alignment review before expanding your architecture. It catches early mismatches between your preferences and problem domain inputs, preventing wasted effort on incompatible or overly complex technology selections.