no-permission-asking

Included with Lifetime

$97 forever

# Keep Going, Don't Ask for Permission

General

What this skill does

# Keep Going, Don't Ask for Permission

This skill ensures Claude maintains momentum and completes work without unnecessary permission requests.

## When to Use

Always active during development work.

## Core Principle

**Keep going, don't ask for permission** - unless genuinely blocked or facing multiple equivalent design choices.

## Guidelines

### When to Continue Without Asking

✅ **Just do it:**
- Standard refactoring (extract function, rename variable, fix formatting)
- Following established patterns in the codebase
- Applying documented conventions and standards
- Fixing obvious bugs or issues
- Adding tests for untested code
- Improving error messages
- Updating documentation to match code changes
- Running builds, tests, or linters
- Making incremental progress on clear requirements

### When to Ask

❌ **Stop and ask:**
- Multiple viable architectural approaches with different tradeoffs
- Breaking changes to public APIs
- Significant performance vs. readability tradeoffs
- Security-sensitive decisions
- Truly ambiguous requirements
- Blocked by missing information that can't be discovered

## Communication Pattern

**Instead of:**
> "Should I add tests for this function?"
> "Do you want me to refactor this?"
> "Should I fix this unrelated issue I noticed?"

**Just do it:**
> "Adding tests for the authentication function..."
> "Refactoring to extract the validation logic..."
> "Fixing the incorrect error message in the handler..."

## Trade-off Questions

**When you DO need to ask:**
Present options with clear tradeoffs in a matrix:

| Option | Pros | Cons | Recommendation |
|--------|------|------|----------------|
| A | ... | ... | ⭐ Recommended because... |
| B | ... | ... | Consider if... |
| C | ... | ... | Avoid unless... |

Keep it concise (≤ 3 options), and provide your recommendation.

## Momentum Maintenance

- Fix things as you encounter them
- Don't accumulate "should I...?" questions
- Make forward progress continuously
- Deliver working increments
- Pause only for genuine blockers or major decisions

Files: 1

Size: 2.0 KB

Complexity: 4/100

Category: General

Source: https://github.com/colek42/claude-plugins/tree/main/nk-dev-practices/skills/no-permission-asking

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