quick-plan
This skill should be used when the user asks to "create a quick plan", "draft a plan", "capture this idea", "plan this feature", or wants a lightweight plan without full feature planning. Creates concise plans in backlog/plans/ for later expansion.
What this skill does
# Quick Plan
Create a lightweight plan document for: **$ARGUMENTS**
## Overview
This skill creates concise plan documents in `backlog/plans/` using the standard template. Suitable for:
- Capturing ideas quickly before context is lost
- Scoping small-to-medium features
- Creating starting points for later `/planner` expansion
For complex features requiring full analysis, spec, research, and TDD task breakdown, use `/planner` instead.
## Workflow
### Step 1: Generate Filename
Create filename using today's date and a slug derived from the input:
- Format: `YYYYMMDD-short-description.md`
- Example: `20260127-add-user-authentication.md`
### Step 2: Gather Context (Optional)
When input references existing code or systems:
- Briefly scan relevant files to understand current state
- Note obvious constraints or dependencies
Limit context gathering to under 2 minutes. Extensive research indicates `/planner` may be more appropriate.
### Step 3: Create Plan
Create the plan file at `backlog/plans/{filename}`:
```markdown
---
title: "{Descriptive title}"
status: open
priority: {low|medium|high|critical}
created: {YYYY-MM-DD}
---
# {Plan Title}
## Summary
{1-2 sentences describing what this plan achieves}
## Motivation
{Why is this needed? What problem does it solve? 2-3 sentences.}
## Proposal
### Goals
- {Primary goal}
- {Secondary goal if applicable}
### Non-Goals
- {What this explicitly does NOT cover}
## Design
{High-level approach in 3-5 sentences or bullet points. Include key technical decisions if obvious.}
## Tasks
- [ ] {Task 1}
- [ ] {Task 2}
- [ ] {Task 3}
## Open Questions
- {Any uncertainties requiring resolution}
```
### Step 4: Output Summary
After creating the plan:
```
Created: backlog/plans/{filename}
{title}
Priority: {priority}
Tasks: {count}
Next steps:
- Review and refine the plan
- Adjust priority if needed
- Expand with /planner if complexity warrants
- Or start implementation directly for simple plans
```
## Guidelines
| Guideline | Detail |
|-----------|--------|
| Concise | Quick capture, not exhaustive planning |
| Priority inference | Blocking issues = high, nice-to-have = low |
| Task count | 3-7 tasks; more than 7 suggests `/planner` |
| Optional sections | Omit "Open Questions" if none exist |
| Time limit | Context gathering under 2 minutes |
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.