scottwater
- 58 skills
- 0 followers
- 5 hours ago last updated
- ▌ Solopowers Receiving Code Review · scottwaterUse 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 implementation (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Test Driven Development · scottwater bundleUse when implementing any feature or bugfix, before writing implementation code (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Verification Before Completion · scottwaterUse 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 always (Solopowers/SoloTerm adaptation.)
- ▌
- ▌ Agent Speak · scottwater bundleWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
- ▌ Tracer Handoff · scottwater bundleCompact the current conversation into a handoff document for another agent to pick up.
- ▌ Tracer Codebase Design · scottwater bundleShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
- ▌ Tracer Domain Modeling · scottwater bundleBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
- ▌ Loops Plan · scottwaterTransform feature ideas/bugs into comprehensive implementation plans in docs/plans with research, flow analysis, and actionable phases.
- ▌ Loops Work · scottwaterExecute a plan/spec/todo to completion with task tracking, incremental validation, and quality gates.
- ▌ Loops Review · scottwaterRun comprehensive review for a target change/request, defaulting to multi-agent review when useful.
- ▌ Loops Compound · scottwater bundleCapture solved problems as categorized documentation with YAML frontmatter for fast lookup
- ▌ Loops Research · scottwaterConduct comprehensive codebase research, then synthesize into a dated research document with metadata.
- ▌ Loops Brainstorming · scottwaterExplore requirements and approaches through collaborative dialogue before planning implementation. Use before loops-plan when requirements are ambiguous or tradeoffs are unclear.
- ▌ Solopowers Brainstorming · scottwater bundleYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Writing Plans · scottwater bundleUse when you have a spec or requirements for a multi-step task, before touching code (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Writing Skills · scottwater bundleUse when creating new skills, editing existing skills, or verifying skills work before deployment (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Executing Plans · scottwaterUse when you have a written implementation plan to execute in a separate session with review checkpoints (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Using Solopowers · scottwater bundleUse when starting any conversation - establishes how to find and use skills, requiring host skill-loading mechanism invocation before ANY response including clarifying questions (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Commit Scratchpad · scottwaterUse when the user wants to persist SoloTerm scratchpad content into repository files and commit it to Git. (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Using Git Worktrees · scottwaterUse 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 fallback (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Systematic Debugging · scottwater bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Requesting Code Review · scottwater bundleUse when completing tasks, implementing major features, or before merging to verify work meets requirements (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Dispatching Parallel Agents · scottwaterUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Subagent Driven Development · scottwater bundleUse when executing implementation plans with independent tasks in the current session (Solopowers/SoloTerm adaptation.)
- ▌ Solopowers Finishing A Development Branch · scottwaterUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup (Solopowers/SoloTerm adaptation.)
- ▌
- ▌ How · scottwater bundleExplain how a subsystem works or where code should live. Use for runtime walkthroughs, architectural ownership, layering questions, and architecture critique; use why for historical motivation.
- ▌ Why · scottwater bundleInvestigate why code or a design decision exists. Use for rationale, rejected alternatives, regressions, postmortems, historical constraints, and evidence-backed thresholds; use how for runtime behavior.
- ▌ Solo · scottwater bundleUse when the user asks to use Solo (MCP) to spawn coding agents, manage scratchpads, todos, or timers, to inspect Solo-managed processes, or when another skill delegates its agent dispatch to Solo.
- ▌ Rigor · scottwater bundleApply a focused, evidence-driven engineering workflow to one concrete task.
- ▌
- ▌ Simplify · scottwaterRefine an implementation by simplifying, deduplicating, reorganizing, and removing low-value tests or unnecessary churn while preserving behavior.
- ▌ Code Quorum · scottwater bundleRun independent code-review agents and synthesize verified findings.
- ▌ Slop Monkey · scottwater bundleRewrite prose to sound direct, readable, and distinctly human. Use when drafting, revising, or reviewing reader-facing writing.
- ▌
- ▌ Herdr Quorum · scottwater bundleRun a saved model quorum in visible Herdr panes and synthesize its reports.
- ▌ Github Social · scottwater bundleGenerate a 1280x640 GitHub repository social preview (Open Graph) image and link it at the top of the README.
- ▌ Rails Security · scottwater bundleRun a multi-agent security review of Rails application code. Use when the user asks for a Rails security review or audit, or raises a specific concern — authorization/IDOR/tenant isolation, XSS/SQL injection/SSRF, vulnerable gems/Brakeman/bundle audit, or prompt injection in AI features.
- ▌ Session Review · scottwater bundleReport what recent project work took from coding-agent session logs: usage, cost, delegation, customizations, and friction.
- ▌ Gpt Image Prompts · scottwater bundleTurn a visual idea into a production-ready prompt and API settings for OpenAI GPT Image models (gpt-image-2).
- ▌ Tracer Tdd · scottwater bundleTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- ▌ Tracer Wat · scottwater bundleAsk which skill or flow fits your situation. A router over the tracer skills.
- ▌ Dsa Codebase Audit · scottwater bundleAudit a whole codebase for material simplifications in data structures, state, algorithms, control flow, and ownership.
- ▌ Tracer Setup · scottwater bundleConfigure a repo for the tracer skills — set up its issue tracker and domain doc layout. Run once before first use; everything falls back to local files if you skip it.
- ▌ Tracer To Spec · scottwater bundleTurn a settled interview or cleared Wayfinder map into a spec and publish it — no new interview, just synthesis of decisions already made.
- ▌ Tracer Research · scottwater bundleInvestigate a focused question against high-trust primary sources and capture cited findings as one Markdown note. Use for documentation, API, specification, or local knowledge-base research, including AFK Wayfinder research tickets.
- ▌ Tracer Autopilot · scottwater bundleDeliver a ticket or spec through bounded review, fresh proof, and a branch-finishing choice.
- ▌ Tracer Implement · scottwater bundleImplement a ticket or spec with a visible task plan, sequential task commits, two bounded ticket-wide review passes, and a final test run.
- ▌ Tracer Prototype · scottwater bundleBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
- ▌ Tracer Wayfinder · scottwater bundlePlan an effort too large and foggy for one agent session as a shared map of decision tickets, then resolve them one at a time until the route to a spec is clear.
- ▌ Tracer Worktrees · scottwater bundleSet up an isolated workspace when feature work starts on main/master — reuse any existing feature branch or isolation, prefer the harness's native worktree tool, and fall back to git worktree.
- ▌ Tracer To Tickets · scottwater bundleBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges — one file per ticket locally, or native blocking links on a real tracker.
- ▌ Tracer Code Review · scottwater bundleStandards-versus-Spec review. Use when the user requests Tracer's two-axis verdicts or a workflow assigns this review.
- ▌ Tracer Convince Me · scottwater bundleBuild the strongest honest, end-to-end case that completed work satisfies its original goal.
- ▌ Committing With Guidelines · scottwater bundleCreate git commits with atomic scope and product-focused messages. Use whenever preparing, writing, or reorganizing commits.
- ▌ Tracer Interview Me · scottwater bundleA relentless interview that asks every frontier question at once, round by round. The entry point of the main flow — interview until shared understanding, then hand off to /tracer-to-spec. Docs-aware in a codebase (reads/writes CONTEXT.md and ADRs), stateless without one.
- ▌ Tracer Finish Branch · scottwater bundleFinish a development branch — verify tests with fresh evidence, then present merge / PR / keep / discard options and execute the choice, cleaning up worktrees safely.