# Auto-Generated Specification Template

**Generated From:** [source type - patterns/logs/existing_specs/all]
**Focus:** [novel/variant/evolution/hybrid]
**Created:** [timestamp]
**Auto-Generated:** Yes
**Meta-Patterns Applied:** [list of patterns discovered and used]

---

**Note:** This is a template file. When `/generate-spec` command runs, it will create new specification files based on this template structure but with content derived from analyzed patterns.

---

## Overview

[Abstract description of what to generate - focuses on structure and patterns, not specific examples]

## Discovered Patterns

This spec was auto-generated by analyzing:
- [Source 1 and what was learned]
- [Source 2 and what was learned]
- [Source 3 and what was learned]

### Pattern Discovery Insights

**Structural Patterns Found:**
- [Pattern 1]: [description and frequency]
- [Pattern 2]: [description and frequency]
- [Pattern 3]: [description and frequency]

**Meta-Level Insights:**
- [Insight 1 about what makes generations successful]
- [Insight 2 about structural effectiveness]
- [Insight 3 about evolution potential]

## Structural Framework

[High-level architecture and organization based on successful patterns]

```
[Abstract structure template]
```

## Generation Patterns

### Pattern 1: [Auto-Discovered Pattern Name]

**Abstract Structure:**
```
[Template derived from pattern analysis]
```

**Reasoning Flow:**
1. [Step 1 - generalized from successful iterations]
2. [Step 2 - pattern that worked well]
3. [Step 3 - common successful approach]

**Quality Criteria:**
- [Measurable criterion 1]
- [Measurable criterion 2]
- [Measurable criterion 3]

**Why This Pattern Works:**
[Meta-analysis of why this pattern emerged as successful]

### Pattern 2: [Another Auto-Discovered Pattern]

**Abstract Structure:**
```
[Template derived from pattern analysis]
```

**Reasoning Flow:**
1. [Generalized successful approach]
2. [Common effective technique]
3. [Validated pattern step]

**Quality Criteria:**
- [Measurable criterion]
- [Measurable criterion]

**Why This Pattern Works:**
[Analysis of pattern effectiveness]

## Quality Dimensions

[Measurable criteria derived from successful iterations]

### 1. [Dimension 1 Name] (0-10)
- [What this measures]
- [How to evaluate]
- [Why it matters]

**Target:** ≥ [threshold from historical data]

### 2. [Dimension 2 Name] (0-10)
- [What this measures]
- [How to evaluate]
- [Why it matters]

**Target:** ≥ [threshold from historical data]

### 3. Meta-Awareness (0-10)
- Self-referential understanding demonstrated
- Reflection on generation process included
- Evolution potential identified

**Target:** ≥ 7.0

### 4. Generalizability (0-10)
- Pattern applicability across contexts
- Minimal example-dependency
- Principle-driven design

**Target:** ≥ 7.5

## Creative Constraints

[Constraints that enabled creativity in source generations]

**Must include:**
- [Constraint 1 - derived from successful patterns]
- [Constraint 2 - enables uniqueness while maintaining quality]
- [Constraint 3 - promotes meta-awareness]

**Should apply:**
- [Principle 1 - structural guideline]
- [Principle 2 - abstract framework]
- [Principle 3 - meta-level capability]

**Cannot:**
- [Anti-pattern 1 - what to avoid]
- [Anti-pattern 2 - common failure mode]
- [Anti-pattern 3 - quality inhibitor]

## Naming Convention

[Pattern-based naming derived from analysis]

```
[prefix]_[domain]_[pattern]_[iteration].[extension]
```

**Examples:**
- [Example 1 following the pattern]
- [Example 2 showing variation]
- [Example 3 demonstrating evolution]

## File Structure

[Expected organization based on successful iterations]

```
[Structure template with meta-level annotations]
```

### Required Sections

1. **Header Meta-Information**
   - Structural pattern identification
   - Complexity self-assessment
   - Quality metrics

2. **Core Implementation**
   - [What should be included]
   - [How it should be organized]

3. **Meta-Level Annotations**
   - Design rationale
   - Trade-off acknowledgment
   - Improvement suggestions
   - Evolution path

4. **Self-Assessment**
   - Quality scores
   - Pattern effectiveness
   - Generalizability notes

## Success Criteria

A successful generation demonstrates:

1. **Pattern Adherence** - Follows discovered structural patterns
2. **Meta-Awareness** - Reflects on own design and process
3. **Quality Metrics** - Meets or exceeds target thresholds
4. **Generalizability** - Patterns are transferable and abstract
5. **Evolution Potential** - Clear paths for improvement identified
6. **Principle-Driven** - Based on frameworks, not examples
7. **Novel Synthesis** - Combines patterns in unique ways

## Meta-Instructions for Generators

When generating content for this auto-generated spec:

1. **Understand Pattern Origins**
   - This spec was derived from [X] successful iterations
   - Patterns represent what worked best
   - Trust the structural frameworks provided

2. **Apply Structure Over Content**
   - Focus on HOW to generate, not WHAT
   - Use abstract templates as guides
   - Minimize example-dependency

3. **Maintain Meta-Awareness**
   - Reflect on your generation process
   - Note what patterns you're applying
   - Identify improvement opportunities
   - Document evolution potential

4. **Validate Against Criteria**
   - Self-assess against quality dimensions
   - Ensure all required elements present
   - Check generalizability of approach
   - Confirm meta-level annotations included

5. **Enable Future Evolution**
   - Your output will be analyzed for new patterns
   - May influence next spec generation
   - Contribute to pattern library evolution
   - Help system improve itself

## Evolution Hooks

This auto-generated spec can evolve further:

**Complexity Progression:**
- Current level: [assessed from sources]
- Next level: [potential enhancement]
- Long-term: [advanced evolution path]

**Domain Variations:**
- Current domain: [primary focus area]
- Related domains: [transfer opportunities]
- Cross-domain: [hybrid possibilities]

**Pattern Extensions:**
- Base patterns: [what's included now]
- Combination potential: [pattern mixing opportunities]
- Meta-patterns: [recursive pattern applications]

**Meta-Level Enhancements:**
- Current meta-capability: [what's present]
- Next enhancement: [what to add]
- Ultimate capability: [meta-meta-improvement potential]

## Generation Lineage

**Parent Specs:** [which specs influenced this]
**Pattern Sources:** [where patterns came from]
**Success Metrics:** [what defined success in sources]
**Innovation Points:** [novel combinations or insights]

## Validation and Testing

When this spec is first used:

1. Generate small batch (3-5 iterations)
2. Measure quality against target dimensions
3. Validate pattern effectiveness
4. Refine spec if needed based on results
5. Document actual vs. expected outcomes

**Auto-Refinement Triggers:**
- Quality consistently below targets
- Patterns not producing expected results
- New patterns emerge from iterations
- Better abstractions discovered

## Meta-Note on Auto-Generation

This specification was created by the `/generate-spec` command using meta-prompting principles:

- **Structure-Oriented:** Focused on patterns and frameworks
- **Data-Driven:** Based on analysis of actual successful iterations
- **Generalizable:** Designed to work across similar contexts
- **Self-Improving:** Can evolve as new patterns emerge
- **Meta-Aware:** Understands it's auto-generated and can be regenerated

**Regeneration Frequency:**
- After 20+ new iterations in source domain
- When quality metrics shift significantly
- When new patterns are discovered
- When requested via `/generate-spec`

---

*This template demonstrates how auto-generated specs should be structured. When `/generate-spec` runs, it will fill in all bracketed sections with actual analyzed data and discovered patterns, creating a fully functional specification ready for use with `/infinite-meta`.*

**Version:** 1.0.0
**Last Regenerated:** [timestamp when actually generated]
**Pattern Count:** [number of patterns incorporated]
**Source Iterations Analyzed:** [count of iterations studied]
