3.4 KiB

Raw Blame History

Create Tech-Spec - Spec Engineering for Game Development

Communicate in {communication_language}, tailored to {user_skill_level} Generate documents in {document_output_language} Conversational spec engineering - ask questions, investigate code, produce complete spec Spec must contain ALL context a fresh dev agent needs to implement it Focus on game-specific considerations: performance, feel, engine patterns

Load and execute {advanced_elicitation}, then return to current step Load and execute {party_mode_workflow}, then return to current step Load and execute {quick_dev_workflow} with the tech-spec file

Greet {user_name} and ask them to describe what they want to build or change in their game.

Ask game-specific clarifying questions:

What's the feature/mechanic?
How does it affect gameplay feel?
Performance requirements? (60fps critical path?)
Which game systems does it touch?
Existing code to integrate with?

Check for existing context in {output_folder} and {implementation_artifacts}

[a] Advanced Elicitation [c] Continue [p] Party Mode

If brownfield: identify game engine (Unity/Unreal/Godot/custom)

Get file paths, read code, identify:

Engine patterns and conventions
Existing game systems to integrate with
Performance-critical code paths
Test patterns if any

Document: engine version, code patterns, files to modify, system dependencies

[a] Advanced Elicitation [c] Continue [p] Party Mode

Create tech-spec using this game-focused structure:

# Tech-Spec: {title}

**Created:** {date}
**Status:** Ready for Development
**Engine:** {engine_name} {version}

## Overview

### Feature/Mechanic Description

### Gameplay Impact

### Scope (In/Out)

## Context for Development

### Engine Patterns

### Existing Systems Integration

### Files to Reference

### Technical Decisions

## Implementation Plan

### Tasks

- [ ] Task 1: Description
- [ ] Task 2: Description

### Performance Considerations

- Frame budget impact
- Memory considerations
- Critical path notes

### Acceptance Criteria

- [ ] AC 1: Given/When/Then (include feel/responsiveness criteria)
- [ ] AC 2: ...

## Additional Context

### Dependencies

### Testing Strategy

### Notes

Save to {implementation_artifacts}/tech-spec-{slug}.md

Present spec to {user_name}, ask if it captures intent, make changes as needed

Tech-Spec Complete! 🎮

Saved to: {implementation_artifacts}/tech-spec-{slug}.md

[a] Advanced Elicitation - refine further [b] Begin Development (not recommended - fresh context better) [d] Done - exit [p] Party Mode - get feedback

Recommended: Run quick-dev in fresh context with this spec.

Choice (a/b/d/p):

3.4 KiB Raw Blame History

Create Tech-Spec - Spec Engineering for Game Development

3.4 KiB

Raw Blame History