Menu
archives a local agent task directory so it can be recalled for future reference
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
create tasks as files in local project directory
orchestration skill for tasks, takes a task folder as input and runs one sub-agent for each individual task file. Should NOT execute or make any changes on its own, only sub-agents may do that.
coding best-practices and architecture skill
Plan and structure a new application from a vague prompt or PRD. Use when starting a greenfield project, building an app from scratch, or when the user provides a project idea or PRD that needs to be broken down into a structured development plan.
Break down a greenfield project blueprint into executable task-creator-ready research documents. Use after greenfield-init has produced a project blueprint, or when a project plan needs to be decomposed into buildable chunks with validation gates.
One-shot greenfield build orchestration. Takes a project blueprint and executes the full build pipeline using subagents for each phase, including intermediate verification gates. Use when you want to run an entire greenfield project build in one session without manual intervention between phases.
| name | task-archiver |
| description | archives a local agent task directory so it can be recalled for future reference |
Archive completed task projects by compressing artifacts while preserving a human-readable summary.
Use this skill when:
.agent-tasks/archive/.agent-tasks/archive (will be requested by user)You must be provided:
.agent-tasks/archive/20260130-facebook-api-v24-upgrade)Verify the project has:
ORCHESTRATOR.md file (required - serves as the summary)complete/If ORCHESTRATOR.md is missing, stop and ask the user to create one or provide an alternative summary.
Create ARCHIVE_INFO.md with:
Using tar, compress all subdirectories:
tar -czvf artifacts.tar.gz complete/ pending/ testing/ agent-transcripts/ --ignore-failed-read
Note: --ignore-failed-read handles missing folders gracefully.
After successful compression, remove the original folders:
complete/pending/testing/agent-transcripts/NOTE: you MUST delete these empty directories
Keep these files uncompressed:
ORCHESTRATOR.md — Primary summary documentARCHIVE_INFO.md — Archive metadataIMPLEMENTATION_COMPLETE.md — If present, useful summaryartifacts.tar.gz — The compressed archiveProvide:
NOTE: if not done yet, the task/project folder MUST be moved to .agent-tasks/archive/
archive/[project-name]/
├── ORCHESTRATOR.md # Human-readable project summary
├── ARCHIVE_INFO.md # Archive metadata and restore instructions
├── IMPLEMENTATION_COMPLETE.md # (if present)
└── artifacts.tar.gz # Compressed: all task folders and transcripts
To restore an archived project:
cd .agent-tasks/archive/[YYYYMMDD-task-folder]
tar -xzvf artifacts.tar.gz
Use the task-archiver skill to archive:
- Project: .agent-tasks/archive/20260130-facebook-api-v24-upgrade
# Archive Information
**Project:** [Project Name]
**Archived:** [Date]
**Archived By:** Cursor Agent
## Contents
The following folders have been compressed into `artifacts.tar.gz`:
| Folder | File Count | Description |
|--------|------------|-------------|
| complete/ | X files | Completed task definitions |
| pending/ | X files | Remaining/skipped tasks |
| testing/ | X files | Testing strategies |
| agent-transcripts/ | X files | Agent execution logs |
## Restoration
To extract the archived contents:
\`\`\`bash
tar -xzvf artifacts.tar.gz
\`\`\`
## Summary
See `ORCHESTRATOR.md` for the complete project summary, task list, and progress notes.
Before archiving, verify:
ORCHESTRATOR.md exists and is completeORCHESTRATOR.md uncompressed because it serves as the project's historical recordIMPLEMENTATION_COMPLETE.md or similar summary file, preserve it as welltar command