From harness-kit
> Use when: You need to track and triage new AI engineering ideas over time for possible adoption in
How this skill is triggered — by the user, by Claude, or both
Slash command
/harness-kit:ai-techniques-radarThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Use when: You need to track and triage new AI engineering ideas over time for possible adoption in
Use when: You need to track and triage new AI engineering ideas over time for possible adoption in this repository.
Capture high-signal external ideas as concise entries in committed memory, then triage them into adopted, parked, or rejected decisions using the harness loop model.
Before capturing or triaging entries, read these repository surfaces:
.github/harness/memory/radar/README.md.github/harness/memory/radar/_template.md.github/harness/loops/technique-triage.json.github/harness/memory/radar/.github/harness/memory/radar/ using _template.md.technique-triage to classify each candidate.Every entry should follow the current template and include:
candidate, adopted, parked, or rejectedKeep one idea per file. If two ideas have different adoption paths, split them.
Use the technique-triage loop as a review-only gate. For each candidate:
adopted: worth pursuing as a real local taskparked: promising but not worth immediate adoptionrejected: intentionally not suitable hereDecision Log.adopted, define a concrete next step and point to the likely target files/domains.The loop must not implement code directly. Triage and route only.
An entry should move to adopted only when all of these are true:
If an idea is interesting but the local application is vague, leave it parked.
For any radar entry centered on adopting an external skill file or skill-pack pattern:
skillspector scan <path> --no-llm when available, orDo not mark a skill-file entry as adopted without the scan result or waiver being captured in the
entry.
Adopted ideas do not go straight to implementation. They must become a normal harness task:
When an adopted idea ships, update the radar entry with the resulting brief, files, or PR/commit reference.
A practical maintenance rhythm for this repo:
technique-triage on a regular cadence (for example weekly)Use these defaults unless the evidence strongly points elsewhere:
adopted: concrete repo problem, clear target surface, bounded next stepparked: interesting, but not current-priority or not yet sufficiently groundedrejected: conflicts with repository constraints, duplicates existing practice, or lacks enough
value to justify adoptioncandidate indefinitely without periodic triageTools like mvanhorn/last30days-skill can be used by individual developers as a local discovery aid.
Before concluding a radar session:
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub dfintz/fintz-harness-kit --plugin harness-kit