advisor-triggerslisted

# Advisor Auto-Invoke Triggers ## Purpose Detect patterns in user requests that indicate a need for critical thinking analysis. Suggests running `/advise` when users propose significant changes without first considering trade-offs. ## Detection Patterns ### Pattern 1: New Dependencies **Triggers:** - "add [package/library/service]" - "use [technology]" - "integrate [external service]" - "switch to [different tool]" **Examples:** - "Let's add Redis for caching" - "Use TensorFlow for ML" - "Integrate Stripe for payments" - "Switch to PostgreSQL" **Why advise?** New dependencies increase complexity and maintenance burden. ### Pattern 2: Architecture Changes **Triggers:** - "refactor to [pattern]" - "restructure as [architecture]" - "migrate to [architecture]" - "convert to [pattern]" **Examples:** - "Refactor to microservices" - "Restructure as event-driven" - "Migrate to serverless" - "Convert to monorepo" **Why advise?** Architectural changes have far-reaching implications. ### Pattern 3: Scope Expansions **Triggers:** - "also add [feature]" - "extend to [capability]" - "support [new use case]" - "make it [do more]" **Examples:** - "Also add real-time collaboration" - "Extend to mobile platforms" - "Support multi-tenancy" - "Make it work offline" **Why advise?** Scope creep can derail projects. ### Pattern 4: Technology Replacements **Triggers:** - "[X] instead of [Y]" - "replace [X] with [Y]" - "swap [X] for [Y]" **Examples:** - "GraphQL instead of REST" -