name: Feature request
description: Propose a new capability or product improvement.
title: "[Feature]: "
labels:
  - enhancement
body:
  - type: markdown
    attributes:
      value: |
        Prepared via the `openclaw-feedback` skill template copy.
        Draft the request for the user instead of replaying the form field-by-field when the intent is already clear.
        Help evaluate the request with concrete use cases and tradeoffs.
        Automatically mask obvious secrets and unnecessary PII before filing.
        Ask only a very short grouped follow-up when a few missing facts would materially improve the request.
  - type: textarea
    id: summary
    attributes:
      label: Summary
      description: One-line statement of the requested capability.
      placeholder: Add per-channel default response prefix.
    validations:
      required: true
  - type: textarea
    id: problem
    attributes:
      label: Problem to solve
      description: What user pain this solves and why current behavior is insufficient. Recover terse requests into a concrete problem statement when the user intent is clear.
      placeholder: Agents cannot distinguish persona context in mixed channels, causing misrouted follow-ups.
    validations:
      required: true
  - type: textarea
    id: proposed_solution
    attributes:
      label: Proposed solution
      description: Desired behavior/API/UX with as much specificity as possible. Draft the strongest accurate proposal you can from the user’s intent and a brief follow-up if needed.
      placeholder: Support channels.<channel>.responsePrefix with default fallback and account-level override.
    validations:
      required: true
  - type: textarea
    id: alternatives
    attributes:
      label: Alternatives considered
      description: Other approaches considered and why they are weaker.
      placeholder: Manual prefixing in prompts is inconsistent and hard to enforce.
  - type: textarea
    id: impact
    attributes:
      label: Impact
      description: |
        Explain who is affected, severity/urgency, how often this pain occurs, and practical consequences.
        Include:
        - Affected users/systems/channels
        - Severity (annoying, blocks workflow, etc.)
        - Frequency (always/intermittent/edge case)
        - Consequence (delays, errors, extra manual work, etc.)
      placeholder: |
        Affected: Multi-team shared channels
        Severity: Medium
        Frequency: Daily
        Consequence: +20 minutes/day/operator and delayed alerts
    validations:
      required: true
  - type: textarea
    id: evidence
    attributes:
      label: Evidence/examples
      description: Prior art, links, screenshots, logs, or metrics. Automatically redact obvious secrets and unnecessary PII before filing.
      placeholder: Comparable behavior in X, sample config, and screenshot of current limitation.
  - type: textarea
    id: additional_information
    attributes:
      label: Additional information
      description: Extra context, constraints, or references not covered above. If a small targeted follow-up still does not produce enough grounded substance for the request, respond with exactly `NOT_ENOUGH_INFO`.
      placeholder: Must remain backward-compatible with existing config keys.