Topic: agentic-workflow
2,980 skills in this topic.
-
nw-canary
Canary skill for auto-injection detection
nWave-ai/nWave 341
-
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD
nWave-ai/nWave 341
-
nw-buddy-wave-knowledge
Wave methodology knowledge for the buddy agent — what each wave does, its inputs and outputs, and how to route questions.
nWave-ai/nWave 341
-
nw-buddy-ssot-knowledge
Single Source of Truth detection — where truth lives in an nWave repo and how to avoid contradicting it.
nWave-ai/nWave 341
-
nw-fp-domain-modeling
Domain modeling with algebraic data types, smart constructors, and type-level error handling
nWave-ai/nWave 341
-
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec
nWave-ai/nWave 341
-
nw-fp-algebra-driven-design
Algebra-driven API design with monoids, semigroups, and interpreters via algebraic equations
nWave-ai/nWave 341
-
nw-formal-verification-tlaplus
TLA+ and PlusCal for specifying distributed system invariants. Decision heuristics for when formal verification adds value, key patterns, state explosion management, and alternatives comparison.
nWave-ai/nWave 341
-
nw-buddy-command-catalog
All /nw-* commands — what they do, when to use them, which agent they invoke. For the buddy agent to help users pick the right command.
nWave-ai/nWave 341
-
nw-forge
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification.
nWave-ai/nWave 341
-
nw-five-whys-methodology
Toyota 5 Whys methodology with multi-causal branching, evidence requirements, and validation techniques
nWave-ai/nWave 341
-
nw-finalize
Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes.
nWave-ai/nWave 341
-
nw-fast-forward
Fast-forwards through remaining waves end-to-end without stopping for review between waves.
nWave-ai/nWave 341
-
nw-execute
Dispatches a single roadmap step to a specialized agent for TDD execution. Use when implementing a specific step from a roadmap.json plan.
nWave-ai/nWave 341
-
nw-dr-review-criteria
Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews
nWave-ai/nWave 341
-
nw-dor-validation
Definition of Ready checklist criteria, antipattern detection patterns, UAT quality rules, and domain language enforcement for product owner review
nWave-ai/nWave 341
-
nw-domain-driven-design
Strategic and tactical DDD patterns, bounded context discovery, context mapping, aggregate design rules, and decision frameworks for when to apply DDD
nWave-ai/nWave 341
-
nw-document
Creates evidence-based documentation following DIVIO/Diataxis principles. Use when writing tutorials, how-to guides, reference docs, or explanations.
nWave-ai/nWave 341
-
nw-divio-framework
DIVIO/Diataxis four-quadrant documentation framework - type definitions, classification decision tree, and signal catalog
nWave-ai/nWave 341
-
nw-command-design-patterns
Best practices for command definition files - size targets, declarative template, anti-patterns, and canonical examples based on research evidence
nWave-ai/nWave 341
-
nw-interviewing-techniques
Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design
nWave-ai/nWave 341
-
nw-diverge
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.
nWave-ai/nWave 341
-
nw-diverger-review-criteria
Review criteria for the nw-diverger-reviewer — validates JTBD rigor, research quality, option diversity, taste application correctness, and recommendation coherence in DIVERGE wave artifacts
nWave-ai/nWave 341
-
nw-discuss
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
nWave-ai/nWave 341