enterprise-stack-review

Automating enterprise tech stack decisions involves analyzing your TDD and current stack profile to identify required domains. The skill evaluates runtime, database, and framework options, then locks final selections into a machine-readable JSON file for governance and downstream planning.

Documenting an architecture audit trail is best handled by generating a human-readable markdown file alongside a locked JSON decisions file. This records evaluated options and incumbent pre-selections, ensuring planned technology choices remain traceable for enterprise governance and review.

Generating a stack profile from a TDD involves scanning the document to auto-detect required technology domains like auth and deployment. The skill matches these against your existing profile, presenting structured evaluation matrices to finalize architecture choices for planning.

Yes, you can skip resolved technology domains using built-in auto-skip logic. When the skill detects existing decisions in your stack profile, it bypasses those domains while preserving the original audit trail, maintaining governance continuity without re-evaluating settled choices.

The stack review workflow expects an existing stack profile as input to compare against the TDD. Without a stack-profile.json file, the skill cannot detect incumbent technologies or evaluate new domain options against your current enterprise architecture baseline.