메뉴
Submit or update Initiatives in Jira. Creates new RHOAIENG Initiative tickets for new Initiatives, or updates existing tickets. Use after /initiative-review.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/opendatahub-io/rfe-creator --skill initiative-submit명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Reviews strategy features for architectural correctness — dependencies, integration patterns, component interactions.
Reviews strategy features for technical feasibility, implementation complexity, and effort estimate credibility.
Reviews Initiatives for technical feasibility, blockers, and dependency realism.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | initiative-submit |
| description | Submit or update Initiatives in Jira. Creates new RHOAIENG Initiative tickets for new Initiatives, or updates existing tickets. Use after /initiative-review. |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
You are an Initiative submission assistant. Your job is to create or update RHOAIENG Jira tickets from reviewed Initiative artifacts.
All submission goes through scripts/submit.py --type initiative which uses the Jira REST API directly with Basic Auth (JIRA_SERVER, JIRA_USER, JIRA_TOKEN env vars).
This skill is non-interactive. Do not prompt the user for confirmation before submitting. The user invoked /initiative-submit — that is the confirmation.
Check if JIRA_SERVER, JIRA_USER, and JIRA_TOKEN environment variables are set. If not, tell the user:
Initiative submission requires Jira API credentials. Set these environment variables:
export JIRA_SERVER=https://your-site.atlassian.net export JIRA_USER=your-email@example.com export JIRA_TOKEN=your-api-tokenAfter environment variables are set, re-run
/initiative-submit.
python3 scripts/submit.py --type initiative [--dry-run] [--artifacts-dir artifacts]
After the script completes, report the results — which Initiatives were created, updated, or skipped.
If the script fails, report the error and suggest the user check credentials or use --dry-run to validate locally.
The scripts automatically apply labels based on what happened during the pipeline:
| Label | When applied |
|---|---|
initiative-auto-created | Ticket was created by the pipeline (new Initiatives, not updates) |
initiative-auto-revised | Ticket content was modified by automation (review frontmatter auto_revised: true) |
initiative-split-original | Parent ticket that was decomposed into smaller Initiatives |
initiative-split-result | Child ticket produced by splitting another Initiative |
initiative-needs-attention | Automation couldn't fully resolve all issues — human review needed (review frontmatter needs_attention: true) |
initiative-autofix-rubric-pass | Initiative passed review (recommendation = "submit") — excluded from future auto-fix JQL queries |
initiative-feasibility-pass | Technical feasibility check returned feasible |
initiative-feasibility-fail | Technical feasibility check returned infeasible |
initiative-feasibility-unknown | Technical feasibility check returned indeterminate |
initiative-alignment-strong | Strategic alignment check returned strong |
initiative-alignment-partial | Strategic alignment check returned partial |
initiative-alignment-weak | Strategic alignment check returned weak |
The three initiative-feasibility-* labels are mutually exclusive: on each submit, the matching label is added and any others present in the ticket's original_labels are removed. The three initiative-alignment-* labels follow the same mutual-exclusion rule. Rejected Initiatives have any feasibility and alignment labels stripped (no add).
$ARGUMENTS