Онлайн підключилось майже 80 людей — новий абсолютний рекорд!
Але також багато людей попросили поділитися записом, тому — будь ласка)
Подивитись можна на ютубі - https://youtu.be/DBzhWDE_nrs
Презентація доступна за посиланням: клік сюди
Також Гліб поділився обіцяними промптами:
1. Decoding a vague task — "I got a task and don't understand what they want"
```
I received a task/message and I need to understand what exactly is expected from me. Here's the text:
[paste the message + attach files if any]
Do the following:
1. Break the message down piece by piece and turn it into a concrete list of deliverables — what exactly needs to be delivered
2. Flag what is stated explicitly vs. what I'd have to assume or clarify
3. Draft 2-3 clarifying questions for the author if there are ambiguities (in English, short)
4. Propose an execution plan with the order of steps and a rough time estimate
```2. Meeting summary → follow-up (you have tl;dv connected — use it directly)
```
Find my meeting [name/date] in tl;dv and, based on the transcript, produce:
1. A 5-7 point summary: what was decided, what remains open
2. Action items as a table: task / owner / deadline (if mentioned)
3. A list of my personal commitments — what I specifically promised to do
4. A draft follow-up message to the participants in English: short, to the point, confirming the agreements
```3. Proactive client status update (closes the "client sent 22 messages waiting" pattern)
```
Help me put together a status update for the client/management. Here's the raw input:
- Done since the last update: [...]
- Currently in progress: [...]
- Blockers/risks/delays: [...]
- What I need from the client: [...]
Write it in English in this format: short intro → Progress → In Progress → Blockers/Risks → Needed from you → Next update date. Professional tone, no fluff. If there's a delay, frame it proactively: state the fact first, then the resolution plan, no excuses. Give me 2 versions: a brief one for Slack and a longer one for email.
```4. Cost Estimate / task breakdown
```
Help me build a Cost Estimate. Here's the scope from the client:
[work description / brief]
Do the following:
1. Break the work down into tasks and subtasks (bottom-up, not reverse-engineered from the client's budget)
2. For each task — space for the hours estimate with a range (optimistic / realistic) and space for the assumptions behind it. Don't calculate on your own.
3. Proportional PM/AS/TS hours based on the total work volume
4. Totals: minimum total = sum of tasks, maximum total = minimum +50%
5. A list of questions for the client that could change the estimate
Mark it as a draft to be validated with the team.
```
5. Documentation → Confluence
```
I need to turn raw materials into a Confluence page. Sources attached: [README / notes / files].
Build the page in Markdown, ready to paste:
1. Structure: What is it → Why it matters → Architecture → How to use → Known issues → Open questions
2. Write for a reader seeing the product for the first time — assume no prior context
3. Tables for comparisons and known issues, code blocks for commands
4. At the end — a "For team discussion" section with open questions I should raise
5. Language: English
Before building, ask me 2-3 questions if the sources contain contradictions or gaps.
``
