Internal Developer CLI Consolidation Brief

Role: Staff Developer Productivity Engineer specializing in internal developer platform interfaces.

Context

• Engineering organization scale: {{engineering_org_size}}
• Legacy utilities to consolidate: {{disparate_toolchain_list}}
• Target deployment environments: {{primary_runtime_environments}}
• Security and authentication provider: {{security_auth_standard}}
• Priority developer bottlenecks: {{productivity_friction_points}}
• Phased rollout timeline: {{rollout_phases}}

Task

Author a high-impact developer tooling brief detailing the design, command hierarchy, authentication model, and rollout strategy for a single-binary CLI consolidating {{disparate_toolchain_list}}.

Method

1. Audit {{disparate_toolchain_list}} to extract core command flags, outputs, and overlapping logic.
2. Group utilities into a clean, contextual command taxonomy addressing {{productivity_friction_points}}.
3. Specify an authentication middleware integrating {{security_auth_standard}} with token caching.
4. Design cross-platform binary compilation and automated self-update routines for {{primary_runtime_environments}}.
5. Standardize structured output formats (JSON/table) to facilitate local scripting and CI/CD interoperability.
6. Establish telemetry hooks to measure command latency and adoption across {{engineering_org_size}} engineers.
7. Structure a non-disruptive migration plan across {{rollout_phases}}.

Constraints

• MUST distribute as a zero-external-dependency static binary.
• MUST NOT break backward compatibility for mission-critical CI pipelines without a deprecation shim.
• Command startup latency must remain under 50 milliseconds.
• Shell completion scripts must be generated dynamically for Bash, Zsh, and Fish.
• Brief length must stay under 550 words.

Output format

1. Command Tree Taxonomy

• Hierarchical list: tool [domain] [resource] [verb] --flags

2. Runtime & Security Architecture

• Binary distribution, execution lifecycle, and {{security_auth_standard}} integration (max 120 words)

3. Developer Experience & Output Standards

• Terminal styling, error rendering, and telemetry standards (max 100 words)

4. Deprecation & Rollout Schedule

• Phase-by-phase execution plan mapped to {{rollout_phases}}

Self-review

• Verify every script in {{disparate_toolchain_list}} maps cleanly to the new command tree.
• Check that authentication lifecycle handles token expiration gracefully without terminal lockup.
• Confirm adoption metrics directly address {{productivity_friction_points}}.