← ClaudeAtlas

which-skilllisted

Ask which of my skills fits the situation. A router over this repository, naming the flow to take and the order to take it in.
Udhay-Adithya/skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill Udhay-Adithya/skills
# Which skill Nobody remembers twenty skills, so ask. **Before claiming what a skill does, or recommending a step be skipped, read that skill's SKILL.md.** The summaries below are for orientation. They go stale; the skills do not. A **flow** is a path through several skills. Most work travels the main flow, and two on-ramps merge onto it. Everything else is standalone. ## The main flow: idea to merged 1. **Too big for one session, and foggy?** Start at **`atlas`**. It charts the effort as issues on the tracker and resolves them one at a time until there is nothing left to decide. It produces decisions, not code, and then hands off at step 2. Only reach for it when the way to the destination genuinely is not visible yet, never for a well-scoped feature. 2. **`spec-first`** turns the idea into a gated spec: assumptions surfaced, vague requirements reframed as testable criteria, then a hard stop for approval before anything is planned. Where `atlas` ran, this is where its linked decisions collapse into one buildable plan. Going from a map straight to code throws that collapse away. `spec-first` then breaks the plan into tasks. Keep steps 1 and 2 in **one window**: the charting, the spec and the task breakdown all build on the same thinking. 3. **Build each task in its own window.** Each task is self-contained, so the previous one's context is disposable. **`flutter-riverpod-mvvm`** fires by itself on anything in Dart. Anything with a