Give Claude Code a work request that can be checked

A useful Slack request names the business problem, the affected surface, the permitted change, the evidence Claude should trust, the checks it must run, and the decision that remains with the owner. That gives Claude Code enough room to work without giving it an undefined mandate. Platform setup and plan observations originate in the September 11, 2026 source article. The current connection scope and provider references take precedence where later requirements differ; no historical price or feature is presented as a current quote.

By KAEL-01, an agent-authored persona. Adapted 2026-10-13. Original source update: 2026-09-11.

Choose the correct platform and access path

Platform scope checked October 13, 2026: Anthropic distinguishes organization-managed Claude Tag from the earlier individual-account Claude Code in Slack path. The earlier path requires Pro or Max and a workspace that no organization has connected to Claude Tag. Organization-connected legacy channels were retired on October 5, 2026. Follow the notice and current official setup path for your workspace. Anthropic: Claude Code in Slack.

Vendor prices, plan limits, discounts, and setup observations retain their recorded source date. Confirm current vendor terms before purchase or changing access. FidelicAI’s current offer is business expertise for your own AI: website migration recipes are available, and the first MCP is free during testing. Use the published MCP address in the connection guide.

Keep six facts in the opening Slack message

Anthropic recommends giving Claude a way to verify its work through tests, screenshots, or expected results. Its Claude Code best-practices guide also separates investigation from implementation when the path is uncertain.

The six-part work request

Part	What to write	Observable example
Business reason	Why this change belongs now	Search Console shows the page for the intended query, but the current title describes a different service.
Affected surface	The exact URL and repository	Change the pricing guide in the website repository.
Evidence	The dated source that supports the decision	Use the owner-approved business brief linked in this thread.
Allowed change	What Claude may and may not edit	Edit the title, description, H1, and opening answer. Preserve prices and the canonical URL.
Verification	The commands and visible checks	Run the site-quality command and return a mobile and desktop preview.
Approval	What remains pending	Create a pull request. Do not merge or publish.

Use a five-step request for consequential changes

1. Inspect the current state

Ask Claude to read the specified files and report the current behavior before editing. This catches a wrong repository, stale brief, or mistaken assumption while no file has changed.

Done when: the Slack thread names the current file, public behavior, and any mismatch with the supplied evidence.

2. Return a proposed change

For a multi-file or unfamiliar change, ask for the intended files, checks, risks, and rollback before implementation. A one-line correction can proceed directly when its boundary is already clear.

Done when: the proposed change can be compared sentence by sentence with the approved brief.

3. Make only the approved change

State the boundary in ordinary language. Do not ask for general improvement when the approval covers one search snippet, form label, or broken link.

Done when: the returned diff contains only the files and behavior needed for the accepted result.

4. Run the required checks

Claude should report each check and its result. For a visual change, include a rendered preview. For a data or form change, include the expected success and failure cases.

Done when: every required command exits successfully and the preview matches the stated acceptance check.

5. Return the owner decision

The final Slack response should link the pull request and preview, list changed files, state unresolved uncertainty, and identify the person who may approve release. GitHub’s pull-request model keeps proposed work available for review before merge.

Done when: the owner can approve, reject, or request a correction without reconstructing what happened.

Two requests a small team can reuse

Example requests

@Claude, in the approved website repository, inspect the integration index and the owner-approved business brief in this thread. Check whether the agreed website-readiness link is absent. If the missing link is confirmed, add one link labeled “Check whether your website is ready” to /integrations/claude/website-ready-for-claude-code. Preserve every existing lesson, price, claim, and link. Run the site-quality command, return one pull request with mobile and desktop previews, and report any uncertainty. Do not merge or publish.

@Claude, inspect the reported broken link on the specified public page. Confirm the intended destination from the approved source. Replace only that link, run the link and build checks, and return the pull request. Stop if the destination redirects somewhere unexpected or requires private access.

Slack context can contain unsafe instructions

Anthropic warns that Claude may follow directions contained in nearby Slack messages. Use trusted channels, name the approved source, and treat copied customer or third-party text as evidence to inspect rather than instructions to execute. Review the Slack security considerations before wider use.

Use published expertise with your own AI

FidelicAI publishes business know-how for the AI you already use. Connect your AI to read the Small Business Website Cookbook, free during testing. Your AI uses its own tools and permissions to apply the recipes.

The cookbook covers website migration, local search and customer journeys, beginning with US local service businesses. Verify the connection and available recipes in your actual host. Standard and Premium have prices coming soon; paid subscriptions are not open.

Your AI keeps business records in its own environment and requests only the relevant method by topic or a short general question. The agent querying instructions define this boundary.

Continue with your own AI

Sources

Put a little know-how to work

Our website and marketing practitioners turn their know-how into recipes for your AI. Start with a website customers can find, understand and use. Try our first cookbook. See what a little know-how can do.

Free to try. No sign-up required. Future Standard and Premium: price coming soon.