HAR: Sync Plans.md with implementation. Drift detect, marker update, retrospective. Trigger: sync-status, where am I, check progress. --snapshot for snapshots. Do NOT load for: planning, implementation, review, release.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
HAR: Sync Plans.md with implementation. Drift detect, marker update, retrospective. Trigger: sync-status, where am I, check progress. --snapshot for snapshots. Do NOT load for: planning, implementation, review, release.
description-en
HAR: Sync Plans.md with implementation. Drift detect, marker update, retrospective. Trigger: sync-status, where am I, check progress. --snapshot for snapshots. Do NOT load for: planning, implementation, review, release.
Reconciles Plans.md against implementation status and detects/updates drift.
Standalone version of legacy sync-status and the harness-plan sync subcommand.
Quick Reference
User input
Action
harness-sync
Progress sync + retrospective (default ON)
harness-sync --no-retro
Progress sync only (skip retrospective)
harness-sync --snapshot
Save snapshot (point-in-time progress record)
harness-sync --plan roadmap
Sync the roadmap named plan
"Where am I?" / "Check progress"
Same as above
Options
Option
Description
Default
--snapshot
Save current progress as a snapshot
false
--no-retro
Skip retrospective
false (runs by default)
--plan NAME
Use a named plan from plans/manifest.json
active/default
Step 0: Plans.md validation
Verify Plans.md exists and is properly formatted. If issues are found, guide and stop immediately.
In repos with multiple Plans.md files, confirm the target plan with scripts/plan-registry.sh list or --plan NAME before reading.
State
Guidance
Plans.md does not exist
Plans.md not found. Create it with harness-plan create. → Stop
Header missing DoD / Depends columns (v1 format)
Plans.md is in old format (3 columns). Regenerate to v2 (5 columns) with harness-plan create. Existing tasks will be carried over automatically. → Stop
Design intent: Snapshots are for manual use when users want to "record the current state."
This is a different feature from the automatic progress feed during breezing (26.2.3).
Step 5: Next action suggestions
Next steps
**Priority 1**: {{task}}
- Reason: {{requested / waiting for unblock}}
**Recommended**: harness-work, harness-review
Anomaly detection
Situation
Warning
Multiple cc:WIP
Multiple tasks in progress simultaneously
pm:requested unprocessed
Handle PM requests first
Large drift
Task management not keeping up
WIP not updated for 3+ days
Check if blocked
Step 6: Retrospective (default ON)
If there is at least 1 cc:done task, automatically run a retrospective.
Can be explicitly skipped with --no-retro.
Step R1: Collect completed tasks
# Extract cc:done / pm:approved tasks from Plans.md
grep -E 'cc:done|pm:approved' Plans.md
# Recent completion commit history
git log --oneline --since="7 days ago"# Change scale
git diff --stat HEAD~10
Step R2: Retrospective 4 items
Item
Analysis method
Estimation accuracy
Infer expected file count from Plans.md task descriptions → compare with actual changed files from git diff --stat
Block causes
Aggregate reason patterns for tasks with blocked marker (technical / external dependency / unclear spec)
Quality marker accuracy
For tasks tagged [feature:security] etc., check if related issues actually occurred
Scope variation
Task count in Plans.md at first commit vs current count (added/removed count)
Step R3: Retrospective summary output
## Retrospective Summary**Period**: {{start_date}} – {{end_date}}
| Metric | Value |
|--------|-------|
| Completed tasks | {{count}} |
| Blocks occurred | {{blocked_count}} |
| Scope variation | +{{added}} / -{{removed}} |
| Estimation accuracy | Expected {{est}} files → Actual {{actual}} files |
### Learnings
- {{1-2 lines of learning}}
### Actions for next time
- {{1-2 lines of improvement actions}}
Step R4: Record to harness-mem
Record retrospective results in harness-mem for reference during the next create.
Record location: Relevant agent memory under .claude/agent-memory/.
