code-ai-installer 1.5.6 → 2.1.0

package/domains/content/locales/en/.agents/workflows/quick-post.md

@@ -0,0 +1,230 @@
+# Workflow: /quick-post — Quick Post Pipeline
+
+## Description
+An accelerated pipeline for creating simple publications without a full strategic cycle. Minimum gates, maximum speed — with guaranteed brand compliance.
+
+## When to use
+- A simple post with **blast radius ≈ 0** (see checklist below).
+- No complex factual assertions.
+- The topic is clear, the audience is known.
+- A quick result is needed (deadline, news hook, trend).
+- Reaction to an event losing relevance quickly.
+
+## When NOT to use
+- Controversial, sensitive, or political topic → `/start-content`.
+- Contains complex factual assertions requiring research → `/start-content`.
+- Strategic elaboration is needed (new audience, new platform) → `/start-content`.
+- A drafted text exists, needs editing → `/edit-content`.
+- The post takes > 30 minutes of work → `/start-content`.
+
+## Workflow Input
+
+| Field | Required | Description |
+|------|:-----------:|----------|
+| Topic / idea | ✅ | What the post is about — specifically |
+| Platform | ✅ | Where we publish |
+| Brand guidelines | ✅ | From `$brand-guidelines` — ToV, stop-list. Brand compliance is impossible without them |
+| Goal | ⬚ | Engagement / awareness / traffic / opinion (if not specified — Conductor determines) |
+| Context | ⬚ | Trend, news hook, date — why precisely now |
+| Content calendar | ⬚ | If the post is from `$content-calendar` — unit ID |
+
+## Blast Radius Checklist
+
+The Conductor **must** complete this before choosing `/quick-post`:
+
+| # | Criterion | ✅ Quick OK | ❌ Not Quick |
+|---|----------|:----------:|:-----------:|
+| 1 | Topic is **not** controversial / sensitive / political | ✅ | → `/start-content` |
+| 2 | **No** factual assertions requiring verification | ✅ | If 1-2 simple facts — quick + `$fact-checking`. If many → `/start-content` |
+| 3 | Audience and platform are **known** (not new) | ✅ | → `/start-content` with Strategist |
+| 4 | Post is **not** promo / offer / advertisement | ✅ | Promo requires more thorough elaboration |
+| 5 | Blast radius on error is **minimal** | ✅ | If an error → scandal/fine → `/start-content` |
+| 6 | Estimated time ≤ 30 minutes | ✅ | → `/start-content` or `/edit-content` |
+
+**Result:** All ✅ → `/quick-post`. At least one ❌ → switch mode.
+
+## Types of quick-posts
+
+| Type | Description | Structure Template |
+|-----|----------|-----------------|
+| **Opinion / insight** | Brand's personal stance on a topic | Hook (provocation/question) → Opinion (2-3 sentences) → CTA (question for the audience) |
+| **Reaction to a trend** | Adapting a trend to the brand | Trend format + our angle + CTA |
+| **Reaction to a news hook** | Commentary on an event | Event (1 sentence) → Our stance → CTA |
+| **Quote / fact of the day** | Inspiring quote or interesting fact | Quote/fact → Context (why it matters) → CTA |
+| **Behind the scenes** | Behind the scenes of the brand | Describe the moment → Insight → CTA |
+| **Engagement** | Poll, question, challenge | Question / condition → Answer / participation options |
+| **Repost with commentary** | Sharing someone else's content with added value | Our commentary (hook) → Link/repost → CTA |
+
+> The Conductor determines the type at Gate 1 → Copywriter uses the corresponding template.
+
+## Pipeline
+
+```
+CONDUCTOR → COPYWRITER → REVIEWER → RELEASE CHECK (mini)
+   G1            G2          G3           G4
+```
+
+### Rule of Parallelism
+
+| Mode | When | How it works |
+|-------|-------|-------------|
+| **Sequential** (default) | Standard quick-post | Copywriter → Approved → Reviewer → Approved → Release |
+| **Fast** (with user's permission) | Extremely urgent, user explicitly requested | Copywriter → Reviewer **without a pause for Approved** between them. Approved only after Reviewer |
+
+> Fast mode = exception to Rule 1. Only if the user **explicitly** requested acceleration.
+
+## Gates and Deliverables
+
+### Gate 1: Conductor
+**Input:** User task
+**Actions:**
+1. Pass the **Blast Radius checklist** — confirm that the task is suitable for the Quick Pipeline.
+2. Determine the **type of quick-post** from the table.
+3. Determine the platform and key parameters (topic, ToV, CTA).
+4. Formulate the task for the Copywriter in **3-5 sentences**.
+5. Initialize the mini-board (`$board` — Quick Pipeline).
+**Mandatory skills:** `$board`
+**Deliverable:** Short brief: topic + platform + post type + ToV + CTA goal
+**Verification:** Blast Radius checklist passed, type determined
+**→ Wait for "Approved"**
+
+> **Auto-transition:** If the task is obvious (user provided topic + platform) and explicitly said "quickly" — Conductor can suggest an auto-transition. But the decision belongs to the user.
+
+### Gate 2: Copywriter
+**Input:** Short brief from Conductor
+**Actions:**
+1. Apply ToV (`$tone-of-voice`).
+2. Choose the structure template according to the **type of quick-post**.
+3. Write the post for the platform (`$social-media-formats`).
+4. Formulate the hook / headline (`$headline-formulas`).
+5. Add CTA (`$cta-optimization`).
+6. Check platform limits (characters, hashtags).
+7. If there are factual assertions → `$fact-checking` (mandatory).
+**Mandatory skills:** `$tone-of-voice`, `$social-media-formats`, `$cta-optimization`
+**Optional:** `$headline-formulas`, `$fact-checking` (if facts are in the text)
+**Deliverable:** Ready post text + hashtags
+**Verification:** Text is complete, matches platform, ToV, post type
+**→ Wait for "Approved" (or immediate handoff in fast mode)**
+
+### Gate 3: Reviewer
+**Input:** Text from Copywriter
+**Actions:**
+1. **Quick check** against `$content-review-checklist` — **Blockers and Critical only**:
+   - [ ] Topic matches the task
+   - [ ] CTA is present
+   - [ ] ToV matches the brand
+   - [ ] No prohibited words (stop-list)
+   - [ ] No factual errors (if facts exist)
+   - [ ] Platform limits followed
+2. Brand compliance (`$brand-compliance`) — **core parameters** (not the full checklist).
+3. Platform compliance (`$platform-compliance`) — **technical requirements**.
+**Mandatory skills:** `$brand-compliance`
+**Optional:** `$platform-compliance`
+**Deliverable:** APPROVED or **1-2 specific fixes** (not lists, not a detailed checklist)
+
+**If APPROVED:** → Gate 4 (Release Check)
+**If fixes:** → Reverse handoff → Copywriter → fix → repeat Gate 3
+
+**Verification:** No Blockers
+**→ Wait for "Approved"**
+
+### Gate 4: Release Check (mini)
+**Input:** APPROVED from Reviewer
+**Actions:**
+- Final reconciliation (30 seconds):
+  - [ ] Text = final version (not draft)
+  - [ ] Hashtags are in place
+  - [ ] Publication time is optimal (if matters)
+  - [ ] Brand compliance ✅
+- Update `$board` — all gates `[✓]`
+- Update `domains/content/CONTEXT.md` (brief entry)
+**Deliverable:** Post is ready for publication
+**→ Final "Approved" → Publish immediately**
+
+## Reverse Handoff — Return Protocol
+
+If Reviewer gives **fixes** (not APPROVED):
+
+```
+Reviewer (1-2 fixes)
+    │
+    └── Reverse $handoff → Copywriter
+        └── Copywriter makes fixes (< 5 min)
+            └── Forward $handoff → Reviewer (repeat G3)
+```
+
+**Rules for Quick Pipeline:**
+1. Reviewer gives **maximum 1-2 fixes** — no detailed checklist. Quick = fast.
+2. If fixes > 3 → task is **not quick** → suggest `/edit-content`.
+3. Maximum of **2 iterations** (Copywriter → Reviewer → Copywriter → Reviewer). If not APPROVED → escalate to user.
+4. Update `$board` at each return.
+
+## Execution Time
+
+| Stage | Target time | Maximum |
+|------|--------------|----------|
+| Gate 1: Conductor | 1-2 min | 5 min |
+| Gate 2: Copywriter | 3-8 min | 15 min |
+| Gate 3: Reviewer | 1-3 min | 5 min |
+| Gate 4: Release Check | 30 sec | 1 min |
+| **Total** | **5-15 min** | **30 min** |
+
+> If > 30 minutes → stop, suggest `/start-content` or `/edit-content`.
+
+## Mode Limitations
+
+- ❌ Do not conduct research (`$trend-research`, `$topic-research`, `$source-verification`).
+- ❌ Do not create a visual brief (text only). If visuals are needed → `/start-content` or `/edit-content`.
+- ❌ Do not revise strategy (audience, platform).
+- ❌ Do not launch `$moodboard`, `$image-prompt-engineering`.
+- ❌ Reviewer does not perform full `$content-review-checklist` — only Blockers.
+- ✅ If there are factual assertions in the text → `$fact-checking` is **mandatory** even in Quick.
+- ✅ `$brand-compliance` is **always** mandatory (Rule 7 from pipeline-rules).
+
+## Anti-patterns
+
+| Mistake | Why it's bad | How to do it right |
+|--------|-------------|---------------|
+| Quick for controversial topic | Scandal, negativity, reputational loss | Blast Radius checklist. Controversial → `/start-content` |
+| Quick for promo / offer | No elaboration of CTA, offer, funnel | Promo → `/start-content` or `/edit-content` |
+| Skip brand compliance | "It's quick" — but the brand is compromised | Brand compliance is ALWAYS mandatory. Rule 7 |
+| Facts without verification | "It's quick" — but the fact is wrong → loss of trust | Facts → `$fact-checking` even in Quick |
+| Quick dragged heavily > 30 min | It's not quick anymore — scope creep | Stop, switch mode |
+| Reviewer writes 10 remarks | It's not a quick review — the task is too complex | Maximum 1-2 fixes. If > 3 → `/edit-content` |
+| No hashtags / CTA | "Fast = can be without CTA" — no | CTA is mandatory. Hashtags per platform rules |
+| Quick without `$board` | Tracking loss | Mini-board is mandatory |
+
+## Output Template (Gate 1 — Conductor)
+
+```
+### Quick Post — Initialization
+
+**Topic:** [topic]
+**Platform:** [platform]
+**Type of quick-post:** [opinion / trend / news hook / quote / BTS / engagement / repost]
+**Goal:** [engagement / awareness / traffic / opinion]
+**Context:** [why now — trend, event, date]
+
+#### Blast Radius checklist
+- [✅] Topic is not controversial / political
+- [✅] No complex factual assertions
+- [✅] Audience and platform are known
+- [✅] Not a promo / offer
+- [✅] Blast radius on error is minimal
+- [✅] Estimated time ≤ 30 min
+
+**Mode:** [sequential / fast (if requested by user)]
+
+#### Brief for Copywriter (3-5 sentences)
+[Topic. Platform. Tone. CTA goal. Structure template by post type.]
+
+#### Mini-board
+| # | Gate | Status |
+|---|------|--------|
+| G1 | Conductor | [→] In progress |
+| G2 | Copywriter | [ ] Waiting |
+| G3 | Reviewer | [ ] Waiting |
+| G4 | Release Check | [ ] Waiting |
+
+→ Waiting for "Approved" to proceed to Copywriter
+```

package/domains/content/locales/en/.agents/workflows/start-content.md

@@ -0,0 +1,273 @@
+# Workflow: /start-content — Full Content Pipeline
+
+## Description
+Full pipeline for creating content from scratch. Maximum elaboration: strategy, research, copywriting, visual, review, release gate. Used for new publications, campaigns, and content requiring deep preparation.
+
+## When to use
+- New publication or campaign from scratch.
+- Content requires data research / factual basis.
+- Strategic elaboration is needed (audience, platform, goals).
+- No drafted text or concept exists.
+- Edits of existing content > 50% (switching from `/edit-content`).
+
+## When NOT to use
+- Ready text exists, needs edits ≤ 50% → `/edit-content`.
+- Simple post, blast radius ≈ 0 → `/quick-post`.
+- When in doubt — **use** `/start-content` (better safe than sorry).
+
+## Workflow Input
+
+| Field | Required | Description |
+|------|:-----------:|----------|
+| Task / topic | ✅ | What needs to be created — from user |
+| Brand guidelines | ✅ | From `$brand-guidelines`. Without them — request before start |
+| Business goals | ⬚ | Awareness / leads / sales / community |
+| Target platform | ⬚ | If known in advance. If not — Strategist will define |
+| Audience personas | ⬚ | If `$audience-analysis` already exists. If not — Strategist will create |
+| Budget | ⬚ | If there's a paid component |
+| Deadline | ⬚ | Influences prioritization and research depth |
+
+> If brand guidelines are not provided — Conductor requests them **before starting** the pipeline. Without them, brand compliance (Rule 7) is impossible.
+
+## Pipeline
+
+```
+CONDUCTOR → STRATEGIST → RESEARCHER → COPYWRITER → VISUAL CONCEPT → REVIEWER → RELEASE GATE
+   G1            G2            G3           G4            G5             G6          G7
+```
+
+### Parallelism
+
+| Gates | Parallel? | Condition |
+|-------|:------------:|---------|
+| G1→G2→G3 | ❌ Strictly sequential | Each depends on the previous one |
+| **G4 + G5** | ✅ Possible | If visual is created from brief (not from text). Conductor decides |
+| G4→G5 | Sequential by default | Visual Concept often depends on the final text |
+| G6 | ❌ Only after G4+G5 | Reviewer checks both text and visual |
+| G7 | ❌ Only after G6 APPROVED | Release Gate = final check |
+
+> The Conductor at Gate 1 determines whether G4+G5 will be parallel and informs the user.
+
+## Gates and Deliverables
+
+### Gate 1: Conductor
+**Input:** User task + workflow input
+**Actions:**
+1. Determine content type, platform (if known), scope.
+2. Check the presence of `$brand-guidelines`. If not → request.
+3. Determine if G4+G5 will be parallel.
+4. Initialize the board (`$board` — Full Pipeline).
+5. Formulate the task for Strategist.
+6. Execute `$handoff` (forward) → Strategist.
+**Mandatory skills:** `$board`, `$handoff`
+**Deliverable:** Handoff Envelope → Strategist (task + scope + limitations)
+**Verification:** `$gates` — task is specific, board is created, brand guidelines exist
+**→ Wait for "Approved"**
+
+### Gate 2: Strategist
+**Input:** `$handoff` from Conductor
+**Actions:**
+1. Audience analysis (`$audience-analysis`) — personas, pain points, triggers.
+2. Platform selection (`$platform-strategy`) — channels, formats, frequency.
+3. Competitor analysis (`$competitor-content-analysis`) — gaps, differentiation.
+4. Content plan (`$content-calendar`) — if a series / campaign is planned.
+5. ToV formation (`$tone-of-voice`) — if not defined earlier.
+6. Brief formation (`$content-brief`) — full brief for Researcher + Copywriter.
+7. Execute `$handoff` (forward) → Researcher.
+**Mandatory skills:** `$audience-analysis`, `$platform-strategy`, `$content-brief`
+**Optional:** `$competitor-content-analysis`, `$content-calendar`, `$tone-of-voice`
+**Deliverable:** Content brief + content plan (if series)
+**Verification:** `$gates` — brief contains: topic, persona, platform, format, ToV, CTA, volume
+**→ Wait for "Approved"**
+
+### Gate 3: Researcher
+**Input:** `$handoff` from Strategist (brief)
+**Actions:**
+1. Trend analysis (`$trend-research`) — what is relevant on the topic.
+2. Topic research (`$topic-research`) — facts, statistics, experts.
+3. Source verification (`$source-verification`) — all sources checked.
+4. Narrative formation (`$data-storytelling`) — if data-driven content.
+5. Execute `$handoff` (forward) → Copywriter.
+**Mandatory skills:** `$topic-research`, `$source-verification`
+**Optional:** `$trend-research`, `$data-storytelling`
+**Deliverable:** Data package — facts (verified), statistics, quotes, narrative, structure for copywriter
+**Verification:** `$gates` — all facts verified, sources ≥ minimum rating, narrative formed
+**→ Wait for "Approved"**
+
+### Gate 4: Copywriter
+**Input:** `$handoff` from Researcher (data) + brief from Strategist (G2)
+**Actions:**
+1. Apply ToV (`$tone-of-voice`).
+2. Select storytelling framework (`$storytelling-framework`).
+3. Write headlines (`$headline-formulas`) — 3-5 options.
+4. Write text based on brief + data.
+5. Platform adaptation (`$social-media-formats` / `$email-copywriting`).
+6. CTA optimization (`$cta-optimization`).
+7. SEO optimization (`$seo-copywriting`) — if indexable content.
+8. Execute `$handoff` (forward) → Visual Concept (or Reviewer, if visual is in parallel).
+**Mandatory skills:** `$tone-of-voice`, `$headline-formulas`, `$cta-optimization`
+**Optional:** `$storytelling-framework`, `$social-media-formats`, `$email-copywriting`, `$seo-copywriting`
+**Deliverable:** Final text + headline options + CTA
+**Verification:** `$gates` — text matches brief (topic, thesis, persona), ToV, volume, platform
+**→ Wait for "Approved"**
+
+### Gate 5: Visual Concept
+**Input:** `$handoff` from Copywriter (text) or from Conductor (brief, if parallel to G4)
+**Actions:**
+1. Apply brand guidelines (`$brand-guidelines`).
+2. Create moodboard (`$moodboard`) — if new campaign / series.
+3. Visual brief (`$visual-brief`) — detailed specification.
+4. Platform specs (`$platform-visual-specs`) — dimensions, ratio, safe zones.
+5. AI prompts (`$image-prompt-engineering`) — if AI generation.
+6. Execute `$handoff` (forward) → Reviewer.
+**Mandatory skills:** `$visual-brief`, `$platform-visual-specs`
+**Optional:** `$moodboard`, `$image-prompt-engineering`, `$brand-guidelines`
+**Deliverable:** Visual brief + AI prompts (or spec for designer)
+**Verification:** `$gates` — brief is complete, specs match platform, style = brand
+**→ Wait for "Approved"**
+
+### Gate 6: Reviewer
+**Input:** `$handoff` from Visual Concept (text + visual)
+**Actions:**
+1. Review checklist (`$content-review-checklist`) — full, 38 items.
+2. Brand compliance (`$brand-compliance`) — ToV, visual, messaging, legal.
+3. Fact-checking (`$fact-checking`) — all factual assertions.
+4. Readability (`$readability-scoring`) — if text format.
+5. Platform compliance (`$platform-compliance`) — technical + rules + algorithmic.
+
+**If APPROVED:** → `$handoff` (forward) → Release Gate.
+**If REQUIRES CHANGES:** → Reverse `$handoff` → Copywriter / Visual Concept (by remark type).
+
+**Mandatory skills:** `$content-review-checklist`, `$brand-compliance`
+**Optional:** `$fact-checking`, `$readability-scoring`, `$platform-compliance`
+**Deliverable:** APPROVED or a list of fixes with severity (Blocker / Major / Minor)
+**Verification:** `$gates` — all Blockers closed, Majors ≤ 2 (fixed or accepted)
+**→ Wait for "Approved"**
+
+### Gate 7: Release Gate
+**Input:** APPROVED from Reviewer
+**Actions:**
+1. Final checklist (`$content-release-gate`) — artifacts, meta, legal.
+2. Prepare publication package: text + visual + hashtags + links + UTM + schedule.
+3. Update `$board` — all gates `[✓]`.
+4. Update `domains/content/CONTEXT.md`.
+**Mandatory skills:** `$content-release-gate`
+**Deliverable:** Full publication package
+
+**If READY TO PUBLISH:** → Final "Approved" → Publication.
+**If HOLD:** → Reverse `$handoff` by blocker type (see `$content-release-gate` rollback).
+
+**→ Final "Approved" → Publication**
+
+## Reverse Handoff — Return Protocol
+
+### From Gate 6 (Reviewer)
+
+```
+Reviewer (REQUIRES CHANGES)
+    │
+    ├── Text remarks → Reverse $handoff → Copywriter (G4)
+    │   └── Copywriter fixes → Forward $handoff → Reviewer (repeat G6)
+    │
+    ├── Visual remarks → Reverse $handoff → Visual Concept (G5)
+    │   └── Visual Concept fixes → Forward $handoff → Reviewer (repeat G6)
+    │
+    ├── Factual errors → Reverse $handoff → Researcher (G3)
+    │   └── Researcher fixes/replaces → Forward → Copywriter → Reviewer
+    │
+    └── Both (text + visual) → Reverse $handoff → Copywriter + Visual Concept → Reviewer
+```
+
+### From Gate 7 (Release Gate)
+
+```
+Release Gate (HOLD)
+    │
+    ├── Text → Copywriter → Reviewer → Release Gate (repeat)
+    ├── Visual → Visual Concept → Reviewer → Release Gate (repeat)
+    ├── Legal → Escalate to user
+    └── Meta / links → Conductor fixes → Release Gate (repeat)
+```
+
+### Reverse Handoff Rules
+1. Reverse `$handoff` contains: **specific remarks** + **severity** + **what NOT to touch**.
+2. Update `$board`: current gate → `[↩] Return`, target → `[→] In progress`.
+3. After fixes — **re-check** `$gates` → forward `$handoff`.
+4. Maximum of **3 iterations** at the Reviewer gate. If not APPROVED after 3 → escalate to user.
+
+## Escalation
+
+| Situation | Action | Who |
+|----------|----------|-----|
+| Blocker on any gate | `$board` → `[!]`, notify user, do not proceed | Current agent |
+| Brand guidelines undefined | Stop pipeline, request from user | Conductor (G1) |
+| Insufficient data for Researcher | Reverse → Strategist for brief clarification, or request from user | Researcher (G3) |
+| Fixes > 3 iterations at Reviewer | Escalate to user — issue might be in the brief | Conductor |
+| User is unresponsive | Wait. Do not proceed without Approved. Remind | Conductor |
+| Tight deadline | Suggest reducing scope or switching to `/quick-post` for part of the content | Conductor |
+| Conflict between gates | Escalate to user with arguments from both sides | Conductor |
+| Task proved too simple | Suggest switching to `/quick-post`. User decides | Conductor (G1-G2) |
+
+## Threshold for mode switching
+
+| Indicator | Direction | Decision |
+|-----------|-------------|---------|
+| Task is trivial (clear topic, no facts, blast radius ≈ 0) | → `/quick-post` | Conductor suggests at G1 |
+| Strategist determined strategy already exists, only text needed | → `/edit-content` (if draft exists) or proceed without G2 | Conductor suggests, user decides |
+| During G3-G4 it became clear task is simpler than it seemed | → Cannot skip (Rule 2), but reduce gate depth | Conductor |
+
+> Mode switching is **always the user's decision**. Conductor suggests, but does not switch on their own.
+
+## Orchestration Skills (used at every gate)
+
+| Skill | When | Description |
+|------|-------|----------|
+| `$board` | G1 (creation), every transition (update), G7 (closure) | Single source of truth on status |
+| `$gates` | Before every transition | Deliverable check: PASS / CONDITIONAL PASS / FAIL |
+| `$handoff` | Upon every transition (forward and reverse) | Transfer of artifacts + context + task |
+
+## Anti-patterns
+
+| Mistake | Why it's bad | How to do it right |
+|--------|-------------|---------------|
+| Skip Strategist "the topic is already clear" | No brief → Copywriter works blind | Rule 2: do not skip gates |
+| Researcher without verification | Unverified facts in text → loss of trust | `$source-verification` is mandatory |
+| Copywriter ignores the brief | Text does not match the strategy | `$gates` checks compliance with the brief |
+| Visual Concept without brand guidelines | Visual cannot be recognized as brand | `$brand-guidelines` is mandatory |
+| Reviewer checks only the text | Visual with AI artifacts slips through | Reviewer checks both text and visual |
+| Release Gate "it's all good anyway" | Broken links, no UTM, no disclaimer | `$content-release-gate` — full checklist |
+| Parallel G4+G5 when visual depends on text | Visual Concept redoes everything after getting text | Parallel only if visual is based on brief, not text |
+| 5+ iterations at Reviewer | Infinite loop, time wasted | Max 3 iterations → escalate |
+| Conductor rewrites text instead of Copywriter | Role violation, no quality review | Rule 6: fixes go to the executor |
+
+## Output Template (Gate 1 — Conductor)
+
+```
+### Full Pipeline — Initialization
+
+**Task:** [description from user]
+**Scope:** [what is created — content unit / series / campaign]
+**Brand guidelines:** [✅ exist / ❌ request]
+
+#### Pipeline Parameters
+- **Mode:** Full Pipeline (`/start-content`)
+- **Parallelism G4+G5:** [Yes — visual by brief / No — visual depends on text]
+- **Deadline:** [date or "no"]
+
+#### Board
+
+| # | Gate | Agent | Status |
+|---|------|-------|--------|
+| G1 | Conductor | Conductor | [→] In progress |
+| G2 | Strategist | Strategist | [ ] Waiting |
+| G3 | Researcher | Researcher | [ ] Waiting |
+| G4 | Copywriter | Copywriter | [ ] Waiting |
+| G5 | Visual Concept | Visual Concept | [ ] Waiting |
+| G6 | Reviewer | Reviewer | [ ] Waiting |
+| G7 | Release Gate | Conductor | [ ] Waiting |
+
+#### Task for Strategist
+[Clear formulation: what to elaborate, for whom, on what platform, with what goal]
+
+→ Waiting for **"Approved"** to proceed to Strategist
+```

package/domains/content/locales/en/AGENTS.md

@@ -0,0 +1,72 @@
+# Content Domain Orchestrator
+
+## Overview
+The Content Domain is an agent system for content production: social media, emails, blogs, and visual concepts.
+
+## Pipeline
+```
+CONDUCTOR → STRATEGIST → RESEARCHER → COPYWRITER → VISUAL_CONCEPT → REVIEWER → RELEASE GATE
+```
+
+## Agents
+
+| Role | File | Area of Responsibility |
+|------|-------|---------------------|
+| Conductor | agents/conductor.md | Orchestration, task routing, gate control |
+| Strategist | agents/strategist.md | Content strategy, calendar, audience |
+| Researcher | agents/researcher.md | Trends, fact-checking, sourcing |
+| Copywriter | agents/copywriter.md | Texts, ToV, headlines, CTA |
+| Visual Concept | agents/visual_concept.md | Visual concept, AI prompts, brand |
+| Reviewer | agents/reviewer.md | Quality, fact-checking, compliance |
+
+## Workflow
+
+| Command | Mode | Gates |
+|---------|-------|-------|
+| `/start-content` | Full Pipeline | CONDUCTOR → STRATEGIST → RESEARCHER → COPYWRITER → VISUAL_CONCEPT → REVIEWER → RG |
+| `/edit-content` | Edit Pipeline | CONDUCTOR → COPYWRITER → REVIEWER |
+| `/quick-post` | Quick Pipeline | CONDUCTOR → COPYWRITER+REVIEWER |
+
+## Skills
+
+### Conductor
+- `$board` — task board management
+- `$handoff` — handoff between gates
+- `$gates` — gate control
+- `$content-release-gate` — final gate before publication
+
+### Strategist
+- `$content-calendar` — content calendar
+- `$audience-analysis` — target audience analysis
+- `$platform-strategy` — cross-platform strategy
+- `$competitor-content-analysis` — competitor content analysis
+- `$content-brief` — content creation brief
+
+### Researcher
+- `$trend-research` — trend research
+- `$topic-research` — deep topic research
+- `$source-verification` — source verification
+- `$data-storytelling` — data-driven narratives
+
+### Copywriter
+- `$tone-of-voice` — brand tone of voice
+- `$headline-formulas` — headline formulas
+- `$social-media-formats` — social media formats
+- `$email-copywriting` — email copywriting
+- `$storytelling-framework` — storytelling framework
+- `$cta-optimization` — CTA optimization
+- `$seo-copywriting` — SEO copywriting
+
+### Visual Concept
+- `$visual-brief` — visual brief
+- `$brand-guidelines` — brand guidelines
+- `$image-prompt-engineering` — image prompt engineering
+- `$platform-visual-specs` — platform visual specifications
+- `$moodboard` — moodboard
+
+### Reviewer
+- `$content-review-checklist` — content review checklist
+- `$brand-compliance` — brand compliance
+- `$fact-checking` — fact-checking
+- `$readability-scoring` — readability scoring
+- `$platform-compliance` — platform compliance

package/domains/content/locales/en/AGENTS.yaml

@@ -0,0 +1,63 @@
+version: 1
+name: "content_production_orchestra"
+display_name: "AGENTS.md — Content Production Orchestra"
+description: "Orchestration contract for roles, skills, and delivery gates for content production."
+default_prompt: "Use AGENTS.md when the task requires content pipeline orchestration."
+triggers:
+  - "AGENTS.md"
+  - "content orchestrator"
+  - "content pipeline"
+roles:
+  - "conductor"
+  - "strategist"
+  - "researcher"
+  - "copywriter"
+  - "visual_concept"
+  - "reviewer"
+skills:
+  - "audience-analysis"
+  - "board"
+  - "brand-compliance"
+  - "brand-guidelines"
+  - "competitor-content-analysis"
+  - "content-brief"
+  - "content-calendar"
+  - "content-release-gate"
+  - "content-review-checklist"
+  - "cta-optimization"
+  - "data-storytelling"
+  - "email-copywriting"
+  - "fact-checking"
+  - "gates"
+  - "handoff"
+  - "headline-formulas"
+  - "image-prompt-engineering"
+  - "moodboard"
+  - "platform-compliance"
+  - "platform-strategy"
+  - "platform-visual-specs"
+  - "readability-scoring"
+  - "seo-copywriting"
+  - "social-media-formats"
+  - "source-verification"
+  - "storytelling-framework"
+  - "tone-of-voice"
+  - "topic-research"
+  - "trend-research"
+  - "visual-brief"
+pipeline:
+  - "CONDUCTOR"
+  - "STRATEGIST"
+  - "RESEARCHER"
+  - "COPYWRITER"
+  - "VISUAL_CONCEPT"
+  - "REVIEWER"
+  - "RELEASE_GATE"
+invocation:
+  explicit: false
+  implicit: true
+localization:
+  default_locale: "ru"
+  available_locales:
+    - "ru"
+    - "en"

package/domains/content/locales/en/CONTEXT.md

@@ -0,0 +1,19 @@
+# Project Overview
+
+| Field | Value |
+|------|----------|
+| **Domain** | Content Production |
+| **Description** | System of agents for content production |
+| **Current Phase** | MVP |
+
+## Pipeline Results
+
+| Gate | Status | Key Deliverable | Date |
+|------|--------|---------------------|------|
+| Conductor | ☐ | — | — |
+| Strategist | ☐ | — | — |
+| Researcher | ☐ | — | — |
+| Copywriter | ☐ | — | — |
+| Visual Concept | ☐ | — | — |
+| Reviewer | ☐ | — | — |
+| Release Gate | ☐ | — | — |