メニュー
Create a new RFC (Request for Comments / design document) for a planned feature or significant change. Saves to docs/rfcs/ following the RFC-NNN naming convention.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-rfc |
| description | Create a new RFC (Request for Comments / design document) for a planned feature or significant change. Saves to docs/rfcs/ following the RFC-NNN naming convention. |
Before implementing:
List files in docs/rfcs/ and find the highest RFC number, then increment.
Create docs/rfcs/RFC-<NNN>-<short-title>.md:
# RFC-<NNN>: <Title>
**Status**: Draft | Accepted | Implemented | Superseded
**Date**: YYYY-MM-DD
**Author**: @lqdev
## Summary
One paragraph: what is this RFC proposing?
## Motivation
Why is this change needed? What problem does it solve?
What is the current limitation?
## Detailed Design
### Data Model Changes (if any)
```rust
// New or modified structs/enums
// New or modified functions/traits
{
"section": {
"new_field": "default_value"
}
}
| Option | Pros | Cons | Verdict |
|---|---|---|---|
| Option A | ... | ... | Chosen |
| Option B | ... | ... | Rejected because ... |
Document non-obvious choices inline as numbered design decisions:
Design Decision #N: We chose X over Y because...
### 3. Update the status when implemented
Change `**Status**: Draft` to `**Status**: Implemented` and add a reference to the implementing PR/commit.
Add a new device profile to podcast-tui's config.json so episodes sync to an MP3 player / DAP / USB drive with device-appropriate filenames and folder layout. Covers device research, field selection, and safe config editing.
Prepare a new release by finalizing CHANGELOG, tagging, and verifying builds. Covers everything before pushing the tag that triggers CI.
Query the GitHub project board to find the next stack-ranked issue to work on. Returns the top actionable Todo item from the Task List view, checking issue dependencies and filtering out epics, closed issues, and blocked items.
Reorder items on the Task List project board to reflect current priorities. Supports full strategic reranks and targeted insertions. Always shows proposed order for user confirmation before executing.
Write a checkpoint file at session end so the next session can pick up exactly where you left off. Captures what was done, what's next, key decisions, and reminders.
Bootstrap a new session from a previous session's checkpoint. Reads the handoff file, confirms the project board state, and prepares to continue work.