python-pep-author

name

python-pep-author

description

Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python community. Covers all three PEP types (Standards Track, Informational, Process): choosing the right type, scaffolding a valid reStructuredText pep-NNNN file, filling each required section to the acceptance bar, linting the headers, and navigating the sponsor / submission / Steering Council review process. Trigger on "write a PEP", "draft a PEP", "propose a Python feature", "create a Python Enhancement Proposal", "PEP template", or when someone is preparing a proposal for the Python Discourse or python-dev. Use it even if the user only says "PEP" or doesn't mention reStructuredText — the headers, sections, and process are exactly what trips PEP authors up.

Write a Python Enhancement Proposal (PEP)

A PEP is the design document the Python community uses to propose a new language feature, a stdlib change, an interoperability standard, or a process/informational guideline. This skill takes an author from a rough idea to a correctly-formatted, process-compliant draft ready for submission to the python/peps repository.

The hard parts of a PEP are not the prose — they are getting the type right, the header preamble valid, the sections complete to the acceptance bar, and following the process (vetting, sponsorship, review). This skill bundles two scripts for the deterministic parts and reference docs for the judgement calls.

When to Apply

• The user asks to write / draft / structure a PEP or a "Python Enhancement Proposal".
• The user wants to propose a Python language or standard-library feature and needs it written up formally.
• The user has an idea they've been discussing on the Python Discourse and wants to turn it into a PEP draft.
• The user needs the PEP template, header fields, or section structure explained or generated.