archive
Archive completed AIDLC workflows to aidlc-docs/completed/
What this skill does
# Archive Completed Workflows
$ARGUMENTS
Archive completed AIDLC workflows by moving them from `aidlc-docs/{workflowId}/` to `aidlc-docs/completed/{workflowId}/`.
## Step 1: Scan for Workflows
List all directories under `aidlc-docs/` (excluding the `completed/` directory). For each directory that contains a `checkpoint.json`, read the checkpoint and classify:
- **Archivable**: `status` is `"complete"` AND the workflow is NOT already inside `aidlc-docs/completed/`
- **Active**: `status` is NOT `"complete"` and NOT `"archived"`
- **Already archived**: Located in `aidlc-docs/completed/` or has `archived_path` set
## Step 2: Parse Arguments
- **No arguments**: List all archivable workflows and ask the user which to archive (or offer `--all`)
- **`--all`**: Archive all archivable workflows without prompting
- **`<workflow-id>`**: Archive only the specified workflow (must be archivable)
If no archivable workflows are found, report: "No completed workflows to archive. Active workflows must reach completion before archiving."
## Step 3: Archive Each Selected Workflow
For each workflow to archive:
1. **Create target directory**: `aidlc-docs/completed/{workflowId}/`
2. **Read the checkpoint**: Load `aidlc-docs/{workflowId}/checkpoint.json`
3. **Stamp archival metadata** on the checkpoint:
- Set `archived_at` to current ISO 8601 timestamp
- Set `archived_path` to `aidlc-docs/completed/{workflowId}`
4. **Write the updated checkpoint** back to the source location
5. **Move the entire workflow directory** from `aidlc-docs/{workflowId}/` to `aidlc-docs/completed/{workflowId}/`
6. **Update master plan** (best-effort): If `.olympus/plans/{workflowId}-plan.md` exists, append a note:
```
---
_This workflow was archived to `aidlc-docs/completed/{workflowId}/` on {archived_at}_
```
7. **Update CLAUDE.md** (best-effort): If the project `.claude/CLAUDE.md` references this workflow as the active workflow, remove or comment out that reference since it is no longer active.
## Step 4: Report Results
Display a summary table:
```
Archived workflows:
| Workflow | Feature | Archived To |
|----------|---------|-------------|
| {id} | {name} | aidlc-docs/completed/{id}/ |
{count} workflow(s) archived successfully.
```
If any archival failed, report the error but continue with remaining workflows.
## Edge Cases
- **Workflow not found**: Report "Workflow '{id}' not found in aidlc-docs/"
- **Workflow not complete**: Report "Workflow '{id}' has status '{status}' — only completed workflows can be archived"
- **Already archived**: Report "Workflow '{id}' is already archived at aidlc-docs/completed/{id}/"
- **Move failure on Windows**: If the move fails with EBUSY, suggest closing any open files in the workflow directory
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.