Feature Request: /custom-commands CLI Integration

Background

Many projects document common terminal workflows in Markdown, but users still have to copy and paste. This feature will allow contributors to define custom commands directly inside a .md file (e.g. COMMANDS.md) and invoke them from the terminal like this:

./my-cli /custom-hello

This would look up the hello command in the documentation and run the corresponding prompt or script automatically.

Proposed Solution

1. Markdown Parsing

   • Parse configured .md files (e.g. COMMANDS.md) for fenced code blocks or specially formatted comments labeled as /custom-<name>.

2. Command Registry

   • Map each /custom-<name> to its associated prompt or script snippet, stored in memory at runtime.

3. CLI Integration

   • Extend the CLI to recognize and route /custom-<name> arguments.
   • On invocation, retrieve and execute the matching command prompt from the Markdown source.

4. Help & Validation

   • ./my-cli /custom-commands --list should display all available custom commands.
   • Provide clear error messages for undefined or improperly formatted commands.
   • Fallback to --help when no valid /custom- argument is provided.

Acceptance Criteria

• Custom commands are defined in Markdown and are discoverable via --list.
• Running ./my-cli /custom-<name> executes the correct snippet.
• Error handling for undefined or malformed command blocks is in place.
• The feature is documented with examples in README.md.

Additional Context

This feature will:

• Make common workflows easier to discover and use
• Reduce copy-paste from documentation
• Keep project documentation executable and in sync with real behavior