python-cli-command-designlisted

# Outcome Produce a concrete, reviewable result for the workflow below without overstating what was observed, executed, or verified. ## Compatibility Portable across Claude Code, Codex, and OpenCode. The optional JSON-spec validator requires Python 3.11, reads one local file, and executes no commands. Map the resulting contract to the actual argparse, Click, Typer, or other framework version. ## Use this skill when - A new Python CLI needs a command and option model. - An existing interface has inconsistent names, deep nesting, ambiguous arguments, or automation-hostile prompts. - Configuration files, environment variables, stdin, output formats, color, or paging need a documented contract. - Destructive commands, help, entry points, or deprecation behavior need design review. ## Do not use this skill when - The command structure is fixed and only diagnostics, stderr, tracebacks, or exit statuses need design; use `python-cli-error-output`. - The interface is fixed and the outcome is a test suite; use `python-cli-testing`. - The task is a shell script or HTTP API rather than a Python command interface. ## Inputs Inspect or obtain: - Primary user tasks, objects, read/write effects, and automation use cases. - Existing parser code, help text, examples, command transcripts, and compatibility commitments. - Supported operating systems, shells, TTY/non-TTY environments, and stdin behavior. - Configuration sources, precedence, secret handling, and effective-config requirem