srekit rfc¶
Generate an RFC / ADR scaffold with Context, Decision, Alternatives, Consequences, References. Status field is validated.
Synopsis¶
Flags¶
| Flag | Required | Description |
|---|---|---|
--title |
yes | RFC subject |
--status |
no | One of proposed, accepted, rejected, superseded, deprecated. Default: proposed. |
--author |
no | Override author (resolved like license) |
--email |
no | Override email |
Plus the shared output flags. Default filename: rfc-<slug-of-title>.md.
Examples¶
Accept upgrade:
Invalid status rejected:
srekit rfc --title "X" --status maybe --stdout
# Error: --status must be one of proposed|accepted|rejected|superseded|deprecated
Section structure¶
- Front matter:
title,status,tags,id - Контекст (Context)
- Решение (Decision)
- Альтернативы (Alternatives)
- Последствия (Consequences) — split into Positive / Negative / Neutral
- Ссылки (References)
Template shape¶
rfc ships as a v1 YAML artifact (internal/tmpl/templates/rfc.yaml) — frontmatter (id, status, type: rfc, title, deciders, supersedes, …), H1 (RFC-<shortID> — <title>), meta_bullets, sections (context, decision, alternatives_considered, consequences, references). Template expressions reference .Meta.<Field> for ID, Title, Status, Now, Author.Name, Author.Email. See srekit postmortem for the full schema reference.