improve-pipelinelisted

# Improve Pipeline Use this skill when real-world usage of the pipeline reveals a weakness in the pipeline itself. The triggering incident may happen in another repository, but the improvement target is always `chrislacey89/skills`: the skills, docs, checklists, and workflow guidance that shape future agentic development. This is not automatic self-modification. Default output is a GitHub issue in `chrislacey89/skills`. The issue should explain what happened, why it is a pipeline problem rather than only a project problem, what change is recommended, what repo-wide effects the change could have, and which files in `chrislacey89/skills` would need to change if the recommendation is approved. If the user asks for implementation after reviewing the proposal, implementation can follow as a separate step. Do not skip the proposal. > **One question per turn.** If key facts are missing, ask one question at a time and wait for the user's answer before asking the next. Never turn incident intake or review into a questionnaire. > > **Prefer single-select.** Use single-select multiple choice when the user is choosing one direction, one priority, or one next step. > > **Use multi-select rarely.** Reserve it for compatible sets — goals, constraints, non-goals, success criteria — that can all coexist. If prioritization matters, follow up asking which selected item is primary. > > **Use the platform's question tool when available.** In Claude Code, use `AskUserQuestion`; in Codex, `requ