agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration
Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry. Use when creating or scaffolding a new project.
$ npx -y skills add jmagly/aiwg --skill new-project --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/new-projectContext preview
The summary Claude sees to decide when to auto-load this skill.
Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry. Use when creating or scaffolding a new project.
namespace: aiwg name: new-project platforms: [all] description: Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry. Use when creating or scaffolding a new project. triggers: - scaffold a project - create a project - new project - aiwg new - project scaffolding - project-local bundle
<!-- AIWG-SKILL-CALLOUT --> > **Skill access pattern (post-kernel-pivot, 2026.5+)** > > Skill names referenced in this document are AIWG skills, **not slash commands**. Most are not kernel-listed and cannot be invoked as `/skill-name` by the platform. Reach them via: > > ```bash > aiwg discover "<capability>" > aiwg show skill <name> > ``` > > Only kernel-listed skills (`aiwg-doctor`, `aiwg-refresh`, `aiwg-status`, `aiwg-help`, `use`, `steward`) are directly invokable as slash commands. See [skill-discovery rule](../../../addons/aiwg-utils/rules/skill-discovery.md).
You scaffold a new AIWG-managed project, creating the `.aiwg/` directory structure, deploying a starter CLAUDE.md, and initialising the framework registry.
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
| Pattern | Example | Action | |---------|---------|--------| | Named project | "new project my-app" | Run `aiwg new my-app` | | With template | "create project my-app using research template" | Run `aiwg new my-app --template research` | | With provider | "scaffold project my-app for copilot" | Run `aiwg new my-app --provider copilot` | | In-place | "set up aiwg here" | Run `aiwg new .` | | Template list | "what project templates are available?" | Run `aiwg new --list-templates` |
When triggered:
1. **Extract arguments**:
2. **Run the appropriate command**:
# Default: create named project directory aiwg new <project-name> # With a specific template aiwg new <project-name> --template research # With a specific provider aiwg new <project-name> --provider copilot # In the current directory aiwg new . # Combined aiwg new my-app --template sdlc --provider cursor
3. **What the command creates**:
4. **Report the result** — confirm directories created, files written, and next recommended step (`aiwg use sdlc` or `intake-wizard`).
**User**: "Create a new project called customer-portal"
**Extraction**: Project name `customer-portal`, default template, default provider
**Action**:
aiwg new customer-portal
**Response**: "Created `customer-portal/` with `.aiwg/` structure (10 subdirectories), starter `CLAUDE.md`, and empty framework registry. Next step: run `aiwg use sdlc` inside the project to deploy the SDLC framework."
**User**: "Set up AIWG in the current directory"
**Extraction**: In-place scaffold (`.`), default template
**Action**:
aiwg new .
**Response**: "Initialised `.aiwg/` in the current directory. Starter `CLAUDE.md` written. Run `aiwg use sdlc` to deploy frameworks."
**User**: "Bootstrap a new project called signal-study using the research template for Cursor"
**Extraction**: Project name `signal-study`, template `research`, provider `cursor`
**Action**:
aiwg new signal-study --template research --provider cursor
**Response**: "Created `signal-study/` with research-template `.aiwg/` structure and deployed research-complete framework to `.cursor/`. Open the project and run `intake-wizard` to begin."
**User**: "What templates can I use when creating a project?"
**Extraction**: Template listing request
**Action**:
aiwg new --list-templates
**Response**: Lists available templates (e.g., `sdlc`, `research`, `forensics`, `marketing`) with one-line descriptions.
If the user's intent is ambiguous:
Reusable project context and specialist workflows for the AI tools you already use. Plan software, coordinate specialist reviews, prepare campaigns, investigate incidents, organize research, curate media, and maintain operational knowledge.
Repo: jmagly/aiwg
Crash-resilient external agent loop with state persistence and CI/CD integration
Detect requests for iterative autonomous agent loops and route to the appropriate loop executor
Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern
Enable agent loops to learn from similar past tasks and share patterns across loops
Query and manage the executable feedback debug memory
Execute tests on generated code and iterate until passing