cf-adviselisted

Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike $cf-plan (builds) or $cf-ask (looks up code), this only advises.
dinhanhthi/coding-friend · ★ 3 · AI & Automation · score 79

Install: claude install-skill dinhanhthi/coding-friend

# $cf-advise Advise on: **$ARGUMENTS** ## Purpose Turn a raw idea, question, prompt, or URL into an actionable **decision** through a structured interview. Vague questions yield vague answers — so this skill interviews before it advises, uncovering the hidden requirements behind the surface question, then delivers a verdict-first recommendation. - **Advisory-only** — NEVER writes, edits, or refactors code. NEVER writes a plan file. Produces a recommendation, nothing else. If the user decides to act on it, hand off to `$cf-plan`. - Unlike `$cf-plan`: decides _whether / which_, not _how to build_. No plan doc, no execution. - Unlike `$cf-ask`: reasons about a decision or trade-off, not a lookup of how existing code works. - Unlike `$cf-research`: a focused verdict for one decision, not a multi-doc research dump. ## Flags Parsed from `$ARGUMENTS`; strip before using the rest as the topic. | Flag | Effect | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | `--quick` (alias `--fast`) | Fewer interview questions (aim for 2–3, the highest-signal ones). Use when the decision is narrow. | | `--save` | After delivering the verdict, persist it