stacklisted

# stack: choose deliberately, then be born current "Stack" here means whatever the product is built *on*: a language and framework on self-chosen infrastructure, or a hosted platform where the product is largely configured (Power Platform, ServiceNow, Salesforce, Google's builders, or any successor). This skill carries a method, not a platform table; every platform fact is looked up live from the vendor's current official documentation, so platforms and practices that appear after this skill was written are in scope automatically. ## 1. Decide the stack: options on merit Derive candidates from BRIEF.md (target, users, constraints, integrations, team). Hosted platforms are candidates on equal footing when the brief points there (existing tenant, licensing, citizen-developer handover). Present 2-3 genuinely different options with honest trade-offs (fit, ecosystem maturity, hiring/handover, cost, compliance implications, e.g. EU data residency of managed services). Recommend one; the owner confirms. Record as a decision record with the options and the reason. **Verify before recommending.** Versions, support status, pricing, EU-residency: check current authoritative sources (official docs, release pages). Model memory is a rumor with a cutoff. ## 2. Generate `docs/standards/<stack>.md` Start from `docs/standards/TEMPLATE-STACK.md`, which owns the shape. Its floor table is the part `checks/check.mjs` reads: six classes of risk, each answered with a command, a reasoned `not