/pine-manager

name: pine-manager
description: Orchestrates complex Pine Script projects by coordinating multiple development phases. Use for complete trading systems.
disable-model-invocation: true

Pine Script Manager

Responsible for orchestrating the entire Pine Script development workflow by coordinating specialized capabilities.

Project Scoping Process

When starting ANY new project, first gather requirements using: 1. Standard flow: `/docs/project-scoping-flow.md` and `/docs/scoping-questions.md` 2. Unknown patterns: `/docs/comprehensive-scoping-flow.md` 3. Edge cases: `/docs/edge-case-handler.md`

Adaptive Scoping Strategy

Step 1: Pattern Recognition

First, identify if the request matches known patterns:

• Standard indicators (RSI, MACD, Moving Averages, etc.)
• Common strategies (trend following, mean reversion, breakout)
• Typical visualizations (overlays, oscillators, tables)

Step 2: Discovery Mode (if pattern unknown)

If request doesn't match known patterns: 1. "Can you describe what you're trying to achieve?" 2. "What problem does this solve?" 3. "Have you seen something similar elsewhere?" 4. Identify category: Data/Calculation/Display/Trading/Integration/Custom

Step 3: Feasibility Assessment

Determine what's possible in Pine Script:

• ✅ **Fully Feasible**: Proceed normally
• ⚠️ **Partially Feasible**: Design workarounds, explain limitations
• ❌ **Not Feasible**: Suggest alternatives, hybrid approaches

Step 4: Adaptive Questioning

Based on feasibility and category:

• For standard requests: Ask minimal questions (5-10)
• For complex requests: Ask detailed questions (10-20)
• For edge cases: Deep discovery mode (as many as needed)

Key Principles

• **Always find a way** - Even if not perfect
• **Set clear expectations** - Explain limitations upfront
• **Think creatively** - Use workarounds when needed
• **Document everything** - Clear spec with limitations noted
• **Progressive enhancement** - Start simple, add complexity

When User Mentions Something Unusual

Examples: "machine learning", "options flow", "market profile", "pairs trading", "on-chain data"

1. Don't say it's impossible 2. Check `/docs/edge-case-handler.md` for workarounds 3. Explain what CAN be done 4. Offer creative alternatives 5. Set realistic expectations

Core Responsibilities

Project Analysis

• Understand user requirements holistically
• Identify project scope and complexity
• Determine which capabilities are needed
• Create comprehensive development plan
• **Rename blank.pine to appropriate project name immediately upon project definition**

Workflow Orchestration

• Delegate tasks to appropriate capabilities
• Ensure proper task sequencing
• Monitor progress across phases
• Handle inter-task dependencies

Quality Assurance

• Verify all requirements are met
• Ensure code consistency
• Check for completeness
• Validate final deliverables

Progress Management

• Track task completion
• Update todo lists
• Report status to user
• Handle issues and blockers

Capability Coordination Matrix

When to Use Each Capability

| User Request | Primary Capability | Supporting Capabilities | |-------------|-------------------|------------------------| | "Create indicator that..." | Visualizer → Developer | Debugger, Optimizer | | "Build strategy for..." | Visualizer → Developer → Backtester | Debugger, Optimizer | | "My script has errors..." | Debugger | Developer (if fixes needed) | | "Optimize my script..." | Optimizer | Backtester (for validation) | | "Test strategy performance..." | Backtester | Debugger (for insights) | | "Prepare for publishing..." | Publisher | Optimizer (for polish) | | "Complex multi-part project..." | Manager (orchestrates all) | All as needed |

Project Initialization

When Starting Any New Project:

1. **AUTOMATICALLY** rename `/projects/blank.pine` to an appropriate filename:

• Format: `descriptive-name.pine` (e.g., `rsi-divergence-indicator.pine`, `ma-crossover-strategy.pine`)
• Use lowercase with hyphens
• Include type suffix if helpful (e.g., `-indicator`, `-strategy`)

2. **IMMEDIATELY** create a new blank.pine for future projects

3. Update the renamed file's header with project details

4. Begin development workflow

Important: Blank.pine Management

• Always check if blank.pine exists before starting
• If it exists: rename it for current project, create new blank.pine
• If it doesn't exist: create project file directly, recreate blank.pine
• This ensures blank.pine is always available for the next project

Workflow Templates

1. New Indicator Development

1. RENAME: blank.pine → [indicator-name].pine
2. VISUALIZER: Break down indicator concept
3. DEVELOPER: Implement core calculations
4. DEBUGGER: Add debugging capabilities
5. OPTIMIZER: Enhance performance and UX
6. PUBLISHER: Prepare documentation (if needed)

2. New Strategy Development

1. RENAME: blank.pine → [strategy-name].pine
2. VISUALIZER: Define entry/exit logic
3. DEVELOPER: Implement strategy code
4. BACKTESTER: Add performance metrics
5. DEBUGGER: Add trade debugging
6. OPTIMIZER: Improve execution
7. PUBLISHER: Finalize for release

3. Script Debugging

1. DEBUGGER: Identify issues
2. DEVELOPER: Fix identified problems
3. DEBUGGER: Verify fixes
4. OPTIMIZER: Improve problematic areas

4. Performance Enhancement

1. OPTIMIZER: Analyze current performance
2. BACKTESTER: Measure baseline metrics
3. OPTIMIZER: Implement improvements
4. BACKTESTER: Validate improvements

Task Delegation Examples

Example 1: Complex Strategy Request

**User**: "I want a mean reversion strategy that uses Bollinger Bands and RSI, with proper risk management and backtesting"

**Scoping process**:

1. Script Type? → Strategy (already provided)
2. Trading Complexity? → Standard (single asset mean reversion)
3. Use TV Functions? → Yes (for backtesting)
4. Need Automation? → [Ask user]
5. Project Purpos