nasa-se

What this skill does

# NASA Systems Engineering Skill

> **Version:** 1.2.0
> **Framework:** Jerry NASA SE (NSE)
> **Standards:** NASA/SP-2016-6105 Rev2, NPR 7123.1D, NPR 8000.4C
> **Constitutional Compliance:** Jerry Constitution v1.0

---

## Document Audience (Triple-Lens)

This SKILL.md serves multiple audiences:

| Level | Audience | Sections to Focus On |
|-------|----------|---------------------|
| **L0 (ELI5)** | Project stakeholders, new users | [Purpose](#purpose), [When to Use](#when-to-use-this-skill), [Routing Disambiguation](#routing-disambiguation), [Quick Reference](#quick-reference) |
| **L1 (Engineer)** | Engineers invoking agents | [Invoking an Agent](#invoking-an-agent), [Adversarial Quality Mode](#adversarial-quality-mode), [Agent Details](#agent-details) |
| **L2 (Architect)** | SE workflow designers | [Orchestration Flow](#orchestration-flow), [State Passing](#state-passing-between-agents), [NPR Processes](#nasa-common-technical-processes-npr-71231d) |

---

## Purpose

The NASA Systems Engineering skill provides a structured framework for applying NASA SE processes through specialized agents. Each agent implements specific NASA Common Technical Processes (NPR 7123.1D) and produces **persistent artifacts** following NASA work product standards.

### Key Capabilities

- **Requirements Engineering** - Formal "shall" statements, traceability matrices (NPR 7123.1D Process 2, 11)
- **Verification & Validation** - VCRMs, test planning, evidence collection (NPR 7123.1D Process 7, 8)
- **Risk Management** - 5x5 risk matrices, risk registers, mitigation tracking (NPR 8000.4C)
- **Technical Reviews** - SRR/PDR/CDR/FRR packages with entrance/exit criteria (NPR 7123.1D Appendix G)
- **System Integration** - Interface control documents, integration verification (NPR 7123.1D Process 6, 12)
- **Configuration Management** - Baseline control, change management (NPR 7123.1D Process 14, 15)
- **Technical Architecture** - Trade studies, design decisions, logical decomposition (NPR 7123.1D Process 3, 4, 17)
- **SE Status Reporting** - Technical assessment, progress metrics (NPR 7123.1D Process 16)

---

## Disclaimer

```
DISCLAIMER: This guidance is AI-generated based on NASA Systems Engineering
standards. It is advisory only and does not constitute official NASA guidance.
All SE decisions require human review and professional engineering judgment.
Not for use in mission-critical decisions without SME validation.
```

---

## When to Use This Skill

Activate when:

- Defining or managing system requirements
- Planning or executing verification/validation activities
- Identifying, assessing, or mitigating risks
- Preparing for technical reviews (SRR, PDR, CDR, FRR)
- Managing system interfaces and integration
- Controlling configuration baselines
- Making architectural design decisions
- Reporting on systems engineering status

---

## Available Agents

| Agent | Role | NASA Processes | Output Location |
|-------|------|----------------|-----------------|
| `nse-requirements` | Requirements Engineer | 1, 2, 11 | `requirements/` |
| `nse-verification` | V&V Specialist | 7, 8 | `verification/` |
| `nse-risk` | Risk Manager | 13 | `risks/` |
| `nse-reviewer` | Technical Review Gate | All (assessment) | `reviews/` |
| `nse-integration` | System Integration | 6, 12 | `integration/` |
| `nse-configuration` | Config Management | 14, 15 | `configuration/` |
| `nse-architecture` | Technical Architect | 3, 4, 17 | `architecture/` |
| `nse-explorer` | **Exploration Engineer (Divergent)** | 5, 17 | `exploration/` |
| `nse-qa` | **Quality Assurance Specialist** | 14, 15, 16 | `qa/` |
| `nse-reporter` | SE Status Reporter | 16 | `reports/` |

All agents produce output at three levels:
- **L0 (ELI5):** Executive summary for non-technical stakeholders
- **L1 (Software Engineer):** Technical implementation details
- **L2 (Principal Architect):** Strategic implications and trade-offs

---

## NASA Common Technical Processes (NPR 7123.1D)

### System Design Processes (1-4)
1. Stakeholder Expectations Definition
2. Technical Requirements Definition
3. Logical Decomposition
4. Design Solution Definition

### Product Realization Processes (5-9)
5. Product Implementation
6. Product Integration
7. Product Verification
8. Product Validation
9. Product Transition

### Technical Management Processes (10-17)
10. Technical Planning
11. Requirements Management
12. Interface Management
13. Technical Risk Management
14. Configuration Management
15. Technical Data Management
16. Technical Assessment
17. Decision Analysis

---

## Invoking an Agent

### Option 1: Natural Language Request

Simply describe what you need:

```
"Create a requirements specification for the authentication module"
"Assess risks for the deployment phase"
"Prepare CDR entrance checklist for the API service"
"Generate a traceability matrix for Phase 1 requirements"
"Review interfaces between frontend and backend systems"
```

The orchestrator will select the appropriate agent based on keywords and context.

### Option 2: Explicit Agent Request

Request a specific agent:

```
"Use nse-requirements to define shall-statements for user authentication"
"Have nse-risk create a 5x5 risk matrix for the integration phase"
"I need nse-reviewer to prepare the PDR entrance package"
```

### Option 3: Task Tool Invocation

For programmatic invocation within workflows:

```python
Task(
    description="nse-requirements: Auth Requirements",
    subagent_type="general-purpose",
    prompt="""
You are the nse-requirements agent (v1.0.0).

## NSE CONTEXT (REQUIRED)
- **Project ID:** PROJ-002
- **Entry ID:** e-001
- **Topic:** Authentication Requirements

## MANDATORY PERSISTENCE (P-002)
Create file at: projects/PROJ-002-nasa-systems-engineering/requirements/proj-002-e-001-auth-requirements.md

## REQUIREMENTS TASK
Define formal requirements for user authentication following NPR 7123.1D Process 2.
Include: shall-statements, rationale, verification method, parent traceability.
"""
)
```

---

## Orchestration Flow

### Technical Review Preparation Example

For preparing a Critical Design Review (CDR):

```
User Request: "Prepare for CDR on the API service"

1. nse-requirements → Verify all requirements baselined
   Output: requirements/proj-002-e-001-requirements-status.md

2. nse-architecture → Confirm design decisions documented
   Output: architecture/proj-002-e-002-design-summary.md

3. nse-risk → Update risk register, identify RED risks
   Output: risks/proj-002-e-003-risk-status.md

4. nse-verification → V&V planning status
   Output: verification/proj-002-e-004-vv-status.md

5. nse-reviewer → CDR entrance checklist evaluation
   Output: reviews/proj-002-e-005-cdr-entrance.md
```

### Agent Dependency Graph

```
                    ┌─────────────────┐
                    │  nse-reporter   │ (Terminal - aggregates all)
                    └────────┬────────┘
           ┌─────────────────┼─────────────────┐
    ┌──────▼──────┐   ┌──────▼──────┐   ┌──────▼──────┐
    │ nse-reviewer│   │  nse-risk   │   │nse-config   │
    └──────┬──────┘   └──────┬──────┘   └──────┬──────┘
    ┌──────▼──────┐   ┌──────▼──────┐   ┌──────▼──────┐
    │nse-verific. │   │nse-integr.  │   │nse-archit.  │
    └──────┬──────┘   └──────┬──────┘   └──────┬──────┘
           └─────────────────┼─────────────────┘
                    ┌────────▼────────┐
                    │nse-requirements │ (Foundation)
                    └─────────────────┘
```

### State Passing Between Agents

Agents can reference each other's output using state keys:

| Agent | Output Key | Provides |
|-------|------------|----------|
| nse-requirements | `requirements_output` | Requirements baseline, traceability |
| nse-verification | `verification_output` | V&V status, VCRM |
| nse-risk | `risk_output` | Risk register, mitigation status |
| nse-reviewer | `review_output` | Review findings, action items |
| nse-integration | `integration_output` | Interface status, ICD |
| nse-configuration | `c