What problem does it solve? Building CLI plugins with oclif often leads to bloated command classes, inconsistent contracts, missing hook semantics, and untested package releases. This Skill provides a structured set of standards for designing, implementing, testing, and releasing oclif-based plugins with clean architecture and verifiable quality evidence. ## Core Features & Use Cases - Command and Hook Standards: Enforces logicless command classes that delegate to domain services, with typed flags, stable stdout/stderr/exit codes, and JSON output contracts. - Plugin Capability Manifests: Defines contracts covering plugin id, commands, hooks, permissions, configuration schema, host compatibility, and deprecation policy. - Security and QA Evidence: Mandates safe shell execution with spawn/execFile, path and URL validation, least-privilege permissions, plus test evidence for CLI behavior, hooks, and React/Vite UI surfaces. - Use Case: When adding a new command to an Open Orchestra plugin, use this Skill to structure the command class, define its manifest entry, write contract tests, and produce release-ready QA evidence. ## Quick Start Ask the assistant to scaffold a new oclif command with typed flags, a manifest entry, and contract tests following the plugin development standards.
