Create Cli

**Judgement:** High-quality, opinionated CLI design helper that aligns with modern best practices (clig.dev). Well-suited for creating or refactoring CLIs that must be both pleasant for humans and robust for automation. **Strengths & Risks** - **Strengths:** - Produces a compact yet comprehensive spec: command tree, usage, flags, output rules, exit codes, safety semantics. - Explicit focus on **safe** and **predictable** behavior: dry-run, confirmations, non-interactive flags, and secrets-handling. - Encourages clear I/O contracts (stdout vs stderr, TTY behavior, JSON/plain modes), which is crucial for scripting and CI. - Language- and platform-agnostic guidance, making it broadly applicable across tech stacks. - **Risks / Limitations:** - Focuses on **design**, not implementation; you still need to choose libraries and write code to realize the spec. - Assumes willingness to follow opinionated guidelines (cli-guidelines); teams with non-standard UX norms may need to adapt output. - Quality of the result can depend on how clearly you describe your problem space and constraints. **Recommended Scenarios** - Planning a new CLI tool (internal or public) and wanting a solid, implementation-ready spec before coding. - Cleaning up a messy or organically grown CLI to standardize flags, subcommands, and help output. - Designing CLIs that must be **automation-friendly** (stable output, clear exit codes) without sacrificing human usability. - Establishing team-wide conventions for CLI behavior, safety, and configuration precedence that can be reused across projects.