initlisted

One-time, idempotent project bootstrap. Detects which magi-workflow project files are missing (root CLAUDE/README/SPEC, magi/PRD/TECHSTACK/BACKLOG) and offers to scaffold them. Never overwrites existing files. Run once when adopting magi-workflow on a new or existing project. Safe to re-run.
bozkurtonur3-lgtm/magi-workflow · ★ 1 · AI & Automation · score 74

Install: claude install-skill bozkurtonur3-lgtm/magi-workflow

# /magi:init — project bootstrap You are the coordinator. Detect which magi-workflow files are missing in this project and offer to scaffold the missing ones with minimal templates. Existing files are **never** overwritten. **You do not write production code.** ## 0. Preflight ```bash PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-}" [[ -z "$PLUGIN_ROOT" ]] && PLUGIN_ROOT="$(cd "$(dirname "$BASH_SOURCE[0]")/../.." 2>/dev/null && pwd)" USER_CONFIG="$HOME/.config/magi-workflow/config.json" ``` If `$USER_CONFIG` is missing, tell the user to run `/magi:setup` first (init needs `output_language` from there). This skill does not require a git repo, but warns the user if not in one (a typical magi-workflow project will be). ## 1. Scan for missing files Check existence of each well-known project file: | Path | Tier | Role | |------|------|------| | `CLAUDE.md` | 1 (root) | AI agent entry / instructions index | | `README.md` | 1 (root) | Human-readable project description | | `SPEC.md` | 1 (root) | Architecture & feature spec for AI agents | | `magi/PRD.md` | 2 (`magi/`) | Product requirements | | `magi/TECHSTACK.md` | 2 (`magi/`) | Tech stack constraints | | `magi/BACKLOG.md` | 2 (`magi/`) | Pending items promoted from sprint DRIFT.md | Build two lists: - **missing** — files that don't exist - **existing** — files that do exist (will be skipped, never modified) Show the user both lists clearly. If `missing` is empty, tell the user "project is already bootstrapped" and suggest `/magi:p