openwhisper-headless-first

Enforce headless-first workflow with CLI placeholders and TASK review gates.

2|Updated Apr 22, 2026

Search Tags:#architecture #cli #task-management #library-api #headless-first #openwhisper

Ready to run

npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill openwhisper-headless-first

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openwhisper-headless-first
Source: https://github.com/jimmi-joensson/OpenWhisper/tree/main/.claude/skills/openwhisper-headless-first
Command: npx skills add https://github.com/jimmi-joensson/OpenWhisper --skill openwhisper-headless-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides and enforces architectural discipline so features consistently travel through the public library API and the headless CLI before the user-facing UI, ensuring shared behavior and easier maintenance.

Core Features & Use Cases

Enforces a two-gate workflow: Gate 1 ensures a CLI placeholder exists under cli/src/commands for the parent task before UI work; Gate 2 ensures no outstanding TASK references are present before code review.
Aligns library, CLI, and UI surfaces by pairing with openwhisper-orchestration-in-rust and TASK-81 doctrine, preventing divergence between layers.

Quick Start

Before implementing a UI feature, verify that a CLI placeholder exists in cli/src/commands and that there are no outstanding TASK references in core.

Frequently Asked Questions about openwhisper-headless-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce a headless-first architecture for library, CLI, and UI features?▼

Enforce headless-first architecture by gating features so they flow through the public library API and headless CLI before the UI. This ensures shared behavior and easier maintenance across all layers.

What is a headless-first workflow for CLI and UI development?▼

A headless-first workflow requires features to travel through the public library API and headless CLI before the user-facing UI, ensuring shared behavior and easier maintenance across layers.

How do I verify cross-layer parity between my library API, CLI, and UI?▼

Verify cross-layer parity by applying a two-gate workflow that checks for CLI placeholders under cli/src/commands and resolves outstanding TASK references before code review.

How do I prevent UI divergence from my library and CLI layers during development?▼

Prevent UI divergence by pairing with orchestration doctrine and applying review gates that align canonical surfaces for the library, CLI, and UI, stopping divergence before code review.

Can I use a two-gate review workflow to manage CLI and UI task coordination?▼

Yes, you can use a two-gate workflow where Gate 1 ensures a CLI placeholder exists for the parent task before UI work, and Gate 2 ensures no outstanding TASK references exist before code review.

When should I not use a headless-first discipline approach for feature development?▼

You should not use headless-first discipline when your development tasks lack coordination across library, CLI, and UI layers, or when explicit TASK placeholders and review gates are not applicable.