generatelisted

## Intent Produce a new artifact that satisfies specified constraints and serves a defined purpose. Generation is creative synthesis bounded by requirements, not mere retrieval or transformation. **Success criteria:** - Artifact satisfies all stated constraints - Rationale explains design decisions - Quality signals demonstrate fitness for purpose - Safety considerations documented **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `artifact_type` | Yes | string | Type of output: text, code, plan, config, schema, etc. | | `constraints` | Yes | object\|array | Requirements the artifact must satisfy | | `context` | No | string\|object | Background information, examples, or references | | `format` | No | string | Output format: markdown, json, yaml, typescript, etc. | | `alternatives_requested` | No | boolean | Whether to provide alternative designs | ## Procedure 1) **Clarify artifact requirements**: Ensure constraints are understood - Must-have: absolute requirements (format, structure, compatibility) - Should-have: preferences (style, conventions, optimization) - Must-not-have: exclusions (patterns to avoid, security constraints) 2) **Gather context**: Collect relevant reference material - Read existing code/docs for style consistency - Identify patterns to follow or avoid - Understand integration points and dependencies 3) **Design approach**