Skills
.Work. You
Rest

derive-technical-risks

Community

Surface architecture risks before launch.

Software Engineering#technical debt#deterministic planning#enterprise delivery#decision manifest#architecture risk#compliance readiness#risk registry
Authorkapilvirenahuja
Version1.0.0
Installs0

System Documentation

What problem does it solve?

It helps teams identify and document concrete technical risks late in the architecture process so failures don’t surprise you during implementation or production rollout.

Core Features & Use Cases

  • Stage-locked risk identification (Stage 6, runs last): Halts if earlier architecture artifacts are missing to avoid blind or speculative risk registers.
  • Eight grounded discovery scans: Derives risks from logical/physical architecture, tech stack conditions (EOL/bleeding-edge), system inventory maturity, quality profile targets, epic failure conditions, compliance patterns, and KB-described failure modes.
  • Decision-manifest traceability: Writes a technical-risks.yaml register plus a decision manifest that records how each risk was surfaced and how it should be handled.

Quick Start

Ask an orchestrator to run derive-technical-risks after Steps 1–5 have produced the quality profile, systems inventory, logical/physical architecture, and tech-stack artifacts to generate technical-risks.yaml and decision-manifest-derive-technical-risks.yaml.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: derive-technical-risks
Download link: https://github.com/kapilvirenahuja/garura/archive/main.zip#derive-technical-risks

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.