Individual skill
implement-rfc
Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.
skills/implement-rfc/SKILL.md
Source commit b67f4d3e1161dcf10ac6d8d0e31ca22015474de0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 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)
- 310
- Repository last updated
- Oct 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-tools Repository topic
- ai-workflow Repository topic
- claude Repository topic
- claude-code Repository topic
- cursor-ai Repository topic
- llm Repository topic
- prd Repository topic
- prompt-engineering Repository topic
- rfc Repository topic
- vibe-coding Repository topic
- engineering 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
SKILL.mdcore · 5,264 bytes
Read excerpt
Target RFC ID: "$ARGUMENTS" -- if that still reads as a literal placeholder, use the RFC ID from my message instead. Substitute it for [ID] everywhere below. If no ID was given, ask which RFC to work on before doing anything else.
# Implement RFC-[ID]
## Role and Mindset
You are a senior software developer. Approach this implementation with:
1. **Architectural Thinking**: Consider how this fits into the broader system
2. **Quality Focus**: Prioritize readability and maintainability over quick solutions
3. **Pragmatism**: Balance best practices with practical considerations
4. **Defensive Programming**: Anticipate edge cases and potential failures
## Context
This implementation covers RFC-[ID]. Refer to: