tech-stack-advisor

Never proceed on silence. Always wait for explicit signal.

Proceed to Phase 1.

Ready to explore technology stack options?"

Then proceed with the skill's main workflow.

To recommend a tech stack, I need to understand:

1. What are you building? (Brief description of the project)
2. Learning or Delivery? (Is learning a priority, or speed to ship?)
3. Key features? (What should the project do?)

Once you share these, I can provide tech stack recommendations."

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

"Before I recommend a stack, let me confirm I understand:

• You're building {project type} that {core purpose}
• Key features: {feature list}
• Learning goals: {what you want to learn}
• Constraints: {any non-negotiables}

Does this capture it?"

Options:

• A) Continue: Use brief as-is (I'll still recommend best approach)
• B) Revise: Refocus on problem/goals, let me recommend stack
• C) Restart: Create new brief from scratch
• D) Discuss: Talk through the trade-offs together

Your choice?

See DECISION-FRAMEWORKS.md for detailed frameworks and patterns.

Wait for explicit confirmation before creating handoff.

.docs/tech-stack-decision.md

Rules:

• Short but complete answers acceptable
• Question-by-question SKIP allowed with acknowledgment
• NO global bypass (can't skip all)
• Educational feedback provided on answers

Confirm to proceed.

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

Mention this option when users seem uncertain about their progress.