← Files LightbringerARCHIVED FILE

skills/setup/references/unresolved-needs.md

4.14 KB · Nov 21, 2026 · 18:11 UTC

↓ Download file

# Unresolved customer needs

Use this guidance across Lightbringer workflows when useful assistance leaves a material customer problem unresolved, or the user wants to report one. Help first and keep the original task moving. Do not solicit feedback after every action or repeat an offer the user declined.

## Understand the remaining problem

Reuse the conversation and available evidence. Establish what the person still cannot accomplish or decide after the help provided. When unclear, a short follow-up such as “What still prevents you from moving forward?” is enough; do not require a second interview or ask for a feature design.

Distinguish a confirmed missing capability from missing access, evidence, unclear service discovery, delivery constraints, cost or a limitation of this conversation. Use a suitable existing route when available, including an existing adviser. Do not claim Lightbringer cannot provide a service merely because the assistant cannot perform it here. Keep the cause unknown when it has not been established.

## Draft a problem report

Offer to share a concise report when the remaining gap is material. Include only supported, non-confidential information:

- **Desired outcome:** what the person was trying to accomplish.
- **Why it matters now:** stated timing or consequences, if known.
- **Help provided:** the part we resolved, or that we could not make progress.
- **Unresolved problem:** what they still cannot do or decide and the observed limitation.
- **Current alternative:** how they handle that part today and why it is insufficient, if known.

These are evidence lenses, not required fields. Omit unnecessary details and identify material unknowns. Report the problem in the customer's terms without copying transcripts. Do not add feature proposals, solution suggestions, inferred purchase intent or invented urgency. If the user proposes a feature, recover its underlying problem from the conversation or ask what it would enable them to do; do not invent the rationale.

For example: “The user needs to explain how existing patents support a product before an investor discussion. We helped organise the available information. They still cannot determine which important product capabilities are covered or explain the gaps confidently. According to the user, their adviser handles individual filings, but this broader assessment remains unresolved.” This illustrates the form; it is not evidence about the current user or service availability.

## Share only an approved report

Use `send_developer_feedback` only when advertised with write permission and its description supports the intended report. An older definition limited to tool issues can still accept a genuine tool issue; do not send broader service needs under that contract. If unavailable or out of scope, retain the useful discussion without claiming the need was recorded or sending it through another channel.

Choose `general` for an unmet customer need, `bug` for broken behaviour, or `tool_request` for a missing tool capability. Even a missing-capability report should describe the problem rather than prescribe a solution. Omit `tool_name` unless a specific tool is relevant. Keep the report within the advertised length limit.

Show the exact report text, category and optional tool name. Explain that only these fields go to Lightbringer's human-reviewed engineering Slack channel, which the user cannot view; no account or client metadata is automatically attached. Exclude names, conversation transcripts, document text, invention details and other confidential material. Obtain explicit approval for that report and recipient, honouring approval already given. Permission to get help, save a Strategy or complain is not permission to send feedback. If the user corrects the report, send only their approved version.

Report `delivered` or `not_delivered` accurately. After an uncertain response, do not automatically resend and risk a duplicate; explain the uncertainty. Continue the main task regardless. Delivery records feedback only: it does not request professional work, contact the patent team, promise a reply or commit Lightbringer to a solution. Patent-review comments use their own workflow.

SHA-256: b043babba678d3fb01460e0a5810d42110b645beb2d8084bde9331a3b8885b36