skillit-cli-docs

Improve CLI help text by aligning Commander.js `.description()`, `.option()`, `.argument()`, and `.usage()` strings so each command entry point explains intent clearly. This ensures command-line documentation is consistent and discoverable for both users and generated skills.

Document routing tags by adding `@useWhen`, `@avoidWhen`, and `@never` JSDoc annotations directly onto `<PascalCommandName>Options` TypeScript interfaces. This correlates configuration surfaces with capability-driven execution hints for generated skills.

Document environment variables and positional arguments by refining `.argument()` inputs and `.usage()` strings alongside `.option()` flags. This provides complete guidance for every input value and environment-variable behavior within the command-line tool.

Yes, JSDoc annotations on `<PascalCommandName>Options` interfaces are required. They provide the structured metadata needed to correlate capability-driven routing tags and configuration surfaces with the generated skill's execution hints.

Yes, you can fix sparse help output by systematically improving `.description()` text and flag guidance across the entire Commander-based CLI tree. This transforms incomplete help into clear, discoverable documentation for every flag and positional value.

Generated skills lack routing hints when TypeScript option interfaces are missing `@useWhen`, `@avoidWhen`, and `@never` JSDoc annotations. Adding these tags correlates capabilities with the correct execution paths for the command-line tool.