agentmods.dev

discuss

discuss is a command for Claude Code from nWave-ai/nWave. It costs 35 tokens per session (2,877 once invoked), scanned A, original, MIT.

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.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the nw plugin — 12 commands shipped together

not rated 605 +3 today A scan 35 tokens MIT
View the source file nWave-ai/nWave nwave.ai
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/nwave-ai/nwave/discuss
Clone the repo
git clone --depth 1 https://github.com/nWave-ai/nWave

Made for: Claude Code.

Or install nw, the plugin that ships this one along with the rest of its 12 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for discuss

README.md
[![agentmods](https://agentmods.dev/badge/commands/nwave-ai/nwave/discuss.svg)](https://agentmods.dev/commands/nwave-ai/nwave/discuss)
Your own site
<a href="https://agentmods.dev/commands/nwave-ai/nwave/discuss"><img src="https://agentmods.dev/badge/commands/nwave-ai/nwave/discuss.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,877 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.02877
Opus 5 $0.00017 $0.01438
Sonnet 5 $0.00007 $0.00575
Haiku 4.5 $0.00003 $0.00288

Measured today against content hash 6832b56a5fa7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

discuss scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/nw/commands/discuss.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NW-DISCUSS: Jobs-to-be-Done Analysis, UX Journey Design, and Requirements Gathering

Wave: DISCUSS (wave 2 of 6) | Agent: Luna (nw-product-owner) | Command: /nw-discuss

Overview

Execute DISCUSS wave through Luna's integrated workflow: JTBD analysis|UX journey discovery|emotional arc design|shared artifact tracking|requirements gathering|user story creation|acceptance criteria definition. Luna uncovers jobs users accomplish, maps to journeys and requirements, handles complete lifecycle from user motivations through DoR-validated stories ready for DESIGN. Establishes ATDD foundation.

For greenfield projects (no src/ code, no docs/feature/ history), Luna proposes Walking Skeleton as Feature 0.

Interactive Decision Points

Decision 1: Feature Type

Question: What type of feature is this? Options:

  1. User-facing -- UI/UX functionality visible to end users
  2. Backend -- APIs, services, data processing
  3. Infrastructure -- DevOps, CI/CD, tooling
  4. Cross-cutting -- Spans multiple layers (auth, logging, etc.)
  5. Other -- user provides custom input

Decision 2: Walking Skeleton

Question: Should we start with a walking skeleton? Options:

  1. Yes -- recommended for greenfield projects
  2. Depends -- brownfield; Luna evaluates existing structure first
  3. No -- feature is isolated enough to skip

Decision 3: UX Research Depth

Question: Priority for UX research depth? Options:

  1. Lightweight -- quick journey map, focus on happy path
  2. Comprehensive -- full experience mapping with emotional arcs
  3. Deep-dive -- extensive user research, multiple personas, edge cases

Prior Wave Consultation

Before beginning DISCUSS work, read SSOT and prior wave artifacts:

  1. SSOT (if docs/product/ exists):
    • docs/product/journeys/{name}.yaml — existing journey to extend (if applicable)
    • docs/product/jobs.yaml — validated jobs and opportunity scores
    • docs/product/vision.md — product vision
  2. Project context: docs/project-brief.md | docs/stakeholders.yaml
  3. DISCOVER artifacts: Read docs/feature/{feature-id}/discover/ (if present)
  4. DIVERGE artifacts: Read docs/feature/{feature-id}/diverge/ (if present)
    • recommendation.md is the primary input — the selected design direction and job statement
    • job-analysis.md — validated JTBD job statements and ODI outcome statements — use directly, do not re-run JTBD analysis

Read the full file on GitHub · 240 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 240 lines · 35 tokens per session scan A 6832b56a5fa7

Subscribe to this mod's changes

discuss is a command published in the GitHub repository nWave-ai/nWave (605 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 2,877 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.

Design and UXDevOps and cloudFrontendPlanningTDDagentic-aiaiclaude-codesoftware-architecture
Related

Other commands, from other repositories

accessibility-audit

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.

wshobson/agents · 0 tokens

map-states

Model a component's states and transitions end to end — states, events, guards, and edge cases.

Owl-Listener/designer-skills · 21 tokens

design-screen

Design a complete screen layout from a description or requirements.

Owl-Listener/designer-skills · 11 tokens

responsive-audit

Audit a design's responsive behaviour across breakpoints — layout, touch targets, and content reflow.

Owl-Listener/designer-skills · 20 tokens

apply-design-md

Consume the project's design contract — a .design file or DESIGN.md — and thread its tokens through UI code (CSS, Tailwind, or design-system components).

AgentsORG/design-engineering · 36 tokens

agentation-fix

Session-2 fix loop for Agentation — read structured annotations from the dev overlay and apply targeted UI fixes.

AgentsORG/design-engineering · 27 tokens