Editing CC-016: Mira Growth Hack (section)

== Concrete group activities ==

The campaign should not ask groups to "use an AI bot" in the abstract. Each pilot group gets a simple 7-day playbook with concrete actions inside the existing Telegram chat.

Suggested default playbook:

* '''Day 0 — Crew setup:''' add @mira to the group, explain the 7-day sprint, ask members to opt in, and let Mira produce a short group profile: who is here, what the group appears to work on, and what the sprint will try to improve.
* '''Daily morning kickoff:''' Mira asks each member for one goal, one blocker, and one help request. Mira summarizes owners and priorities for the day.
* '''Daily blocker clinic:''' members mention a blocker during the day; Mira groups similar blockers, suggests next actions, and identifies who can help whom.
* '''Daily evening recap:''' Mira summarizes what changed, what remained blocked, what decisions were made, and what should happen tomorrow.
* '''Decision log:''' when the group makes a decision, Mira records it as a short decision note with context, owner, deadline, and open risks.
* '''Use-case day:''' once or twice during the sprint, the group tries one specific Mira capability relevant to them, for example content planning, lead follow-up, crypto alert, task list, meeting summary, or research digest.
* '''Proof card / recap artifact:''' Mira creates a shareable non-sensitive summary: "what this crew clarified in 7 days", "blockers resolved", "ritual streak", and one safe testimonial quote.
* '''Referral/share step:''' the group shares the proof artifact with a UTM link so another Telegram group can start the same sprint.
* '''Day 7 retrospective:''' Mira asks what was useful, what was annoying, whether the group wants to keep Mira, and which one workflow should continue after the sprint.

Examples by group type:

* '''Founder / operator chat:''' goals, blockers, follow-ups, investor/customer update draft.
* '''Creator squad:''' content calendar, daily publishing commitments, post recap, idea backlog.
* '''Crypto / Web3 group:''' token/news watchlist, decision log, community update, lightweight risk reminder.
* '''Student / hackathon team:''' task split, deadline reminders, demo script, final retrospective.
* '''Community moderation group:''' incoming issue triage, FAQ draft, weekly community summary.

The minimum viable version needs only kickoff, recap, retrospective, and one proof artifact. Everything else is optional. This keeps the hack executable in 10 days.