hellblazer
44 verified skills44 total stars
brainstorming-gate
Use when about to implement any feature, build any component, or make any behavioral change — requires design exploration and user approval before implementation
development1
pdf-processing
Use when PDF documents need to be indexed into nx store for semantic search
documentation1
strategic-planning
Use when facing multi-step development work that needs decomposition into tasks, before writing any implementation code
development1
substantive-critique
Use when architectural decisions, implementations, or documentation need deep constructive critique against specs or evidence
testing1
writing-nx-skills
Use when creating new nx plugin skills, editing existing skills, or verifying skill quality before committing
tools1
plan-promote
Use when surveying the plan library's runtime metrics to propose plans for promotion to a higher scope — advisory-only; dispatches the plan-promote-propose meta-seed (no lifecycle ops — those ship in RDR-079)
development1
plan-inspect
Use when inspecting plan runtime metrics or enumerating dimension-registry usage — dispatches plan_match with dimensions={verb:plan-inspect}; strategy:default reports per-plan metrics, strategy:dimensions reports registry usage counts
business1
orchestration
Use when unsure which agent to use for a task, or when coordinating work across multiple agents in a pipeline
devops1
test-validation
Use when implementation is complete and test coverage needs verification, before merge or pull request
testing1
rdr-close
Use when an RDR is done — close it with optional post-mortem, bead status gate, and T3 archival
tools1
debug
Use when debugging a failing code path (intentionally flat — Serena handles symbol navigation) — tries the debug plan library first for per-file authoring context and summarises design intent, falls through to /nx:query if nothing matches
development1
review
Use when critiquing / auditing / reviewing a change set against decision history — tries the review plan library first (catalog lookup → decision-evolution traversal → extract → compare), falls through to /nx:query if nothing matches
development1
rdr-create
Use when starting a new research-design-review document to think through a technical decision
testing1
rdr-gate
Use when an RDR appears complete and needs finalization validation — structural, assumption, and AI critique checks
testing1
analyze
Use when synthesising across prose and code corpora or ranking candidates by a criterion — tries the analyze plan library first (search prose + code → reference-chain traversal → rank → generate), falls through to /nx:query if nothing matches
development1
architecture
Use when complex features need architectural design before implementation, or when system design decisions span multiple modules
testing1
catalog
Use when working with catalog entries, resolving tumblers, creating links, understanding what's linked to a file, or seeding link context for the auto-linker. Covers resolve, link, context, and seed operations.
tools1
codebase-analysis
Use when exploring an unfamiliar codebase, onboarding to a project, or needing to understand module structure before making changes
development1
code-review
Use when code changes are ready for quality, security, or best practices review, before committing or creating a pull request
development1
development
Use when a plan has been approved and implementation work is ready to begin, before writing production code
development1
document
Use when authoring or auditing documentation against existing coverage — tries the document plan library first (search prose follow_links=cites + search code → documentation-for traversal → compare), falls through to /nx:query if nothing matches
development1
finishing-branch
Use 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
development1
git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
tools1
knowledge-tidying
Use when validated findings need to be consolidated in nx T3 knowledge store.
testing1
nexus
Use when running nx commands for search, memory, knowledge storage, or indexing — or when unsure which nx subcommand to use
data-ai1
plan-validation
Use when a plan needs validation before implementation — catches gaps and codebase misalignment.
development1
query
Use when answering any analytical question over nx knowledge collections. This is the canonical entry point; direct search/query calls for analytical questions are an anti-pattern.
databases1
rdr-research
Use when adding, tracking, or verifying structured research findings for an active RDR
testing1
rdr-show
Use when needing detailed information about a specific RDR including content, research findings, and linked beads
development1
research
Use when doing design / architecture / planning work that walks from prose (RDRs, docs, knowledge) into the modules implementing a concept
documentation1
serena-code-nav
Use when navigating code by symbol — finding definitions, all callers, type hierarchies, renaming safely, or editing a method body without reading the whole file. Use instead of Grep for any symbol-level task.
development1
receiving-review
Use when receiving any code review feedback, before implementing any suggestion - requires technical rigor and verification, not performative agreement or blind implementation
development1
cli-controller
Use when controlling interactive CLI applications, debugging with pdb/gdb/jshell, spawning Claude Code instances, or working with REPLs and long-running processes
tools1
deep-analysis
Use when surface-level analysis is insufficient and problems require hypothesis-driven investigation across multiple system components
testing1
rdr-audit
Use when auditing a project's RDR lifecycle for silent-scope-reduction frequency, or when inspecting or managing scheduled periodic audits
testing1
rdr-list
Use when needing to see all RDRs in the project with their status, type, and priority
tools1
using-nx-skills
Use when starting any conversation or task — establishes that nx skills must be checked before every response, including clarifying questions. If a skill plausibly applies, invoke it.
testing1
debugging
Use when tests fail, exceptions occur, or behavior is non-deterministic, especially after 2+ failed manual fix attempts
development1
composition-probe
Use when a coordinator bead's inter-bead composition needs verification before downstream beads begin
tools1
enrich-plan
Use when beads need enrichment with execution context — file paths, code patterns, constraints, test commands.
development1
plan-author
Use when authoring a new plan template from scratch — dispatches the plan-author meta-seed which surveys prior art, the plan-authoring guide, and the dimension registry before drafting a candidate plan_json
documentation1
plan-first
Use when starting any retrieval task — the gate that tries plan_match first, executes via plan_run if a match clears the threshold, and falls through to /nx:query only on a miss
databases1
rdr-accept
Use when a gated RDR returned PASSED and you want to officially accept it for implementation
testing1
research-synthesis
Use when researching unfamiliar topics, comparing technology approaches, or building comprehensive understanding from multiple sources
development1