← ClaudeAtlas

intuitive-flowlisted

Orchestrate a staged idea-to-execution workflow across planning, review, GSD handoff, implementation, cleanup, and verification. Use when the user asks for fuzzy idea shaping, durable planning, implementation from a plan, Matt Pocock skills + gstack + GSD together, broad refactor routing, or one coherent source of truth from idea to verified work.
MiaoDX/intuitive-flow · ★ 41 · Code & Development · score 84
Install: claude install-skill MiaoDX/intuitive-flow
# Intuitive Flow Route work through the smallest staged workflow that preserves a clear source of truth. This skill is an orchestrator: use downstream skills for their own mechanics, and keep canonical route decisions in the main session. ## Latest User Intent Gate Before Hot Resume, Read First, route discovery, worker relaunch, or any edit, treat the latest user message as authoritative. If the latest message asks to stop, pause, avoid changes, discuss first, inspect status only, or challenges why implementation is happening, enter read-only control mode. Do not resume the previous goal, launch workers, run tests, edit files, or create commits. Allowed actions are limited to reporting current goal/worktree state, reading small status artifacts, and proposing the next decision. Resume execution only after a later user message explicitly asks to implement, run, continue, or resume. This gate overrides durable-run auto-continue, Hot Resume, GSD execution, worker babysitting, and inherited handoff instructions. ## Host Goal Gate When the host exposes persistent goal state, check it before treating an active run as resumable. A host-level goal that is `blocked` or `complete` is a stop gate, not a cue to continue. If the latest user message asks to stop or pause, close or block the goal when host policy allows, then treat the run as stopped. An active host goal is evidence of prior intent, not authorization to override the latest user message. Restart a stopped goal only a