9.5 KiB

Raw Blame History

Technical Research Step 2: Technology Stack Analysis

MANDATORY EXECUTION RULES (READ FIRST):

🛑 NEVER generate content without web search verification
📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
✅ ALWAYS use {{current_year}} web searches for current technology data
📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator
💬 FOCUS on languages, frameworks, tools, and platforms
🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT

EXECUTION PROTOCOLS:

🎯 Show web search analysis before presenting findings
⚠️ Present [C] continue option after technology stack content generation
📝 WRITE TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY
💾 ONLY proceed when user chooses C (Continue)
📖 Update frontmatter stepsCompleted: [1, 2] before loading next step
🚫 FORBIDDEN to load next step until C is selected

CONTEXT BOUNDARIES:

Current document and frontmatter from step-01 are available
Research topic = "{{research_topic}}" - established from initial discussion
Research goals = "{{research_goals}}" - established from initial discussion
Focus on languages, frameworks, tools, and platforms
Web search capabilities with source verification are enabled

YOUR TASK:

Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms using current {{current_year}} web data with rigorous source verification.

TECHNOLOGY STACK ANALYSIS SEQUENCE:

1. Begin Technology Stack Analysis

UTILIZE SUBPROCESSES AND SUBAGENTS: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.

Start with technology stack research approach: "Now I'll conduct technology stack analysis for {{research_topic}} using current {{current_year}} web data to understand the technology landscape.

Technology Stack Focus:

Programming languages and their evolution
Development frameworks and libraries
Database and storage technologies
Development tools and platforms
Cloud infrastructure and deployment platforms

Let me search for current technology stack insights."

2. Parallel Technology Stack Research Execution

Execute multiple web searches simultaneously:

WebSearch: "{{research_topic}} programming languages frameworks {{current_year}}" WebSearch: "{{research_topic}} development tools platforms {{current_year}}" WebSearch: "{{research_topic}} database storage technologies {{current_year}}" WebSearch: "{{research_topic}} cloud infrastructure platforms {{current_year}}"

Analysis approach:

Look for recent technology trend reports and developer surveys
Search for technology documentation and best practices
Research open-source projects and their technology choices
Analyze technology adoption patterns and migration trends
Study platform and tool evolution in the domain

3. Analyze and Aggregate Results

Collect and analyze findings from all parallel searches:

"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:

Research Coverage:

Programming languages and frameworks analysis
Development tools and platforms evaluation
Database and storage technologies assessment
Cloud infrastructure and deployment platform analysis

Cross-Technology Analysis: [Identify patterns connecting language choices, frameworks, and platform decisions]

Quality Assessment: [Overall confidence levels and research gaps identified]"

4. Generate Technology Stack Content

WRITE IMMEDIATELY TO DOCUMENT

Prepare technology stack analysis with web search citations:

Content Structure:

When saving to document, append these Level 2 and Level 3 sections:

## Technology Stack Analysis

### Programming Languages

[Programming languages analysis with source citations]
_Popular Languages: [Most widely used languages for {{research_topic}}]_
_Emerging Languages: [Growing languages gaining adoption]_
_Language Evolution: [How language preferences are changing]_
_Performance Characteristics: [Language performance and suitability]_
_Source: [URL with {{current_year}} language data]_

### Development Frameworks and Libraries

[Frameworks analysis with source citations]
_Major Frameworks: [Dominant frameworks and their use cases]_
_Micro-frameworks: [Lightweight options and specialized libraries]_
_Evolution Trends: [How frameworks are evolving and changing]_
_Ecosystem Maturity: [Library availability and community support]_
_Source: [URL with {{current_year}} framework data]_

### Database and Storage Technologies

[Database analysis with source citations]
_Relational Databases: [Traditional SQL databases and their evolution]_
_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_
_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_
_Data Warehousing: [Analytics and big data storage solutions]_
_Source: [URL with {{current_year}} database data]_

### Development Tools and Platforms

[Tools and platforms analysis with source citations]
_IDE and Editors: [Development environments and their evolution]_
_Version Control: [Git and related development tools]_
_Build Systems: [Compilation, packaging, and automation tools]_
_Testing Frameworks: [Unit testing, integration testing, and QA tools]_
_Source: [URL with {{current_year}} tools data]_

### Cloud Infrastructure and Deployment

[Cloud platforms analysis with source citations]
_Major Cloud Providers: [AWS, Azure, GCP and their services]_
_Container Technologies: [Docker, Kubernetes, and orchestration]_
_Serverless Platforms: [FaaS and event-driven computing]_
_CDN and Edge Computing: [Content delivery and distributed computing]_
_Source: [URL with {{current_year}} cloud data]_

### Technology Adoption Trends

[Adoption trends analysis with source citations]
_Migration Patterns: [How technology choices are evolving]_
_Emerging Technologies: [New technologies gaining traction]_
_Legacy Technology: [Older technologies being phased out]_
_Community Trends: [Developer preferences and open-source adoption]_
_Source: [URL with {{current_year}} adoption data]_

5. Present Analysis and Continue Option

Show analysis and present continue option:

"I've completed technology stack analysis using current {{current_year}} data to understand the technology landscape for {{research_topic}}.

Key Technology Stack Findings:

Programming languages and frameworks thoroughly analyzed
Database and storage technologies evaluated
Development tools and platforms documented
Cloud infrastructure and deployment options mapped
Technology adoption trends identified

Ready to proceed to integration patterns analysis? [C] Continue - Save this to document and proceed to integration patterns

6. Handle Continue Selection

If 'C' (Continue):

CONTENT ALREADY WRITTEN TO DOCUMENT
Update frontmatter: stepsCompleted: [1, 2]
Load: ./step-03-integration-patterns.md

APPEND TO DOCUMENT:

Content is already written to document when generated in step 4. No additional append needed.

SUCCESS METRICS:

✅ Programming languages and frameworks thoroughly analyzed ✅ Database and storage technologies evaluated ✅ Development tools and platforms documented ✅ Cloud infrastructure and deployment options mapped ✅ Technology adoption trends identified ✅ Content written immediately to document ✅ [C] continue option presented and handled correctly ✅ Proper routing to next step (integration patterns) ✅ Research goals alignment maintained

FAILURE MODES:

❌ Not using {{current_year}} in technology web searches ❌ Missing critical programming languages or frameworks ❌ Incomplete database and storage technology analysis ❌ Not identifying development tools and platforms ❌ Not writing content immediately to document ❌ Not presenting [C] continue option after content generation ❌ Not routing to integration patterns step

❌ CRITICAL: Reading only partial step file - leads to incomplete understanding and poor decisions ❌ CRITICAL: Proceeding with 'C' without fully reading and understanding the next step file ❌ CRITICAL: Making decisions without complete understanding of step requirements and protocols

TECHNOLOGY STACK RESEARCH PROTOCOLS:

Research technology trend reports and developer surveys
Use technology documentation and best practices guides
Analyze open-source projects and their technology choices
Study technology adoption patterns and migration trends
Focus on current {{current_year}} technology data
Present conflicting information when sources disagree
Apply confidence levels appropriately

TECHNOLOGY STACK ANALYSIS STANDARDS:

Always cite URLs for web search results
Use authoritative technology research sources
Note data currency and potential limitations
Present multiple perspectives when sources conflict
Apply confidence levels to uncertain data
Focus on actionable technology insights

NEXT STEP:

After user selects 'C', load ./step-03-integration-patterns.md to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.

Remember: Always write research content to document immediately and emphasize current {{current_year}} technology data with rigorous source verification!

9.5 KiB Raw Blame History