decide-stacklisted

Use this skill to turn a list of project stack slots (decision categories like "web framework", "test framework", "database") into concrete, version-pinned, security-vetted tool choices. This is the decision stage that comes after identify-stack-slots and before install-stack. Trigger it whenever a user has a slots YAML and needs to pick the actual tools, or says "pick my stack", "choose tools for these slots", "research and recommend my dependencies", "what should I use for each part of my stack", or hands you a slots list to fill in. This skill collects hard preferences, settles the keystone language/framework decision first (presented as a coupled pair when the two are tightly linked, so a downstream pick never silently corners the language), researches each remaining open slot's options and versions in that constraint, gets the user's picks, then pulls the exact version-specific install steps from each chosen tool's official docs, checks known vulnerabilities and recent-release supply-chain threats, and o
pricklywiggles/fractally-claude-marketplace · ★ 1 · AI & Automation · score 62

Install: claude install-skill pricklywiggles/fractally-claude-marketplace

# Decide Stack Turn a list of stack **slots** (decision categories) into concrete, version-pinned, vetted tool choices, and emit an approved YAML that the `install-stack` skill consumes. This skill is read-only with respect to the user's system: it researches and converses, it does not install. ## Input Expect a slots YAML, normally from the `identify-stack-slots` skill: ```yaml project: description: ... type: ... platforms: [...] slots: - slot: <category> required: <true|false> rationale: ... preference: <tool the user already wants, or null> source: ... ``` Look for the slots YAML at **`.claude/stack-it/slots.yaml`** (where `identify-stack-slots` writes it), or use a path the user gives. If none is present, ask for it or point the user to `identify-stack-slots` first. This skill fills slots; it doesn't discover them. Validate the input with `${CLAUDE_PLUGIN_ROOT}/scripts/validate_yaml.py --stage slots .claude/stack-it/slots.yaml` before proceeding so a malformed input fails fast. ## Step 1: Collect hard preferences up front Before researching anything, ask the user whether they have hard preferences for any slots. People often arrive already set on a few tools and open on the rest, and asking first avoids researching slots that are already decided. Merge these answers with any `preference` values already in the input YAML. A preference from either source means that slot is decided unless the user later changes their mind. If a preference alre