Skip to content

zendev-lab/ulota / .agents/skills/spark-change-scope

spark-change-scope

Verified

Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.

Spark change scope

Establish the change boundary from live repository evidence before recommending edits.

Procedure

  1. Read the nearest AGENTS.md, architecture/packages.json, the owning specification, package README, and nearby tests.
  2. Identify one authoritative owner for every state transition, protocol, policy, and persisted field in scope.
  3. Trace callers and consumers far enough to find cross-package, compatibility, public-documentation, and migration effects.
  4. Separate required behavior from adjacent cleanup. Choose the smallest slice that can prove the requested outcome.
  5. Turn the request into observable acceptance criteria, including failure and compatibility cases.

Do not choose an owner from directory names or prompt prose when an enforced inventory or runtime path contradicts it. Resolve ambiguity from those sources first. If a new state owner or unresolved product choice requires an architecture decision, report the specific decision and continue independent scoped work.

Return owner, surfaces, invariants, risks, acceptanceCriteria, outOfScope, and blockers, citing paths and symbols.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall