Loading...
Loading...
Found 6 Skills
Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
Expert in understanding and navigating legacy codebases. Covers code archaeology techniques, finding hidden knowledge, mapping dependencies, and extracting understanding from code without documentation. Knows how to read the stories that old code tells. Use when "legacy code, old codebase, understand this code, archaeology, what does this do, no documentation, ancient code, " mentioned.
30/60/90/120 day ramp milestones. Activity expectations by week, certification progress, early warning indicators.
Use to stress-test predictions by assuming they failed and working backward to identify why. Invoke when confidence is high (>80% or <20%), need to identify tail risks and unknown unknowns, or want to widen overconfident intervals. Use when user mentions premortem, backcasting, what could go wrong, stress test, or black swans.
Direct technical advisor mode for counting/estimation and architecture/design