feature-risk-assessment

Produces structured deep-dive risk assessments for escalated product features.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/tk1cntt/PhapChe --skill feature-risk-assessment-tk1cntt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-risk-assessment
Source: https://github.com/tk1cntt/PhapChe/tree/main/docs/claude-for-legal-main/product-legal/skills/feature-risk-assessment
Command: npx skills add https://github.com/tk1cntt/PhapChe --skill feature-risk-assessment-tk1cntt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Launch reviews are broad but shallow; when a single feature raises a novel or high-stakes legal issue, teams need a standalone, structured risk assessment rather than a one-line table entry. ## Core Features & Use Cases - Structured Risk Analysis: Breaks each risk into scenario, affected parties, likelihood, severity, existing mitigations, gaps, and residual risk. - Regulatory and Precedent Context: Covers active regulator attention and comparable company outcomes, with mandatory source attribution and citation verification tags. - Decision Framing: Presents 2-3 shipping options with trade-offs and a clear recommendation, ending in a next-steps decision tree. - Use Case: After a launch review flags a new AI recommendation feature, run this skill to produce a 2-4 page decision document covering what could go wrong, how likely it is, and which mitigation option to ship with. ## Quick Start Ask the assistant to run a feature risk assessment on the escalated feature, for example: "Do a deep-dive risk assessment for the new recommendation feature."

Frequently Asked Questions about feature-risk-assessment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I do a legal risk assessment for a product feature?

Run this skill on the escalated feature to produce a structured document covering risk scenarios, likelihood, severity, existing mitigations, gaps, and residual risk. It ends with 2-3 shipping options and a recommendation so a decisionmaker can act.

When should a feature get a deep-dive risk assessment instead of a launch review?

Use it when a launch review flags a novel issue, something in the usually-blocks category, active regulatory attention such as AI or children's products, or when leadership asks for more than a one-line answer. Most features only need the standard launch review.

Does the risk assessment make the ship or no-ship decision?

No. The assessment frames the decision by presenting options, trade-offs, and a recommendation, but someone with authority picks the option. It is a decision document, not a decision.

How are legal citations in the risk assessment verified?

Every citation in the Regulatory landscape and Precedent sections must be tagged with its source, such as Westlaw, CourtListener, web search, or model knowledge. Citations tagged verify must be checked against a legal research tool before the document reaches a decisionmaker.

What are the limitations of this feature risk assessment?

It is qualitative only and does not perform quantitative risk modeling; companies with formal numeric risk frameworks should use those instead. It also does not replace a PIA or AI governance record, which are generated by separate skills.