Codex

devkit-create-command

Create a new slash command with AI-guided behavior definition

104 stars

Best use case

devkit-create-command is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

It is a strong fit for teams already working in Codex.

Create a new slash command with AI-guided behavior definition

Teams using devkit-create-command should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/devkit-create-command/SKILL.md --create-dirs "https://raw.githubusercontent.com/jmagly/aiwg/main/.agents/skills/devkit-create-command/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/devkit-create-command/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How devkit-create-command Compares

Feature / Agentdevkit-create-commandStandard Approach
Platform SupportCodexLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create a new slash command with AI-guided behavior definition

Which AI agents support this skill?

This skill is designed for Codex.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Create AIWG Command

Create a new slash command with AI assistance to define arguments, behavior, and output.

## Usage

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

## Arguments

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

## Required Options

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

## Optional Options

| Option | Description |
|--------|-------------|
| --template | Command template: utility (default), transformation, orchestration |
| --interactive | Enable interactive mode with guided questions |

## Templates

### utility (default)
Simple operation, single action command.
- Best for: Quick tasks, file operations, status checks
- Example: `/lint-check`, `/deploy-status`

### transformation
Content/code transformation pipeline with input/output handling.
- Best for: Format conversion, code refactoring, content processing
- Example: `/convert-format`, `/refactor-code`

### orchestration
Multi-agent workflow coordination with phases and parallel execution.
- Best for: Complex workflows, phase transitions, multi-step processes
- Example: `/flow-deploy-to-production`, `/flow-security-review`

## Interactive Mode

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

1. **Purpose**: What does this command do?
2. **Arguments**: What inputs does it need?
3. **Options**: What configuration options should it support?
4. **Steps**: What are the execution steps?
5. **Output**: What should the output look like?

## Examples

```bash
# Simple utility command
/devkit-create-command lint-fix --to aiwg-utils

# Transformation pipeline
/devkit-create-command convert-docs --to sdlc-complete --template transformation

# Orchestration workflow
/devkit-create-command deploy-all --to sdlc-complete --template orchestration --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 utility
4. **Gather behavior**: In interactive mode, ask about command behavior
5. **Generate command file**: Create with frontmatter and sections
6. **Update manifest**: Add command to manifest.json
7. **Report success**: Show location and usage instructions

## Output Location

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

## Command File Structure

```markdown
---
name: command-name
description: Command description
args: [arg1] [--option value --guidance "text"]
---

# Command Title

[Description]

## Usage
[How to invoke]

## Arguments
[Input parameters]

## Options
[Configuration flags]

## Execution
[Step-by-step behavior]

## Output
[What to expect]
```

## CLI Equivalent

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

## Related Commands

- `/devkit-create-agent` - Create an agent
- `/devkit-create-skill` - Create an auto-triggered skill
- `/devkit-validate` - Validate command structure

## References

- @$AIWG_ROOT/agentic/code/addons/aiwg-dev/README.md — aiwg-dev addon overview
- @$AIWG_ROOT/docs/extensions/extension-types.md — Extension types including command type
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference including add-command command
- @$AIWG_ROOT/docs/extensions/creating-extensions.md — Guide to building custom extensions
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/README.md — SDLC framework with example commands