Slack App Initial Setup Support

Workflow

1. Read docs/setup-guide.md and identify the user's current setup phase.
2. Inspect local prerequisites only when they matter for the next step:
   • repository checkout and branch state
   • .env presence and placeholder values
   • slack.json deployment configuration
   • commands from the guide such as deno task check, deno task test, and slack deploy --env production
3. Give the next smallest useful step with:
   • the exact command or file to touch
   • the expected success signal
   • the human confirmation needed in Slack
4. Before advancing, restate the completion criteria for that phase using docs/setup-guide.md.
5. When something fails, troubleshoot against the guide's よくある詰まりどころ section first, then inspect repository-specific configuration if needed.

Guardrails

• Do not treat slack run as sufficient for Workflow Builder availability; the guide requires slack deploy --env production.
• Do not edit secrets or production workspace settings unless the user clearly asked for that change.
• Prefer flagging missing or placeholder configuration over auto-filling values.
• Call out human checkpoints explicitly for channel membership, private channel invitations, and post-deploy verification.
• If you discover recurring setup drift, propose a doc update and make that change when the user asks for it.