m3taz-ahmed/aizee / skills/bmad-advanced-elicitation
bmad-advanced-elicitation
VerifiedPushes a draft off its first answer with critique methods and proposes one revision. Use when the user or another skill names bmad-advanced-elicitation, or the user says "advanced elicitation". Not for a critique or a named method such as pre-mortem without that name.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.1 KB |
| assets/methods.csv | other | 8.9 KB |
| bmod.toml | config | 122 B |
| customize.toml | config | 3.4 KB |
| evals/cases.json | config | 6.1 KB |
| evals/files/pantry-pal.md | markdown | 1.2 KB |
| evals/files/prd-notifications.md | markdown | 3.2 KB |
| evals/files/rollout-plan.md | markdown | 1.3 KB |
| evals/triggers.json | config | 3.1 KB |
| scripts/pick_methods.py | script | 16.1 KB |
| scripts/tests/test_pick_methods.py | script | 14.5 KB |
evals/files/prd-notifications.md
View on GitHub# PRD — Section 4: Notifications
## 4.1 Purpose
Teams using Tasklane miss changes to the tasks they care about. Today the only signal is the activity feed, which users check about twice a day according to our analytics. This section defines a notification system that tells users about the changes that matter to them, through the channel they prefer, without adding noise.
## 4.2 Users
- **Contributors** own tasks and need to know when someone comments on, reassigns or changes the due date of a task they own.
- **Leads** watch a project and need to know when a task in it becomes blocked or overdue.
- **Admins** manage the workspace and need to know about billing and security events.
## 4.3 Channels
Notifications go out in three channels:
- In-app: the bell icon in the top bar, with an unread count.
- Email: one message per notification, sent from `notifications@tasklane.io`.
- Mobile push: through our iOS and Android apps.
Every user gets all three channels by default.
## 4.4 Functional requirements
**FR-1 Task events.** The system sends a notification to a task's owner when another user comments on the task, reassigns it, or changes its due date.
**FR-2 Project events.** The system sends a notification to every lead watching a project when a task in that project is marked blocked or passes its due date.
**FR-3 Admin events.** The system sends a notification to every admin when a payment fails or a new admin is added.
**FR-4 Timeliness.** Notifications must feel timely to the user.
**FR-5 Grouping.** When several events about the same task happen within a short time, the system groups them into one notification that lists each event.
**FR-6 Quiet hours.** A user can set quiet hours. During quiet hours no push notifications are sent; they are delivered when quiet hours end. Quiet hours are evaluated in the server's time zone (UTC).
**FR-7 Read state.** Reading a notification in any channel marks it read in every channel.
## 4.5 Non-functional requirements
**NFR-1 Latency.** A notification is delivered to every channel within 1 second of the triggering event at p99.
**NFR-2 Volume.** The system handles 2 million notifications per day at launch and 10 million within a year.
**NFR-3 Reliability.** No notification is lost. Delivery is at least once; duplicates are acceptable for in-app but not for email.
## 4.6 Architecture notes
The notification service consumes task events from the existing event bus. To keep email and push costs down, the service batches pending notifications and sends each batch every 5 minutes. In-app notifications are written to the notifications table at the same time as the batch send.
## 4.7 Acceptance criteria
- A contributor who owns a task receives a notification in all three channels when another user comments on it.
- A lead receives a notification when a watched task becomes blocked.
- An admin receives a notification when a payment fails.
- Grouped notifications list every grouped event in order.
- Reading a notification on mobile marks it read on the web within 10 seconds.
## 4.8 Out of scope
- Slack and Microsoft Teams integrations.
- Digest emails (daily or weekly summaries).
- Per-project notification settings.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |