Develop

---
name: behavior:development:develop
description: Full task development workflow with multi-agent orchestration
argument-hint: "--task <description> --repo <name> --branch <name> [--description <text>]"
agents:
  - name: zzaia-developer-specialist
    description: Implementation and development tasks with user feedback integration
parameters:
  - name: task
    description: Task description or requirements
    required: true
  - name: repo
    description: Target repository name for the development
    required: true
  - name: branch
    description: Target branch name for the development
    required: true
  - name: auto-continue
    description: Skip interactive refinement loop and user approval; implement tests automatically without prompting
    required: false
  - name: description
    description: Additional context or instructions for the operation
    required: false
---

## PURPOSE

Execute focused implementation tasks for development work. Uses task specification from `/behavior:management:plan` command or assumes requirements are already clarified.

## EXECUTION

1. **Development Execution**

   - In case of not defined by the user, identify the related file or project by checking the user selected file or code lines in the IDE
   - In case of not being able to access selected file or code line, ask user which repository, branch and application to work
   - Executes implementation using zzaia-developer-specialist agent
     - Can execute multiple agents for parallel implementations

2. **Testing Development**

   - If `--auto-continue` is set, implement tests automatically as part of the implementation
   - Otherwise ask the user if tests should be implemented before proceeding

3. **Finalizing**

   - If `--auto-continue` is set, complete immediately after implementation without requesting user feedback
   - Otherwise present results, ask for improvements, and continue loop until user approves

## DELEGATION

**MANDATORY**: Always invoke the agents defined in this command's frontmatter for their designated responsibilities. Never skip, replace, or simulate their behavior directly.

- `zzaia-developer-specialist` — Implementation and development tasks with user feedback integration

## WORKFLOW

```mermaid
sequenceDiagram
    participant U as User
    participant C as /behavior:development:develop Command
    participant DS as Developer Specialist
    participant P as Project

    U->>C: /develop [task] [repo] [branch]

    alt auto-continue set
        C->>DS: Execute implementation + tests
        DS->>P: Apply code changes
        P-->>DS: Implementation complete
        DS-->>C: Implementation results
        C-->>U: Development complete
    else Interactive mode
        loop Implementation & Refinement
            C->>DS: Execute implementation
            DS->>P: Apply code changes
            P-->>DS: Implementation complete
            DS-->>C: Implementation results
            C->>U: Present implementation results
            alt User approves completion
                C-->>U: Development complete
            else User provides improvements
                C->>DS: Apply user suggestions
            end
        end
    end

EXAMPLES

# Plan first (recommended)
/behavior:management:plan implement user authentication system
/behavior:development:develop Add user authentication with JWT tokens repo=auth-service branch=feature/jwt-auth

# Develop in specific repository and branch
/behavior:development:develop payment processing repo=compliance-hub branch=feature/payments

Language Rules

Apply the appropriate rule file before any code modification:

C#/.NET: @commands/behavior/development/rules/dotnet-coding-rules.md Python: @commands/behavior/development/rules/python-coding-rules.md Jupyter/Python Notebook: @commands/behavior/development/rules/python-notebook-rules.md JavaScript/TypeScript: @commands/behavior/development/rules/javascript-coding-rules.md TypeScript/Node.js: @commands/behavior/development/rules/typescript-coding-rules.md — always TypeScript, never plain JavaScript

Acceptance Criteria

Defines when the whole process must be considered completed

• Implementation satisfies user requirements
• When --auto-continue is set: tests implemented automatically and workflow completes without user interaction
• When interactive: user approval granted for completion

OUTPUT

• Implementation progress updates
• Code changes and file modifications
• Implementation completion status
• Final development completion confirmation