production

Generates final deliverables from structured inputs with no preamble, filler, or meta-commentary.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill production-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: production
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/workflows/production
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill production-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a decision is already made and the spec is clear, generic AI responses still add preamble, hedging, filler phrases, and meta-commentary that dilute the final artifact. This Skill enforces a strict production mode where the output is the deliverable itself and nothing else. ## Core Features & Use Cases - Structured input gathering: Collects required slots (deliverable, objective, audience, constraints, voice/format, evidence base, exclusions) before producing anything, eliminating filler caused by missing context. - Failure-condition self-check: Deletes exploratory language, unsourced quantifiers, soft-skill boilerplate, and format violations before emitting output. - Goal-loop for code deliverables: Writes a .goal-active sentinel with objective, stop condition, and budget ceilings when the deliverable is a code/build artifact. - Use Case: Ask for a 350-word cover letter with specific constraints and exclusions, and receive only the letter text — no "Here is your letter" wrapper, no sign-off, no commentary. ## Quick Start Invoke /production and provide the deliverable, objective, audience, constraints, and evidence base to receive the final artifact with no extra text.

Frequently Asked Questions about production

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get AI output with no preamble or filler text?▼

Invoke /production with the required input slots: deliverable, objective, audience, constraints, voice, evidence base, and exclusions. The skill emits only the artifact itself, deleting preamble, wrappers, sign-offs, and meta-commentary before output.

What inputs does production mode require before generating a deliverable?▼

It requires seven slots: deliverable, objective, audience, measurable constraints, voice or format reference, evidence base, and exclusions. Missing slots are the primary cause of filler output, so the skill asks for them before producing anything.

How should I handle a vague 'make it better' request on a deliverable?▼

Do not respond directly to 'make it better' since it causes regressions or filler. Instead, run the output through /evaluation against the personal-quality rubric, identify the three lowest-scoring dimensions, and re-enter /production with those named in exclusions.

When does production mode activate the goal-loop for code deliverables?▼

The goal-loop engages only when the deliverable is a code or build artifact such as a module, feature, or multi-file change. It writes a .goal-active sentinel with objective, stop condition, and budget ceilings; prose deliverables like emails or memos never trigger it.

What are the limitations of production mode for exploratory work?▼

Production mode is wrong for exploratory work because it deletes exploratory language and assumes the decision is already made. Use it only when the spec is clear; brainstorming or option-comparison tasks belong in a different mode.