audit-stack

Audit preferences.md stack choices against problem domain documents in docs/input/.

Updated May 24, 2026

Search Tags:#requirements #compatibility #preferences #technology selection #stack audit #deploy target #architecture fit

Ready to run

npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill audit-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-stack
Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/audit-stack
Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill audit-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted effort by checking whether your choices in preferences.md are orthodox, idiomatic, compatible with your inputs, and right-sized for the project described in docs/input/.

Core Features & Use Cases

Stack Auditing: Reviews language, frameworks, deploy target, and conventions from preferences.md against the problem domain described in docs/input/.
Orthodoxy & Idiomaticity Checks: Flags when the selected stack is unlikely to be the “standard boring choice” or when tooling/testing/deployment conventions diverge from community norms.
Right-Sizing & Compatibility Evaluation: Infers a shed/house/skyscraper quality tier and checks whether complexity matches that tier, while verifying component interoperability and integration library support.

Quick Start

Use audit-stack to sanity-check your preferences.md against the files in docs/input/ before running /expand.

Frequently Asked Questions about audit-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit my tech stack choices against project requirements before building?▼

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.

What is tech stack right-sizing and how does it fit my project architecture?▼

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.

How do I check if my technology selection is idiomatic and follows community norms?▼

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.

Can I use a stack audit for client-mandated technology constraints and deploy targets?▼

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.

Does auditing preferences.md automatically change my configuration files?▼

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.

When should I run a stack audit during the project bootstrap process?▼

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.