Write a useful command request

Make the request specific

A useful request explains what should be understood or planned, which business process it concerns and what the result should contain. Keep the work within the capabilities assigned to your workspace identity.

1. State the business question or intended outcome.
2. Identify the relevant process and environment without including credentials.
3. Describe the limits, expected output and person who should review the plan.

• For example: prepare a plan to investigate delayed status updates between the order and fulfillment systems.
• Do not paste passwords, tokens, private keys or private sign-in links.

Separate planning from execution

Workspaces can prepare plans and record approvals; execution depends on current product availability and a configured, verified environment. A request to change a system cannot make that missing capability available or turn an unverified connection into a live source.

• Ask the plan to identify dependencies and evidence needed.
• Require human review for consequential changes.
• Check whether the plan depends on information that has not been verified.

If a request is rejected

Read the error before trying again. Recognizable credential patterns are rejected, but you should never rely on that check to make sharing secrets safe. A capability error requires an access decision by the workspace owner.

• The action you intended to request.
• The workspace, capability and redacted error.
• The time of the attempt; leave out the sensitive text that caused a rejection.