PRD: Agent Builder — Create Your Own Sub-Agent banner
Gentleman-Programming Gentleman-Programming

PRD: Agent Builder — Create Your Own Sub-Agent

AI community intermediate

Description

> **Your ecosystem, your rules. Build custom AI sub-agents from the TUI — no code required.** **Version**: 0.1.0-draft **Author**: Gentleman Programming **Date**: 2026-04-03 **Status**: Draft **Parent

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for Gentleman-Programming/gentle-ai, shared by 4 entries in this directory. It describes the repository, not this entry specifically.

PRD: Agent Builder — Create Your Own Sub-Agent

**Your ecosystem, your rules. Build custom AI sub-agents from the TUI — no code required.**

**Version**: 0.1.0-draft **Author**: Gentleman Programming **Date**: 2026-04-03 **Status**: Draft **Parent PRD**: [PRD.md](PRD.md) (Gentleman AI Installer)


1. Problem Statement

The Gentleman AI ecosystem ships with a powerful set of pre-built skills and SDD phases. But every developer works differently. A frontend architect needs a design system reviewer. A security engineer needs a vulnerability scanner agent. A technical writer needs a documentation generator.

**Today, creating a custom sub-agent requires:**

  1. Understanding the skill file format (SKILL.md) for each AI agent
  2. Knowing where each agent stores its configuration (Claude Code: ~/.claude/skills/, OpenCode: ~/.config/opencode/skills/, etc.)
  3. Writing the system prompt, triggers, and patterns manually
  4. Duplicating the skill across every AI agent you use
  5. If it's SDD-related, understanding the orchestrator config and how to register a new phase

**This is a barrier that shouldn't exist.** If you can describe what you want your agent to do in natural language, the ecosystem should generate it, validate it, and install it across all your configured AI agents — from a single TUI flow.


2. Vision

**A guided TUI experience where you describe what you want, and the ecosystem uses one of your installed AI agents to generate a production-ready sub-agent skill — installed across all your tools instantly.**

Think of it as the "Create Agent" flow from Claude's `/agents` command, but:

  • Cross-agent: generates once, installs everywhere (Claude Code, OpenCode, Gemini CLI, Cursor, etc.)
  • SDD-aware: can optionally integrate as a new SDD phase or as support for an existing phase
  • Ecosystem-native: the generated agent has access to Engram (persistent memory), MCP servers, and follows the Gentleman skill format
  • Preview before install: you see exactly what will be generated before it touches your filesystem

**Before**: "I want an agent that reviews my CSS for accessibility... I guess I need to write a SKILL.md manually, figure out triggers, and copy it to 4 different directories."

**After**: Select "Create your own Agent" → pick your AI engine → describe what you want → preview the generated skill → it's installed everywhere. Done.


3. Target Users

Primary

  • Professional developers who want specialized AI assistance beyond the pre-built skills
  • Team leads who want to create standardized agents for their team's workflow (e.g., "our API review agent")
  • SDD users who need custom phases or phase augmentation for their specific domain

Secondary

  • Educators creating custom teaching agents
  • Open source maintainers who want project-specific review agents

4. User Experience

4.1 Entry Point — Welcome Screen

The Agent Builder is a **top-level menu option** on the