Generate an art production pipeline specification
Generates comprehensive art production pipeline specifications covering workflows, naming conventions, automation, and quality assurance.
/plugin marketplace add sponticelli/gamedev-claude-plugins/plugin install technical-art@gamedev-claude-pluginsCreate a comprehensive art pipeline specification document.
Before generating the pipeline spec, understand the project:
Use this context to design appropriate pipeline.
# Art Pipeline Specification: [Project Name]
## Overview
**Asset types covered:** [What this pipeline handles]
**DCC tools:** [Software used]
**Target engine:** [Destination]
**Team size:** [Number of artists]
## Pipeline Diagram
[DCC] → [Export] → [Process] → [Import] → [Engine] ↓ ↓ ↓ [Validate] [Optimize] [Verify]
## Directory Structure
### Source (Art Repo)
/Art ├─ /Characters ├─ /Environment ├─ /Props ├─ /VFX └─ /UI
### Intermediate
[Where exports go before engine import]
### Engine Assets
[Final asset locations in engine project]
## Naming Conventions
| Asset Type | Pattern | Example |
|------------|---------|---------|
| [Type] | [Pattern] | [Example] |
## Per-Asset Workflows
### [Asset Type]
**Source format:** [.blend, .psd, etc.]
**Export format:** [.fbx, .png, etc.]
**Engine format:** [prefab, asset, etc.]
#### Workflow Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]
#### Validation Rules
| Rule | Check | Error Handling |
|------|-------|----------------|
| [Rule] | [What's checked] | [What happens on fail] |
[Repeat for each asset type]
## Automation
### Export Scripts
| Script | Purpose | Trigger |
|--------|---------|---------|
| [Name] | [What it does] | [When it runs] |
### Import Automation
| Processor | Asset Types | Actions |
|-----------|-------------|---------|
| [Name] | [What it handles] | [What it does] |
### CI/CD Integration
[How pipeline integrates with builds]
## Quality Assurance
### Automated Checks
| Check | When | Pass Criteria |
|-------|------|---------------|
| [Check] | [Export/Import/Build] | [Requirements] |
### Manual Review
[What requires human review]
## Troubleshooting
| Issue | Cause | Solution |
|-------|-------|----------|
| [Problem] | [Why] | [Fix] |
## Maintenance
### Documentation
[Where docs are kept, how updated]
### Training
[How artists learn the pipeline]
### Feedback
[How issues are reported and addressed]
Generate based on the user's project and pipeline needs.