architecture-rfc-review
Skill0 starsChanged 5 months agoMITView on GitHub
Use when reviewing architecture RFCs, system design docs, diagrams, proposals, or technical decision records for tradeoffs, missing constraints, risk, and decision readiness.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when a technical proposal needs a decision-quality review before implementation.
- Distinctive: line 15
Do not use when the task is only code style cleanup or a small isolated bug fix.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture RFC Review
Purpose
Review architecture proposals for clarity, risk, tradeoffs, and readiness to decide.
Fit
- Use when a technical proposal needs a decision-quality review before implementation.
- Do not use when the task is only code style cleanup or a small isolated bug fix.
Inputs
- RFC, design doc, diagram, ADR, or proposal.
- Requirements, constraints, scale expectations, and non-goals if available.
- Existing system boundaries or migration context.
Workflow
- Restate the proposal in one paragraph.
- Identify assumptions, constraints, and missing requirements.
- Review tradeoffs across reliability, operability, cost, security, and complexity.
- List decision blockers separately from nice-to-have improvements.
- Recommend approve, revise, reject, or spike with rationale.
Output
Produce Markdown with:
- Proposal Summary
- Strengths
- Risks And Tradeoffs
- Missing Information
- Decision Blockers
- Recommendation
- Follow-Up Checks
Validation
- Critique is tied to the actual proposal.
- Alternatives are not invented unless clearly labeled.
- Decision blockers are distinct from polish.
- Recommendation includes confidence.
- Operational and security concerns are considered.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

