pre-mortem
Pre-mortem
Skill workflow — pre-mortem can be used standalone or as a gate between steps:
create-prd (gather requirements) → pre-mortem (stress-test before building) → plan-from-prd (phase it out)
Two modes
Mode 1 — Idea exploration: The user has an idea, not yet a document. Interview them relentlessly to surface assumptions, constraints, and design implications. Help them reach a first draft design.
Mode 2 — PRD stress-test: The user has an existing PRD, plan, or design doc. Read it first, then interrogate every assumption, surface contradictions, and explore functional ramifications they may not have considered.
In both modes: walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
If a question can be answered by exploring the codebase, explore the codebase instead. Always use subagents to explore the codebase or for research.
Complexity challenge
When the scope of what emerges feels large — many moving parts, cross-cutting concerns, or a broad user-facing surface area — challenge the user to identify a first sufficient MVP wave before exploring all edge cases. Ask: "What is the smallest version of this that delivers real value?" Encourage decomposing the work into successive waves rather than attempting a complete solution upfront.
More from yldgio/vibe-grimoire
create-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
11setup-repo
>-
11prd-slice
Break a PRD into independently-deliverable work items (vertical slices / tracer bullets) and create them in Azure DevOps, GitHub Issues, or Jira. Use when a user wants to convert a PRD into implementation tickets, decompose a product spec into trackable slices, create work items from requirements, or break down a PRD for any issue tracker — even if they don't say "vertical slice" or "tracer bullet".
11plan-from-prd
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
11tdd
>-
9adr
Create an Architectural Decision Record (ADR) to formally document a significant technical or architectural choice. Use whenever a user says "write an ADR", "document this decision", "record why we chose X", "capture this architecture choice", "explain why we went with Y", "document the trade-offs", "write up this tech decision", or makes any significant architectural choice that future teammates will need to understand. Also use proactively when you observe a meaningful decision being made during a session — even if the user hasn't explicitly asked for an ADR. ADRs prevent teams from re-debating settled choices and preserve context that would otherwise become tribal knowledge lost to future maintainers.
7