Skip to content

Epic: Rust skills gap fill from systems programming best practices #62

@AlexMikhalev

Description

@AlexMikhalev

Context

Gap analysis of existing rust-development and rust-performance skills against the Rust System Programming Best Practices guide (mid-2025 edition, 14 sections).

Full analysis: cto-executive-system/plans/rust-systems-skills-gap-analysis.md

Current Coverage

  • Well covered: Project structure, memory/zero-copy, basic async, error handling, performance optimization, unsafe code policy
  • Partial: Advanced async (missing Tower/backpressure), testing (missing Miri/fuzzing), build profiles (missing size-opt)
  • Gaps: Concurrency primitives, FFI, CI/CD pipeline, production observability

Approach: Extend Existing + Two New Skills

Extend rust-development, rust-performance, and testing with missing sections. Create two new skills for genuinely new cross-cutting capabilities.

Disciplined Engineering Alignment

Every sub-issue includes a V-model phase mapping table showing how the Rust-specific guidance integrates with the disciplined-* skills:

  • disciplined-research (Phase 1): Each skill extension specifies what to audit/profile during research
  • disciplined-design (Phase 2): Each specifies design-time decisions (e.g., Tower stack, memory ordering rationale, CI gate thresholds)
  • disciplined-implementation (Phase 3): Each defines incremental implementation steps
  • disciplined-verification (Phase 4): Each maps to verification tools (Miri, TSan, fuzz, benchmarks)
  • disciplined-validation (Phase 5): Each defines production-readiness criteria

Cross-references to quality-gate and devops skills are included where applicable.

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions