Skip to content

RFC Index

Request for Comments (RFCs) are how the PromptPack specification evolves. Each substantial change — a new entity type, a major capability, a breaking schema change — starts as an RFC, gets discussed in public, and lands in the spec when it’s accepted and implemented.

For the process itself (lifecycle, template, criteria), see the RFC Process.

Status

StatusMeaning
DraftInitial proposal under discussion
ReviewFormal review period, seeking feedback
AcceptedApproved for implementation
ImplementedMerged into the specification
DeferredPostponed to future consideration
RejectedNot accepted (with reasoning in the RFC)

RFCs

#TitleStatusSpecCreatedUpdated
RFC-0001Core PromptPack SchemaImplementedv1.02025-10-012025-10-31
RFC-0002YAML File FormatImplementedv1.02025-10-052025-10-31
RFC-0003Template Variable SystemImplementedv1.02025-10-102025-10-31
RFC-0004Multimodal Content SupportImplementedv1.12025-11-062025-11-15
RFC-0005PromptPack Workflow Specification ExtensionImplementedv1.32025-11-172025-11-17
RFC-0006Evals ExtensionImplementedv1.22026-02-142026-02-14
RFC-0007Agents ExtensionImplementedv1.32026-02-152026-02-15
RFC-0008Skills ExtensionImplementedv1.3.12026-02-212026-02-21
RFC-0009Agent Loop ExtensionImplementedv1.42026-03-262026-04-18
RFC-0010Workflow Composition ExtensionImplementedv1.5.02026-04-282026-06-15
RFC-0011Workflow States as AgentsImplementedv1.4.12026-06-132026-06-13
RFC-0012Provider RequirementsImplementedv1.5.12026-06-252026-06-25

At a Glance

Count
Total RFCs12
Implemented12
Draft0
In Review0
Rejected0

Propose an RFC

Have an idea for the spec? Start here:

  1. Read the RFC Process for the lifecycle, template, and review criteria
  2. Discuss the idea first in GitHub Discussions to gauge interest
  3. Draft an RFC using the proposal template
  4. Submit a pull request against altairalabs/promptpack-spec

Start your RFC →