getting-started

Included with Lifetime

$97 forever

This skill is loaded automatically at session start via SessionStart hook. Establishes protocols for finding and using skills, checking skills before tasks, brainstorming before coding, and creating tasks for checklists.

General

What this skill does


# Getting Started with Skills

## Skill Discovery

Before starting any task, check if a skill exists for that task type:

| Task Type | Skill |
|-----------|-------|
| New feature, bug fix, behavior change | `test-driven-development` |
| Bug, test failure, unexpected behavior | `systematic-debugging` |
| Deep call stack errors | `root-cause-tracing` |
| Flaky tests, race conditions | `condition-based-waiting` |
| Claiming work is done | `verification-before-completion` |
| Code review feedback received | `receiving-code-review` |
| Bug fix validation layers | `defense-in-depth` |
| Architecture, file organization | `pragmatic-architecture` |
| Test quality review | `testing-anti-patterns` |
| Git worktree operations | `simple-git-worktrees` |
| Branch completion, merge/PR | `finishing-a-development-branch` |

If a skill matches: load it with the Skill tool, then follow it.

## Skill Priority

When multiple skills apply:

1. **Process skills first** — determine HOW to approach (debugging, brainstorming)
2. **Implementation skills second** — guide execution (TDD, architecture)
3. **Verification skills last** — confirm results (verification-before-completion)

Examples:
- "Build X" → brainstorming first, then TDD
- "Fix bug" → systematic-debugging first, then TDD for the fix
- "Add feature" → TDD (implementation is the process)

## Skill Types

**Rigid** (TDD, debugging, verification): Follow exactly. The structure IS the value.

**Flexible** (architecture, brainstorming): Adapt principles to context.

## Checklists

If a skill contains a checklist, create tasks using TaskCreate for each step. Mental tracking leads to skipped steps.

## Reference

See `references/skill-integration.md` for decision trees and skill chains.

---

## Planning Workflows

### Plugin Commands (Recommended)

```
/dev-workflow:brainstorm → /dev-workflow:write-plan → /dev-workflow:execute-plan
```

- Plans persist to `docs/plans/` (version controlled, reviewable)
- Parallel execution via `Task(run_in_background)` + `TaskOutput`
- Dependency tracking via `addBlockedBy`
- Post-completion: code review + finish branch enforced
- Resume: TaskList tracks progress

### How Parallel Execution Works

1. Create tasks with TaskCreate, express dependencies via addBlockedBy
2. For each round of unblocked tasks:
   - Launch with `Task(run_in_background: true)`
   - Collect with `TaskOutput(block: true)`
   - Mark completed with TaskUpdate
3. Proceed to post-completion actions

### When to Use EnterPlanMode Directly

Use `EnterPlanMode` without plugin commands for:
- Quick prototyping (plan doesn't need to persist)
- Simple 1-3 task features
- Interactive planning

For features needing plan persistence, code review, and resume capability, use the plugin commands flow.

### Executing Existing Plans

1. Read and validate the plan file
2. Choose sequential or parallel execution
3. After all tasks: code review → receiving-code-review → finishing-a-development-branch

Files: 1

Size: 3.2 KB

Complexity: 12/100

Category: General

Source: https://github.com/pproenca/dot-claude/tree/main/plugins/dev-workflow/skills/getting-started

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts