/execute-task

Execute specific development tasks with context-aware implementation that adapts to your project's patterns and conventions.

Overview

• Purpose: Intelligent task implementation
• Category: Core Orchestration
• Type: Dynamic prompt
• MCP Tools: None (uses Claude's native abilities)

Syntax

/execute-task [task-description]

Usage Examples

# Feature implementation
/execute-task "Add user authentication with email/password"

# API endpoint
/execute-task "Create CRUD endpoints for products"

# UI component
/execute-task "Build responsive navigation menu"

# Integration
/execute-task "Integrate Stripe payment processing"

How It Works

Context Discovery

1. Analyzes existing code structure
2. Identifies current patterns
3. Understands conventions
4. Finds related code

Adaptive Implementation

• Matches your coding style
• Uses existing utilities
• Follows established patterns
• Integrates seamlessly

Quality Assurance

• Implements error handling
• Adds appropriate tests
• Updates documentation
• Validates implementation

Best Practices

1. Clear Task Definition

# Good: Specific goal
/execute-task "Add password reset via email with 24-hour expiration"

# Vague: Unclear requirements
/execute-task "Fix authentication"

2. One Task at a Time

Focus on single, complete features:

/execute-task "Add user registration"
/review
/execute-task "Add email verification"

3. Leverage Context

The command uses:

• Existing patterns
• Available libraries
• Current architecture
• Team conventions

Output

Code Changes

• New files created
• Existing files updated
• Tests added
• Documentation updated

Status Updates

📋 Analyzing task requirements...
🔍 Discovering existing patterns...
💡 Found authentication utilities in src/lib/auth
🛠️ Implementing user registration...
✅ Created src/features/auth/register.ts
✅ Added tests in tests/auth/register.test.ts
📝 Updated API documentation

Prompt Adaptation

This prompt dynamically adapts based on:

Context Discovery

• Code Patterns: Analyzes existing implementation patterns
• Architecture: Understands project structure and conventions
• Dependencies: Identifies available libraries and utilities
• Style Guide: Matches your coding style and formatting

Intelligence Patterns

• Discovers relevant existing code before implementing
• Adapts to your error handling patterns
• Follows your testing conventions
• Maintains consistency with surrounding code
• Learns from previous implementations

Execution Intelligence

• Breaks complex tasks into logical steps
• Implements incrementally with validation
• Adds appropriate error handling
• Creates tests that match your patterns

Memory Integration

This prompt actively uses and updates distributed memory:

Reads From

• CLAUDE.md - Project conventions and patterns
• src/*/CLAUDE.md - Feature-specific patterns
• .orchestre/patterns/*.md - Established patterns
• docs/architecture/CLAUDE.md - Architectural decisions

Updates

• src/[feature]/CLAUDE.md - Documents new implementations
• .orchestre/tasks/completed.md - Task history
• .orchestre/patterns/[pattern].md - New patterns discovered
• CLAUDE.md - Updates with significant changes

Memory Evolution

• Each task adds to pattern knowledge
• Successful approaches become templates
• Error solutions documented for reuse
• Performance optimizations captured

Integration

With Planning

/orchestrate requirements.md
# Generates phases and tasks
/execute-task "Phase 1: Set up authentication"

With Review

/execute-task "Implement shopping cart"
/review  # Verify implementation
/execute-task "Address review feedback"

Error Handling

Issue	Solution
Task unclear	Provide more details
Pattern not found	Specify approach
Tests fail	Review and fix
Integration issues	Check dependencies

Direct Invocation

This is a dynamic prompt that Claude executes directly:

# Simply type the command
/execute-task "Add user authentication"

# Claude will:
# 1. Discover existing auth patterns
# 2. Analyze project structure
# 3. Implement following your conventions
# 4. Add appropriate tests
# 5. Update relevant documentation

Related

• /orchestrate - Plan before executing
• /review - Review after executing
• /update-state - Track task completion