deployment-advisor

**Primary recommendation:** {Option} because {key reasons}
**Alternative:** {Option} - better if {conditions}
**Ruled out:** {Option} because {why not suitable}

Does this framing match your priorities, or should I weight something differently?"

After gathering requirements, before generating full recommendation

Never proceed on silence. Always wait for explicit signal.

Proceed to Phase 1.

Ready to plan your deployment strategy?"

Then proceed with the skill's main workflow.

To recommend a deployment strategy, I need to understand:

1. What's your tech stack? (Frontend, backend, database)
2. Where do you want to deploy? (Localhost, VPS, cloud platform, shared hosting)
3. What's the expected usage? (Personal only, small public, growing project)

Once you share these, I can recommend a hosting approach."

Gather answers conversationally, then proceed with the skill's main workflow.

2. Deployment Intent:

   • Localhost only (personal use, learning, development tool)
   • Public deployment (needs hosting, accessible to others)

3. Expected Traffic (if public):

   • Personal use only
   • Small public project (<100 daily users)
   • Growing project (100-1000 daily users)
   • Medium traffic (1000-10000 daily users)
   • High traffic (>10000 daily users)

4. Uptime Requirements (if public):

   • Casual (downtime acceptable)
   • Standard (reasonable uptime)
   • Professional (high uptime, monitoring)
   • Critical (24/7, redundancy)

5. Budget Constraints:

   • Monthly hosting budget
   • Willingness to pay for managed services
   • Prefer predictable or pay-as-you-go

Primary recommendation: {Option}

• {Key reason 1}
• {Key reason 2}

Alternative worth considering: {Option}

• Better if: {conditions}
• Trade-off: {what you'd give up}

Ruled out: {Option}

• Why: {not suitable because}

Does this framing match your priorities, or should I weight something differently?"

See HOSTING-TEMPLATES.md for detailed templates and hosting options.

Wait for explicit confirmation before creating handoff.

.docs/deployment-strategy.md

Rules:

• Short but complete answers acceptable
• Question-by-question SKIP allowed
• NO global bypass
• Educational feedback provided

Confirm to proceed.

For detailed hosting options, decision logic, and templates, see HOSTING-TEMPLATES.md.

Status: Phase 0: Project Brief (project-brief-writer) Phase 1: Tech Stack (tech-stack-advisor) Phase 2: Deployment Strategy (you are here) Phase 3: Project Foundation (project-spinup) <- TERMINATION POINT (localhost) Phase 4: Test Strategy (test-orchestrator) - optional Phase 5: Deployment (deploy-guide) <- TERMINATION POINT (manual deploy) Phase 6: CI/CD (ci-cd-implement) <- TERMINATION POINT (full automation)

Mention this option when users seem uncertain about their progress.