How do I install the Propose Jep skill?

Run npx skillmds@latest add jumpstarter-dev/propose-jep in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Propose Jep skill do?

Create a new Jumpstarter Enhancement Proposal (JEP) It is listed under Coding & Dev Tools on SkillMD.

Is Propose Jep safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Propose Jep?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Propose Jep free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Propose Jep?

jumpstarter-dev (@jumpstarter-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Propose Jep by jumpstarter-dev — Agent Skill

Name: Propose Jep
Rating: 4.5 (4 reviews)
Author: jumpstarter-dev

File contents

Propose a JEP

You are helping the user create a new Jumpstarter Enhancement Proposal (JEP).

Context

JEPs are design documents for substantial changes to the Jumpstarter project - changes that affect multiple components, alter public APIs or protocols, or require community consensus. Read .cursor/rules/jep-process.mdc for the full process definition.

JEP topic: $ARGUMENTS

Steps

1. Determine the next JEP number

List existing files in docs/source/contributing/jeps/ and pick the next available incrementing integer. JEP-0000 through JEP-0009 are reserved for process/meta-JEPs, so start from JEP-0010 for regular proposals.

2. Gather information

Before writing the JEP, ask the user clarifying questions to understand:

What problem does this solve? - The motivation section needs a concrete problem description.
Who is affected? - Which components, drivers, or user workflows are impacted?
What are the alternatives? - Each design decision needs at least two alternatives considered.
What are the compatibility implications? - Does this break existing APIs, protocols, or workflows?

If the user provided a description in $ARGUMENTS, use it as a starting point but still ask about gaps.

3. Create the JEP file

Copy the template from docs/source/contributing/jeps/JEP-NNNN-template.md and create a new file at docs/source/contributing/jeps/JEP-NNNN-short-title.md where:

NNNN is the zero-padded next number
short-title is a descriptive slug derived from the proposal title

Fill in:

The metadata table with the JEP number, title, author (ask the user), status Draft, type, and today's date
All mandatory sections based on the information gathered
Mark optional sections that need further input with TODO comments

4. Update the JEP index

Add the new JEP to the appropriate table in docs/source/contributing/jeps/index.md (Process, Standards Track, or Informational).

Add the new JEP file to the {toctree} directive at the bottom of docs/source/contributing/jeps/index.md.

5. Present the result

Show the user:

The file path of the new JEP
A summary of sections that are complete vs need further work
Remind them to set status to Discussion when the PR is ready for review
Remind them to apply the jep label to their pull request

---name: propose-jepdescription: Create a new Jumpstarter Enhancement Proposal (JEP)---# Propose a JEPYou are helping the user create a new Jumpstarter Enhancement Proposal (JEP).## ContextJEPs are design documents for substantial changes to the Jumpstarter project - changes that affect multiple components, alter public APIs or protocols, or require community consensus. Read `.cursor/rules/jep-process.mdc` for the full process definition.JEP topic: $ARGUMENTS## Steps### 1. Determine the next JEP numberList existing files in `docs/source/contributing/jeps/` and pick the next available incrementing integer. JEP-0000 through JEP-0009 are reserved for process/meta-JEPs, so start from JEP-0010 for regular proposals.### 2. Gather informationBefore writing the JEP, ask the user clarifying questions to understand:- **What problem does this solve?** - The motivation section needs a concrete problem description.- **Who is affected?** - Which components, drivers, or user workflows are impacted?- **What are the alternatives?** - Each design decision needs at least two alternatives considered.- **What are the compatibility implications?** - Does this break existing APIs, protocols, or workflows?If the user provided a description in `$ARGUMENTS`, use it as a starting point but still ask about gaps.### 3. Create the JEP fileCopy the template from `docs/source/contributing/jeps/JEP-NNNN-template.md` and create a new file at `docs/source/contributing/jeps/JEP-NNNN-short-title.md` where:- `NNNN` is the zero-padded next number- `short-title` is a descriptive slug derived from the proposal titleFill in:- The metadata table with the JEP number, title, author (ask the user), status `Draft`, type, and today's date- All mandatory sections based on the information gathered- Mark optional sections that need further input with TODO comments### 4. Update the JEP indexAdd the new JEP to the appropriate table in `docs/source/contributing/jeps/index.md` (Process, Standards Track, or Informational).Add the new JEP file to the `{toctree}` directive at the bottom of `docs/source/contributing/jeps/index.md`.### 5. Present the resultShow the user:- The file path of the new JEP- A summary of sections that are complete vs need further work- Remind them to set status to `Discussion` when the PR is ready for review- Remind them to apply the `jep` label to their pull request

Frequently asked questions

Propose Jep