stack-advisorlisted

# Stack Advisor ## Purpose Recommend the right technology stack for a project based on what the project actually needs, not based on trend or familiarity bias. This skill exists to prevent projects from defaulting to a stack before the trade-offs have been honestly examined. It should: - ask the right qualifying questions - consult available MCP tools for current ecosystem health and version recency - surface real trade-offs, not just a winner - keep the recommendation proportional to the declared project stage and scope - avoid recommending complexity the project does not yet need ## When to Use Use this skill when: - the project is in the blueprint stage - the architect agent needs a stack recommendation grounded in project reality - the orchestrator has identified stack selection as an open decision - no stack has been decided yet, or the current stack assumption needs validation ## When Not to Use Do not use this skill when: - the stack is already decided and validated - the request is only to resume or inspect context - the project has not yet completed research ## Required Context Minimum required inputs: - project type: what category of product this is (web app, API, mobile, CLI, AI-powered app, data pipeline, etc.) - platform target: where does this run? browser, iOS, Android, server, edge, embedded? Helpful optional inputs: - team size and experience profile - performance or scalability requirements - delivery timeline constraints - languages the team