dariovr1

configuring-sixth-sense

One-time interactive setup — configures model preferences and effort levels for Sixth Sense subagents.

Testing & QA Listed

Turn the current conversation into a structured spec document, then implement it — orchestrates TDD, typechecking, code review, and commit. The two halves of one sequential artifact (`.sixth-sense/spec.md`); use Spec when a design agreed on in conversation needs to be persisted before dispatch, and Implementation once a spec or ticket exists and needs building.

using-sixth-sense

Use when starting any conversation — establishes how to find and use skills, and platform adaptation.

Web & Frontend Listed

crossroad-stack

Use before applying test-driven-development, diagnosing-bugs, or requesting-code-review to detect whether the task targets Java/Spring Boot backend, Angular, React, Next.js, Python, or other stacks, and route to the correct conventions.

diagnosing-bugs

Use when encountering bugs, test failures, or unexpected behavior — replaces random fixes with a disciplined, hypothesis-driven diagnosis loop. Trigger on "diagnose", "debug", "broken", "failing", "throwing".

dispatching-parallel-agents

Use when facing multiple independent tasks that can be worked on without shared state or sequential dependencies — dispatches specialized subagents with Effort Routing, batching, and agent cap.

dylan-dog

The nightmare investigator — hunts edge cases and runs premortems on failure modes. Invoke it directly with /investigate, or it gets called by requesting-code-review, specifying-and-implementing, and domain-modeling.

managing-development-branches

Covers the full lifecycle of a development branch — creating an isolated git worktree with systematic safety checks, resolving an in-progress merge/rebase conflict by intent, and closing out a finished branch (merge/PR/cleanup). Use when starting feature work that needs isolation from current branch, when `git status` shows unmerged paths or a merge/rebase is stuck on conflicts, or when implementation is complete and all tests pass and you need to decide how to integrate the work.

requesting-code-review

Use when completing tasks, implementing features, or before merging — dispatches Dylan Dog (edge-case hunting) and processes feedback with technical rigor, not performative agreement.

roundtable

Put the user's plan or design through a relentless round of questioning until a shared understanding is reached. Use when the user wants to pressure-test a plan or design before building.

Testing & QA Listed

test-driven-development

Use when implementing a feature or fixing a bug. Enforces red-green-refactor. Loads stack-specific conventions for Java/Spring Boot, Angular, React/Next.js, or Python.

verification-before-completion

Use 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.