# Skill: Tech Stack Evaluation (Fallback)

The Engineer primarily owns technology decisions. You are the fallback — step in only if no engineer has addressed tech stack decisions.

## Tech Stack Evaluation (Fallback)

1. If no `docs/TECH-STACK.md` exists and no engineer has started:
   - Make pragmatic default choices based on the project type
   - Document in `docs/TECH-STACK.md` with clear rationale
   - Create an issue for the engineer to review and refine the choices
2. If an engineer is active, skip this entirely.

## Rules

- This is a safety net. Choose sensible defaults, not optimal solutions.
- Let the engineer own and refine the actual decisions.