Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From chief-skills
Runs a milestone or batch retrospective by checking goal/contract coverage, summarizing planned vs delivered work, and proposing rule updates.
npx claudepluginhub thaitype/chief --plugin chief-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/chief-skills:chief-retroThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run a retrospective on the current milestone.
Runs context-aware retrospectives auto-gathering git metrics, learnings, away-logs, and handoffs into pre-populated tables for interactive or agent-summary review.
Generates adaptive-depth session retrospective reports (retro.md) from plan.md and lessons.md, converting outcomes into persistent process improvements. Supports deep/light modes and directory resolution logic.
Conducts project or sprint retrospectives by gathering data from status reports, velocity metrics, and artifacts; structures what went well, improvements, and generates actionable items with owners and due dates. Use at sprint ends, milestones, or reviews.
Share bugs, ideas, or general feedback.
Run a retrospective on the current milestone.
Auto-detect the scope:
_plan/_todo.md in the active milestone.[x] → milestone retro._report/autopilot-run-batch-<N>.md_plan/_todo.md (completed vs remaining)_goal/ and _contract/ filesgit log for commits since the previous batch report (or milestone start)_report/ files (batch reports, task outputs, etc.)_plan/_todo.md (full history)_goal/ and _contract/ filesgit log for the entire milestoneWrite the report with these sections:
# Retro: <milestone> — <batch N | milestone>
## Coverage Check
For each goal and contract file, check whether the work done satisfies it:
| File | Status | Notes |
|------|--------|-------|
| _goal/xxx.md | ✅ Satisfied / ⚠️ Partial / ❌ Missing | what's done or missing |
| _contract/xxx.md | ✅ / ⚠️ / ❌ | ... |
## Planned vs Delivered
- What was in the TODO
- What was actually completed
- What was skipped or changed mid-execution
## Blockers Hit
- Issues encountered during execution
- How they were resolved (or not)
## Lessons Learned
- Patterns observed (good and bad)
- Recurring problems
- Surprises or unexpected outcomes
- What worked well and should be repeated
## Proposed Rule Updates
For each proposal:
- **What:** the rule to add or change
- **Where:** which file in `.chief/_rules/` (e.g. `_standard/auth.md`, `_verification/tests.md`)
- **Why:** what happened that motivates this rule
- **Suggestion:** recommended for the user
## User Action Needed
Items requiring human decision:
- Uncovered goals or contracts that need another batch
- Decisions to promote to permanent rules
- Manual steps that automation couldn't handle
.chief/<milestone>/_report/retro-batch-<N>.md.chief/<milestone>/_report/retro-milestone.mdWhere <N> matches the batch number being reviewed.
Present the proposed rule updates to the user. Ask:
"Want me to apply any of these rule proposals?"
.chief/_rules/._rules/ can be updated.