Operations maintenance
Skill krkruk/openspec-vibe-with-esa-touch/.claude/skills/operations-maintenance
Use ESA's SDLC, develop some agent skills and hope for the bestFrom the repository description
npx -y skills add krkruk/openspec-vibe-with-esa-touch --skill operations-maintenanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.2 KB, 615 tokens by cl100k_base, as published. Nobody here has run it
Operations & Maintenance
This skill guides you through the Operations and Maintenance phase of the ECSS software development pipeline.
Purpose
This phase involves continuous support and modification of the software after it is in use. It covers helpdesk support, error correction, migration to new environments, and eventually retirement.
Key Activities
- Helpdesk support: Provide ongoing operational support to users
- Error correction: Identify, analyze, and fix defects found during operations
- Software updates: Create and deploy new releases with fixes or enhancements
- Migration to new environments: Move software to new hardware/software platforms as needed
- Operational testing: Test new releases before deployment
- Ongoing security analysis: Continuously monitor and address security vulnerabilities
Maintenance Activities
Different types of maintenance:
- Corrective maintenance: Fix defects discovered during operations
- Adaptive maintenance: Adapt software to changes in environment
- Perfective maintenance: Improve performance or maintainability
- Preventive maintenance: Address potential issues before they occur
V&V Focus
Verification and validation activities in this phase focus on:
- Operational testing for new releases
- Verification that changes don't introduce regressions
- Ongoing security analysis and vulnerability assessment
- Verification of migration procedures
- Regression testing for software updates
Milestone: ORR (Operational Readiness Review)
The ORR confirms software readiness for mission start. Before ORR approval, ensure:
- Software is installed and operational
- Support procedures are in place
- Helpdesk support is available
- Initial operational testing is completed
- Security analysis is current
- Operational procedures are documented
- Training is complete
- Software is ready for mission operations
Lifecycle End
When software reaches end of life:
- Plan retirement activities
- Migrate or decommission as appropriate
- Preserve historical data and documentation
- Complete final security analysis
Inputs & Outputs
| Inputs | Outputs |
|---|---|
| Operational software | Error reports |
| User feedback | Error corrections |
| New requirements | Software updates |
| Environment changes | Migration documentation |
| Retired software (at end of life) |
Checklist
- Helpdesk support procedures established
- Support team trained and available
- Error tracking system in place
- Error correction process defined
- Software release process defined
- Operational testing for releases completed
- Regression testing procedures in place
- Security analysis ongoing
- Vulnerability management process active
- Migration procedures documented
- Backup and recovery procedures in place
- Operational documentation current
- ORR package prepared and reviewed
Related Phases
- Previous: Delivery & Acceptance (invoke
/delivery-acceptance) - Next: None (final phase)
End of ECSS Software Development Lifecycle
After completion of this phase, the software enters ongoing operations and maintenance until retirement or replacement.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 615 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- fix defects found during operations
- deploy new releases with fixes or enhancements
- move software to new platforms as needed
- test new releases before deployment
- monitor and address security vulnerabilities
- ensure software is installed and operational
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.