autospec.worktree-setup

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

You are generating a project-specific setup script that will be run when creating new git worktrees. This script handles copying essential configuration files and running package manager install commands instead of copying large dependency directories.

Follow this execution flow:

1. Analyze project structure:

   • Identify package managers by checking for lockfiles:

     • package-lock.json -> npm
     • yarn.lock -> yarn
     • pnpm-lock.yaml -> pnpm
     • bun.lockb -> bun
     • go.sum or go.mod -> go
     • requirements.txt or Pipfile.lock -> pip/pipenv
     • poetry.lock or pyproject.toml with [tool.poetry] -> poetry
     • Cargo.lock -> cargo
     • Gemfile.lock -> bundler
     • composer.lock -> composer

   • Identify essential directories/files to copy:

     Autospec-related (REQUIRED for autospec workflows):

     • .autospec/ - Contains constitution, config, memory, and generated scripts. The constitution.yaml is REQUIRED for all workflow stages (specify, plan, tasks, implement).
     • .agents/skills/ (if exists) - Shared autospec skills for Codex and OpenCode skill-aware sessions.
     • .claude/skills/ (if exists) - Claude Code project skills. Required if using agent_preset: claude.
     • opencode.json (if exists) - OpenCode configuration file with permissions and model settings. Located at project root, not inside .opencode/.

     IDE/Editor configuration:

     • .vscode/ (if exists)
     • .idea/ (if exists)
     • Other gitignored config directories needed for development

   • Identify files/directories to EXCLUDE:

     • Dependency directories: node_modules/, vendor/, __pycache__/, .venv/, venv/, target/, dist/, build/, .bundle/
     • Generated files: *.log, *.tmp, .cache/, coverage/

2. Handle secrets:

   • By default, EXCLUDE these secret patterns:
     • .env* (.env, .env.local, .env.production, etc.)
     • credentials.*
     • secrets.*
     • *.pem
     • *.key
     • *.p12
     • *token* files
     • .ssh/
   • If --include-env was specified in the user input, include .env* files but still exclude other secret patterns