メニュー
Look up and cite international protocol standards (RFC/IEEE) (TR-F021). Any change to RADIUS/EAP/accounting/CoA/IPv6 protocol behavior should first check docs/rfcs and cite the clause.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review merged PRs since the last Git tag and decide whether a ToughRADIUS release is warranted. Use when Codex is asked to prepare a version release, audit unreleased changes, decide whether to publish, create a new release tag, or tag origin/main after PR review.
Global orchestrator / dispatcher role. Activated when the user issues an "auto-delegate development / continue the roadmap / auto-delegate" command (without naming a specific subtask); runs the full loop - select task, pick SOP, dispatch, quality gates, open PR, self-iterate the roadmap.
Independent review gate for auto-delegation PRs (TR-F022). Use after an orchestration round opens a PR, and as the first step of every new round to clear in-flight PRs - run an adversarial, CI-anchored review, request changes via labels + comments, and auto-merge only when the review passes and CI is green.
Standard-library-style Go API documentation and comment conventions (TR-F024). Use when adding or changing exported Go identifiers, writing package comments, or backfilling godoc on a package so it reads like the Go standard library.
Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.
Add a group of Admin REST endpoints in the management backend (TR-F012). Use when a feature needs management APIs such as create/read/update/delete.
| name | reference-rfc |
| description | Look up and cite international protocol standards (RFC/IEEE) (TR-F021). Any change to RADIUS/EAP/accounting/CoA/IPv6 protocol behavior should first check docs/rfcs and cite the clause. |
Feature ID:
TR-F021(protocol material) | Scope: all protocol-related changes
Any change to RADIUS / EAP / accounting / CoA / IPv6 protocol behavior must cite the corresponding international standard clause (RFC / IEEE, etc.), preferring material already in the repo.
The repo's docs/rfcs/ already holds 50+ RFCs (see docs/rfcs/README.md); common ones:
| Topic | File |
|---|---|
| RADIUS auth / accounting | rfc2865-radius-authentication.txt / rfc2866-radius-accounting.txt |
| RADIUS extensions / protocol extensions | rfc2869-radius-extensions.txt / rfc6929-protocol-extensions.txt |
| RADIUS carrying EAP | rfc3579-radius-eap-support.txt |
| EAP framework / EAP-TLS / TTLS / TEAP | rfc3748-eap.txt / rfc5216-eap-tls.txt / rfc5281-eap-ttls.txt / rfc7170-teap.txt |
| Fragmentation | rfc7499-packet-fragmentation.txt |
| Dynamic authorization / CoA | rfc3576-dynamic-authorization.txt / rfc5176-coa-disconnect.txt |
| IPv6 / prefix delegation | rfc3162-radius-ipv6.txt / rfc4818-ipv6-prefix-delegation.txt / rfc6911-ipv6-access-networks.txt |
| RadSec / RADIUS over TCP | rfc6614-radsec.txt / rfc6613-radius-over-tcp.txt |
| Status-Server / implementation issues | rfc5997-status-server.txt / rfc5080-implementation-issues.txt |
Search:
grep -rni "Message-Authenticator" docs/rfcs/
view docs/rfcs/rfc5216-eap-tls.txt
ls docs/rfcs/ | grep <number>).docs/rfcs/FILE-NAMING.md (e.g. rfcXXXX-<slug>.txt).docs/rfcs/README.md index, noting the implemented or to-be-implemented feature ID.// per RFC 5216 section 2.1.5, fragment via EAP-TLS Length+More-Fragments).TR-F021 boundary).