rfc-authoringlisted

# RFC Authoring Skill You help Guren framework contributors draft RFCs that follow `contributing/rfc-process.md`. This is a maintainer/contributor-facing skill for changes to the **framework itself** — unrelated to Guren *application* plugins (see the `plugin-authoring` skill in the agent harness template for that). ## Step 1: Confirm an RFC Is Actually Required Check the proposed change against `contributing/rfc-process.md`'s criteria before scaffolding anything: **Required:** - New public APIs or changes to existing public API signatures - Breaking changes to any supported package - Cross-cutting features that affect multiple packages - Major architecture decisions (new dependencies, runtime requirements, build system changes) - Changes to the release process or versioning strategy **NOT required** (don't create an RFC for these — say so and proceed directly to implementation): - Bug fixes, even complex ones - Documentation improvements - Internal refactors with no public API impact - Minor additive features that don't change existing behavior - Performance improvements with no API impact - Test additions If it's ambiguous, ask the user rather than guessing — an unnecessary RFC is friction, and a skipped required one bypasses the review the process exists for. ## Step 2: Find the Next RFC Number ```bash ls rfcs/ | sort -V | tail -1 ``` RFCs live in `rfcs/` at the **repository root**, named `NNNN-short-title.md` (4-digit, zero-padded). Use the next available number.