rfe-creator

End-to-end RFE pipeline. Accepts a single idea, Jira key(s), or a YAML batch file. Creates, reviews, auto-fixes (with splits), and submits. Supports --headless, --announce-complete, and --dry-run for CI.

Review and fix batches of RFEs automatically. Accepts explicit IDs or a JQL query. Reviews, auto-revises, and splits oversized RFEs. Non-interactive.

Review and improve RFEs. Accepts one or more Jira keys (e.g., /rfe.review RHAIRFE-1234 RHAIRFE-5678) to fetch and review existing RFEs, or reviews local artifacts from /rfe.create. Runs rubric scoring, technical feasibility checks, and auto-revises issues it finds.

Split oversized RFEs into smaller, right-sized RFEs. Accepts one or more IDs (e.g., /rfe.split RHAIRFE-1234 RHAIRFE-5678). Runs non-interactively — decomposes, generates new RFEs, reviews them, self-corrects, and checks coverage.

Reviews RFEs for technical feasibility, blockers, and alignment with technical strategy.

Reviews strategy features for architectural correctness — dependencies, integration patterns, component interactions.

Write a new RFE from a problem statement, idea, or need. Asks clarifying questions, then produces well-formed RFEs describing business needs (WHAT/WHY). Use when starting from scratch.

Reviews strategy features for technical feasibility, implementation complexity, and effort estimate credibility.

Submit or update RFEs in Jira. Creates new RHAIRFE tickets for new RFEs, or updates existing tickets for RFEs fetched from Jira. Use after /rfe.review.

Reviews strategy features for scope — is each strategy right-sized, does the effort match the scope, should anything be split?

Reviews strategy features for testability — are acceptance criteria measurable, are edge cases covered, can this be validated?

Force update all vendored dependencies — assess-rfe skills and architecture context. Use when you want the latest versions.