risk-assessment
Risk Assessment
Make delivery risk visible before it becomes schedule surprise or production pain.
Context
Risk assessment identifies what could derail the plan and what the team will do about it. In Prodcraft, this is not generic project management paperwork. It is the technical and delivery-focused pass that protects sequencing, scope, and release confidence.
This skill matters most when work crosses service boundaries, introduces migrations, depends on outside teams, or lands in brownfield systems where rollback and coexistence are real constraints.
Inputs
- task-list -- The work items being considered for execution.
- dependency-graph -- The sequencing map that reveals where blockage or critical path fragility exists.
- architecture-doc -- The system context needed to identify structural and operational risk.
Process
Step 1: Identify Risk Categories
More from yknothing/prodcraft
system-design
Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
6ci-cd
Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
6intake
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
6feature-development
Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
6monitoring-observability
Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
6incident-response
Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
6