CTA Format
Canonical CTA "Next Step" block format for every /dr-* command and pipeline agent. Single source of truth — load when generating slash-command output.
Overview
CTA Format is the canonical specification for the "Next Step" Call-to-Action block emitted at the end of every /dr-* command response. Introduced in v1.16.0 (TUNE-0032), it solves the problem of ambiguous next-step routing when users are working on multiple parallel tasks: every CTA now includes the resolved task ID, exactly one explicit primary marker, and an optional menu of other active tasks.
Why it exists
Before v1.16.0, each /dr-* command emitted free-form prose like "→ /dr-prd для ARCA-0004 (Research & PRD), или /dr-plan если хотите сразу перейти к планированию…" — the user had to mentally map task IDs to commands, with no explicit primary recommendation. Audit of the 15 commands showed 0/15 included a task ID in their CTA and 0/15 marked a primary action. The fix: a structured, predictable block emitted by every command in every situation.
Canonical block — single active task
---
**Следующий шаг — TUNE-0032** (L3, in_progress)
1. `/dr-design TUNE-0032` — **рекомендуется** — auto-transition после plan
2. `/dr-do TUNE-0032` — если creative-phase не нужен
3. `/dr-status` — backlog overview
---
Multi-task variant (Variant B)
When more than one task is active in activeContext.md, the block appends an "Другие активные задачи" section listing each parallel task with its own recommended next command. This is the discovery surface for users juggling 5-10 tasks across projects.
FAIL-Routing variant
When /dr-qa returns BLOCKED or /dr-compliance returns NON-COMPLIANT, the header changes to **QA failed для {ID} — earliest failed layer: Layer N (Layer name)** and the primary CTA points to the layer-return command per the Layer-to-command map (Layer 1 → /dr-prd, 2 → /dr-design, 3 → /dr-plan, 4 → /dr-do).
Design constraints (research-driven)
- 3 options sweet spot, 5 maximum — Miller's Law, Hick's Law, Chernev 2015 meta-analysis on choice overload
- Markdown
---HR, never box-drawing─— Claude Code issue #34247: U+2500 causes mojibake on Windows - Inline bold for headers, never
##— Claude Code GFM renderer collapses all header levels to bold; no hierarchy distinction - Russian shell, English commands — matches existing framework convention for slash-command names
Loaded by
Mandatory: planner, architect, developer, reviewer, compliance. Referenced from all 17 /dr-* command files.
Tested by
tests/cta-format.bats — 39 spec-regression tests covering skill structure, command references, agent loading, routing skill alignment, and anti-pattern guards (no box-drawing in commands, exactly one primary marker per fixture).
Source
TUNE-0032, v1.16.0, 2026-04-25. PRD: datarim/prd/PRD-TUNE-0032.md. Research: datarim/insights/INSIGHTS-TUNE-0032.md.