How do I install the Aspice Fundamentals skill?

Run npx skillmds@latest add ksmyl/aspice-fundamentals in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aspice Fundamentals safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aspice Fundamentals?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aspice Fundamentals free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aspice Fundamentals?

ksmyl (@ksmyl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aspice Fundamentals by ksmyl — Agent Skill

Name: Aspice Fundamentals
Author: ksmyl

Aspice Fundamentals

ASPICE 3.1 V-model reference for Agent V. Use this skill whenever you encounter ASPICE process IDs (SYS.1, SWE.2, SUP.8, etc.), base practice references (BP1, BP6), work product IDs (WP 17-12, WP 04-04), capability levels, traceability requirements, or any mention of the V-model. Also use when you need to understand what an ASPICE assessor expects, how processes relate to each other, or what 'assessment-ready' means. This is foundational context — consult it early in any Agent V task.

ksmyl Updated Sep 17, 2026

File contents

Automotive SPICE 3.1 — Quick Reference

What ASPICE Is

Automotive SPICE (ASPICE) is a process assessment framework published by VDA QMC, based on ISO/IEC 15504. It defines how software and systems should be developed, verified, and managed. An assessor evaluates whether your project demonstrates that each process was performed (CL1) and managed (CL2) by examining work products, traceability, and review evidence.

Capability Levels

Level	Name	What It Means
0	Incomplete	Process not implemented or fails to achieve its purpose.
1	Performed	Process achieves its purpose. Base practices are demonstrated. Work products exist.
2	Managed	Process is planned, monitored, and adjusted. Work products are managed (reviewed, versioned, baselined).
3	Established	Defined process exists at organizational level and is deployed to projects.
4	Predictable	Process operates within defined limits using quantitative data.
5	Optimizing	Process is continuously improved based on quantitative understanding.

Agent V targets CL2 — every process must be performed AND managed.

The V-Model

The left side specifies (requirements -> architecture -> design -> code). The right side verifies (unit tests -> integration tests -> qualification tests). Each left-side level has a corresponding right-side verification level.

SYS.1+SYS.2 (Stakeholder & System Reqs)  <->  SYS.5 (System Qualification)
SYS.3 (System Architecture)               <->  SYS.4 (System Integration Test)
SWE.1 (SW Requirements)                   <->  SWE.6 (SW Qualification)
SWE.2 (SW Architecture)                   <->  SWE.5 (SW Integration Test)
SWE.3 (Detailed Design & Code)            <->  SWE.4 (Unit Verification)

What an Assessor Checks

Work product existence. Every required WP file exists with substantive content.
Bidirectional traceability. Every requirement traces down to implementation/tests AND up to parent. No orphans.
Consistency. Linked items are content-aligned, evidenced by review records (WP 13-19).
Review evidence. Every stage has a review record with participants, findings, and dispositions.
Change control. Modifications after baseline are traceable to change requests (SUP.10).
Independence. QA (SUP.1) is performed by someone/something other than the producer.

Detailed References

For the 17 ASPICE processes (SYS, SWE, SUP, MAN) and key terminology, read references/processes.md.
For the Doorstop traceability chain and how an assessor traces items, read references/traceability-chain.md.
For ASPICE 4.0 migration notes, read references/aspice-40-migration.md.

---name: aspice-fundamentalsdescription: ASPICE 3.1 V-model reference for Agent V. Use this skill whenever you encounter ASPICE process IDs (SYS.1, SWE.2, SUP.8, etc.), base practice references (BP1, BP6), work product IDs (WP 17-12, WP 04-04), capability levels, traceability requirements, or any mention of the V-model. Also use when you need to understand what an ASPICE assessor expects, how processes relate to each other, or what 'assessment-ready' means. This is foundational context — consult it early in any Agent V task.---# Automotive SPICE 3.1 — Quick Reference## What ASPICE IsAutomotive SPICE (ASPICE) is a process assessment framework published by VDA QMC, based on ISO/IEC 15504. It defines how software and systems should be developed, verified, and managed. An assessor evaluates whether your project demonstrates that each process was performed (CL1) and managed (CL2) by examining work products, traceability, and review evidence.## Capability Levels| Level | Name | What It Means ||-------|------|---------------|| 0 | Incomplete | Process not implemented or fails to achieve its purpose. || 1 | Performed | Process achieves its purpose. Base practices are demonstrated. Work products exist. || 2 | Managed | Process is planned, monitored, and adjusted. Work products are managed (reviewed, versioned, baselined). || 3 | Established | Defined process exists at organizational level and is deployed to projects. || 4 | Predictable | Process operates within defined limits using quantitative data. || 5 | Optimizing | Process is continuously improved based on quantitative understanding. |Agent V targets **CL2** — every process must be performed AND managed.## The V-ModelThe left side specifies (requirements -> architecture -> design -> code). The right side verifies (unit tests -> integration tests -> qualification tests). Each left-side level has a corresponding right-side verification level.```SYS.1+SYS.2 (Stakeholder & System Reqs) <-> SYS.5 (System Qualification)SYS.3 (System Architecture) <-> SYS.4 (System Integration Test)SWE.1 (SW Requirements) <-> SWE.6 (SW Qualification)SWE.2 (SW Architecture) <-> SWE.5 (SW Integration Test)SWE.3 (Detailed Design & Code) <-> SWE.4 (Unit Verification)```## What an Assessor Checks1. **Work product existence.** Every required WP file exists with substantive content.2. **Bidirectional traceability.** Every requirement traces down to implementation/tests AND up to parent. No orphans.3. **Consistency.** Linked items are content-aligned, evidenced by review records (WP 13-19).4. **Review evidence.** Every stage has a review record with participants, findings, and dispositions.5. **Change control.** Modifications after baseline are traceable to change requests (SUP.10).6. **Independence.** QA (SUP.1) is performed by someone/something other than the producer.## Detailed References- For the 17 ASPICE processes (SYS, SWE, SUP, MAN) and key terminology, read `references/processes.md`.- For the Doorstop traceability chain and how an assessor traces items, read `references/traceability-chain.md`.- For ASPICE 4.0 migration notes, read `references/aspice-40-migration.md`.

Frequently asked questions