vllm-rfc-generatorlisted

# vLLM RFC Generator Generate a vLLM-style RFC Markdown document from user-provided information and save it to `./outputs/`. ## Inputs Collect the following from the user (ask if not provided): | Field | Required | Description | |-------|----------|-------------| | **RFC Title** | Yes | Short, descriptive title (will be prefixed with `[RFC]:`) | | **Main Content** | Yes | Description of the motivation and proposed changes | | **Related PRs** | No | List of PR numbers or URLs; classify them by category | | **Feedback Period** | No | Duration for feedback (default: "At least 1 week") | | **CC List** | No | GitHub usernames to CC (e.g., `@user1`, `@user2`) | | **Other Notes** | No | Any additional context or notes | ## Workflow 1. **Collect inputs** — gather all necessary information from the user 2. **Classify PRs** — if PRs are provided, group them by category (see PR Classification below) 3. **Generate RFC content** — write each section following the template 4. **Save output** — write to `./outputs/rfc-<slug>.md` 5. **Confirm** — tell the user the output path ## PR Classification When the user provides related PRs, classify them into appropriate categories such as: - **Background / Motivation PRs** — existing issues, bugs, or prior discussions that motivate this RFC - **Implementation PRs** — concrete code changes implementing the proposed design - **Dependency PRs** — prerequisite changes that must land first - **Related / Follow-up PRs** — tangential improvements