devkit-create-agent

Included with Lifetime

$97 forever

Create a new agent with AI-guided expertise definition following the Agent Design Bible

Design

What this skill does


# Create AIWG Agent

Create a new agent with AI assistance to define expertise, workflow, and capabilities.

**Follows**: [Agent Design Bible](~/.local/share/ai-writing-guide/docs/AGENT-DESIGN.md) - 10 Golden Rules for production-grade agents.

**Research Foundation**: REF-001 (Bandara et al.), REF-002 (Roig 2025) failure archetype prevention.

## Usage

```
/devkit-create-agent <name> --to <target> [options]
```

## Arguments

| Argument | Required | Description |
|----------|----------|-------------|
| name | Yes | Agent name (kebab-case recommended) |

## Required Options

| Option | Description |
|--------|-------------|
| --to | Target addon or framework |

## Optional Options

| Option | Description |
|--------|-------------|
| --template | Agent template: simple (default), complex, orchestrator |
| --interactive | Enable interactive mode with guided questions |

## Templates

Templates are in `~/.local/share/ai-writing-guide/templates/agent-scaffolding/`.

### simple (default)
Single-purpose, focused agent with minimal structure (Rule 1: Single Responsibility).
- Best for: Utility agents, single-task specialists
- Model: haiku (efficiency tier)
- Tools: Read, Write (Rule 2: Minimal Tools)

### complex
Full reasoning agent with all safeguards including failure archetype prevention.
- Best for: Subject matter experts, reviewers, analysts
- Model: sonnet/opus (based on complexity)
- Tools: Read, Write, Grep (Rule 2: 0-3 tools)
- Includes: Grounding, uncertainty handling, recovery protocol

### orchestrator
Multi-agent coordination with workflow patterns and agent assignment tables.
- Best for: Workflow coordinators, phase managers
- Model: opus (Rule 8: reasoning tier for coordination)
- Tools: Task only (Rule 2: single tool for delegation)

### validator
Read-only validation agent that doesn't modify state.
- Best for: Quality gates, compliance checks, code review
- Model: haiku/sonnet
- Tools: Read, Grep (read-only)

## Interactive Mode

When `--interactive` is specified, I will ask:

1. **Role**: What is this agent's primary role?
2. **Expertise**: What domains does it specialize in?
3. **Responsibilities**: What are its key responsibilities?
4. **Tools**: What tools does it need access to?
5. **Workflow**: How should it approach tasks?
6. **Output**: What format should its output take?

## Examples

```bash
# Simple agent
/devkit-create-agent code-reviewer --to aiwg-utils

# Complex domain expert
/devkit-create-agent security-auditor --to sdlc-complete --template complex

# Orchestrator agent
/devkit-create-agent deployment-coordinator --to sdlc-complete --template orchestrator --interactive
```

## Execution

1. **Validate inputs**: Check name and target
2. **Verify target exists**: Ensure addon/framework is installed
3. **Select template**: Use specified or default to simple
4. **Gather expertise**: In interactive mode, ask about domain knowledge
5. **Generate agent file**: Create with frontmatter and sections
6. **Update manifest**: Add agent to manifest.json
7. **Report success**: Show location and customization tips

## Output Location

```
<target>/agents/<name>.md
```

## Agent File Structure

```markdown
---
name: agent-name
description: Agent description
model: claude-sonnet-4-6
tools: Read, Write, MultiEdit, Bash, WebFetch
---

# Agent Title

[Description]

## Expertise
[Domain knowledge]

## Responsibilities
[What the agent does]

## Workflow
[How it approaches tasks]

## Output Format
[Expected output structure]
```

## CLI Equivalent

```bash
aiwg add-agent <name> --to <target> --template <type>
```

## 10 Golden Rules Validation

After creation, validate against the Agent Design Bible:

```bash
aiwg lint agents <target>/agents/<name>.md --verbose
```

| Rule | Check |
|------|-------|
| 1. Single Responsibility | One clear purpose, no "and" overload |
| 2. Minimal Tools | 0-3 tools, justified |
| 3. Explicit I/O | Inputs and outputs defined |
| 4. Grounding | Verify before acting (Archetype 1) |
| 5. Uncertainty | Escalate ambiguity (Archetype 2) |
| 6. Context Scope | Filter distractors (Archetype 3) |
| 7. Recovery | Handle errors (Archetype 4) |
| 8. Model Tier | Match task complexity |
| 9. Parallel Ready | Concurrent execution safe |
| 10. Observable | Traceable output |

## Related Commands

- `/devkit-create-command` - Create a slash command
- `/devkit-create-skill` - Create an auto-triggered skill
- `/devkit-validate` - Validate agent structure
- `aiwg lint agents` - Validate against 10 Golden Rules

## References

- @$AIWG_ROOT/agentic/code/addons/aiwg-dev/README.md — aiwg-dev addon overview
- @$AIWG_ROOT/docs/extensions/extension-types.md — Extension types including agent type
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference including add-agent command
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/god-session.md — Single-responsibility rules for agents
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/agent-deployment.md — Agent metadata structure and multi-provider deployment

Files: 1

Size: 5.1 KB

Complexity: 12/100

Category: Design

Source: https://github.com/jmagly/aiwg/tree/main/agentic/code/addons/aiwg-dev/skills/devkit-create-agent

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts