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/rollout-plan.md
View on GitHub# Keyring SSO Rollout Plan
## Goal
Move every customer tenant from our in-house login to Keyring SSO by the end of Q1, so we can retire the legacy auth service and its two open security findings.
## Approach
We migrate tenant by tenant. For each tenant we import its users into Keyring, switch the tenant's login route to Keyring, and turn off the legacy password form for that tenant. Users keep their email addresses as identifiers, so no one needs a new account.
## Team
Two backend engineers, full time, for six weeks. Support is briefed before each phase.
## Phases
| Phase | Week | Tenants | Notes |
|---|---|---|---|
| 1 | 1–2 | 5 internal and friendly tenants | Shake out the import script |
| 2 | 3–4 | 60 self-serve tenants | Automated import, no manual review |
| 3 | 5 | 40 enterprise tenants | Each needs its own SAML setup with the customer's IT team |
| 4 | 6 | Cleanup | Remove the legacy login code |
## Cutover
At cutover for a tenant, all existing sessions are invalidated so that every user logs in once through Keyring. The legacy password hashes are deleted the same day.
## Risks
- Import script bugs. Mitigated by phase 1.
- Keyring outage. Keyring's SLA is 99.95%.
## Success
The migration is a success if it goes smoothly and customers are happy.
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 |