メニュー
Use when a consequential change needs a decision before coding: write or improve an RFC, design doc, architecture proposal, migration plan, option comparison, rollout plan, or measurable implementation contract.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | octocode-rfc-generator |
| description | Use when a consequential change needs a decision before coding: write or improve an RFC, design doc, architecture proposal, migration plan, option comparison, rollout plan, or measurable implementation contract. |
Produce evidence-backed decisions that an implementer and reviewer can execute. Flow:
UNDERSTAND → RESEARCH → PREREQUISITES? → COMPARE → WRITE → CLOSE QUESTIONS → KPIs → VALIDATE → DELIVER.
For existing RFCs, run REASSESS (see references/workflow.md § Reassess existing RFCs) instead of WRITE — audit against live code, not prior checkboxes.
RFC.md owns goals, scope, and decision. Other files link to its anchors rather than restating them..octocode/rfc/ (delete/implemented/fixed calls) always requires a dated ## Audit Reasoning block written into the RFC itself, backed by fresh reads of the live code.RFC.md with plan, acceptance, and inline references.<workspace>/.octocode/rfc/{name}/: RFC.md (decide), PREREQUISITES.md (ready, existing code only), IMPLEMENTATION.md (build), KPI.md (verify), and RESOURCES.md (source appendix).references/workflow.md — select mode, gates, claim ledger, artifact set, traceability, validation, and delivery.references/octocode.md then references/research-playbook.md — delegate exact research and keep claims auditable.references/rfc-template.md — structure options, goals/non-goals, reversibility, and pre-mortem.references/rfc-prerequisites.md before planning — expose baselines, blockers, owners, and setup.references/rfc-implementation.md — close questions, order dependencies, and define rollout/rollback.references/rfc-kpi.md — connect user stories, metrics, decision rules, and verification in a traceability matrix.references/rfc-resources.md — record provenance without moving decisive citations out of the RFC.octocode-eval; otherwise load references/improve-loop.md — enforce measurable accept/revert.octocode-brainstorming before RFC when worth-building is unresolved; octocode-research to close factual questions; octocode-eval for KPI rigor.octocode-awareness while coordinating drafts; octocode-skills when changing this skill folder.scripts/eval-rfc.mjs --case <id> — validate the document contract and report the real result.Use when coordinating work in a shared repo — multi-agent or solo across sessions: collision avoidance, handoffs, verification debt, durable memory/wiki, hooks setup/debug, and repo learning before planning, editing, reviewing, or testing.
Use when an idea needs disciplined exploration before building: generate options, test worth-building, map adjacent solutions, challenge assumptions, narrow scope, or choose Build RFC / Prototype / Narrow / Park — even without saying brainstorm.
Use when browser debugging needs Chrome DevTools evidence: network, console, performance, DOM/CSS, screenshots/PDF, security, cookies/storage, or auth-gated live pages via CDP — not just opening a URL.
Use when writing or updating docs: README, API docs, runbooks, AGENTS.md, CLAUDE.md, ADRs, Diátaxis restructuring, or codebase documentation for humans or coding agents.
Use when measuring whether a change helped: ACCEPT/REVERT, keep/discard, goal→KPI contracts, eval suites, graders, held-out checks, benchmarks, or TDD failing-case-first.
Use when saving tokens with a local Ollama worker while the cloud agent keeps tools and judgment: summarize, extract, classify, translate, article digest after fetch, draft, checklist, vision caption, map-reduce, or phrases like ollama worker, local model, offload, use ollama.