Codex

new-project

Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry

104 stars

Best use case

new-project 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.

Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry

Teams using new-project 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/new-project/SKILL.md --create-dirs "https://raw.githubusercontent.com/jmagly/aiwg/main/.agents/skills/new-project/SKILL.md"

Manual Installation

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

How new-project Compares

Feature / Agentnew-projectStandard Approach
Platform SupportCodexLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Scaffold a new AIWG-managed project with .aiwg/ directory structure, starter CLAUDE.md, and framework registry

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

# New Project

You scaffold a new AIWG-managed project, creating the `.aiwg/` directory structure, deploying a starter CLAUDE.md, and initialising the framework registry.

## Triggers

Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):

- "start a new project" → scaffold with default template
- "set up aiwg for my project" → scaffold in current directory
- "bootstrap project" → scaffold with default template
- "create aiwg project" → scaffold with default template

## Trigger Patterns Reference

| 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` |

## Behavior

When triggered:

1. **Extract arguments**:
   - What is the project name or target directory?
   - Is a specific template requested? (default: `sdlc`)
   - Is a specific provider requested? (default: `claude-code`)
   - Is this in-place (`.`) or creating a new directory?

2. **Run the appropriate command**:

   ```bash
   # 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**:
   - `.aiwg/` with subdirectories: `intake/`, `requirements/`, `architecture/`, `planning/`, `risks/`, `testing/`, `security/`, `deployment/`, `working/`, `reports/`
   - `.aiwg/frameworks/registry.json` — installed framework registry
   - `CLAUDE.md` (or provider-equivalent) — starter instructions
   - Initial framework deployment for the selected provider

4. **Report the result** — confirm directories created, files written, and next recommended step (`aiwg use sdlc` or `/intake-wizard`).

## Examples

### Example 1: Basic new project

**User**: "Create a new project called customer-portal"

**Extraction**: Project name `customer-portal`, default template, default provider

**Action**:
```bash
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."

### Example 2: In-place scaffold

**User**: "Set up AIWG in the current directory"

**Extraction**: In-place scaffold (`.`), default template

**Action**:
```bash
aiwg new .
```

**Response**: "Initialised `.aiwg/` in the current directory. Starter `CLAUDE.md` written. Run `aiwg use sdlc` to deploy frameworks."

### Example 3: Research project with specific provider

**User**: "Bootstrap a new project called signal-study using the research template for Cursor"

**Extraction**: Project name `signal-study`, template `research`, provider `cursor`

**Action**:
```bash
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."

### Example 4: List available templates

**User**: "What templates can I use when creating a project?"

**Extraction**: Template listing request

**Action**:
```bash
aiwg new --list-templates
```

**Response**: Lists available templates (e.g., `sdlc`, `research`, `forensics`, `marketing`) with one-line descriptions.

## Clarification Prompts

If the user's intent is ambiguous:

- "What should the project be called, or should I scaffold in the current directory?"
- "Which template would you like — `sdlc` (default), `research`, `forensics`, or `marketing`?"
- "Which provider should I target? (detected: claude-code)"

## References

- @$AIWG_ROOT/src/cli/handlers/subcommands.ts — `new` command handler
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/README.md — SDLC framework overview

Related Skills

project-timeline-simulator

104
from jmagly/aiwg

Simulate project outcomes with variable modeling, risk assessment, and resource optimization scenarios.

Codex

project-status

104
from jmagly/aiwg

Analyze project state from .aiwg/ artifacts and provide contextual status with recommended next steps

Codex

project-health-check

104
from jmagly/aiwg

Analyze overall project health and metrics

Codex

project-awareness

104
from jmagly/aiwg

Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions

Codex

orchestrate-project

104
from jmagly/aiwg

Plan iterations, delegate to SDLC agents, and compile iteration status

Codex

aiwg-setup-project

104
from jmagly/aiwg

Update project CLAUDE.md with AIWG framework context and configuration

Codex

aiwg-orchestrate

104
from jmagly/aiwg

Route structured artifact work to AIWG workflows via MCP with zero parent context cost

venv-manager

104
from jmagly/aiwg

Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.

pytest-runner

104
from jmagly/aiwg

Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.

vitest-runner

104
from jmagly/aiwg

Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.

eslint-checker

104
from jmagly/aiwg

Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.

repo-analyzer

104
from jmagly/aiwg

Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.