prime-feat
This skill should be used when the user asks to "load feature context", "resume feature work", "prime feature N", "continue feature N", or wants to load all planning artifacts for a specific feature number.
What this skill does
# Prime Feature Context
Load all planning artifacts and context for feature {{feature_number}}.
## Artifact Locations
1. Find the feature folder: check `backlog/plans/{{feature_number}}-*/` first, then `backlog/plans/_completed/{{feature_number}}-*/`
2. Read all planning documents:
- analysis.md
- spec.md
- research.md
- plan.md
- data-model.md
- tasks.md
- contracts/ (all files)
3. Read spec tests: `specs/tests/{{feature_number}}-*.md`
4. Check git branch status for `feature/{{feature_number}}-*`
## Workflow
1. Check `backlog/plans/` first for in-progress features, then `backlog/plans/_completed/` for completed ones
2. Use `ls backlog/plans/ backlog/plans/_completed/` to find the folder matching `{{feature_number}}-*`
3. Once found, extract the full feature ID (e.g., `001-mcp-integration`) and path
4. Read all files in `{feature-path}/`:
- Start with `analysis.md`, `spec.md`, `plan.md` (core docs)
- Then `data-model.md`, `tasks.md`, `research.md`
- Finally list and read files in `contracts/` directory
5. Read `specs/tests/{feature-id}.md` if it exists
6. If `.ainotes/memory.md` exists, read it for accumulated agent context
7. Run `git status` and `git branch --show-current` to check current branch
8. If not on the feature branch, suggest: `git checkout feature/{feature-id}`
9. Analyze `tasks.md` and summarize:
- Total task count
- Completed count (checked boxes)
- Current phase based on task completion
- Next uncompleted task
## Output Summary
Present a concise status report in this format:
```
┌─────────────────────────────────────────────────────────────┐
│ Feature {NNN}-{slug} │
├─────────────────────────────────────────────────────────────┤
│ Branch: feature/{NNN}-{slug} ✓ (or ✗ if not on branch) │
│ Progress: {completed}/{total} tasks ({percent}%) │
├─────────────────────────────────────────────────────────────┤
│ Phase Progress: │
│ Phase 1: {name} ████████████ {done}/{total} ✓ │
│ Phase 2: {name} ██████░░░░░░ {done}/{total} ← current │
│ Phase 3: {name} ░░░░░░░░░░░░ {done}/{total} │
│ ... │
├─────────────────────────────────────────────────────────────┤
│ Recently Completed: │
│ • T{N} - {description} │
│ • T{N} - {description} │
├─────────────────────────────────────────────────────────────┤
│ Next Up: │
│ → T{N} - {description} ← START HERE │
│ T{N} - {description} │
│ T{N} - {description} │
└─────────────────────────────────────────────────────────────┘
```
### Report Guidelines
1. **Phase Progress**: Show all phases with a visual progress bar (█ for done, ░ for remaining)
2. **Recently Completed**: Show last 2-3 completed tasks from the current phase
3. **Next Up**: Show next 3 uncompleted tasks, marking the first with "← START HERE"
4. **Keep it scannable**: Use consistent formatting, avoid prose
### Progress Bar Calculation
For each phase, calculate: `done / total * 12` filled blocks (█), remainder as empty (░)
**Important:** Do NOT provide a detailed summary of the documents - they are already loaded into context. The report replaces verbose explanations.
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.