osprey-development

Coordinate cross-implementation development for Osprey parity across OspreySharp and Rust osprey.

17|2|Updated Jan 10, 2026

Search Tags:#workflow #csharp #rust #guidelines #parity #osprey #cross-implementation

Ready to run

npx skills add https://github.com/ProteoWizard/pwiz-ai --skill osprey-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: osprey-development
Source: https://github.com/ProteoWizard/pwiz-ai/tree/main/claude/skills/osprey-development
Command: npx skills add https://github.com/ProteoWizard/pwiz-ai --skill osprey-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate cross-implementation development for Osprey parity across OspreySharp and Rust osprey.

Core Features & Use Cases

Dual-tree development guidance: follows Skyline conventions for OspreySharp and upstream Rust conventions for Rust osprey.
Cross-implementation parity validation: provides cross-impl validation gates, parity checks, and documentation references to ensure consistent behavior between implementations.
Workflow & governance: outlines the required workflows, critical rules, and TODO/tracking system to coordinate multi-team work.

Quick Start

Consult the Osprey development guide before touching OspreySharp or Rust osprey code to ensure parity and proper workflow.

Frequently Asked Questions about osprey-development

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

FAQPage Schema

How do I maintain parity between C# and Rust implementations of the same project?▼

To maintain parity between C# and Rust implementations, use cross-implementation coordination workflows that enforce conventions for each language and provide validation gates to ensure consistent behavior across both codebases.

What are parity validation gates in cross-implementation development?▼

Parity validation gates are cross-implementation checks used during development to verify that C# and Rust implementations exhibit consistent behavior, serving as required verification stops before merging code.

How do I track TODOs across multiple teams working on different language implementations?▼

Track cross-team TODOs by utilizing a governance system that outlines required workflows, critical rules, and TODO-tracking practices to ensure multi-team work stays aligned across both implementation trees.

Does the Osprey development workflow follow standard C# and Rust conventions?▼

Osprey development follows dual-tree conventions: Skyline conventions for OspreySharp in C# and upstream Rust conventions for the Rust osprey implementation, ensuring both projects adhere to their respective language standards.

When do I need to consult cross-implementation development guidelines?▼

Consult cross-implementation development guidelines before touching either the OspreySharp or Rust osprey codebases to ensure proper workflow adherence, parity validation, and end-to-end verification before making changes.

What is the best way to verify end-to-end behavior across OspreySharp and Rust osprey?▼

The best way to verify end-to-end behavior is to apply provided tooling for end-to-end verification and pass cross-implementation parity checks, validating that both implementations produce matching results.