Install the "aif-archive" agent skill from https://github.com/unxed/f4/tree/main/.agents/skills/aif-archive into .claude/skills/aif-archive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aif-archive", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add unxed/f4 --skill aif-archive -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "aif-archive" agent skill from https://github.com/unxed/f4/tree/main/.agents/skills/aif-archive into .agents/skills/aif-archive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aif-archive", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add unxed/f4 --skill aif-archive -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "aif-archive" agent skill from https://github.com/unxed/f4/tree/main/.agents/skills/aif-archive into .cursor/skills/aif-archive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aif-archive", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add unxed/f4 --skill aif-archive -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "aif-archive" agent skill from https://github.com/unxed/f4/tree/main/.agents/skills/aif-archive into .gemini/skills/aif-archive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aif-archive", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install unxed/f4 aif-archive
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add unxed/f4 --skill aif-archive -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "aif-archive" agent skill from https://github.com/unxed/f4/tree/main/.agents/skills/aif-archive into .github/skills/aif-archive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aif-archive", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add unxed/f4 --skill aif-archive -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "aif-archive" agent skill from https://github.com/unxed/f4/tree/main/.agents/skills/aif-archive into .opencode/skills/aif-archive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aif-archive", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
aif-archive
GitHub stars
243
Token cost
~3.2k tokens
SKILL.md length
1,237 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
BSD-3-Clause
At a glance
Archive completed plans and roadmap milestones. An agent skill from unxed/f4.
Works in 3 steps: Load Config → Parse Arguments → Execute Mode
User says archive plans
SKILL.md covers Workflow, Important Rules and Artifact Ownership
Calls git
What it does
Aif Archive is an agent skill from unxed/f4. Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management. The repository describes itself as: dual pane like a charm. The licence is BSD-3-Clause.
Read from SKILL.md and the folder at commit 772edc7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Read
Write
Edit
Glob
Grep
Bash(mv *)
Bash(mkdir *)
Bash(git *)
AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Aif Archive loads about 3.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,237 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~64
When it runs· the whole SKILL.md, loaded when a task matches
~3.2k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/aif-archive/SKILL.md (or your agent's skills folder).
name
aif-archive
description
Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".
Archive — Move completed plans and roadmap snapshots
Archive completed single-file plans and ultra bundle directories from
paths.plans/ into paths.archive/plans/ and
optionally trim closed milestones from ROADMAP.md into dated snapshots
under paths.archive/roadmap/.
Workflow
Step 0: Load Config
Read .ai-factory/config.yaml if it exists to resolve:
paths.plans (default: .ai-factory/plans/)
paths.archive (default: .ai-factory/archive/)
paths.plan (default: .ai-factory/PLAN.md)
paths.fix_plan (default: .ai-factory/FIX_PLAN.md)
paths.roadmap (default: .ai-factory/ROADMAP.md)
workflow.plan_id_format (default: slug) — active values: slug and
sequential. timestamp and uuid are reserved and behave like slug.
Treat any unknown value as slug.
language.ui for user-facing prompts
If config doesn't exist, use defaults listed above.
Read .ai-factory/skill-context/aif-archive/SKILL.md if it exists —
project-specific overrides take priority over general instructions.
Step 1: Parse Arguments
Extract mode from arguments:
(no args) → interactive mode: scan, show completable plans, ask which to archive
list → show archive contents, then STOP
--roadmap → trim closed milestones from ROADMAP.md into a snapshot
--all → archive ALL completed plans (ask confirmation first)
<plan-name> → archive a specific plan by filename or partial stem match
Parsing rules:
list and --roadmap are mutually exclusive with <plan-name> and --all
If multiple conflicting modes are given, emit error and STOP
<plan-name> can be:
full filename: 0005_feature-auth.md
ultra directory/entrypoint: 0005_feature-auth or 0005_feature-auth/index.md
stem without extension: 0005_feature-auth
partial match: feature-auth (must match exactly one plan)
Step 2: Execute Mode
Mode: Interactive (no arguments)
Scan paths.plans/ for root *.md files and direct child */index.md
candidates using Glob. Exclude the resolved paths.plan and
paths.fix_plan; count a directory only when its entrypoint declares
<!-- aif:plan-mode:ultra -->. Do not treat phase files or unrelated directories as plans.
For each artifact, read the entrypoint's ## Tasks section.
Determine completion: a plan is completed when ALL task checkboxes
are - [x]. Plans with any - [ ] are incomplete.
AskUserQuestion: Which plans to archive?
Options:
1. All completed plans listed above
2. Select specific plans (enter numbers)
3. Cancel
Execute archive operation for selected plans (see Archive Operation).
Mode: list
Check if <paths.archive>/plans/ exists.
If not: Archive is empty. No plans have been archived yet. → STOP.
Glob root <paths.archive>/plans/*.md files and direct child
<paths.archive>/plans/*/index.md entrypoints containing exactly one
<!-- aif:plan-mode:ultra -->.
For each archived artifact, extract its date from YAML frontmatter (full
plans) or <!-- aif:archived:YYYY-MM-DD --> immediately after the ultra
marker (index.md).
Resolve <plan-name> to one artifact in paths.plans/:
Try exact root filename, exact ultra directory, or exact */index.md match
Then try with .md extension appended
Then try partial match against root filenames and ultra directory names
If no match: Plan not found: <plan-name> with suggestions → STOP.
If multiple matches: list them and ask user to be more specific → STOP.
For a directory match, read the entrypoint and require
<!-- aif:plan-mode:ultra -->;
otherwise it is not an archivable AI Factory plan.
Read the matched entrypoint and check completion status.
If incomplete:
Plan <filename> is not completed (5/8 tasks done).
Only completed plans can be archived.
→ STOP.
Execute archive operation (see Archive Operation).
Mode: --all
Scan paths.plans/ for completed plans (same logic as interactive mode).
If no completed plans: inform and STOP.
Display list and ask confirmation:
AskUserQuestion: Archive ALL completed plans?
1. 0001_feature-alpha.md
2. 0003_feature-gamma.md
Options:
1. Yes, archive all 2 plans
2. Cancel
Execute archive operation for all confirmed plans.
Mode: --roadmap
Read the resolved paths.roadmap file.
If it doesn't exist: No ROADMAP.md found at <path>. → STOP.
Find milestones with - [x] checkbox (completed milestones).
If no completed milestones: No closed milestones to archive. → STOP.
Display and ask confirmation:
Closed milestones found in ROADMAP.md:
- [x] MVP Launch — core features shipped
- [x] Beta Testing — user feedback round
AskUserQuestion: Trim these milestones from ROADMAP.md into a snapshot?
Options:
1. Yes, create snapshot and trim
2. Cancel
If the file exists, append a counter suffix to produce a non-colliding name:
YYYY-MM-DD_roadmap-snapshot-2.md, YYYY-MM-DD_roadmap-snapshot-3.md, etc.
Check each candidate until a free name is found.
Edit paths.roadmap: remove the archived - [x] lines from the
## Milestones section. Keep the ## Completed table if it exists.
Do NOT edit paths.roadmap unless the snapshot write in step 6 succeeded.
Logging: INFO [aif-archive] roadmap snapshot: <resolved-path> (<N> milestones archived)
Show full SKILL.md (656 more words)Show less
Archive Operation (plans)
For each plan artifact to archive:
mkdir -p <paths.archive>/plans/
Collision check. Before moving, verify the destination does not already exist:
Read <paths.archive>/plans/<original-name> # full plan
Read <paths.archive>/plans/<original-name>/index.md # ultra bundle
If the file exists:
Single plan (interactive or <plan-name>): STOP with an error:
ERROR [aif-archive] destination already exists: <paths.archive>/plans/<filename>
A previously archived plan has the same filename. This can happen when
sequential numbering reuses a freed number after archiving.
To resolve: rename the existing archive file, or delete it if it is no
longer needed.
Batch (--all): SKIP this plan with a warning, continue to the next:
Validate an ultra bundle before moving it. Read index.md and require:
exactly one <!-- aif:plan-mode:ultra -->, as the first line or immediately
after an optional first-line <!-- handoff:task:<id> -->;
a non-empty ## Phase Index;
every linked phase path is a direct child of the bundle and exists.
A malformed bundle is not safe to archive. STOP for a single plan, or emit
WARN [aif-archive] skipped malformed ultra bundle: <filename> and continue
in --all mode.
Move the complete source artifact into the archive path first:
For ultra, <name> is the whole directory, so all linked phase files move
together. This atomically removes the plan from active discovery.
Add archive metadata to the moved entrypoint using Edit (index.md for
ultra, the moved plan file otherwise).
For ultra, preserve the canonical header and insert this comment immediately
after <!-- aif:plan-mode:ultra -->:
markdown
<!-- aif:archived:YYYY-MM-DD -->
Never prepend YAML or move the ultra marker: it must remain the first line or
immediately after an optional first-line Handoff annotation.
For a full plan, if the file already has YAML frontmatter (between ---
markers at the top):
Use Edit to add archived: YYYY-MM-DD field inside the existing frontmatter block.
If the full plan has no YAML frontmatter:
Use Edit to prepend a minimal frontmatter block before the first line:yaml
---
archived: YYYY-MM-DD
---
The original filename or directory name is preserved exactly, including any
sequential NNNN_ prefix.
Logging: INFO [aif-archive] archived: <filename> -> <paths.archive>/plans/<filename>
After all plans are processed, display summary:
## Archive Complete
Archived N plan(s) to <paths.archive>/plans/:
- 0001_feature-alpha.md
- 0003_feature-gamma.md
Skipped: K (destination already exists)
- 0002_feature-beta.md
Plans directory: <paths.plans/> (M plans remaining)
Omit the "Skipped" section when K is 0.
Completion Detection Algorithm
A plan is completed when:
The plan entrypoint contains a ## Tasks section (case-insensitive header match).
ALL lines matching the pattern - [x] or - [ ] within the Tasks section
(and its subsections) are checked: every checkbox is - [x].
If the Tasks section contains zero checkboxes, the plan is considered
not completed (empty plans are not archivable).
Edge cases:
Checkboxes outside ## Tasks (e.g., in ## Settings or ## Commit Plan)
are NOT counted for completion.
Nested checkboxes (indented - [x]) ARE counted.
Plans whose entrypoint lacks ## Tasks are not archivable — emit
WARN [aif-archive] <name> has no ## Tasks section; skipping.
Completion Date Inference
When displaying "completed" dates in interactive mode:
Check YAML frontmatter for a completed field — use if present.
Fall back to git: git log -1 --format=%ai -- <plan-file> to get last
modification date.
Fall back to filesystem: entrypoint modification time.
Important Rules
Never archive incomplete plans — all tasks must be - [x]
Always ask confirmation before --all and --roadmap operations
Preserve original file/directory names — including sequential NNNN_ prefix
Add archive metadata — YAML frontmatter for full plans; the stable
<!-- aif:archived:YYYY-MM-DD --> comment after the ultra marker for bundles
Do not modify fast plans (paths.plan) or fix plans (paths.fix_plan) —
those are single-file artifacts managed by /aif-implement and /aif-fix
Do not count archived plans for sequential numbering — archived plans
live in paths.archive/plans/, not paths.plans/, so /aif-plan
sequential scan does not include them
Artifact Ownership
Owns:paths.archive/plans/*.md, archived ultra bundle directories, and paths.archive/roadmap/*.md
Reads: root paths.plans/*.md, direct child ultra */index.md + linked phases, and paths.roadmap
Modifies:paths.roadmap (only with --roadmap, only after confirmation)
Does NOT touch:paths.plan, paths.fix_plan, paths.description,
paths.architecture, paths.rules_file
Aif Archive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.
Archive completed plans and roadmap milestones. An agent skill from unxed/f4. Aif Archive is an agent skill from unxed/f4. Archive completed plans and roadmap milestones.
Run `npx skills add unxed/f4 --skill aif-archive -a claude-code`. Or copy the skill folder (.agents/skills/aif-archive in unxed/f4) into .claude/skills/aif-archive in your project. Claude Code loads it when a task matches its description.
How do I install Aif Archive in Codex?
Run `npx skills add unxed/f4 --skill aif-archive -a codex`. Or copy the skill folder (.agents/skills/aif-archive in unxed/f4) into .agents/skills/aif-archive in your project. Codex loads it when a task matches its description.
Can I use Aif Archive in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add unxed/f4 --skill aif-archive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aif-archive, .gemini/skills/aif-archive, .github/skills/aif-archive and .opencode/skills/aif-archive in your project.
What does Aif Archive need to run?
Going by SKILL.md and its folder, Aif Archive needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash(mv *), Bash(mkdir *), Bash(git *), AskUserQuestion.
Does Aif Archive access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Aif Archive safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Aif Archive use?
Aif Archive is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Aif Archive use?
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Aif Archive?
Skills that share tags, products or a category with Aif Archive: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.8k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Aif Archive?
unxed (a GitHub user) maintains it in unxed/f4, which has 243 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 10, 2026.
Source: unxed/f4 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
