29 reviewed prompts.
Maps how a feature or system you own could be attacked or misused and lists prioritized defenses, detection and tests. Use during design or before a security review of your own product.
Reviews an infrastructure-as-code change and its plan output for destroyed or replaced resources, leaked secrets, blast radius and version drift, then gives a validation and rollback plan. Use it before applying changes to shared environments.
Looks at what came in and went out this month, compares it with your plan, spots where money leaked and suggests small changes for next month. Use at the end of each month in about ten minutes.
Turns rough notes about your work into an evidence-based self-review with impact stories, collaboration examples and a growth plan. Use it before an annual or mid-year review.
Reads a product requirements document (PRD) and points out missing pieces, vague requirements, untested assumptions and open questions, ranked by how much they could hurt the project. Use before sign-off or handover to design and engineering.
