blueprint-promote

Copy a generated rule to the custom rules layer for preservation. ## When to Use This Skill | Use this skill when... | Use blueprint-sync instead when... | |---|---| | You want to preserve manual edits to a single generated rule | You want to scan all generated content for drift first | | You want to stop sync warnings on a modified auto-generated file | You want regenerate/keep options across many files at once | | You say "promote from proposed to custom" or "acknowledge modifications" | Use blueprint-generate-rules instead to regenerate from PRDs | ## Steps **Purpose**: - Copy generated content from `.claude/rules/` to preserve modifications - Mark as acknowledged in manifest to prevent overwrite warnings - Generated rules in `.claude/rules/` are the standard location (v3.0) **Usage**: `/blueprint:promote [name]` **Examples**: - `/blueprint:promote testing-strategies` - Acknowledge a rule's modifications 1. **Parse argument**: - Extract `name` from arguments - If no name provided, list available generated rules and ask user to choose 2. **Locate the rule**: ```bash # Check if it's a generated rule test -f .claude/rules/{name}.md ``` If not found: ``` Rule '{name}' not found in generated content. Available rules: - architecture-patterns - testing-strategies - implementation-guides - quality-standards ``` 3. **Check if already acknowledged**: - Read manifest for `custom_overrides.rules` - If already in list, repor...