What problem does it solve?
Consequential code changes fail when decisions live only in chat: alternatives disappear, assumptions go untested, and rollback plans are discovered too late. This Skill turns research into a reviewable decision document before risky work begins.
Core Features & Use Cases
- Decision Documents: Writes RFCs, design docs, architecture proposals, migration plans, and option comparisons with goals, non-goals, alternatives, and pre-mortem analysis.
- Evidence-Backed Claims: Gathers current-state proof from local code, GitHub paths, PRs, commits, and packages via Octocode, citing exact file:line anchors for every recommendation.
- Structured Artifact Set: Produces RFC.md, PREREQUISITES.md, IMPLEMENTATION.md, KPI.md, and RESOURCES.md under .octocode/rfc/{name}/ with dependency-ordered steps, rollout/rollback plans, and measurable success criteria.
- Use Case: Before migrating a production database schema, ask the agent to compare migration strategies, document current-state constraints, and produce an RFC with a phased rollout plan and rollback triggers that reviewers can approve.
Quick Start
Ask the agent to write an RFC for your planned change, for example: draft an RFC comparing two approaches for migrating our authentication service, with evidence from the current codebase.