Menu
Use to design, implement, review, or test CLI tools, flags, config precedence, terminal UX, errors, and docs.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | dev-cli-tooling-workflow |
| description | Use to design, implement, review, or test CLI tools, flags, config precedence, terminal UX, errors, and docs. |
| metadata | {"version":"0.3","updated":"2026-06-12"} |
Use this workflow when a task changes or creates a command-line interface.
Map the existing command surface.
Define user flows.
Design compatibility.
Implement ergonomically.
Validate.
--help or equivalent.Return:
Use only when the user explicitly invokes this skill to map unresolved product, domain, repository, or delivery unknowns before choosing a path.
Use only when the user explicitly invokes this skill to create or resume a persistent file-based goal tracker across sessions.
Use only when the user explicitly invokes this skill to stress-test an existing plan or design through one load-bearing question at a time.
Use only when the user explicitly invokes this skill to evaluate a skill with representative cases, isolated runs, independent judging, and evidence-driven edits.
Use for a concrete defect or regression that needs reproduction, root-cause diagnosis, a fix, and regression validation. Do not trigger for routine localized edits or primarily performance-focused work.
Use when the requested feature genuinely spans at least two delivery layers such as frontend, backend, API, data, scripts, or tests. Do not expand a single-layer change into a full-stack workflow.