complete-plan
Verify and complete a plan after implementation - summon the gods of code
What this skill does
[PLAN COMPLETION MODE - VERIFICATION REQUIRED]
$ARGUMENTS
## The Completion Oath
**Summon the gods of code.** A plan is NOT complete until EVERY acceptance criterion is VERIFIED.
This is NOT a rubber stamp. This is a court of judgment.
## Phase 1: Plan Analysis (MANDATORY)
First, read and analyze the plan file:
1. **Locate the Plan**: If no path provided, check `.olympus/plans/` for the most recent plan
2. **Extract All Criteria**: List EVERY acceptance criterion, deliverable, and success metric
3. **Identify Verification Methods**: For each criterion, determine HOW to verify it
## Phase 2: Systematic Verification (MANDATORY)
For EACH criterion, you MUST:
| Step | Action | Required Evidence |
|------|--------|-------------------|
| 1 | Read the relevant code/files | File paths, line numbers |
| 2 | Run verification commands | Test output, build output |
| 3 | Check for edge cases | Error handling, validation |
| 4 | Document the evidence | Screenshots, logs, diffs |
### Verification Commands
\`\`\`bash
# Tests pass
npm test / pytest / go test
# Build succeeds
npm run build / make / cargo build
# Types check
npm run typecheck / mypy / tsc --noEmit
# Lint passes
npm run lint / ruff / golangci-lint
\`\`\`
## Phase 3: Judgment
Based on your verification, assign ONE status:
| Status | Meaning | Criteria |
|--------|---------|----------|
| **COMPLETED** | All criteria verified | 100% of acceptance criteria met with evidence |
| **PARTIAL** | Some criteria met | >50% verified, blockers documented |
| **INCOMPLETE** | Significant gaps | <50% verified, major work remaining |
| **ABANDONED** | Plan no longer relevant | Context changed, plan obsolete |
**COMPLETED requires Oracle review**: Before marking COMPLETED, spawn Oracle to review your verification evidence.
## Phase 4: Documentation
Create completion record at `.olympus/completions/{plan-name}-completion.md`:
\`\`\`markdown
# Plan Completion: {Plan Name}
## Status: {COMPLETED|PARTIAL|INCOMPLETE|ABANDONED}
## Verification Date: {date}
## Criteria Verification
| # | Criterion | Status | Evidence |
|---|-----------|--------|----------|
| 1 | {criterion} | ✅/❌ | {file:line, test output, etc} |
## Summary
{What was accomplished, what remains}
## Oracle Review
{Oracle's assessment if COMPLETED}
\`\`\`
## Phase 5: Archive
If COMPLETED:
1. Move plan to `.olympus/archive/`
2. Update any tracking documents
3. Report completion to user
If NOT COMPLETED:
1. Keep plan in `.olympus/plans/`
2. Document blockers and remaining work
3. Recommend next steps
---
**Remember: Summon the gods of code. Verify everything. Trust nothing without evidence.**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.