| name | artifact-pipeline |
| description | Use when transforming one artifact into another, such as transcript to brief, brief to article, document to landing page, spreadsheet to dashboard, script to diagrams, images to slides, or research notes to presentation. |
Artifact Pipeline
Use this for multi-step knowledge work where artifacts compound.
Pipeline Flow
- Identify the source artifact and target artifact.
- Extract the structure, audience, and useful content.
- Preserve source truth; do not invent missing facts.
- Choose the right output format and destination.
- Generate the target artifact in a project output folder.
- Verify the artifact opens/renders.
- Offer the next natural transformation only if it is useful.
Common Pipelines
- Transcript -> summary -> script -> slides -> social posts.
- Research notes -> content brief -> blog post -> LinkedIn/email.
- Doc -> landing page -> browser-tested app.
- Spreadsheet -> charts -> dashboard -> executive memo.
- Product images -> presentation -> Canva/social variants.
- Meeting notes -> tasks -> project plan -> automation.
Output Rules
- Name every output clearly.
- Keep source references attached where possible.
- For documents, sheets, and decks, verify the file opens or renders.
- For web/app outputs, run browser verification.
- For image-heavy outputs, show or reference the generated images.
Quality Gates
- Factual claims must trace back to the source artifact or a cited source.
- Format should match the target medium, not preserve source clutter.
- Do not bury the final artifact path.
- If the source is copyrighted, summarize and transform rather than reproduce large passages.
Source Notes
Distilled from the Codex capabilities transcript: Codex can chain local docs, landing pages, diagrams, images, presentations, browser checks, and plugin outputs.
