← ClaudeAtlas

init-projectlisted

Initialize the workflow scaffold (CLAUDE.md, WORKFLOW.md, memory bank) in this folder. Use when the user asks to init, set up, or bootstrap the project workflow — in an empty folder (interview mode) or an existing codebase (analysis mode).
FrederikEupry/agent-workflow-template · ★ 0 · AI & Automation · score 62
Install: claude install-skill FrederikEupry/agent-workflow-template
# Init project Set up the memory-bank workflow in the current folder. Two modes, chosen automatically. ## Step 0 — verify the scaffold is present Check for `WORKFLOW.md`, `CLAUDE.md`, `AGENTS.md`, and `memory-bank/` in the repo root. (`AGENTS.md` is an identical copy of `CLAUDE.md` for Codex/Cursor/Cline/Aider.) - If missing and this skill arrived via the workflow template repo, copy them from the template (same source this `.claude/skills/` folder came from, or run its `install.sh`). - If you cannot locate the template, ask the user for its path or URL. Do not improvise a different structure — WORKFLOW.md is the canonical spec. Read `WORKFLOW.md` §3 (Memory Bank) before writing anything. ## Step 1 — detect mode Look at the repo root, ignoring the workflow files themselves (`WORKFLOW.md`, `CLAUDE.md`, `AGENTS.md`, `memory-bank/`, `.claude/`, `README.md`, `.git`, `install.sh`, dotfiles). - **Nothing else there → Interview mode** (greenfield project). - **Source code, configs, or docs present → Analysis mode** (existing project). ## Step 2a — interview mode (empty folder) Ask the user, using AskUserQuestion where options are enumerable and free text otherwise. Keep it to two rounds maximum: 1. Project name and one-sentence vision (what outcome it exists to produce) 2. Goals (2–4, concrete) and explicit non-goals 3. Who uses it / who owns it 4. Intended stack and where it will run (may be "undecided" — record that honestly) 5. Any hard constraints (security, cost, com