using-discussion

Persistent discussion

When a user requests or enters iterative clarification/brainstorming, use this protocol alongside the active domain Skill (including grill-me, grilling or superpowers). No name allowlist. Do not initiate questions merely to use it. Reuse the authorized project SQLite and current Hook's opaque agent context. Never manufacture another context, initialize a missing Wiki, or install tooling solely to record. An unavailable store is a capture limitation, not permission to pretend the conversation is saved. Without a resolved context, disclose the gap.

Use lwc contract discussion once for the exact schema and example. CLI lwc discussion apply --json - and MCP lwc_discussion action apply share it. MCP always requires the current absolute projectPath. Never pass shell-interpolated user text: serialize JSON to stdin or structured MCP arguments.

1. Recover discussion current --context CONTEXT before starting or after a compact/restart. No binding means start a discussion with a unique ID, title, description and stable request ID. The first start binds only this context.
2. Save each question and options with stable IDs before displaying identical text. Question preparation is not proof of display. Only report delivery with a host message reference; it remains reported evidence.
3. On each user reply, persist exact visible text before analysis or another question. An answer references its parent question; multiple messages have separate IDs. If association is ambiguous use reply and later move it to a question. Preserve multi-question original responses; never invent a split.
4. Read unassigned host replies first to avoid duplicate recording. Message IDs deduplicate supplied host events; unsupported/missing IDs fall back to this Agent protocol, never a guarantee of complete host capture. Do not reread full transcripts or store expanded prompts, tools, system text or reasoning.
5. Batch the preceding answer and next question when possible. Use the last receipt's revision and one stable request ID. On uncertain result retry the identical input; on conflict reload and reconcile. Never blindly replay with a new ID. Successful receipts are silent: no logging commentary is necessary.
6. On persistent failure, notify the user once that capture is incomplete and keep retrying only within the task's scope. Do not continue claiming durable capture. For excluded secrets submit a gap with a nonsensitive description; never store the secret in the reason, ID or retry log. This is an explicit exception for visible Discussion records, not general prompt logging.