swift-executor

Generate three alternatives and implement the simplest working solution within 15 minutes.

181|30|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/erichowens/some_claude_skills --skill swift-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-executor
Source: https://github.com/erichowens/some_claude_skills/tree/main/.claude/skills/swift-executor
Command: npx skills add https://github.com/erichowens/some_claude_skills --skill swift-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams push tasks forward with rapid, independent decision-making and effective blocker elimination.

Core Features & Use Cases

  • Bias Toward Action: Make reversible decisions quickly.
  • Blocker Elimination Playbook: Generate 3 alternatives in minutes.
  • Execution Patterns: Time-boxing, starting ugly, and shipping fast.
  • Practical Scenarios: Break through analysis paralysis, MVPs, hotfixes.

Quick Start

When stuck, apply the 15-minute rule: implement the simplest working solution and ship.

Frequently Asked Questions about swift-executor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I overcome analysis paralysis and execute decisions quickly?

Overcome analysis paralysis by applying rapid decision-making and bias toward action. Set a 15-minute timeframe to implement the simplest working solution, then ship it. This breaks through indecision and keeps momentum moving forward on urgent tasks and blockers.

What's the best way to eliminate blockers in software development?

Eliminate blockers using a structured playbook: generate three alternatives in minutes, evaluate reversibility, and execute the fastest option. This unblocks teams quickly without requiring perfect information or consensus before acting.

How do I balance speed with reversible decisions when under time pressure?

Distinguish reversible decisions from irreversible ones. Make reversible choices fast with minimal analysis; reserve deeper deliberation for irreversible actions. This lets you ship quickly on hotfixes, MVPs, and rapid prototyping while protecting critical decisions.

Can I use execution patterns like time-boxing and 'start ugly' in real projects?

Yes. Time-boxing limits decision cycles, while starting ugly means shipping imperfect solutions immediately rather than perfecting them first. Both patterns apply across software development, operations, and project delivery to maintain momentum and unblock teams.

Why does ship-first iteration matter for moving past blockers?

Ship-first iteration trades perfect planning for real feedback. By deploying functional but incomplete work quickly, you generate concrete data to guide next steps, eliminating speculative delays and keeping execution momentum through blockers.