Menu
Create and revise a structured topic outline from an evolving brief, audience, angle, thesis, sections, questions, and sources.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Design and maintain truthful HomeRail generative UI for voice or text. Use for dashboards, cards, charts, visual reports, screenshot-ready output, or supervised multi-Actor live panels that update in parallel and across follow-ups.
Exact HomeRail local-source TypeScript CLI command and configuration reference. Use when: (1) configuring or invoking the homerail CLI from a local checkout, (2) listing orchestration templates, starting runs, checking status, (3) supervising DAG runs, inspecting chats/handoffs/scorecards, (4) injecting instructions or replaying runs, or (5) translating a known HomeRail operation into an exact hr command. For workflow topology selection use homerail-dag-patterns; for multi-Actor Surface lifecycle and operational procedure use homerail-dag-ops. For deployment, service startup, or skill installation, use homerail-install-ops first.
Run, monitor, inspect, debug, and author HomeRail DAG workflows through the CLI or Manager Tools, including supervised multi-Actor runs with stable live Surfaces and later per-Actor follow-ups. Use when: (1) listing templates, (2) starting a DAG run, (3) supervising or watching a run, (4) inspecting chats, handoffs, scorecard, eval-run, or replay output, (5) creating multiple parallel UI panels that update while Actors work, (6) sending commands to waiting Actors, (7) injecting instructions into running nodes, or (8) creating custom DAG templates. For installing or starting Manager/Node/Worker services, use homerail-install-ops first.
Select, inspect, instantiate, adapt, and validate HomeRail's built-in DAG design patterns. Use when an agent needs to design a reusable workflow for periodic triage, read-only issue diagnosis, planner/worker fan-out, on-demand executor/advisor consultation, budget admission, graduated trust, standing-goal verification, quorum decisions, adversarial builder/breaker review, monotonic improvement, or evidence-driven process evolution. Also use when deciding whether a workflow needs condition, loop, join, or while gateway semantics. Patterns describe control-flow invariants; for stable live Actor panels, Surface updates, or follow-up commands, use homerail-dag-ops and a concrete presentation-aware Workflow.
Present an evidence-grounded pull request closeout decision after review, CI, or real-machine validation.
Create or replace a complete semantic release-notes snapshot.
| name | topic-outline |
| description | Create and revise a structured topic outline from an evolving brief, audience, angle, thesis, sections, questions, and sources. |
Use this Skill when the user asks to plan, structure, or revise a content topic. Do not use it for a generic task checklist or for an outline the user did not request.
Call the current Tool catalog entry for com.homerail.topic-outline:upsert_topic_outline with the complete current outline. Its harness-safe wire name is supplied by the current turn and must not be guessed. Reuse one stable plugin-owned id such as com.homerail.topic-outline:current across turns so a revision replaces the same semantic node without colliding with Core or another plugin. A partial outline is valid: record what is known, preserve useful prior fields, and put only unresolved decisions in questions.
Keep the shape concise:
title names the topic, not the UI component.brief, audience, angle, and thesis capture the current editorial direction.outline contains ordered sections with short points and truthful status.sources includes only real HTTP(S) references supplied or found through an authorized tool.next_action states the next useful editorial step.confidence reflects evidence, not presentation polish.Use the matching topic-outline Tool only when it is listed for the current turn. Do not substitute a legacy dynamic widget. If the requested outline is not placed on the canvas, tell the user only that visible result and offer to retry.