ctx-archive
Archive completed tasks. Use when TASKS.md has many completed items cluttering the view.
Best use case
ctx-archive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Archive completed tasks. Use when TASKS.md has many completed items cluttering the view.
Teams using ctx-archive should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-archive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-archive Compares
| Feature / Agent | ctx-archive | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Archive completed tasks. Use when TASKS.md has many completed items cluttering the view.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Move completed tasks from TASKS.md to the archive. ## Before Archiving Two questions: if any answer is "no", don't archive: 1. **"Are the completed tasks cluttering the view?"** → If TASKS.md is still easy to scan, there's no urgency 2. **"Are all `[x]` items truly done?"** → Verify nothing was checked off prematurely ## When to Use - When TASKS.md has many completed `[x]` tasks - When the task list is hard to navigate - Periodically to keep context clean ## When NOT to Use - When there are only a few completed tasks (not worth the noise) - When you're unsure if tasks are truly complete (verify first) - **Never delete tasks**: only archive (CONSTITUTION invariant) ## Constitution Rules These are inviolable: - **Archival is allowed, deletion is not**: never delete context history - **Archive preserves structure**: Phase headers are kept for traceability - **Never move tasks**: tasks stay in their Phase section; archiving is the only sanctioned "move" and it's to the archive directory ## Execution ```bash ctx task archive $ARGUMENTS ``` **Example: preview first (recommended):** ```bash ctx task archive --dry-run ``` **Example: archive after confirming the preview:** ```bash ctx task archive ``` Archived tasks go to `archive/tasks-YYYY-MM-DD.md` in the context directory, preserving Phase headers for traceability. Report how many tasks were archived and where the archive file was written.
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.