Skip to content

CLI Capability Map

This page is the compact capability map for the ChatPPT CLI. Use it to review which commands are first-class entries and which are still boundary or planned slots.

Importable Python functions are mapped in Interface Tree. Current package boundaries are tracked in Capability Map.

Current Runtime Command Tree

The block below is rendered by chatppt --tree from the real Click registry. ChatPPT currently has no business subcommands, so only root pseudo-options are shown.

chatppt
├── --help  # Show this message and exit.
├── --version  # Show the version and exit.
├── --tree  # Print the registered CLI tree and exit.
└── --tree-brief  # Print the registered CLI tree without parameter signatures and exit.

chatppt --tree-brief keeps the same nodes and descriptions, but omits parameter signatures once business commands are added.

Base Entries

chatppt --help           # Verify the command is installed and inspect current help
chatppt --version        # Verify the installed version
chatppt --tree           # Print the current real CLI registry with signatures
chatppt --tree-brief     # Print the same CLI registry without signatures

Business Command Status

This package currently has no business subcommands. Do not document template placeholders or sample commands as available entries. Only document a command as implemented after the command, Python function, and tests exist.

Implementation Contract

  • Every implemented command must map back to a Python function, class, or service layer.
  • If a command writes remote state, document credentials, permissions, dry-run/checkpoint behavior, or confirmation boundaries.
  • When adding a command, update README, the interface tree, capability map, tests, and related flow pages together.