Individual skill

octocode-rfc-generator

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. If the idea is still open-ended, use octocode-brainstorming first.

skills/octocode-rfc-generator/SKILL.md

Read pinned source

Source commit c265e3f9413161c900cbf4aa70d451b8e6b3920a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 957
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
claude-ai Repository topic
cursor-ai Repository topic
development Repository topic
mcp Repository topic
modelcontextprotocol Repository topic
octocode Repository topic
ai-agents Repository topic
ai-tools Repository topic
code-intelligence Repository topic
engineering Derived category
design Derived category
legal Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 4,232 bytes
SKILL.mdcore · 4,381 bytes
SKILL.mdcore · 4,381 bytes
references/improve-loop.mddoc · 677 bytes
references/octocode.mddoc · 939 bytes
references/research-playbook.mddoc · 2,988 bytes
references/rfc-audit.mddoc · 1,446 bytes
references/rfc-implementation.mddoc · 1,793 bytes
references/rfc-kpi.mddoc · 1,666 bytes
references/rfc-prerequisites.mddoc · 1,551 bytes
references/rfc-resources.mddoc · 1,293 bytes
references/rfc-template.mddoc · 2,437 bytes
references/workflow.mddoc · 4,451 bytes

Read excerpt


# Octocode RFC Generator

Produce evidence-backed decisions that an implementer and reviewer can execute.
Flow: `UNDERSTAND → RESEARCH → PREREQUISITES → COMPARE → WRITE → CLOSE QUESTIONS → KPI → VALIDATE → DELIVER`.
For existing RFCs, run `REASSESS` (see `references/workflow.md` § Reassess existing RFCs) instead of WRITE — audit against live code, not prior checkboxes.

## Lobby rules
- Skip RFC mode for trivial edits. Ask one focused question when uncertainty changes shape, owner, scope, or decision criteria.
- Compare at least two alternatives, including do-nothing, unless the user explicitly requests one implementation plan.
- Recommendations require verifiable facts; cite exact anchors and commands/checks that actually ran.
- `RFC.md` owns goals, scope, and decision. Other files link to its anchors rather than restating them.
- Resolve every open question with evidence or an explicit deferral; no recommendation may rest on an uncertain claim.
- Order implementation by dependency, not estimates; bind requirements to acceptance and verification.
- Reviewing, rating, or cleaning up `.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.