pr-requirement-capturelisted

# PR Requirement Capture ## Overview GH may send a message beginning with: ```text PR : <요구사항> PR: <요구사항> ``` This means: **save and execute the requirement through a GitHub PR workflow**, not just as an ephemeral Discord/chat instruction. The goal is to make product/app changes traceable: ```text Discord request → branch → requirement summary → implementation/checks → PR → GH review/merge ``` ## When to Use Use this skill when: - The message starts with `PR :` or `PR:`. - GH says in Korean or English that a request should be handled as a PR. - GH wants a feature/change/bugfix to be preserved for formal development. - The request targets a local Git project with a GitHub remote. Do **not** use this skill for: - Simple questions with no repository change. - One-off operational checks. - Emergency hotfixes where GH explicitly says to commit/push directly to `main`. ## Trigger Parsing Strip only the leading trigger and whitespace: ```text PR : Cursor dashboard CSV 기준으로 토큰 수집 바꿔줘 ``` Requirement body: ```text Cursor dashboard CSV 기준으로 토큰 수집 바꿔줘 ``` If the body is empty, ask GH for the requirement using the clarification tool. ## Default Project Resolution 1. If the conversation is clearly about a current project, use that project path. - Example: AI usage board → `/home/geonhee/ai-usage-board` 2. Otherwise inspect the current working directory and `git remote -v`. 3. If multiple projects are plausible, ask one clarification question. Before making changes,