Skip to content

Commit 129372d

Browse files
migmccclaude
andcommitted
docs: mark v0.2 items done and move YAML-driven rules to v0.3
#3 JSON output, #2 more aliases and #4 multi-sheet workbooks are merged. #1 (YAML-driven rules) moved to the v0.3 milestone as a rule-engine refactor that must preserve exact finding-type parity. No version bump; release is a separate step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 74ebbee commit 129372d

1 file changed

Lines changed: 16 additions & 14 deletions

File tree

docs/ROADMAP.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,24 +6,26 @@ severity-weighted score, Markdown report + terminal summary, synthetic examples,
66
See [MVP_SCOPE.md](MVP_SCOPE.md). All work packages (repo skeleton, data models, Excel parser,
77
matching, rules, scoring, report, CLI, examples, tests + CI, docs, release) are complete.
88

9-
## v0.2 — planned
10-
Improve interoperability and real-world workbook compatibility while keeping the tool focused on
11-
PFMEA ↔ Control Plan validation. Tracked under the
12-
[v0.2 milestone](https://github.com/migmcc/quality-docs-validator/milestone/1). Recommended order:
9+
## v0.2 — done (pending release)
10+
Interoperability and real-world workbook compatibility, kept focused on PFMEA ↔ Control Plan
11+
validation. Tracked under the
12+
[v0.2 milestone](https://github.com/migmcc/quality-docs-validator/milestone/1). All three items are
13+
merged to `main`; the `v0.2.0` tag/release is a separate step.
1314

14-
1. **JSON output** ([#3](https://github.com/migmcc/quality-docs-validator/issues/3)) — first PR; a
15-
machine-readable report alongside Markdown (Markdown stays the default).
16-
2. **More PFMEA / Control Plan column aliases**
17-
([#2](https://github.com/migmcc/quality-docs-validator/issues/2)) — broaden real-template coverage.
18-
3. **Multi-sheet workbooks** ([#4](https://github.com/migmcc/quality-docs-validator/issues/4)) —
19-
optional sheet selection.
20-
4. **YAML-driven rules** ([#1](https://github.com/migmcc/quality-docs-validator/issues/1)) —
21-
*stretch / optional*; a rule-engine refactor, deferred to v0.3 if scope grows.
15+
-**JSON output** ([#3](https://github.com/migmcc/quality-docs-validator/issues/3)) — a
16+
machine-readable report alongside Markdown (Markdown stays the default).
17+
-**More PFMEA / Control Plan column aliases**
18+
([#2](https://github.com/migmcc/quality-docs-validator/issues/2)) — broader real-template coverage.
19+
-**Multi-sheet workbooks** ([#4](https://github.com/migmcc/quality-docs-validator/issues/4)) —
20+
optional `--pfmea-sheet` / `--control-plan-sheet` selection.
2221

2322
Still out of scope for v0.2: CSV input, configurable column mapping, HTML output, UI, AI, and any
24-
new document pairs. No dates promised.
23+
new document pairs.
2524

26-
## v0.3+ — More modules (each independent of the core)
25+
## v0.3+ — Rule engine & more modules (each independent of the core)
26+
- **YAML-driven rules** ([#1](https://github.com/migmcc/quality-docs-validator/issues/1)) — make the
27+
YAML the source of the rule *logic*, not just its documented metadata. Moved out of v0.2 because it
28+
is a rule-engine refactor and must keep exact finding-type parity.
2729
- Process Flow ↔ PFMEA consistency.
2830
- Control Plan ↔ Work Instructions.
2931
- PPAP gap check.

0 commit comments

Comments
 (0)