Sw requirements architecture
Skill krkruk/openspec-vibe-with-esa-touch/.claude/skills/sw-requirements-architecture
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 sw-requirements-architectureAssembled 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
2.5 KB, 483 tokens by cl100k_base, as published. Nobody here has run it
Software Requirements & Architecture
This skill guides you through the Software Requirements and Architecture Engineering phase of the ECSS software development pipeline.
Purpose
This phase transforms the Requirements Baseline (RB) into a detailed technical specification and top-level software architecture. It defines the structure, components, and interfaces that will guide implementation.
Key Activities
- Transform RB to technical specification: Convert system requirements into detailed software requirements
- Identify software components: Break down the system into manageable software items
- Define external interfaces: Specify all interfaces between software and external systems/hardware
- Establish computational model: Define the real-time execution model for the software
- Design top-level architecture: Create the structural foundation for the software
V&V Focus
Verification activities in this phase focus on:
- Technical specification verification
- Architectural design verification
- Establishment of Software Verification Plan (SVerP)
- Establishment of Software Validation Plan (SValP)
Milestone: PDR (Preliminary Design Review)
The PDR is the gate to the detailed design phase. Before PDR approval, ensure:
- Technical specification is complete and baselined
- Software architecture is defined and documented
- Software components and their relationships are identified
- External interfaces are specified
- SVerP and SValP are established
- Real-time performance model is defined
Inputs & Outputs
| Inputs | Outputs |
|---|---|
| Requirements Baseline (RB) | Technical specification |
| System architecture | Software architecture design |
| Performance requirements | Component definitions |
| Real-time constraints | Interface specifications |
| SVerP (Software Verification Plan) | |
| SValP (Software Validation Plan) |
Checklist
- Requirements Baseline transformed to technical specification
- Software components identified and defined
- External interfaces specified
- Real-time computational model established
- Top-level architecture designed and documented
- Technical specification complete and verified
- SVerP (Software Verification Plan) created
- SValP (Software Validation Plan) created
- Performance analysis conducted
- PDR package prepared and reviewed
Related Phases
- Previous: System Requirements (invoke
/system-requirements) - Next: Design & Implementation (invoke
/design-implementation)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most architecture codebase skills give in 483 tokens
Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07
- Ask the user which candidate to explorein 45 of 811, across 15 files
- Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
- Read any relevant architecture decision records firstin 31 of 811, across 8 files
- Use exact glossary terms in every suggestionin 30 of 811, across 10 files
- Accept dependencies instead of creating themin 24 of 811, across 5 files
- Include before and after visualisations for each candidatein 24 of 811, across 5 files
- Read the domain glossary before exploringin 24 of 811, across 6 files
- Return results instead of producing side effectsin 23 of 811, across 4 files
- Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
- Introduce seams only where things varyin 22 of 811, across 3 files
- Reduce the number of methodsin 21 of 811, across 2 files
- Design deep modules with small interfacesin 21 of 811, across 3 files
Said here and by no other author read
- transform requirements baseline into technical specification
- identify and define software components
- specify external interfaces
- establish real-time computational model
- design top-level software architecture
- verify technical specification
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.