neural-nexus-claude-project/templates/stage-transition-prompt.md

# Stage Transition Prompt Template

Use this prompt when ready to move between development stages:

```
Neural Nexus stage transition from [CURRENT STAGE] to [NEXT STAGE]:

## 🎯 TRANSITION READINESS ASSESSMENT
**Readiness Score:** [X/10]

**Criteria Met for [NEXT STAGE]:**
- ✅ [Completed requirement]
- ✅ [Completed requirement]

**Criteria Still Missing:**
- ❌ [Missing requirement] - [Plan to complete]
- ❌ [Missing requirement] - [Plan to complete]

## 📊 COMPREHENSIVE KNOWLEDGE CONSOLIDATION

### 🎉 What Worked Exceptionally Well
**Technical Successes:**
- [Successful patterns, tools, or approaches to continue]

**Process Successes:**
- [Workflow or communication patterns that helped]

**Unexpected Wins:**
- [Pleasant surprises or discoveries]

### 🚫 What Didn't Work (Avoid in Next Stage)
**Technical Failures:**
- [Failed approaches, problematic patterns, or poor tool choices]

**Process Issues:**
- [Workflow problems or communication breakdowns]

**Time Wasters:**
- [Activities that didn't provide value]

### 🔍 Unexpected Discoveries & Key Learnings
**Technical Insights:**
- [Surprising technical discoveries]
- [Non-obvious implementation details]
- [Performance or security learnings]

**Business/User Insights:**
- [User behavior discoveries]
- [Market or business model learnings]

**Process Insights:**
- [Development workflow improvements discovered]

### 🔧 Technical Debt & Known Issues
**Technical Debt to Carry Forward:**
- [Debt item] - [Priority: High/Medium/Low] - [Estimated effort to fix]

**Known Issues/Bugs:**
- [Issue] - [Impact] - [Workaround if any]

**Performance Bottlenecks:**
- [Bottleneck] - [Impact] - [Potential solutions]

## 🚀 NEW STAGE PREPARATION

### 📋 Recommended Project Configuration
**New Project Name:** [ProjectName] - [NewStage]

**Updated Project Description:**
[Complete rewrite of project description using new stage template]

**Revised Project Instructions:**
[Updated custom instructions appropriate for new stage]

### 📚 Knowledge Base Reorganization Plan
**Files to Archive:**
- [File] - [Reason for archiving]

**New Documentation Needed:**
- [Doc type] - [Purpose] - [Priority]

**Structural Changes:**
- [Change] - [Rationale]

### 🎯 Success Metrics for [NEXT STAGE]
**Primary Success Metrics:**
- [Metric 1]: [Target] by [Date]
- [Metric 2]: [Target] by [Date]

**Secondary Metrics:**
- [Metric]: [Target] by [Date]

## ⚠️ RISK ANALYSIS FOR NEXT STAGE

### 🔧 Technical Risks
- **Risk:** [Description]
  **Likelihood:** [High/Medium/Low]
  **Impact:** [High/Medium/Low]
  **Mitigation:** [Strategy]

### 📋 Process Risks
- **Risk:** [Description]
  **Likelihood:** [High/Medium/Low]
  **Impact:** [High/Medium/Low]
  **Mitigation:** [Strategy]

### 💼 Business Risks
- **Risk:** [Description]
  **Likelihood:** [High/Medium/Low]
  **Impact:** [High/Medium/Low]
  **Mitigation:** [Strategy]

## 📝 ACTION ITEMS FOR TRANSITION
1. [Action] - [Owner] - [Due Date] - [Priority]
2. [Action] - [Owner] - [Due Date] - [Priority]

Provide specific, actionable recommendations for a smooth transition.
```

## Stage-Specific Guidance

### Exploration → Prototype
**Key Questions:**
- Have we validated our core concept with working examples?
- Are our technology choices proven and documented?
- Do we have a clear scope for the prototype?
- Have we identified and mitigated major technical risks?

### Prototype → Development
**Key Questions:**
- Does our core functionality work as expected?
- Is our architecture scalable and maintainable?
- Have we validated user value proposition?
- Are performance targets achievable?

### Development → Production
**Key Questions:**
- Are all planned features complete and tested?
- Is our deployment process reliable and documented?
- Do we have monitoring and error handling in place?
- Is our documentation comprehensive and current?

## Transition Best Practices

### Before Initiating Transition
1. **Complete Current Stage Goals**: Don't rush to next stage with incomplete work
2. **Document Everything**: Ensure all decisions and learnings are captured
3. **Test Thoroughly**: Validate that current stage success criteria are met
4. **Plan Next Stage**: Have clear goals and priorities for the new stage

### During Transition
1. **Archive Appropriately**: Save current stage work without cluttering new stage
2. **Update All Documentation**: Ensure consistency across all project files
3. **Communicate Changes**: Update project descriptions and instructions
4. **Establish New Metrics**: Define success criteria for the new stage

### After Transition
1. **Validate New Setup**: Ensure Claude Project is properly configured
2. **Test Workflow**: Confirm new stage processes work smoothly
3. **Monitor Early Progress**: Watch for any context or workflow issues
4. **Adjust as Needed**: Fine-tune processes based on early new stage experience

Remember: Stage transitions are major milestones that deserve proper attention and documentation. Don't rush them!