Loading...
Loading...
Found 24 Skills
Use when identifying launch risks, mitigation plans, and escalation owners.
Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".
Use when managing project uncertainty through structured risk tracking, identifying and assessing risks with probability×impact scoring (risk matrix), assigning risk owners and mitigation plans, tracking contingencies and triggers, monitoring risk evolution over project lifecycle, or when user mentions risk register, risk assessment, risk management, risk mitigation, probability-impact matrix, or asks "what could go wrong with this project?".
Build a pre-implementation harness for ambiguous or risky coding tasks by grounding the request in the repository, producing a structured impact map, surfacing ambiguities and risks, defining scope boundaries, and creating a validation-ready implementation contract before any code changes are made. Use when a task is broad, underspecified, cross-cutting, or likely to drift without an explicit planning checkpoint.
Helps fail fast on risky implementation steps by prototyping before committing to full code changes. Use during planning or implementation when a step is ambiguous, depends on multiple subsystems or flaky tools, may invalidate the current plan, or when repeated fix attempts suggest a doom loop. Useful both at planning step and during implementation.
You are **Project Shepherd**, an expert project manager who specializes in cross-functional project coordination, timeline management, and stakeholder alignment. You shepherd complex projects from ...
Use when you need to perform D1 research during the Spec-level design phase (output `{FEATURE_DIR}/design/research.md`), or when you face critical uncertainties/high-risk points that require verification first instead of directly proceeding to D2; common symptoms include lack of evidence to support trade-offs, unknown items written as TODOs/to-be-confirmed issues, attempting to guess the FEATURE_DIR under pressure, or writing research as implementation details.
Use when decisions could affect groups differently and need to anticipate harms/benefits, assess fairness and safety concerns, identify vulnerable populations, propose risk mitigations, define monitoring metrics, or when user mentions ethical review, impact assessment, differential harm, safety analysis, vulnerable groups, bias audit, or responsible AI/tech.
Guidance on when to ask clarifying questions vs proceed with standard approaches. Reduces interaction rounds while preventing wrong assumptions.
Expert legal advisor specializing in technology law, compliance, and risk mitigation. Masters contract drafting, intellectual property, data privacy, and regulatory compliance with focus on protecting business interests while enabling innovation and growth.
/em -stress-test — Business Assumption Stress Testing
Conduct threat modeling using STRIDE methodology. Identify threats, assess risks, and design security controls. Use when designing secure systems or assessing application security.