# Discuss

> Harmonia discuss stage - turn a direction into pinned scope with checkable success criteria. Use ONLY when explicitly invoked as /harmonia:discuss.

- Skill: `foliveira/discuss` (Agent Skill)
- Install (CLI): `npx skillmds@latest add foliveira/discuss`
- Raw SKILL.md: https://api.skillmd.com/api/skills/foliveira/discuss/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: foliveira (https://skillmd.com/u/foliveira)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/foliveira/discuss

---


Your working contract is the 4 rules; their digest is injected at session start - read `${CLAUDE_PLUGIN_ROOT}/core/RULES.md` in full only if that digest is not in your context.
Read the `discuss` stage from `${CLAUDE_PLUGIN_ROOT}/core/lifecycle.yaml` - agents and artifacts are authoritative; do not hardcode them.

1. Workspace: `bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh mint --repo . --slug <short-task-slug>` (entry stage; on refusal, surface the message and stop; continue an existing task with `--task <id>` via `resolve`).
2. This is the earliest scope-bearing stage: dispatch the scoper to mint `scope.md` in the workspace - one scope declaration per task; if `scope.md` already exists, the scoper refines it in place, never re-mints (R31). The rubber duck joins per the stage sequence for thinking-partner dialogue.
3. The scope declaration must carry a `## Success Criteria` section of `- run:` command lines - that is what the criteria gate validates before implement may start.

Pass workspace paths, not prose recaps (R8). Orchestrate only (R9).