Aiwg devkit-create-extension

Create a new AIWG extension (framework expansion pack) with AI-guided setup

install

source · Clone the upstream repo

git clone https://github.com/jmagly/aiwg

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/jmagly/aiwg "$T" && mkdir -p ~/.claude/skills && cp -r "$T/agentic/code/addons/aiwg-dev/skills/devkit-create-extension" ~/.claude/skills/jmagly-aiwg-devkit-create-extension-cb031b && rm -rf "$T"

manifest: agentic/code/addons/aiwg-dev/skills/devkit-create-extension/SKILL.md

source content

Create AIWG Extension

Create a new extension (framework expansion pack) with AI assistance.

Extensions enhance a specific parent framework with additional templates, checklists, and domain-specific content. They cannot operate standalone.

Usage

/devkit-create-extension <name> --for <framework> [--interactive]

Arguments

Argument	Required	Description
name	Yes	Extension name (kebab-case recommended)

Required Options

Option	Description
--for	Parent framework ID (e.g., sdlc-complete, media-marketing-kit)

Optional Options

Option	Description
--interactive	Enable interactive mode with guided questions

What This Creates

agentic/code/frameworks/<framework>/extensions/<name>/
├── manifest.json      # type: "extension", requires: ["<framework>"]
├── README.md          # Documentation
├── templates/         # Domain-specific templates
└── checklists/        # Compliance/verification checklists

Interactive Mode

When

--interactive

is specified, I will ask:

Domain: What compliance/domain does this extension address?
Purpose: What specific requirements or standards does it cover?
Templates: What templates should be included?
Checklists: What verification checklists are needed?
Dependencies: Does it depend on other extensions?

Examples

# Quick creation
/devkit-create-extension hipaa --for sdlc-complete

# Interactive guided creation
/devkit-create-extension sox --for sdlc-complete --interactive

Common Extension Types

Compliance Extensions

```
gdpr
```
- EU data protection
```
hipaa
```
- Healthcare (US)
```
sox
```
- Financial controls (US)
```
pci-dss
```
- Payment card security
```
ftc
```
- FTC advertising rules

Domain Extensions

```
healthcare
```
- Healthcare-specific templates
```
fintech
```
- Financial technology patterns
```
government
```
- Government/public sector

Execution

Validate inputs: Check name and framework
Verify framework exists: Ensure parent framework is installed
Check for duplicates: Verify extension doesn't exist
Gather info: In interactive mode, ask about domain and needs
Generate manifest: Create with
```
requires
```
field for parent
Create structure: Build templates/ and checklists/ directories
Generate README: Document extension purpose and usage
Optionally create content: Offer to create initial templates/checklists
Report success: Show created files and activation instructions

CLI Equivalent

For non-interactive creation:

aiwg scaffold-extension <name> --for <framework> --description "..."

Related Commands

```
/devkit-create-addon
```
- Create standalone addon
```
/devkit-create-framework
```
- Create full framework
```
/devkit-validate
```
- Validate extension structure
```
aiwg add-template
```
- Add template to extension

References

@$AIWG_ROOT/agentic/code/addons/aiwg-dev/README.md — aiwg-dev addon overview
@$AIWG_ROOT/docs/extensions/overview.md — Extension system architecture
@$AIWG_ROOT/docs/extensions/creating-extensions.md — Guide to building custom extensions
@$AIWG_ROOT/docs/cli-reference.md — CLI reference including scaffold-extension command
@$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/README.md — SDLC framework as example parent framework