Starting a New Project

Starting a New Project

You have an idea. You want to build something. AIWG runs a structured intake conversation, generates the foundation documents your project needs, then assigns AI agents to carry the work forward.

This is the full setup — requirements, architecture, test strategy, security baseline — generated from a single conversation.


Step 1 — Install

npm install -g aiwg

Or use the Claude Code plugin:

/plugin marketplace add jmagly/ai-writing-guide
/plugin install sdlc@aiwg

Step 2 — Create your project folder

mkdir my-project && cd my-project
git init

Step 3 — Deploy the SDLC framework

aiwg use sdlc

This installs agents, commands, and rules into `.claude/`. One-time per project.


Step 4 — Open in Claude Code and start intake

claude .

Then tell it what you're building:

I want to build a REST API for a task management app. Users can create tasks,
assign them to teammates, and get notifications when tasks are due.

Or use the explicit intake command:

/intake-wizard "task management API with team assignments and notifications"

The AI will ask clarifying questions, then generate:

  • Intake form — problem statement, users, goals, constraints
  • Use cases — what the system does, who it does it for
  • Architecture sketch — components, tech stack recommendations
  • Risk register — what could go wrong early

These go into `.aiwg/` in your project. You can read them, edit them, and they guide everything that comes next.


Step 5 — Start building

Once intake is complete, the AI knows your project. You can now use natural language to drive development:

Create the user model based on the requirements
Write unit tests for the task assignment feature
Run a security review on the authentication flow
What phase are we in and what's next?

The AI will answer in context — it knows your architecture, your requirements, and what decisions have already been made.


What the `.aiwg/` folder contains

Everything generated during the project lives here:

.aiwg/
├── intake/         ← Your project definition
├── requirements/   ← Use cases and user stories
├── architecture/   ← Architecture decisions (ADRs)
├── testing/        ← Test strategy and plans
├── security/       ← Threat model
├── planning/       ← Phase plans, iteration notes
└── reports/        ← Status and audit reports

You can commit this folder. It becomes part of your project history. New team members can read it to understand the project, and new AI sessions can load it to pick up context.


Moving through phases

AIWG uses a structured lifecycle: Inception → Elaboration → Construction → Transition.

To move between phases, just say so:

Let's move to elaboration
Transition to construction — we're done with design

The AI will run a gate check, verify what needs to be done, and orchestrate the transition.


If you already have some code

Run `/intake-from-codebase` instead of `/intake-wizard` — it scans what you have and fills in the intake from the code rather than asking you from scratch. See Existing Project.