rfe-create

Writes a new work item from a problem statement, idea or objective — an RFE capturing business needs (WHAT and WHY) by default, an Initiative with --type initiative. It resolves the type, loads the type's rubric (bootstrapping and exporting it if absent), reads the type's creation guidance, and asks at most 2-5 clarifying questions — only what it cannot infer from the input. --headless skips the questions but still reads the guidance.

Items are written from the type's template to {TASKS_DIR}/<ID>.md. IDs are allocated atomically by next_rfe_id.py unless --id pre-assigned one, and all frontmatter is set through frontmatter.py set against the type's schema — never written by hand. For a type that sizes its items, the Size Guide assigns S/M/L/XL from the acceptance-criteria count.

Plugin: rfe-creator | User-invocable

Contract

Skill Contract canonical-skill-v1

Turn a problem statement, idea or objective into a well-formed work item of the resolved type — an RFE describing business needs (WHAT and WHY) by default, an Initiative with --type initiative — sized and ready for review.

Identity

Functions

generate

Success

• Produces a well-formed item of the resolved type, sized by the type's rules (S/M/L/XL from acceptance-criteria count for RFEs).
• Writes the type's task file (artifacts/rfe-tasks/RFE-NNN.md, artifacts/initiatives/INIT-NNN.md) with valid frontmatter and rebuilds the index when the type keeps one.

Optimization Targets

task_success judge SKILL.md @ c6eb99d→

Invariants

Must Preserve

• Describe needs and outcomes (WHAT and WHY) only — never prescribe architecture or implementation.
• Use Jira priority values (Blocker/Critical/Major/Normal/Minor), never High/Medium/Low.
• Take every typed literal (template, guidance, dirs, id prefix) from the type registry's launch block — never hand-write a typed path.

Fixed Context

toolsRead, Write, Edit, Glob, Grep, Bash, AskUserQuestion

clipython3

knowledgerepository_contentpublic, task_inputtask_private, tool_outputtask_private

Traceability

Skill

↗.claude/skills/rfe-create/SKILL.md

Supporting

• ↗types/rfe/template.md
• ↗types/rfe/prompts/create-guidance.md
• ↗types/initiative/template.md
• ↗types/initiative/prompts/create-guidance.md

Diagram

Arguments

/rfe-create [--type <t>] [--headless] [--priority <value>] [--labels <csv>] [--id <ID>] [--parent <KEY>] <problem statement>

Argument	Required	Default	Description
problem statement		-	The idea, need or objective to turn into a work item. Free text, taken from whatever arguments remain after the flags.
--type		rfe	Work-item type to create. An explicit --type always wins over inference.
--headless		-	Ask no clarifying questions — generate the item directly from the input. The type's guidance is still read.
--priority		Normal	Override the default priority. Jira values only — never High/Medium/Low.
--labels		-	Labels to apply to the created item.
--id		-	Use this pre-assigned ID instead of allocating one. The placeholder file already exists. --rfe-id / --initiative-id are accepted as aliases.
--parent		-	Parent key to set on the created item. Offered only for a type whose batch entries carry parent_key — PARENT_FLAG is empty for rfe, so in practice this is the Initiative type.

Usage

/rfe-create Users need to verify model signatures at serving time
/rfe-create --type initiative Establish a trusted model supply chain for RHOAI
/rfe-create --headless --priority Critical --labels candidate-3.5 TrustyAI operator crashes on large clusters