p4-setup

/p4-setup – Repository, CI/CD & Development Environment Setup

Sets up the repository, CI/CD pipeline and local development environment. The result is a working development infrastructure in which the team can immediately start with /p5-implement.

Argument: $ARGUMENTS = [Project name]

If provided: Use as repository name and project identifier in configuration files. If not provided: Read CONCEPT.md or PROJECT_PLAN.md and derive the project name. If any context is missing, ask for the project name before starting.

Execution

1. Read Context

Read the following files (if available):

• TECH_STACK.md (technologies determine the setup)
• INFRASTRUCTURE.md (CI/CD pipeline design, hosting platform)
• SECURITY.md (security requirements for pipeline and secrets management)
• TEST_STRATEGY.md (test levels determine pipeline stages)

2. Delegation to DevOps Agent (Lead)

Delegate the technical setup to the devops agent:

Set up the development infrastructure for project $ARGUMENTS. Context from TECH_STACK.md and INFRASTRUCTURE.md: [Insert tech stack, CI/CD design, hosting decisions]

A. Repository Structure

• Create the initial directory structure matching the tech stack
• Basic configuration files: .gitignore, .editorconfig, .nvmrc / .tool-versions
• Document branching strategy (according to INFRASTRUCTURE.md)
• Basic git hooks: pre-commit (lint, format), commit-msg (Conventional Commits)

B. CI/CD Pipeline Implement the pipeline according to INFRASTRUCTURE.md:

• Configuration file(s) for the chosen CI/CD tool (e.g. .github/workflows/)
• Stage 1: Lint & Format Check
• Stage 2: Unit Tests
• Stage 3: Build
• Stage 4: Security Scan (SAST, dependency check e.g. with Trivy or Snyk)
• Stage 5: Deploy to Staging (manually triggered or on main branch)
• Secrets: placeholders and documentation of which secrets need to be configured

C. Docker / Containerization If containers are planned (according to TECH_STACK.md):

• Dockerfile(s) for all services (multi-stage builds for production)
• docker-compose.yml for local development (app + database + additional services if needed)
• .env.example with all required environment variables (without real values)

D. Development Environment

• Document the steps for local setup (will be incorporated into README.md)
• Seed script for test data (populate database with sample data)
• Make targets or npm scripts for common tasks: dev, test, build, lint, migrate

E. Configure Environments

• Environment variable structure for local / staging / production
• Implement secrets management approach (according to SECURITY.md)