olshansk/personal-agent-skills · Archived

cmd-scope-sweep

Final pass to identify missed items, edge cases, and risks before considering a scope done

First seen Aug 8, 2026

Installation

$ npx skills add olshansk/personal-agent-skills --skill cmd-scope-sweep

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from olshansk/personal-agent-skills · top by installs.

npx skills add olshansk/personal-agent-skills

Browse all from olshansk/personal-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 10
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,529 B
  • docs SUMMARY.md 113 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Scope Sweep

Now that we've completed the core work and reviewed it, do a final pass to identify anything we missed or should address before considering this scope "done".

Please check for:

  • Incomplete tasks: anything you planned to do but didn't get to
  • Overlooked requirements: anything implied but not explicitly handled
  • Missing questions: what I should have asked but didn't
  • Hidden assumptions: any assumptions you made that could be wrong
  • Edge cases: scenarios that could break or degrade the solution
  • Failure modes: what happens when inputs are malformed, missing, hostile, or extreme
  • Operational concerns: deployment, monitoring, logging, maintenance, rollback
  • Security and abuse risks: permissions, misuse paths, data exposure
  • Performance bottlenecks: scalability issues, worst-case behavior, cost traps
  • Testing gaps: what still needs tests or validation
  • User experience gaps: confusing flows, unclear outputs, poor defaults
  • Integration risks: dependencies, external APIs, versioning, backward compatibility
  • Future-proofing: what will become painful in 3-6 months if not handled now

Finally:

  • What is the biggest risk remaining?
  • If you were reviewing this as a third party, what would you criticize first?
  • What would you improve if you had one more day?