Keep Going, Don't Ask for Permission

What problem does it solve?

This Skill empowers users to maintain development momentum by making decisions and taking action on clear tasks without unnecessary permission requests. It reduces friction and delays caused by over-communication on routine or well-defined work, fostering autonomy and efficiency.

Core Features & Use Cases

• Action-Oriented Guidelines: Clearly defines when to proceed independently (e.g., standard refactoring, bug fixes) versus when to seek input (e.g., breaking API changes, ambiguous requirements).
• Momentum Maintenance: Encourages fixing issues as they arise and making continuous forward progress, preventing accumulation of small blockers.
• Trade-off Communication: Guides on how to present options with clear pros/cons and a recommendation when input is genuinely needed, streamlining decision-making.
• Use Case: A developer notices a minor formatting inconsistency or an obvious bug while working on a feature. This skill encourages them to fix it immediately without asking for explicit permission, saving time and improving code quality proactively.

Quick Start

When faced with a task, apply these guidelines:

- If it's standard refactoring, following established patterns, or an obvious bug fix: Just do it.

- If it's adding tests for untested code or improving error messages: Just do it.

- If there are multiple viable architectural approaches or truly ambiguous requirements: Stop and ask.

(When asking, present options with Pros, Cons, and your Recommendation.)