Skip to content
cccskills
FreePublished on GitHub

just-stop

Stops "just one more" small tweaks that add scope without changing the outcome. Use when named (just-stop), or when about to implement extra polish, cleanup, or drive-by fixes beyond the stated goal.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

just-stop

True craft is knowing when to stop. "One more small change" is usually how scope dies by a thousand cuts.

When to apply

  • User names this skill (just-stop)
  • You are about to add "a few small tweaks," polish, cleanup, or drive-by fixes after the goal is already met
  • A change is justified as "while we're here" or "this will help overall" but is not required for the stated outcome

What matters

Identify the true goal / end state. Then ask:

  1. Does this change move that goal from unmet → met?
  2. Or does it only make an already-met goal nicer?

If (2), stop. Say what you'd tweak and leave it optional.

This is not anti-quality. Necessary fixes still ship. Nice-to-haves wait.

Operating rules

  • Goal first: Restate the required outcome in one line before adding work.
  • Challenge extras: When you or the user propose another change, classify it as required vs optional. Be explicit.
  • Ship at the value cliff: Stop where further work turns into icing — renames for taste, comment churn, speculative refactors, decorative CSS, "improve README a bit," extra error paths nobody asked for.
  • Necessary still means necessary: Bugs that block the goal, broken verification, or missing DoD items are not "just one more." Fix those.
  • Offer, don't sneak: If optional tweaks are genuinely valuable, list them after you're done. Don't implement them by default.

Response shape

When stopping yourself or the user:

Done for the goal: [one line]

Optional (not doing unless you want them):
- [tweak]
- [tweak]

When something is truly required:

Still required:
- [change] — [why the goal fails without it]

Anti-patterns

  • Implementing polish after DoD / acceptance already passes
  • Batching unrelated cleanup into a finished task
  • Treating taste differences as defects
  • Expanding a fix into a rewrite
  • Confusing "helpful" with "necessary"

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adhd

Free

Formats output for ADHD-friendly action — lead with the next step, number tasks, restate state, cut fluff. Use when named (adhd), when the user mentions ADHD or focus/executive-function constraints, or when they ask for steps they can execute immediately.

The English summary is being prepared. Showing the original description.

nateslabach/skills6Updated Sep 29, 2026

Devil's-advocate attack on AI workflow designs — threat model, assumption challenges, code critiques, and hypothetical redesigns with no file edits. Use for "attack this design", devil's advocate, or hostile challenge on agents/tools/summarization/tokens. Not for PR peer review (code-review) or self-review that applies fixes (ai-systems-review). Prefer: this skill → decide → ai-systems-review.

The English summary is being prepared. Showing the original description.

nateslabach/skills6Updated Sep 29, 2026

Hostile self-review of recently written AI workflow code that then applies fixes (agents, tools, chat context, summarization, tokens, attachments). Use after generating AI systems code, or when asked to self-review and harden it. Not for PR peer review (code-review) or no-edit devil's-advocate attacks (adversarial-challenge). Prefer: adversarial-challenge → decide → this skill.

The English summary is being prepared. Showing the original description.

nateslabach/skills6Updated Sep 29, 2026

Writes in ASD-STE100 simplified technical English — short sentences, plain words, active voice. Use when the user wants terse technical prose, names this skill, or asks for STE100.

The English summary is being prepared. Showing the original description.

nateslabach/skills6Updated Sep 29, 2026

Builds personal brand assets using Seth Godin's frameworks: signature symbol, slogan, surprise (Purple Cow), salient idea, and signature story. Use when named (branding), or when the user asks for a brand symbol, slogan, tagline, Purple Cow, counterintuitive angle, core idea, brand story, or personal brand positioning.

The English summary is being prepared. Showing the original description.

nateslabach/skills6Updated Sep 29, 2026

Disables the AI's default hedging, diplomatic softening, and social-nicety layers to deliver cold, unfiltered, consequentialist analysis on any topic. Use when the user wants the AI's actual assessment without padding, regardless of how harsh or uncomfortable the honest answer is.

The English summary is being prepared. Showing the original description.

nateslabach/skills6Updated Sep 29, 2026

See all skills by nateslabach

Report a problem with this skill