overseer-add-feature

Guide end-to-end Overseer.TUI feature implementation through hexagonal architecture workflows.

3|1|Updated May 18, 2026
One-click install
npx skills add https://github.com/dnlopes/overseer --skill overseer-add-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overseer-add-feature
Source: https://github.com/dnlopes/overseer/tree/main/.claude/skills/overseer-add-feature
Command: npx skills add https://github.com/dnlopes/overseer --skill overseer-add-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the confusion and churn that happen when adding new features to Overseer.TUI across its hexagonal domain, service, adapters, and Bubble Tea UI layers.

Core Features & Use Cases

  • Step-by-step hexagonal workflow: Guides you from domain shape through ports, services, adapters, dashboard composition, and tests.
  • Overseer-specific guardrails: Enforces Overseer’s conventions like async-only service calls from the TUI, typed messages, centralized keybindings, and correct error wrapping/sentinel handling.
  • TDD-first across layers: Promotes RED-first tests at domain, service, adapter, and TUI levels to keep changes safe and incremental.

Use it when you are extending an existing aggregate (for example, adding a new field to a Session) or creating a brand-new aggregate that needs persistence, service use cases, and a corresponding dashboard/TUI surface.

Quick Start

Tell the AI to use the overseer-add-feature skill to add a new field to the Session domain, then implement the service + ports + TUI form and finish by writing layer-by-layer RED-first tests.

Frequently Asked Questions about overseer-add-feature

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

FAQPage Schema
How do I add a new feature to a Bubble Tea TUI using hexagonal architecture in Go?

To add a Bubble Tea TUI feature in Go using hexagonal architecture, implement a step-by-step workflow from domain modeling through ports, service use cases, secondary adapters, and dashboard composition. This ensures proper UI integration with typed-message updates.

What is the best way to structure TDD across hexagonal architecture layers when extending a Go aggregate?

Structuring TDD across hexagonal architecture layers requires writing RED-first tests at the domain, service, adapter, and TUI levels. This incremental approach keeps changes safe when extending aggregates or creating new persistent aggregates.

Does Bubble Tea require async service calls from the TUI layer in a hexagonal Go application?

Yes, Bubble Tea requires async service calls from the TUI layer by wrapping them in tea.Cmd. This Overseer-specific convention prevents UI blocking and maintains responsive terminal interactions during service execution.

How do I handle errors and persistence when creating new aggregates in a Go TUI application?

Handle errors and persistence when creating new aggregates by using sentinel error handling and AtomicWrite persistence practices. Centralizing these practices ensures reliable state management and data integrity across your Go TUI application.

How do I integrate centralized styles and keybindings into a new Bubble Tea dashboard view?

Integrate centralized styles and keybindings into a new Bubble Tea dashboard by applying exhaustive typed-message TUI updates. This enforces Overseer-specific conventions, ensuring consistent UI composition and user interactions across new features.

When should I not use the hexagonal feature workflow for adding TUI functionality?

You should not use the hexagonal feature workflow for simple TUI tweaks that bypass domain modeling, ports, or service use cases. It is designed for comprehensive features requiring end-to-end implementation, persistence, and dashboard integration.