quality.md 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +57 -98
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -1,23 +1,14 @@
1
1
  # QUALITY.md
2
2
 
3
- **QUALITY.md** is an agent-friendly file format and companion agent skill and
4
- CLI for continuously improving the quality of coding agent and AI assistant projects/harnesses.
3
+ **QUALITY.md** is an [open format](./SPECIFICATION.md) for modeling quality:
4
+ what matters most, why, and how. Use it with the `/quality` agent skill to
5
+ continuously improve AI assistant and coding agent projects.
5
6
 
6
- ## Why QUALITY.md
7
-
8
- As software and the agents that write it moves faster, quality erodes
9
- quietly through three accumulating debts:
10
-
11
- - **Technical debt** — code drifting from where it should be.
12
- - **Cognitive debt** — the mounting burden of understanding complex or
13
- under-documented systems.
14
- - **Intent debt** — software diverging from what stakeholders actually need.
15
-
16
- QUALITY.md makes a team's quality expectations explicit and checkable, so those
17
- gaps stay visible and addressable instead of compounding.
18
-
19
- > The three-debt framing draws on Margaret-Anne Storey, *The Triple Debt of
20
- > Software Development* ([arXiv:2603.22106](https://arxiv.org/abs/2603.22106)).
7
+ A QUALITY.md file is a Markdown file with a quality model and supporting
8
+ context. The `/quality` skill helps set up the file, evaluate quality, and
9
+ evolve the model as you learn. The `qualitymd` CLI provides support tooling for
10
+ validating QUALITY.md files, managing quality evaluations, and maintaining a
11
+ QUALITY.md workspace.
21
12
 
22
13
  ## Install
23
14
 
@@ -30,7 +21,7 @@ npx skills add qualitymd/quality.md
30
21
  2. Install the CLI:
31
22
 
32
23
  ```sh
33
- npm install quality.md -g
24
+ npm install -g quality.md
34
25
  ```
35
26
 
36
27
  ## Usage
@@ -42,23 +33,40 @@ Invoke the `/quality` skill to manage quality for your project:
42
33
  /quality wizard Have your AI assistant/agent help you manage quality
43
34
  /quality evaluate Evaluate the quality of your project
44
35
  /quality evaluate security Evaluate a specific quality factor or characteristic
45
- /quality evaluate payments-api Evaluate specific target or project component
36
+ /quality evaluate payments-api Evaluate a specific target or project component
46
37
  /quality evaluate payments-api maintainability Evaluate a target's specific quality
47
38
  ```
48
39
 
49
- ## The Format
40
+ Most users should work with `QUALITY.md` through their coding agent, the
41
+ `/quality` skill, or direct edits. The CLI is primarily support tooling for
42
+ validation, status, and evaluation records.
50
43
 
51
- A `QUALITY.md` file combines a structured quality model with plain-language
52
- rationale. The structured model names what is being evaluated, which quality
53
- factors matter, what requirements define those factors, and how each requirement
54
- should be assessed. The Markdown body explains the context: what the work is,
55
- what "good" means, where the boundaries are, and why these standards matter.
44
+ To keep the model visible to agents, add a short note to `AGENTS.md` or
45
+ `CLAUDE.md`:
56
46
 
57
- ### Specification
47
+ ```text
48
+ See [QUALITY.md](./QUALITY.md) for how this project models and evaluates quality.
49
+ ```
50
+
51
+ ## Why QUALITY.md
52
+
53
+ ### Manage Quality Debt
54
+
55
+ As software — and the agents that write it — moves faster, quality erodes
56
+ quietly through three accumulating debts:
57
+
58
+ - **Technical debt** — code drifting from where it should be.
59
+ - **Cognitive debt** — the mounting burden of understanding complex or
60
+ under-documented systems.
61
+ - **Intent debt** — software diverging from what stakeholders actually need.
58
62
 
59
- The format is specified in [`SPECIFICATION.md`](SPECIFICATION.md).
63
+ QUALITY.md makes a team's quality expectations explicit and checkable, so those
64
+ gaps stay visible and addressable instead of compounding.
60
65
 
61
- ### Example QUALITY.md
66
+ > The three-debt framing draws on Margaret-Anne Storey, *The Triple Debt of
67
+ > Software Development* ([arXiv:2603.22106](https://arxiv.org/abs/2603.22106)).
68
+
69
+ ## Example QUALITY.md
62
70
 
63
71
  ```markdown
64
72
  ---
@@ -117,20 +125,18 @@ This model covers message triage and written replies in the support workspace.
117
125
  It does not cover billing system behavior or product incident response.
118
126
  ```
119
127
 
120
- An agent that reads this file can evaluate support work against the stated
121
- requirements, produce findings, and rate the results against the model's scale.
128
+ ## Format
122
129
 
123
- ## The Specification
130
+ ### Specification
124
131
 
125
- The full format specification lives at [`SPECIFICATION.md`](SPECIFICATION.md).
126
- What follows is a condensed reference.
132
+ The full format is specified in [`SPECIFICATION.md`](SPECIFICATION.md).
127
133
 
128
134
  ### File Structure
129
135
 
130
- A `QUALITY.md` file has two layers:
136
+ A QUALITY.md file has two layers:
131
137
 
132
- 1. **YAML frontmatter** - the structured quality model.
133
- 2. **Markdown body** - the context, rationale, scope, needs, risks, and known
138
+ 1. **YAML frontmatter** the structured quality model.
139
+ 2. **Markdown body** the context, rationale, scope, needs, risks, and known
134
140
  gaps that help people and agents interpret the model.
135
141
 
136
142
  The document begins with the YAML frontmatter. The Markdown body can be empty,
@@ -174,7 +180,7 @@ Targets can nest recursively. `ratingScale` exists only on the root model.
174
180
 
175
181
  | Concept | Meaning |
176
182
  | ------------ | --------------------------------------------------------------- |
177
- | Model | The root quality model in a `QUALITY.md` file. |
183
+ | Model | The root quality model in a QUALITY.md file. |
178
184
  | Target | The thing being evaluated. |
179
185
  | Source | The material assessed for a target, such as a path or selector. |
180
186
  | Factor | A quality dimension that matters for a target. |
@@ -183,72 +189,25 @@ Targets can nest recursively. `ratingScale` exists only on the root model.
183
189
  | Finding | An observation produced by an assessment. |
184
190
  | Rating Scale | The ordered model-wide scale used to rate results. |
185
191
 
186
- ### Evaluation Semantics
187
-
188
- Each requirement has exactly one `assessment`. An evaluator performs that
189
- assessment against the target source, records findings, and rates the
190
- requirement's findings against the model's `ratingScale`. A finding records what
191
- was observed; the rating result records how that observation compares with the
192
- model's scale.
193
-
194
- ```text
195
- assessment -> findings -> rating result
196
- ```
197
-
198
- ## The CLI
199
-
200
- > **The CLI is an early work in progress.** Today the binary ships
201
- > `qualitymd init`, `qualitymd lint`, `qualitymd spec`, `qualitymd status`, and the
202
- > `qualitymd evaluation` run-record surface.
203
-
204
- `qualitymd` draws one hard line: the **CLI never asks an AI model to judge your
205
- project.** It creates and checks `QUALITY.md` files, shows what the file covers,
206
- writes evaluation records for the `/quality` skill, renders reports, and can
207
- fail CI when ratings fall below your chosen bar. The judgment work happens in
208
- the skill, not in the CLI.
209
-
210
- ### Common commands
211
-
212
- | Goal | Command |
213
- | ---------------------- | -------------------------------- |
214
- | Show the format rules | `qualitymd spec` |
215
- | Create a starter file | `qualitymd init [path]` |
216
- | Check a file | `qualitymd lint [path]` |
217
- | Fix simple lint issues | `qualitymd lint --fix [path]` |
218
- | Show project status | `qualitymd status [path] --json` |
219
- | Show version info | `qualitymd version --json` |
220
- | Check for updates | `qualitymd upgrade --check` |
221
- | Show command help | `qualitymd <command> --help` |
222
-
223
- Typical local loop:
224
-
225
- ```sh
226
- qualitymd spec
227
- qualitymd init
228
- qualitymd lint
229
- qualitymd status --json
230
- ```
231
-
232
- The `/quality` skill uses additional evaluation commands behind the scenes.
233
- The detailed command guide lives in the bundled
234
- [`CLI Quick Reference`](skills/quality/resources/cli-quick-reference.md).
235
-
236
- ## Conceptual model
192
+ ## CLI Quick Reference
237
193
 
238
- The way `QUALITY.md` frames quality is informed by the **ISO/IEC 25000 (SQuaRE)**
239
- family of software-quality standards — particularly ISO/IEC 25010 — and, for the
240
- shape of a well-formed requirement, **ISO/IEC/IEEE 29148**. We acknowledge these
241
- as the conceptual lineage, not a conformance target: `QUALITY.md` borrows their
242
- ideas and vocabulary where they help and diverges where they don't (it uses
243
- *Factors* where ISO says *characteristics*), optimizing first for a practical,
244
- readable format.
194
+ | Task | Command |
195
+ | --------------------- | -------------------------------- |
196
+ | Show format spec | `qualitymd spec` |
197
+ | Create a starter file | `qualitymd init [path]` |
198
+ | Validate a file | `qualitymd lint [path]` |
199
+ | Fix lint issues | `qualitymd lint --fix [path]` |
200
+ | Show project status | `qualitymd status [path] --json` |
201
+ | Show version info | `qualitymd version --json` |
202
+ | Check for updates | `qualitymd update --check` |
203
+ | Show command help | `qualitymd <command> --help` |
245
204
 
246
205
  ## Status
247
206
 
248
- The `QUALITY.md` format, `qualitymd` CLI, and `/quality` skill are early and under active development. The format is specified in [`SPECIFICATION.md`](SPECIFICATION.md). Expect the format and tooling to change as they mature.
207
+ The QUALITY.md format, `qualitymd` CLI, and `/quality` skill are early and
208
+ under active development. Expect the format and tooling to change as they
209
+ mature.
249
210
 
250
211
  ## Contributing
251
212
 
252
213
  Contributor setup and local tasks live in [`CONTRIBUTING.md`](CONTRIBUTING.md).
253
- The release runbook lives in
254
- [`docs/guides/cut-a-release.md`](docs/guides/cut-a-release.md).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "quality.md",
3
- "version": "0.4.0",
3
+ "version": "0.5.0",
4
4
  "description": "Companion CLI for the QUALITY.md file format and /quality agent skill, used to evaluate and improve AI assistant projects and harnesses.",
5
5
  "homepage": "https://getquality.md",
6
6
  "keywords": [
@@ -34,12 +34,12 @@
34
34
  "bin"
35
35
  ],
36
36
  "optionalDependencies": {
37
- "@qualitymd/cli-darwin-arm64": "0.4.0",
38
- "@qualitymd/cli-darwin-x64": "0.4.0",
39
- "@qualitymd/cli-linux-arm64": "0.4.0",
40
- "@qualitymd/cli-linux-x64": "0.4.0",
41
- "@qualitymd/cli-win32-arm64": "0.4.0",
42
- "@qualitymd/cli-win32-x64": "0.4.0"
37
+ "@qualitymd/cli-darwin-arm64": "0.5.0",
38
+ "@qualitymd/cli-darwin-x64": "0.5.0",
39
+ "@qualitymd/cli-linux-arm64": "0.5.0",
40
+ "@qualitymd/cli-linux-x64": "0.5.0",
41
+ "@qualitymd/cli-win32-arm64": "0.5.0",
42
+ "@qualitymd/cli-win32-x64": "0.5.0"
43
43
  },
44
44
  "publishConfig": {
45
45
  "access": "public"