Agent-Skills.md

Agent Skills: dart-retro

DART Retro: run a retrospective and capture durable lessons

UncategorizedID: dartsim/dart/dart-retro

Repository

dartsim/dart
dartsimLicense: BSD-2-Clause
1,212304

Install this agent skill to your local

pnpm dlx add-skill https://github.com/dartsim/dart/tree/HEAD/.agents/skills/dart-retro

Skill Files

Browse the full folder contents for 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 in Codex to run the DART dart-retro workflow. The editable workflow source currently lives in .claude/commands/, and this generated Codex skill is a first-class Codex entrypoint.

Invocation

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

Treat the text after the skill name 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 release-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 release-branch 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