無料GitHub で公開

feature-radar-archive

Archive a completed, rejected, or covered feature into .feature-radar/archive/ with mandatory learning extraction. MUST use this skill whenever a feature reaches a terminal state — done, rejected, covered, deferred, or N/A — including casual mentions like "we shipped X". The skill extracts learnings, derives new opportunities, and updates refs. Use when the user reports a feature shipped or finished, decides against building one, defers or postpones one, or asks to close or archive an opportunity. Do NOT use for discovering new features — that's feature-radar-scan's job.

日本語の概要は準備中です。原文の説明を表示しています。

runkids/feature-radarスター 14(GitHub 14 + cccskills 0)

実行スコア未検証

インストール方法を見る

含まれるファイル（1）

SKILL.md3.8 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Archive Feature

Move a feature to .feature-radar/archive/ and run the mandatory extraction checklist.

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 feature — ask the user which feature to archive. Check opportunities/ for an existing file to move.
Determine status:
- Done — fully implemented and working
- Covered — existing functionality handles the use case
- Rejected — decided against implementing
- N/A — not applicable to our architecture
- Deferred — valuable but postponed with rationale
Create archive file — write .feature-radar/archive/{nn}-{slug}.md
Checkpoint — Review & Annotate per ../feature-radar/references/WORKFLOW-PATTERNS.md
Run extraction checklist:

Extraction Checklist

<HARD-GATE> Complete ALL 5 checks below. For each check, you MUST explicitly state the finding. Do NOT proceed to step 6 until every check has a written response.

□ archive/{nn}-{slug}.md created with correct status □ Extract learnings → specs/{topic}.md □ Derive new opportunities → opportunities/{nn}-{slug}.md □ Update references → references/{topic}.md □ Update ecosystem trends → specs/ecosystem-trends.md

Acceptable responses per check:

"No learnings to extract" — acceptable, but must be stated
"New opportunity identified: {description}" — create the file
"No reference updates needed" — acceptable, but must be stated
"No ecosystem trend changes" — acceptable, but must be stated </HARD-GATE>

Remove from opportunities — if the feature had an opportunities/ file, delete it
Update base.md — adjust counts in Tracking Summary

Checkpoint: Present extraction results using this format:

Archive: {nn}-{slug} ({status})
| Check | Result |
|-------|--------|
| Learnings | {created specs/X.md / updated specs/X.md / none} |
| Opportunities | {created opportunities/X.md / none} |
| References | {updated references/X.md / none} |
| Ecosystem | {updated specs/ecosystem-trends.md / none} |

Archive File Format

Use the format defined in ../feature-radar/references/SPEC.md § 3.2 (archive/{nn}-{slug}.md).

Guidelines

The extraction checklist is NOT optional. Every archive action must go through all 5 checks.
If the feature was in opportunities/, use the same number. If it's new, use the next available number.
"Deferred" is not a trash bin — include a clear rationale and conditions for re-evaluation.

Example Output

→ Moved opportunities/04-config-merge.md → archive/04-config-merge.md (Done)
→ Learnings: specs/yaml-config-merge.md (new)
→ New opportunity: opportunities/09-config-validation.md
→ References: no updates | Ecosystem: no changes
→ Updated base.md: archive 3→4, specs 2→3

Completion Summary

Follow the template in ../feature-radar/references/DIRECTIVES.md, with skill name "Archive Complete".

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

同じリポジトリのスキル

feature-radar

無料

Full-cycle feature discovery, evaluation, and prioritization. Builds a persistent knowledge base at .feature-radar/ and runs a 6-phase workflow to recommend what to build next. Modes: full (all phases), quick (scan only), evaluate (prioritize), #N (deep-dive one). MUST use this skill whenever the user asks about feature priorities, roadmaps, what to build, or wants to evaluate/compare feature ideas — even if they don't say "feature radar" explicitly. Use when the user wants to decide what to build next, rank or compare features and backlog items, plan a roadmap or project direction, reassess deferred or open opportunities, or mentions the .feature-radar/ directory.

日本語の概要は準備中です。原文の説明を表示しています。