blueprint-synclisted

Check the status of generated content and offer options for modified or stale files. ## When to Use This Skill | Use this skill when... | Use blueprint-promote instead when... | |---|---| | You want to detect stale or modified generated rules/skills | You've decided to keep one specific edited rule (single artifact) | | You're reconciling drift between `.claude/rules/` and the manifest | You want to acknowledge modifications and stop sync warnings | | You want regenerate/promote/keep options for many files at once | Use blueprint-generate-rules instead to (re)generate from PRDs | | You preview status with `--dry-run` before changing anything | Use blueprint-sync-ids instead for ID assignment, not content drift | ## Flags | Flag | Description | |------|-------------| | `--dry-run` | Preview sync status report without interactive prompts or file modifications | ## Steps **Purpose**: - Detect when generated skills/commands have been manually modified - Detect when source PRDs have changed (making generated content stale) - Offer appropriate actions: regenerate, promote to custom, or keep as-is 1. **Read manifest**: ```bash cat docs/blueprint/manifest.json ``` - Extract `generated.rules` section - If no generated content, report "Nothing to sync" 2. **Check each generated rule**: For each rule in `manifest.generated.rules`: a. **Verify file exists**: ```bash test -f .claude/rules/{name}.md ``` b. **Hash current content**: