All skills
technology-stack-selection
FoundationJIT onlyUse when a framework, platform, infrastructure, or managed service creates a commitment; skip package, runtime, or fixed-stack work.
- Group
- Technology selection
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- technology stack selection framework platform datastore infrastructure component managed service commitment
- existing approved stack novel stack compatibility operational ownership lifecycle supply chain total-change cost
- migration coexistence old new consumers rollback exit reversibility representative workload
Do not use when
Anti-triggers — as binding as the triggers above
- the open decision is a programming language runtime individual package build tool or runtime configuration
- architecture or policy fixes the stack and no new technology commitment or migration is proposed
Required inputs
What must be supplied before this skill can decide anything
- hard product system data protocol deployment security and recovery constraints
- current approved stack and feasible new commitment candidates
- operational lifecycle supply-chain cost migration coexistence and exit evidence
Output contract
What this skill owes the next role
- technology-stack decision with hard-constraint fit existing-stack comparison ownership lifecycle supply chain total-change cost migration coexistence exit proof limits and residual risk
Escalation signals
When this skill must hand the decision back
- A stack commitment can create unsupported compatibility unowned operation supply-chain exposure irreversible data movement or hidden exit cost
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Competing technology-stack commitments require compatibility ownership supply-chain migration cost or exit comparison | Current architecture and policy fix the technology stack and no new commitment or migration is proposed | AnalysisTaskReview |