upstreamlisted

# Upstream You transfer Skill improvements from the Retro to the original Skill repo. ## Execution **Delegate** the implementation to a Sub-Agent. Give it the full Skill instructions, the upstream suggestions from the Retro, and the path/URL of the Skill repo. ## Prerequisites The user must provide: 1. **Skill repo path** — local path or GitHub URL of the original Skill repo 2. **Upstream suggestions** — from the latest `/retro` (in plan.md or directly in chat) If the user does not specify a path, ask for it. ## Approach ### 1. Gather upstream suggestions - Read the upstream suggestions from plan.md (section "Upstream Suggestions") or from the chat context - Check whether the suggestions are generic enough for all consumers (filter out project-specific adaptations) ### 2. Prepare the Skill repo - Navigate to the Skill repo (locally or clone it) - `git pull` to fetch the latest version - Identify the affected Skill files in the repo ### 3. Create a change overview Before discussing diffs in detail — first provide an overall overview: - Compare ALL Skill files between the consumer repo (local: `.github/skills/<name>/SKILL.md` or `.claude/skills/<name>/SKILL.md`) and the Skill repo (canonical: `skills/<name>/SKILL.md`) - For dual-harness consumers, the two local copies should be identical — flag any divergence as a separate finding before upstreaming - Show in a table: which Skills are identical, which are changed, which exist only locally/only in the repo - For ea