Agent Skills: dart-retro

DART Retro: run a retrospective and capture durable lessons

ID: dartsim/dart/dart-retro

Repository

dartsimLicense: BSD-2-Clause
1,212304

Install this agent skill to your local

npx skills add dartsim/dart --skill dart-retro

Skill Files

The files that make up dart-retro.

Download Skill

Loading file tree…

.agents/skills/dart-retro/SKILL.md

Skill Metadata

Name
dart-retro
Description
DART Retro: run a retrospective and capture durable lessons
<!-- AUTO-GENERATED FILE - DO NOT EDIT MANUALLY --> <!-- Source: .claude/commands/dart-retro.md --> <!-- Sync script: scripts/sync_ai_commands.py --> <!-- Run `pixi run sync-ai-commands` to update -->

dart-retro

Use this skill to run the DART dart-retro workflow. The editable workflow source lives in .claude/commands/; this generated skill is its entrypoint for Codex and Muse.

Invocation

  • Claude Code: /dart-retro <arguments>
  • Codex: $dart-retro <arguments>
  • Muse: /dart-retro <arguments>

Treat the text after the skill name, or the user's request when the skill is loaded on demand, as $ARGUMENTS. When the workflow references $1, $2, etc., map those to the positional values supplied by the user.

Command Body

Run a retrospective and capture durable lessons: $ARGUMENTS

Required Reading

@AGENTS.md @docs/AGENTS.md @docs/ai/principles.md @docs/ai/components.md @docs/ai/verification.md @docs/onboarding/ai-tools.md

Skip If

Stop without editing when all are true:

  • no new patterns, gotchas, or failure modes were discovered
  • no workflow improvement is needed
  • the learning is too session-specific to help future agents or contributors
  • existing docs already cover what happened
  • the task was routine and left no durable insight

Workflow

  1. Search existing branch docs before adding content.
  2. Inventory the completed work before routing lessons. Consider compatibility, downstream/Gazebo impact, CI/review failure modes, workflow friction, and cleanup or handoff steps separately.
  3. Decide whether each lesson is general enough for DART AI infra. Do not update AI docs after every session.
  4. Prefer updating an existing owner doc over adding a new file. Use docs/information-architecture.md to choose the owner.
  5. Keep docs/ai/principles.md compact; put procedures in the owner docs it links to.
  6. Avoid ephemeral branch, PR, commit, or username details.
  7. If adding or renaming a workflow command or skill, edit .claude/ source files and run pixi run sync-ai-commands.
  8. Run pixi run lint before committing. For AI workflow changes, also run pixi run sync-ai-commands and pixi run check-ai-commands.

Output

  • What learning was captured
  • Where it was documented
  • Checks run

More agent skills