How do I install the Quality Cm Pm skill?

Run npx skillmds@latest add ksmyl/quality-cm-pm 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 Quality Cm Pm 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 Quality Cm Pm?

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 Quality Cm Pm free to use?

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

Who published Quality Cm Pm?

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

Quality Cm Pm by ksmyl — Agent Skill

Name: Quality Cm Pm
Author: ksmyl

Quality Cm Pm

How to do QA, configuration management, and project management in ASPICE. Use this skill when performing quality assurance audits (SUP.1), managing configuration items and baselines (SUP.8), tracking problems (SUP.9), handling change requests (SUP.10), writing project plans (MAN.3), or defining measurements (MAN.6). Also use when you need to create Git baseline tags, write problem records (PR-xxx), write change requests (CR-xxx), understand QA independence requirements, or define project metrics. Consult this whenever you see SUP.1, SUP.8, SUP.9, SUP.10, MAN.3, MAN.6, or terms like 'baseline,' 'corrective action,' 'non-conformance,' or 'measurement strategy.'

ksmyl Updated Sep 17, 2026

File contents

Quality Assurance, Configuration Management, and Project Management

SUP.1 — Quality Assurance Independence

The QA agent (Agent 09) must be functionally independent from the agents whose work it audits. This means:

QA must NOT create or modify requirements, architecture, design, code, or tests.
QA CAN create: quality plans, quality criteria, quality records, corrective action registers, problem records, and change requests.
QA has the authority to flag non-conformances and escalate without fear of project pressure.

SUP.8 — Baselines and Branch Strategy

A baseline is a formally reviewed snapshot. In Agent V, baselines are Git annotated tags.

git tag -a BL_2026-04-15_requirements -m "Baseline: stakeholder and system requirements complete"

Branch	Purpose
`main`	Latest approved baseline-ready state.
`cr/<CR-ID>-<short>`	Feature branch for a specific change request.

After first baseline, all changes to main require an approved change request. Everything under version control is a CI: reqs/, artifacts/, src/, tests/, pipeline/, scripts/, orchestrate.py, pyproject.toml, .doorstop.yml files.

Detailed References

For problem record (SUP.9) format and lifecycle states, read references/problem-records.md.
For change request (SUP.10) format and bidirectional traceability requirements, read references/change-requests.md.
For MAN.3 project plan structure and MAN.6 measures table, read references/project-management.md.

---name: quality-cm-pmdescription: How to do QA, configuration management, and project management in ASPICE. Use this skill when performing quality assurance audits (SUP.1), managing configuration items and baselines (SUP.8), tracking problems (SUP.9), handling change requests (SUP.10), writing project plans (MAN.3), or defining measurements (MAN.6). Also use when you need to create Git baseline tags, write problem records (PR-xxx), write change requests (CR-xxx), understand QA independence requirements, or define project metrics. Consult this whenever you see SUP.1, SUP.8, SUP.9, SUP.10, MAN.3, MAN.6, or terms like 'baseline,' 'corrective action,' 'non-conformance,' or 'measurement strategy.'---# Quality Assurance, Configuration Management, and Project Management## SUP.1 — Quality Assurance IndependenceThe QA agent (Agent 09) must be **functionally independent** from the agents whose work it audits. This means:- QA must NOT create or modify requirements, architecture, design, code, or tests.- QA CAN create: quality plans, quality criteria, quality records, corrective action registers, problem records, and change requests.- QA has the authority to flag non-conformances and escalate without fear of project pressure.## SUP.8 — Baselines and Branch StrategyA baseline is a formally reviewed snapshot. In Agent V, baselines are Git annotated tags.```bashgit tag -a BL_2026-04-15_requirements -m "Baseline: stakeholder and system requirements complete"```| Branch | Purpose ||--------|---------|| `main` | Latest approved baseline-ready state. || `cr/<CR-ID>-<short>` | Feature branch for a specific change request. |After first baseline, all changes to `main` require an approved change request. Everything under version control is a CI: `reqs/`, `artifacts/`, `src/`, `tests/`, `pipeline/`, `scripts/`, `orchestrate.py`, `pyproject.toml`, `.doorstop.yml` files.## Detailed References- For problem record (SUP.9) format and lifecycle states, read `references/problem-records.md`.- For change request (SUP.10) format and bidirectional traceability requirements, read `references/change-requests.md`.- For MAN.3 project plan structure and MAN.6 measures table, read `references/project-management.md`.

Frequently asked questions