Giova445
- 14 skills
- 0 followers
- 7 hours ago last updated
- ▌ Gate · giova445Run the project gate ladder and report the exact command and exit code. Use before claiming any work is complete.
- ▌ Blast · giova445Compute the blast radius of a symbol from the code graph before changing it. Use before editing any shared function, class, or endpoint.
- ▌ Brainstorming · giova445Use before ANY creative work — new features, components, behavior changes, refactors. Forces intent and approach to be settled and approved before implementation starts.
- ▌ Orchestrating · giova445Drive a multi-task plan through the durable ledger, claim file scope before writing, and obey the fix-loop budget. Use when executing a written plan, running a fan-out, or resuming after a compaction.
- ▌ Writing Plans · giova445Use after a spec is approved and before implementation. Turns a design into tasks small enough to dispatch independently and verify individually.
- ▌ Executing Plans · giova445Use when implementing a written plan. Keeps progress on disk so the run survives compaction, and enforces per-task verification.
- ▌ Using Worktrees · giova445Use before starting feature work that needs isolation, or before running agents in parallel. One writer per worktree, always.
- ▌ Pressure Testing · giova445Test whether a rule or instruction actually changes agent behavior before keeping it. Use when adding, auditing, or deleting rules in AGENTS.md, CLAUDE.md, or a skill.
- ▌ Requesting Review · giova445Use after gates are green and before opening a PR. Dispatches adversarial review that can only add findings, never clear a gate.
- ▌ Verified Autonomy · giova445Use when working in a repo that has .claude/gates.json — explains the mechanical gate contract, what "done" means, and why the Stop hook may refuse to let the turn end
- ▌ Dispatching Agents · giova445Use when work can be split across multiple agents. Explains when parallelism pays, when it does not, and how to keep writers from colliding.
- ▌ Finishing A Branch · giova445Use when implementation is complete and gates are green, to decide how the work gets integrated.
- ▌ Systematic Debugging · giova445Use when encountering any bug, test failure, or unexpected behavior, before proposing a fix. Forces root cause before remedy.
- ▌ Test Driven Development · giova445Use when implementing any feature or bugfix, before writing implementation code. Enforces that the test is written first and proven to fail for the right reason.