dart-retro
GitHub用于运行 DART 回顾工作流，捕获持久化经验教训。通过审查已完成工作、识别新模式或失败模式，将有价值的洞察更新到现有文档中，避免冗余并提升团队知识库质量。
Trigger Scenarios
Install
npx skills add dartsim/dart --skill dart-retro -g -y
SKILL.md
Frontmatter
{
"name": "dart-retro",
"description": "DART Retro: run a retrospective and capture durable lessons"
}
dart-retro
Use this skill in Codex to run the DART dart-retro workflow. The editable
workflow source lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
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
Routing
docs/ai/components.md owns routing for durable session learnings. Use this
command as the hindsight workflow; do not duplicate the routing table here.
Workflow
- Search existing docs before adding content.
- Inventory the completed work before routing lessons. Consider domain/design choices, public API or package compatibility, CI/review failure modes, workflow friction, and cleanup or handoff steps separately so a late operational task does not hide feature-level learnings.
- Decide whether each lesson is general enough for shared AI infra. Do not update AI components after every session.
- Prefer update, remove, consolidate, or restructure over adding new files.
- Make every durable learning discoverable from its owner surface: update an existing owner doc when possible, and when a new durable file is justified, link it from the relevant owner index or plan before retiring temporary context.
- Keep
docs/ai/principles.mdcompact; put procedures in the owner docs it links to. - Avoid ephemeral branch, PR, commit, or username details.
- If adding a workflow command or skill, edit
.claude/source files and runpixi run sync-ai-commands. - Run
pixi run lintbefore committing. For AI docs or adapter changes, also run the verification gates fromdocs/ai/verification.md:pixi run lint-md,pixi run check-lint-md,pixi run sync-ai-commands,pixi run check-ai-commands,pixi run check-docs-policy, andpixi run check-lint-spell.
Output
- What learning was captured
- Where it was documented
- Checks run
Version History
- b9fbefc Current 2026-07-19 11:30
