meta-dotclaude-copilot-start-here-for-any-tasklisted

The single skill to call for ANY task with this dotclaude config, so Simon never has to remember which skill fits. It finds or creates the session's one plan-backed dashboard, returns its link on request, routes the task to the right skills via references/skill-stack.md (verifying each is installed), presents the plan, and drives the whole job to a verified finish — keeping an always-visible progress bar (overall + nested sub-progress), applying each skill at its stage, and gracefully RESUMING the main thread after a tangent (a mid-task fix, a discovered todo). Callable at any stage; it re-reads the tracker and continues where the plan left off. Reuses references/skill-stack.md (the map), the task-intake gate, and rules/process.md (a tangent is a queued task; track every task to completion); it owns the single entry point, the progress bar, verifying skill names, and the resume. Use for "start here", "what should I use for this", "run this the right way", "just handle this", "which skills for this task", "cop
skowalskidev/dotclaude · ★ 2 · AI & Automation · score 78

Install: claude install-skill skowalskidev/dotclaude

# Start here — the one skill to route and run any task You do not want to remember which of 25+ skills fits a task, and you should not have to. Call this for anything. It routes the task to the right skills, shows a live progress bar, and keeps every skill applied through to a verified finish — resuming the main thread after any tangent. ## What it reuses, and what it owns - **The MAP is `references/skill-stack.md`** — task-shape → the right spine skill + what genuinely stacks on it. Read it; never guess a skill from its name, and never restate the map here. - **The intake survey already runs** (`hooks/task-intake.sh` fires on every task); this skill is the user-invocable FRONT DOOR that makes routing deliberate and drives it to the end. - **`rules/process.md` owns** run-to-completion, "a mid-run message is a QUEUED task not an interrupt," track-every-task-to-completion, and commit-when-done. Point to it; do not restate it. - **`rules/living-plan.md` owns** the living plan as the rail — read `.context/<slug>-plan.md` first, keep it current while working, reconcile against it at the end. Point to it; do not restate it. - **This skill OWNS**: the single entry point, the always-on progress bar, verifying each routed skill is installed, returning the current dashboard link, and resuming skills after a tangent. ## Step 0 — open the session record - Apply `rules/living-plan.md` before routing. Run `python3 "$HOME/.claude/bin/workflow-dashboard.py" init --root .`; i