Skip to content

nghyane/luma / .agents/skills/rfc

Workflow for creating, updating, or superseding RFCs in Luma. Use when the task involves opening a new RFC, updating RFC status, marking an RFC as superseded or implemented, or deciding whether a change needs an RFC at all.

RFC Workflow in Luma

Source of truth

docs/rfcs/README.md — contains the full RFC index with current status. docs/rfcs/0000-template.md — canonical template for new RFCs.

Always read these two files before creating or updating any RFC. If they do not exist, create docs/rfcs/ and bootstrap both files before proceeding.

When to open an RFC

RFC is required for:

  • cross-cutting architecture changes (provider, core, config, wire format);
  • changes to prompt assembly layers or instruction loading model;
  • breaking changes to user-facing CLI or config;
  • changes to memory taxonomy or source-of-truth hierarchy.

RFC is NOT required for:

  • prompt wording patches;
  • tool description tweaks;
  • heuristic tuning;
  • bugfix or local refactor;
  • adding tests or docs.

Only open an RFC when there is local evidence or session evidence. Do not open an RFC for brainstorming without evidence.

Creating a new RFC

  1. Read docs/rfcs/README.md to find the next available number.
  2. Copy docs/rfcs/0000-template.md to docs/rfcs/NNNN-short-name.md.
  3. Fill in the metadata header. Set Status: Draft.
  4. Fill in Summary, Motivation, and Reference-level explanation.
  5. Add the new RFC to the table in docs/rfcs/README.md.

Updating an RFC

  • Update the Updated date in the metadata header.
  • Update Status when the state changes.
  • Update Implementation status section when code ships.

Valid status values

  • Draft — open for discussion, not yet accepted.
  • Accepted — approved, implementation in progress.
  • Implemented — fully shipped.
  • Superseded — replaced by another RFC or by a direct code/prompt patch. Set Superseded by field.
  • Withdrawn — no longer pursued. Keep the file, record the reason.

When to supersede

Supersede an RFC when:

  • a newer RFC covers the same ground more accurately;
  • the core intent was implemented directly in code or prompt without needing the full RFC scope.

When superseding, set Status: Superseded and fill in Superseded by with the RFC number or a short description of what replaced it.

Patch nearest layer first

Before opening an RFC, check whether the change can be made as a direct patch:

  • tool description → edit the tool's description string in src/tool/;
  • behavior guidance → edit src/config/prompt/smart.md or the relevant mode file;
  • tool usage policy → edit src/config/prompt/tools_native.md or tools_patch.md;
  • project conventions → edit AGENTS.md.

Only escalate to RFC if the change is cross-cutting and cannot be contained in one layer.

planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall