Menu
Use when analysing feasibility, dependency impact, and sketching API for new features. Load during the Analysis phase of SDLC.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when designing module placement, type design, and API surface for new features in rvlibs. Load during the Design phase of SDLC.
Use when refactoring large files (800+ lines) — both source and test code — by splitting into sibling modules or submodules based on scope and concern boundaries.
Use when reviewing code changes for correctness, style, conventions, testing, and security. Load during Implementation phase as a quality gate.
Use when implementing new features in rvlibs following conventions and existing patterns. Load during the Implementation phase of SDLC.
Use when triaging, diagnosing, and registering bugs or issues. Covers classification, reproduction, severity, and registration.
Use when ensuring feature quality through testing, coverage gates, and pre-merge verification. Load during the Testing phase of SDLC.
| name | system-analysis |
| description | Use when analysing feasibility, dependency impact, and sketching API for new features. Load during the Analysis phase of SDLC. |
SDLC Phase: Analysis
Analyse requirements, determine feasibility, and map dependency impact.
rvlibs.unsafe. If unsafe is unavoidable, it must be documented and justified.Map the change against the dependency graph:
rvlibs.Evaluate implementation viability:
docs/conventions.md). Does the approach require newer Rust features?Before implementation, sketch the public API:
Analysis may uncover issues that require human judgement:
rvlibsunsafe codeWhen such an issue is found, stop and present the finding to the user. Do not proceed to design or implementation without confirmation.