uncovertechtalent/cto-powersuit / plugins/decisions/skills/rfc
rfc
VerifiedWrite a request for comments (RFC) from a problem statement and run it to a decision: draft, open for comments until comments_close, decide, then hand the outcome to the adr skill, which writes the decision record and links back. Use when a change touches more than one team, is hard to undo or needs comments before a decision. Never overwrites a file. Activates on "/rfc", "write an RFC", "draft an RFC", "request for comments", "propose a change for review", "open the RFC for comments", "close the RFC".
RFC
Turns a problem statement into an RFC file in the decision log, opens it for comments with a fixed closing date, and closes it with a recorded outcome. The RFC holds the proposal and the discussion. The decision itself goes into an ADR, written by the adr skill.
Lifecycle: draft, then review (open for comments until comments_close), then accepted, rejected or withdrawn.
Inputs
- Problem statement (required): what is wrong or missing, in the user's words.
- Owner: the person who drives the RFC to a decision. Ask if not given.
- Reviewers: names or teams who must comment. Ask if not given.
- Comment window: default 14 days from the day the RFC opens for comments.
- Folder: default
docs/decisions/at the repository root.
Steps
-
Set up the folder. If
docs/decisions/index.mdordocs/decisions/_templates/is missing, copy the templates without overwriting:mkdir -p docs/decisions rsync -a --ignore-existing "${CLAUDE_PLUGIN_ROOT}/templates/docs/decisions/" docs/decisions/Without rsync, use
cp -Rn "${CLAUDE_PLUGIN_ROOT}/templates/docs/decisions/." docs/decisions/. List the files copied and the files skipped. -
Check the problem statement. It needs who is affected, how often or how much, and what happens if nothing changes. Ask at most three questions for the missing parts. Do not invent numbers.
-
Look for earlier records. Search the titles and summaries of
docs/decisions/rfc-*.mdanddocs/decisions/adr-*.mdfor the same subject. If an open RFC covers it, stop and point the user to it. If an accepted ADR covers it, the RFC must name that ADR and say whether the proposal would supersede it. -
Pick the number. Next number = highest existing RFC number + 1, from file names and
rfc:fields:python3 - docs/decisions rfc <<'EOF' import re, sys, pathlib d, kind = pathlib.Path(sys.argv[1]), sys.argv[2] nums = [0] for p in d.glob(f"{kind}-[0-9]*.md"): nums.append(int(re.match(rf"{kind}-(\d+)", p.name).group(1))) m = re.search(rf"^{kind}:\s*\"?(\d+)", p.read_text(encoding="utf-8"), re.M) if m: nums.append(int(m.group(1))) print(f"{max(nums) + 1:04d}") EOFThe slug is
rfc-NNNN-short-name: the number and two to five lowercase words joined by hyphens. Runtest -e docs/decisions/<slug>.md. If the file exists, never overwrite it: take the next free number. -
Draft. Start from
docs/decisions/_templates/rfc.md(or${CLAUDE_PLUGIN_ROOT}/templates/docs/decisions/_templates/rfc.mdif the repository has none). Fill the front matter:status: draft,dateandreviewedtoday,review_by90 days later,owner,reviewers,comments_closeempty until step 7,decisionempty. Write every section:- Summary: problem, proposal and expected result in two or three sentences.
- Problem: facts from step 2, with numbers where the user gave them.
- Proposal: the systems, files, owners and interfaces it touches.
- Alternatives considered: at least two, one of them doing nothing, each with the reason it is not the proposal.
- Risks and open questions: the questions the reviewers must answer.
- Rollout and rollback: ordered steps, the undo and the signal that starts the undo.
- Decision: one line,
Open. No decision yet.
Replace every
<placeholder>. Quote any front matter value that contains ": ". Compute dates withpython3 -c 'import datetime as d; print(d.date.today() + d.timedelta(days=90))'. -
Show the draft. Print the path and the summary, and ask the owner to read it. Apply their edits.
-
Open for comments. When the owner says the draft is ready: set
status: reviewandcomments_close(today plus the comment window). Add the RFC to the index, as the Index section of theadrskill describes. Comments go on a pull request that adds the RFC file, unless the overlay names another channel. Tell the user to send the pull request link to every reviewer. -
Close. On or after
comments_close, or when the owner asks for an early close:- Collect the comments. With the GitHub CLI:
gh pr view <number> --comments. - List each open question from the RFC with its answer, or mark it unanswered.
- List reviewers who did not comment.
- Ask the owner for the outcome: accepted, rejected or withdrawn. The owner decides. Never pick the outcome yourself.
- Collect the comments. With the GitHub CLI:
-
Record the outcome.
- Accepted or rejected: run the
adrskill with this RFC as input. The ADR getsrfc: <rfc slug>and statusacceptedorrejected. Then set the RFC'sstatusto the outcome anddecision: <adr slug>, and fill the Decision section: outcome, date, who decided, link to the ADR, and the open questions that stay open. - Withdrawn: set
status: withdrawn, leavedecisionempty, and write the reason in the Decision section. No ADR.
- Accepted or rejected: run the
-
Update the index and report.
Output
The RFC path, its number and status, comments_close when open, the reviewers, and the next step: open for comments, close on the date, or the ADR slug after a decision.
Rules
- Never overwrite or delete a file. Never reuse a number, also not the number of a withdrawn RFC.
- One problem per RFC. Split a statement that holds two problems and ask which one comes first.
- After close, the RFC body stays as it was at close. Only the front matter fields
status,decision,reviewedandreview_byand the Decision section change. A new proposal on the same subject is a new RFC. - A comment window shorter than 5 days needs the owner's explicit go.
- Dates are ISO
YYYY-MM-DD. - A written RFC holds no
<placeholder>and none of the words that the gate's placeholder rule flags.
Overlay
This skill works on the generic defaults in this file. Before you start, check for a private overlay:
[ -n "$POWERSUIT_OVERLAY" ] && ls -1 "$POWERSUIT_OVERLAY/decisions" 2>/dev/null || true
If $POWERSUIT_OVERLAY/decisions/ exists, read its README.md first, then the files in decisions/rfc/ if that folder exists. Read other overlay files only when that README or this skill names them. Where the overlay and this file disagree, follow the overlay. If the variable is unset or the folder is missing, use the defaults and do not ask for an overlay. If the permission settings block the command, use the defaults and say in your output that the overlay was not checked. Never copy overlay content into this plugin, into its templates or into any public repository.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |