메뉴
Pull a RHAISTRAT issue from Jira into the local/ workspace for human review. Only works on post-CI strategies.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | strategy-pull |
| description | Pull a RHAISTRAT issue from Jira into the local/ workspace for human review. Only works on post-CI strategies. |
| user-invocable | true |
| allowed-tools | Read, Write, Bash, Glob, Grep |
You are pulling a strategy from Jira into the local workspace so a human can review and iterate on it.
$ARGUMENTS must contain a RHAISTRAT key (e.g., RHAISTRAT-1520). If no key is provided, ask the user for one.
Run the pull script:
python3 ${CLAUDE_SKILL_DIR}/scripts/pull_strategy.py $ARGUMENTS
This will:
strat-creator-rubric-pass or strat-creator-needs-attention)local/strat-tasks/RHAISTRAT-NNNN.md with workflow: local frontmatterlocal/strat-originals/local/strat-reviews/The pull creates three folders under local/:
strat-tasks/ — The strategy document itself (e.g., RHAISTRAT-133.md). This is what you review and edit.strat-originals/ — The source RFE snapshot and its comments at pull time. Read-only context for understanding the business need.strat-reviews/ — CI review output. Contains two files per strategy:
RHAISTRAT-NNNN-review-summary.md — The scoring table and verdict (pass/fail, scores per criterion).RHAISTRAT-NNNN-review.md — The full prose review from independent reviewers (detailed analysis per dimension).If the script exits with code 1 (missing labels or not found), explain that only post-CI strategies can be pulled. If code 2 (missing credentials), tell the user to set JIRA_SERVER, JIRA_USER, and JIRA_TOKEN.
Read the pulled strategy file and the review file (if present). Summarize for the user:
Then advise the user on next steps:
/strategy-refine and /strategy-review to iterate locally, then /strategy-signoff when you're satisfied."/strategy-refine and /strategy-review to fix issues locally, then /strategy-push to resubmit to CI."$ARGUMENTS
Create strategies from approved RFEs by cloning them to RHAISTRAT in Jira, or guiding the user through manual cloning.
Sign off on a CI-approved strategy — pushes content and adds strat-creator-human-sign-off label. For rubric-pass strategies only.
Refine a single strategy — add the HOW, dependencies, impacted teams/components, and non-functional requirements. Requires a strategy key argument.
Adversarial review of a single refined strategy. Scores against rubric, then runs independent forked reviewers for detailed prose. Requires a strategy key argument.
Reviews strategy features for testability — are acceptance criteria measurable, are edge cases covered, can this be validated?
Push a locally-refined strategy back to Jira and resubmit to CI. For needs-attention strategies only.