Stack Detection

Quick Guide: Traverse what is in front of you — manifests, lockfiles, framework configs, one pass per workspace — or, where the user names nothing but the thing they want to build, offer candidate built-in stacks and wait for them to pick. Acquire the catalog and the stacks at run time, map signals to catalog skill ids, mark how each assignment loads per the product's preload mapping, surface exclusive-category conflicts instead of resolving them, and emit a SeedPayload plus a proposal report. The skill proposes. The machinery downstream validates. Nothing is written unattended.

Detailed Resources:

• examples/core.md - A three-workspace monorepo walked end to end: traversal, mapping, an exclusive-category near-miss, the complete SeedPayload, and the proposal report — then the same output reached the other way, from intent alone: candidates, the user's pick, and the gap the pick leaves

<critical_requirements>

CRITICAL: Before Proposing Anything

All output must follow project conventions in CLAUDE.md

(You MUST acquire the catalog at run time and map only to ids it contains — never propose a skill id from memory, and never inline a copy of the catalog into your reasoning as if it were current)