runkids/feature-radar/feature-radar-learn
- community
Checking that the SKILL.md file is still in the repository.
Extract reusable patterns, architectural decisions, and pitfalls from completed work into .feature-radar/specs/. Captures the "why" behind choices so future sessions build on past experience. MUST use this skill when the user reflects on what worked or didn't, wants to record a decision or pattern for future use, or hit a dead end worth documenting. Use when the user asks to remember, document, or extract lessons from recent work. Do NOT use for recording external observations — that's feature-radar-ref's job. Do NOT use for archiving completed features — that's feature-radar-archive's job.
Install
npx vskill@latest install runkids/feature-radar/feature-radar-learnSKILL.md
Extract Learnings
Capture reusable knowledge from completed work into .feature-radar/specs/.
Deep Read
<HARD-GATE> Read and follow ../feature-radar/references/DEEP-READ.md — complete all 6 steps before proceeding. </HARD-GATE>
Behavioral Directives
<HARD-GATE> Read and follow ../feature-radar/references/DIRECTIVES.md. </HARD-GATE>
Workflow
- Identify the source — ask the user what was just completed (feature, bug fix, refactor, investigation)
- Analyze the work — review recent commits, changed files, and implementation decisions
- Extract knowledge — classify each reusable piece into exactly one category, and state the classification in your output:
- Pattern: recurring solution worth replicating (e.g., "three-tier config merge")
- Decision: architectural choice with rationale (e.g., "YAML over JSON because...")
- Pitfall: mistake or dead end to avoid
- Technique: implementation approach that worked well
- Write to specs — create or append to
.feature-radar/specs/{topic}.md - Checkpoint — State what was written and ask: "I've written to
specs/{topic}.md({classification type}). Does this look correct, or should I adjust anything?" Wait for user confirmation before proceeding. - Update base.md — increment the specs count in Tracking Summary
File Format
Use the format defined in ../feature-radar/references/SPEC.md § 3.4 (specs/{topic}.md).
Guidelines
- One topic per file. If the learning spans multiple topics, create multiple files.
- Name files by the pattern, not by the feature that produced it.
- Good:
yaml-config-merge.md,symlink-vs-copy-tradeoffs.md - Bad:
audit-feature-learnings.md,v2-refactor-notes.md - Append to existing files when the new learning extends a known topic.
- Keep it concise — future readers need the insight, not the full story.
Example Output
Completion Summary
Follow the template in ../feature-radar/references/DIRECTIVES.md, with skill name "Learn Complete".
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/feature-radar-learn/SKILL.md
Popularity
- 7-day trend score
- 0
Refreshed 18 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/runkids/feature-radar/feature-radar-learn)