init-project

name	init-project
description	Use when someone asks to initialize a new project, scaffold a project, set up the development workflow, or create project structure. Also trigger on 'start new project', 'workflow setup', 'project scaffold', or 'init from template'. Even if they just say 'set up a new project', this skill is likely what they want.
argument-hint	["target-directory"]

What This Skill Does

Scaffolds a new project with the AI-Assisted Development Workflow: directories for all 5 phases, placeholder files (PROGRESS.md, decisions index), and a starter CLAUDE.md.

Steps

Step 1: Determine the target directory

Target is $ARGUMENTS. If not provided, ask the user. Resolve relative paths against the current working directory.

Step 2: Check if already initialized

If the target has workflow/plan/, ask: full re-init or cancel.

Step 3: Create directory structure

mkdir -p "$TARGET"/{workflow/{research/{manual,final/references},spec,plan/reviews,decisions,retro},src,tests}

Step 4: Create placeholder files

Create .gitkeep in empty directories.

Create workflow/plan/PROGRESS.md:

# Implementation Progress

Last updated: —

## Milestone 1: TBD

| Task | Title | Role | Status | Review | Notes |
|------|-------|------|--------|--------|-------|

## Spec Gaps Discovered
(none yet)

## Blocked Items
(none yet)

Create workflow/decisions/README.md:

# Decision Records

| ID | Title | Phase | Status |
|----|-------|-------|--------|

Step 5: Generate README.md

Create README.md with placeholder sections that phases will fill in:

# {{PROJECT_NAME}}

{{ONE_LINE_DESCRIPTION}}

## Overview

{{FILL_IN_AFTER_PHASE_1 — problem statement, background, what this project does and why}}

## Getting Started

### Prerequisites

{{FILL_IN_AFTER_PHASE_2 — runtime version, system dependencies}}

### Installation

{{FILL_IN_AFTER_PHASE_2 — package manager setup, dependency installation}}

## Usage

{{FILL_IN_AFTER_PHASE_4 — examples, CLI reference, API quickstart}}

## Architecture

{{FILL_IN_AFTER_PHASE_2 — brief architecture overview with link to workflow/spec/SPEC.md}}

## Contributing

{{FILL_IN — contribution guidelines, or link to CONTRIBUTING.md}}

## License

{{FILL_IN — e.g., MIT}}

Step 6: Generate CLAUDE.md

Create CLAUDE.md with the following content:

# Project Instructions

## Project
- Name: {{PROJECT_NAME}}
- Description: {{ONE_LINE_DESCRIPTION}}

## Workflow

This project follows the AI-Assisted Software Development Workflow.

| Phase | Skill | Mode |
|-------|-------|------|
| 1. Research | `/agentic-dev:research` | Normal |
| 2. Specification | `/agentic-dev:spec` | Plan/read-only |
| 3. Task Breakdown | `/agentic-dev:plan` | Normal |
| 4. Execution | `/agentic-dev:execute` | Worktree |
| 5. Verification | `/agentic-dev:verify` | Normal |

### Key Documents
- Spec: `workflow/spec/SPEC.md`
- Plan: `workflow/plan/PLAN.md`
- Progress: `workflow/plan/PROGRESS.md`
- Decisions: `workflow/decisions/`

## Architecture

{{FILL_IN_AFTER_PHASE_2 — architecture summary, 5-10 lines}}

## Build & Test

{{FILL_IN — e.g., npm install, npm test, npm run lint}}

## Tooling Preferences

{{FILL_IN — e.g., Package manager: uv, Python version: >=3.12, Linter: ruff, Formatter: ruff format}}

## Coding Standards

{{FILL_IN_AFTER_PHASE_2 — or link to workflow/spec/SPEC.md}}

Step 7: Create .gitignore if missing

Standard entries: .DS_Store, .env, editor directories.

Step 8: Report next steps

1. Edit README.md and CLAUDE.md — fill in project name, description, and tooling preferences
2. Place research materials in workflow/research/manual/
3. Start Phase 1: /agentic-dev:research

Important

• Do NOT overwrite existing project files without asking
• The {{placeholders}} in CLAUDE.md are for the human to fill in — do not resolve them