nicolas-codemate/init-project

Init Project Skill

Interactive configuration wizard that creates .claude/ticket-config.json to configure the ticket resolution workflow for a project.

When to Use

• First time running /resolve in a project
• Reconfiguring project settings
• Called via /resolve --init

Wizard Flow

1. Welcome

# Configuration du projet pour /resolve

Ce wizard va creer le fichier `.claude/ticket-config.json` pour configurer
le workflow de resolution de tickets dans ce projet.

2. Source Configuration

AskUserQuestion:
  question: "Quelle source de tickets utilisez-vous principalement ?"
  header: "Source"
  options:
    - label: "YouTrack"
      description: "Tickets YouTrack via MCP"
    - label: "GitHub Issues"
      description: "Issues et PRs GitHub via gh CLI"
    - label: "Les deux"
      description: "Detection automatique selon le format"

If YouTrack selected or "Les deux":

AskUserQuestion:
  question: "Quel est le prefixe de votre projet YouTrack ?"
  header: "YouTrack"
  options:
    - label: "Entrer le prefixe"
      description: "Ex: PROJ, MYAPP, BACK..."

User enters prefix (e.g., "PROJ")

If GitHub selected or "Les deux":

AskUserQuestion:
  question: "Quel est le repository GitHub ?"
  header: "GitHub"
  options:
    - label: "Detecter automatiquement"
      description: "Utiliser 'git remote get-url origin'"
    - label: "Entrer manuellement"
      description: "Format: owner/repo"

• If auto-detect: run git remote get-url origin and extract owner/repo
• If manual: user enters "owner/repo"

3. Branch Configuration

AskUserQuestion:
  question: "Quelle est votre branche principale ?"
  header: "Base branch"
  options:
    - label: "main"
      description: "Convention moderne"
    - label: "master"
      description: "Convention classique"
    - label: "develop"
      description: "Gitflow - branche de dev"

AskUserQuestion:
  question: "Comment nommer les branches de feature ?"
  header: "Prefixes"
  options:
    - label: "Standard (Recommended)"
      description: "feat/, fix/, refactor/, docs/"
    - label: "Simple"
      description: "feature/, bugfix/"
    - label: "Avec ticket"
      description: "PROJ-123/description"

4bis. Quality Assurance (optionnelle)

AskUserQuestion:
  question: "Activer la QA pour ce projet ?"
  header: "QA"
  options:
    - label: "Oui, configurer maintenant (Recommended)"
      description: "Cree la section qa dans ticket-config.json. /qa-sync pourra commencer immediatement."
    - label: "Non, plus tard"
      description: "/qa-sync pourra bootstrap la configuration au premier lancement."

If "Oui" selected:

AskUserQuestion:
  question: "Quelle URL utiliser pour la QA en local ?"
  header: "Base URL"
  options:
    - label: "http://localhost:8000"
      description: "Stack PHP/Symfony classique"
    - label: "http://localhost:3000"
      description: "Stack Node/Next/Vite"
    - label: "Autre"
      description: "Saisir manuellement"

AskUserQuestion:
  question: "Demarrer automatiquement docker compose si l'app est down avant /qa-run ?"
  header: "Preflight"
  options:
    - label: "Oui (Recommended)"
      description: "Detecte docker-compose.yml et propose docker compose up -d"
    - label: "Non"
      description: "L'utilisateur demarre l'app manuellement"

Detect pre-run command:

Apply ~/.claude/skills/qa-sync/references/pre-run-detection.md to detect a pre_run candidate (Makefile target / package.json script / Symfony bin/console command). The reference returns a string (the chosen command) or null (skip). Store the result as qa_pre_run.

Store the QA answers as qa_enabled, qa_base_url, qa_docker_autostart, qa_pre_run for use in step 5.

4. Complexity Defaults

AskUserQuestion:
  question: "Comportement par defaut pour la complexite ?"
  header: "Complexite"
  options:
    - label: "Detection automatique (Recommended)"
      description: "Analyser le contenu du ticket"
    - label: "Toujours simple"
      description: "Workflow rapide sans exploration"
    - label: "Toujours complet"
      description: "AEP + Architect systematique"

5. Generate Configuration

Build config object based on answers:

{
  "default_source": "auto|youtrack|github",
  "youtrack": {
    "project_prefix": "PROJ"
  },
  "github": {
    "repo": "owner/repo"
  },
  "branches": {
    "default_base": "main|master|develop",
    "prefix_mapping": {
      "bug": "fix",
      "feature": "feat",
      "task": "feat",
      "refactoring": "refactor",
      "documentation": "docs"
    }
  },
  "complexity": {
    "auto_detect": true|false,
    "default_level": "simple|medium|complex"
  },
  "simplify": {
    "enabled": true,
    "agent": "auto",
    "scope": "modified",
    "auto_apply": false
  },
  "review": {
    "enabled": true,
    "auto_fix": false,
    "severity_threshold": "important",
    "block_on_critical": true
  },
  "pr": {
    "draft_by_default": true,
    "default_target": null,
    "include_ticket_link": true,
    "title_format": "{type}: {title} ({ticket_id})"
  },
  "qa": {
    "test_plan_dir": "docs/qa",
    "base_url": "http://localhost:8000",
    "browser": "playwright",
    "env_file": ".env.qa",
    "label": "qa",
    "auth_profiles": ["anonymous", "user", "admin"],
    "preflight": { "docker_autostart": true },
    "pre_run": null
  }
}

The qa section is included only if qa_enabled was answered "Oui" in step 4bis. Otherwise, omit the key entirely — /qa-sync will bootstrap it on first run.

Set qa.pre_run to the value of qa_pre_run (the detected command string, or null if no candidate was detected and the user picked "Aucun").

6. Save Configuration

mkdir -p .claude

Write to .claude/ticket-config.json.

7. Confirmation

# Configuration sauvegardee

Fichier cree: `.claude/ticket-config.json`

```json
{content of generated config}

Utilisation

# Resoudre un ticket
/resolve PROJ-123

# Mode automatique
/resolve PROJ-123 --auto

# Modifier la config
/resolve --init

Le projet est pret pour utiliser /resolve !

## Output

After completion, the skill creates:
- `.claude/ticket-config.json` - Project configuration file

**IMPORTANT**: After this skill completes, the workflow STOPS. Do not continue to ticket resolution.