Skip to content
cccskills
FreePublished on GitHub

create-rfc

Turn a design request into an OpenShell RFC, a proposal for review and discussion. The skill follows the project template, assigns an available number, and organizes motivation, alternatives, and open questions into a draft.

OriginalShow the original description

Create OpenShell RFC proposals in rfc/ from a design request. Use when the user asks to write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal that should follow the OpenShell RFC process and template.

NVIDIA/OpenShell
See how to install

Good for

  • Drafting an architecture proposal
  • Organizing an API change proposal
  • Documenting a process change
  • Updating an existing RFC

Files included (2)

  • SKILL.md2.6 KB
  • agents/openai.yaml174 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Create RFC

Workflow

Create RFCs by following rfc/README.md and rfc/0000-template/README.md. Keep the template as the source of truth for section guidance.

  1. Read rfc/README.md to confirm when an RFC is appropriate, how to choose the RFC number, and how the lifecycle works.
  2. Read rfc/0000-template/README.md before drafting. Follow its section guidance, including scope, expected detail, and suggested section length.
  3. Choose the next available NNNN from the existing rfc/NNNN-* directories unless the user provided a specific number.
  4. Create rfc/NNNN-short-title/README.md by copying the template and replacing placeholders. Use a short hyphenated folder title.
  5. Fill in front matter with the RFC author, state: draft, and any related links the user provided. If the author is unknown, use the requesting user's GitHub handle when available or leave the template placeholder.
  6. Draft each section from the user's design context. Keep Summary concise, Motivation readable by anyone, Non-goals explicit, Proposal focused on what is being proposed, and Alternatives focused on credible competing approaches.
  7. Preserve uncertainty in Open questions instead of silently deciding unknowns. If a missing decision blocks a coherent RFC, ask the user for that decision.
  8. Check the completed RFC against the template once more before finishing.

Writing Standards

  • Prefer concrete design statements over placeholder language.
  • Link to relevant issues, prior RFCs, and published docs when they provide needed context.
  • Keep rejected or left-out designs in Alternatives, not Proposal.
  • Use Mermaid diagrams for architecture or data flow when a diagram would make the proposal easier to review.
  • Do not update published docs just because an RFC was drafted. Those updates belong with implementation or with an accepted RFC when the user asks for them.

Validation

Before handing the RFC back to the user:

  • Verify the folder name and RFC number match the process in rfc/README.md.
  • Verify every template section is present or intentionally marked as not applicable.
  • Run a Markdown formatting or lint check only if the repo already provides one for Markdown-only changes.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

apply-triage-action

FreeSummary

Process one recommendation selected by ID from a local issue or CI triage report. Apply, reject, or defer it, record the outcome, and obtain separate confirmation before each change made on GitHub.

  • Apply one recommendation selected by its item ID
  • Reject a recommendation and record the reason
  • Defer a decision for the next queue review
NVIDIA/OpenShell16.6KUpdated Oct 19, 2026

build-from-issue

FreeSummary

Turn a GitHub issue into a scoped implementation plan and, when authorized, code changes, tests, documentation, and a pull request that closes it. Check existing ownership and feedback to keep work aligned with acceptance criteria.

  • Creating an implementation plan from a GitHub issue
  • Implementing an authorized issue with focused tests
  • Updating documentation alongside behavior changes
NVIDIA/OpenShell16.6KUpdated Oct 19, 2026

build-openshell-mxc-windows

FreeSummary

Maintain and validate OpenShell builds for Windows on x64 and ARM64 using MSVC, Microsoft's C++ toolchain. Check compilation, build executables, run tests on native hosts, and report artifacts and unsupported driver behavior.

  • Investigating Windows compilation failures
  • Building x64 and ARM64 release executables
  • Checking errors for unsupported drivers
NVIDIA/OpenShell16.6KUpdated Oct 19, 2026

create-github-issue

FreeSummary

Create GitHub issues for OpenShell bugs, feature requests, and tasks using the gh command-line tool. Organize firsthand use cases, impact, and completion criteria into the project's templates, then return the created issue link.

  • Report an OpenShell bug you directly encountered
  • Request a feature for a specific OpenShell use case
  • Register an internal task with completion criteria
NVIDIA/OpenShell16.6KUpdated Oct 19, 2026

create-github-pr

FreeSummary

Create GitHub pull requests with the gh command-line tool. Check linked issues, contributor permissions, branch conventions, and relevant tests, then prepare a title and description that follow the project's contribution rules.

  • Submit code changes for review
  • Open a draft pull request
  • Link a pull request to its issue
NVIDIA/OpenShell16.6KUpdated Oct 19, 2026

create-spike

FreeSummary

Investigate a specific OpenShell problem or feature need and create a structured GitHub issue. Record observed behavior, technical findings, alternatives, and missing evidence so a human can decide what to accept and pursue.

  • Investigate an OpenShell bug and document reproduction steps
  • Compare alternatives for a specific feature need
  • Prepare a structured issue for human review
NVIDIA/OpenShell16.6KUpdated Oct 19, 2026

See all skills by NVIDIA

Report a problem with this skill