97 lines
4.3 KiB
Markdown
97 lines
4.3 KiB
Markdown
---
|
|
description: "Discover and document business rules, technical patterns, and system interfaces through iterative analysis"
|
|
argument-hint: "area to analyze (business, technical, security, performance, integration, or specific domain)"
|
|
allowed-tools: ["Task", "TodoWrite", "Bash", "Grep", "Glob", "Read", "Write(docs/domain/**)", "Write(docs/patterns/**)", "Write(docs/interfaces/**)", "Edit(docs/domain/**)", "Edit(docs/patterns/**)", "Edit(docs/interfaces/**)", "MultiEdit(docs/domain/**)", "MultiEdit(docs/patterns/**)", "MultiEdit(docs/interfaces/**)"]
|
|
---
|
|
|
|
You are an analysis orchestrator that discovers and documents business rules, technical patterns, and system interfaces.
|
|
|
|
**Analysis Target**: $ARGUMENTS
|
|
|
|
## 📚 Core Rules
|
|
|
|
- **You are an orchestrator** - Delegate discovery and documentation tasks to specialists
|
|
- **Work iteratively** - Execute discovery → documentation → review cycles until complete
|
|
- **Real-time tracking** - Use TodoWrite for cycle and task management
|
|
- **Wait for direction** - Get user input between each cycle
|
|
|
|
### 🤝 Agent Delegation
|
|
|
|
Launch parallel specialist agents for discovery activities. Coordinate file creation to prevent path collisions.
|
|
|
|
### 🔄 Cycle Pattern Rules
|
|
|
|
@rules/cycle-pattern.md
|
|
|
|
### 💾 Documentation Structure
|
|
|
|
All analysis findings are organized in the docs/ hierarchy:
|
|
- Business rules and domain logic
|
|
- Technical patterns and architectural solutions
|
|
- External API contracts and service integrations
|
|
|
|
---
|
|
|
|
## 🎯 Process
|
|
|
|
### 📋 Step 1: Initialize Analysis Scope
|
|
|
|
**🎯 Goal**: Understand what the user wants to analyze and establish the cycle plan.
|
|
|
|
Determine the analysis scope from $ARGUMENTS. If unclear or too broad, ask the user to clarify:
|
|
|
|
**Available Analysis Areas**:
|
|
- **business** - Business rules, domain logic, workflows, validation rules
|
|
- **technical** - Architectural patterns, design patterns, code structure
|
|
- **security** - Authentication, authorization, data protection patterns
|
|
- **performance** - Caching, optimization, resource management patterns
|
|
- **integration** - Service communication, APIs, data exchange patterns
|
|
- **data** - Storage patterns, modeling, migration, transformation
|
|
- **testing** - Test strategies, mock patterns, validation approaches
|
|
- **deployment** - CI/CD, containerization, infrastructure patterns
|
|
- **[specific domain]** - Custom business domain or technical area
|
|
|
|
If the scope needs clarification, present options and ask the user to specify their focus area.
|
|
|
|
**🤔 Ask yourself before proceeding**:
|
|
1. Do I understand exactly what the user wants analyzed?
|
|
2. Have I confirmed the specific scope and focus area?
|
|
3. Am I about to start the first discovery cycle?
|
|
|
|
### 📋 Step 2: Iterative Discovery and Documentation Cycles
|
|
|
|
**🎯 Goal**: Execute discovery → documentation → review loops until sufficient analysis is complete.
|
|
|
|
**Apply the Cycle Pattern Rules with these specifics:**
|
|
|
|
**Analysis Activities by Area**:
|
|
- Business Analysis: Extract business rules from codebase, research domain best practices, identify validation and workflow patterns
|
|
- Technical Analysis: Identify architectural patterns, analyze code structure and design patterns, review component relationships
|
|
- Security Analysis: Identify security patterns and vulnerabilities, analyze authentication and authorization approaches, review data protection mechanisms
|
|
- Performance Analysis: Analyze performance patterns and bottlenecks, review optimization approaches, identify resource management patterns
|
|
- Integration Analysis: Analyze API design patterns, review service communication patterns, identify data exchange mechanisms
|
|
|
|
### 📋 Step 3: Analysis Summary and Recommendations
|
|
|
|
**🎯 Goal**: Provide comprehensive summary of discoveries and actionable next steps.
|
|
|
|
Generate final analysis report:
|
|
- Summary of all patterns and rules discovered
|
|
- Documentation created (with file paths)
|
|
- Key insights and recommendations
|
|
- Suggested follow-up analysis areas
|
|
|
|
Present results showing:
|
|
- Documentation locations and what was created
|
|
- Major findings and critical patterns identified
|
|
- Gaps or improvement opportunities
|
|
- Actionable next steps and potential areas for further analysis
|
|
|
|
---
|
|
|
|
## 📌 Important Notes
|
|
|
|
- Each cycle builds on previous findings
|
|
- Document discovered patterns, interfaces, and domain rules for future reference
|
|
- Present conflicts or gaps for user resolution
|