/setup

name: setup
description: "Scaffolds the project and sets up the Conductor environment for spec-driven development"
user_invocable: true
model: opus

/orchestrator-supaconductor:setup — Full Project Initialization

You are an AI agent. Your primary function is to **set up** (scaffold and plan) a software project using the SupaConductor methodology. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions.

**SCOPE BOUNDARY: This command creates the folder structure, project context documents, and development sprint (tracks with specs). It does NOT execute any tracks. After Section 4.0 FINALIZATION, you MUST stop and return control to the user. Do NOT invoke `/go`, `/implement`, or any execution skill.**

CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.

---

1.0 BEGIN RESUME CHECK

**PROTOCOL: Before starting the setup, determine the project's state using the state file.**

1. **Read State File:** Check for the existence of `conductor/setup_state.json`.

• If it does not exist, this is a new project setup. Proceed directly to Step 1.1.
• If it exists, read its content.

2. **Resume Based on State:**

• Let the value of `last_successful_step` in the JSON file be `STEP`.
• Based on the value of `STEP`, jump to the **next logical section**:

| `STEP` value | Resume message | Jump to | |---|---|---| | `"1.2_scaffold"` | "Resuming: Scaffold complete. Next: Project discovery." | **Section 2.0** | | `"2.0_project_discovery"` | "Resuming: Project analyzed. Next: Product definition." | **Section 2.1** | | `"2.1_product_guide"` | "Resuming: Product Guide complete. Next: Tech stack." | **Section 2.2** | | `"2.2_tech_stack"` | "Resuming: Tech stack defined. Next: Product guidelines." | **Section 2.3** | | `"2.3_product_guidelines"` | "Resuming: Guidelines complete. Next: Workflow configuration." | **Section 2.4** | | `"2.4_workflow"` | "Resuming: Workflow configured. Next: Initial sprint generation." | **Section 3.0** | | `"3.3_initial_sprint_generated"` | "Setup already complete. Use `/orchestrator-supaconductor:go` to start or `/orchestrator-supaconductor:new-track` to add tracks." | **HALT** |

• If `STEP` is unrecognized, announce an error and halt.

---

1.1 PRE-INITIALIZATION OVERVIEW

1. **Provide High-Level Overview:**

• Present the following overview to the user:

> "Welcome to SupaConductor. I will guide you through the following steps to set up your project: > 1. **Scaffold:** Create the conductor directory structure and configuration. > 2. **Project Discovery:** Analyze the current directory to determine if this is a new or existing project. > 3. **Product Definition:** Define the product's vision, tech stack, and design guidelines. > 4. **Workflow Configuration:** Set up your development workflow preferences. > 5. **Sprint Generation:** Create the initial development sprint with tracks ready for execution. > > Let's get started!"

---

1.2 SCAFFOLD — Create Directory Structure

1. **Create directories:**

mkdir -p conductor/tracks
mkdir -p conductor/knowledge

2. **Create `conductor/setup_state.json`:**

{"last_successful_step": ""}

3. **Create `conductor/config.json`:**

**Mode-dependent behavior:** Check `$ARGUMENTS` for `--mode` flag. Default is `"agentic"`.

{
  "mode": "agentic",
  "max_fix_cycles": 5,
  "planning_model": "opus",
  "execution_model": "sonnet"
}

**Mode Options:**

• `"agentic"` (default) — Fully autonomous. All decisions resolved by agents. Interactive questions auto-generate after presenting suggestions. Never blocks on user input.
• `"human-in-the-loop"` — Pauses at key decision points. Asks the user questions sequentially with options. Waits for approval before proceeding.

4. **Create `conductor/tracks.md`:**

# Conductor Track Registry

Active and completed development tracks.

## Active Tracks

| Track ID | Name | Type | Status | Step | Priority | Created |
|----------|------|------|--------|------|----------|---------|

## Completed Tracks

| Track ID | Name | Completed | Summary |
|----------|------|-----------|---------|

5. **Create `conductor/index.md`:**

# Project Status

**Last Updated**: YYYY-MM-DD

## Current Focus
(setup in progress...)

## Recent Completions
(none)

## System Health
- Conductor v3 initialized
- orchestrator-supaconductor: enabled

6. **Create `conductor/decision-log.md`:**

# Decision Log

Technical and business decisions made during development.

## Format

### DECISION-XXX: [Title]
- **Date**: YYYY-MM-DD
- **Track**: track-id
- **Decision**: What was decided
- **Rationale**: Why this decision was made
- **Alternatives**: What else was considered
- **Impact**: Effects on architecture/product/business

7. **Create `conductor/knowledge/patterns.md`:**

# Code Patterns & Conventions

Discovered patterns from the codebase.

## Architecture Patterns
(pending project analysis)

## Common Solutions
(pending project analysis)

## Anti-patterns to Avoid
(pending project analysis)

8. **Create `conductor/knowledge/errors.json`:**

{
  "version": 1,
  "errors": []
}

9. **Copy workflow.md** from the plugin's `docs/workflow.md` to `conductor/workflow.md`.

10. **Commit State:**

{"last_successful_step": "1.2_scaffold"}

11. **Continue** immediately to Section 2.0.

---

2.0 PROJECT DISCOVERY

2.0.1 Detect Project Maturity

Classify the project as **Brownfield** (existing) or **Greenfield** (new):

**Brownfield Indicators** — if ANY are true, classify as Brownfield:

• Version control directories exist: `.git`, `.svn`, `.hg`
• Dependency manifests exist: `package.json`, `pom.xml`, `requirements.txt`, `go.mod`,