nickrowlandocom/solo-rfc
A lightweight RFC process for solo developers working with AI agents. Prevents premature complexity by forcing problem-first thinking before jumping to solutions. Use when the user is considering introducing new tools, libraries, architectural patterns, or infrastructure. When they're weighing a significant technical decision. Triggers on phrases like "should I add X", "I'm thinking about introducing Y", "is this overkill", "do I need X", "is X worth it", "/rfc", or when the user is about to adopt a tool/pattern without first articulating the problem it solves.
Overall
score
90%
Does it follow best practices?
Validation for skill structure
rfc-template.mdreferences/
RFC: [Title]
Date: [YYYY-MM-DD] Status: Accepted
Summary
[1-2 sentences: what was decided and why.]
Problem
[The crisp problem statement from Stage 1. What's painful, who's affected, what happens if we do nothing.]
Options Considered
Option A: Do Nothing / Manual Approach
[What the status quo looks like in practice. Be specific about the actual workflow and its costs.]
Option B: [Name]
[Description, what it solves, what it doesn't, complexity and maintenance cost.]
Option C: [Name] (if applicable)
[Description, what it solves, what it doesn't, complexity and maintenance cost.]
Decision
[Which option was chosen.]
Rationale
[Why this option. What tipped the balance. Reference the complexity filter: is this the simplest thing that works at current scale?]
Next Steps
- [Concrete actions to implement the decision]
- [Any trigger points for revisiting: "Reconsider if X happens"]
Install with Tessl CLI
npx tessl i nickrowlandocom/solo-rfc@0.1.0