Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Build [command-line tool] for [task] using the project's established language and conventions.
Define required arguments, optional flags, defaults, and working-directory assumptions. Keep machine-readable results separate from diagnostics and document meaningful exit statuses. If the command changes files, provide a clear target boundary, collision handling, and a dry-run mode that reports intended effects.
Verify valid input, empty or malformed input, paths with spaces, an unwritable destination, and execution through a pipe where relevant. Check interruption and partial output for long operations. Report exact example invocations, observed outputs and exit statuses, and any setup required to reproduce the checks.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Node.js — Parsing command-line arguments with util.parseArgs
- Node.js — Process arguments, standard streams, and exit status
- Node.js — File system operations
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted CLI template. Separate result/diagnostic streams, explicit exit codes, and argument parsing are documented; proposed fixtures were not run.