setup-stacklisted

Use this skill to run the entire stack-it pipeline end to end in one guided pass. It takes a project from nothing to a working, verified, documented tech stack by running each stage skill in order (identify-stack-slots, decide-stack, install-stack, scaffold-and-verify, document-stack), resumes from wherever the project already is, optionally sets up git and commits a checkpoint after each stage, and keeps a running task list so the user can see how much is left. Use it whenever someone wants their whole stack set up rather than just one step. Phrasings like "set up my stack", "set up my whole project stack", "help me start a new project from scratch", "pick, install, and verify my stack", "take me from zero to a working project", "bootstrap my project", or "run the whole stack-it pipeline" should trigger it. It pauses only where it genuinely needs the user (their tool picks in the decide stage, an install confirmation, a stack-fault re-pick, an OK before writing docs) and handles the loop where a broken tool
pricklywiggles/fractally-claude-marketplace · ★ 1 · Code & Development · score 62

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

# Set Up Stack The orchestrator for the stack-it pipeline. It takes a project from nothing to a working, verified, documented tech stack by running the five stage skills in order, resuming from wherever the project already is and pausing only where a human is genuinely needed. Each stage is a real skill with its own `SKILL.md`; this skill's job is to **sequence** them, carry the `.claude/stack-it/` artifacts between them, and handle the one loop where verification sends a bad choice back to be re-decided. Defer to each stage for *how* that stage works; don't reimplement it here. ## The pipeline | # | Stage skill | Produces / does | |---|---|---| | 1 | `identify-stack-slots` | `.claude/stack-it/slots.yaml`: the decision categories | | 2 | `decide-stack` | `.claude/stack-it/stack.yaml`: concrete, pinned, vetted choices | | 3 | `install-stack` | installs the locked stack; updates `stack.yaml` to match reality | | 4 | `scaffold-and-verify` | builds a minimal slice and runs it green; updates `stack.yaml` on pin drift; **escalates a stack fault back to stage 2** | | 5 | `document-stack` | `docs/stack.md` and `docs/stack-notes.md` + the one-line `AGENTS.md` pointer + the `README` block documenting the stack | Run each stage by following that stage's skill, not by re-deriving its behavior. ## Step 0: Set up the workspace Before the first stage, get two things in place that you maintain for the rest of the run. **Git.** Check whether the project is a git repository (`git rev-pa