tcgflow-initlisted
Install: claude install-skill bibennurbani/geekstack-flow
# `/tcgflow-init` — bootstrap the workspace
## When to use
The user typed `/tcgflow-init` or said something equivalent: *"set up geekstackflow here"*, *"initialise the AI workflow"*, *"create the .tcgstackflow"*. The current working directory is the target.
## What to do
1. **Check for prior AI infrastructure** that would conflict. Look for any of: `.tcgstackflow/`, `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`, `.taskRef/`, `ai-mem/`, `.docsRef/`. If found, **do not run init** — route the user to `/tcgflow-migrate` instead, because the right path is a clean cutover with backups, not init alongside an existing setup.
2. **Confirm the target directory.** Verify the current working directory is where the user wants the workspace. If ambiguous, ask.
3. **Walk the user through the prompts in chat first** (don't trust interactive `readline` to compose with tool-use). Collect:
- Project name (default: directory basename)
- Primary stack (e.g. "Next.js 16 + Prisma") — leave blank for multi-project workspaces; auto-detection populates `projects[]`
- Package manager (pnpm/npm/yarn/bun)
- Enable Tempo? If yes, capture Atlassian `cloudId`, quarterly admin key, timezone offset, submission mode (default `approval`)
- Enable Claude Code adapter? (default Y)
- Enable Codex adapter? (default N)
- Enable GitHub Copilot adapter? (default N)
4. **Run `geekstackflow init .`** (or `tcgflow init .`, same binary) in the target directory. If `geekstackflow`