Step 21: Share Feedback with Devs
Phase: iterate • Optional
Context
The build is complete. Before wrapping up, give the user a chance to share feedback with the bld402 team. This helps the devs understand what works, what breaks, and what to improve.
What to do
1. Ask permission
"Before we wrap up — would you like me to share feedback with the bld402 team about how the build went? I'll summarize my experience and you can add anything you'd like. It helps them improve the platform."
If the user says no: thank them and end. Do not send anything.
2. Write your agent summary
Summarize your experience building the app. Include:
- Which template was used (or "custom build")
- Issues you hit (API errors, confusing docs, RLS problems, etc.)
- What went well
- Suggestions for improvement
- Number of iterations
3. Ask the user for their input
"Anything you'd like to add? This is your chance to tell the devs what you thought — totally optional."
4. Send the feedback
Combine your summary and the user's comments (if any) into one message and send it to the bld402 Telegram bot.
First, fetch the bot token from AWS Secrets Manager — never hardcode it:
BLD402_TELEGRAM_TOKEN=$(aws secretsmanager get-secret-value \
--secret-id "bld402/telegram-bot-token" \
--query SecretString --output text \
--region us-east-1 --profile kychee)
Then send the message:
curl -s -X POST \
"https://api.telegram.org/bot${BLD402_TELEGRAM_TOKEN}/sendMessage" \
-H "Content-Type: application/json" \
-d '{
"chat_id": -5159819495,
"text": "YOUR_MESSAGE_HERE"
}'
This is free — no x402 payment needed.
Message format
📋 bld402 build feedback
App: {app_name} ({template_name} template)
Project: {project_id}
Iterations: {iteration_count}
🤖 Agent notes:
- {issue_or_observation_1}
- {issue_or_observation_2}
- {what_went_well}
👤 User says:
"{user_feedback_or_N/A}"
5. Confirm
"Feedback sent — thanks! The bld402 team will use it to make the platform better."
Expected output
feedback_sent—trueif the user opted in and the message was sent,falseif they declined
Next step
None — the build is complete! If the user wants changes later, resume at Step 17.