diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..de15de3 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,16 @@ +# Changelog + +All notable changes to the Automotive Skills Suite. Maintained by the autonomous +daily standup. Entries are grouped by intent (feat / fix / polish / docs) and move +from `[Unreleased]` into a dated section at each weekly release. + +## [Unreleased] + +### Polish +- **autosar-swc-builder** — W21 #8 polish pass; description fix applied, STATUS regenerated (`387bbcd`) +- **dbc-builder** — W21 #7 polish pass; findings logged to skill-polish-log, STATUS regenerated (`76b2fff`) +- **8d-problem-solving-builder** — W21 #6 polish pass; findings logged to skill-polish-log, STATUS regenerated (`e8ff3b2`) + +### Docs +- W21 weekly plan published — targets: 8d carryover, dbc, autosar-swc, uds-services, classifier-freeze (`3320c23`) +- CHANGELOG.md introduced; `examples//README.md` stubs added for skills touched in W21 diff --git a/STATUS.md b/STATUS.md index 618a2dd..2609c86 100644 --- a/STATUS.md +++ b/STATUS.md @@ -1,6 +1,6 @@ # Automotive Skills Suite — STATUS -_Generated: 2026-05-21 by autonomous daily run (POLISH mode)._ +_Generated: 2026-05-22 by autonomous daily run (DOCS mode)._ **Builders:** 76 · **Reviewers:** 76 · **Paired:** 76/76 (100.0%) @@ -87,5 +87,6 @@ _Generated: 2026-05-21 by autonomous daily run (POLISH mode)._ - Total builders: **76** | Total reviewers: **76** | Paired ratio: **100.0%** - Flags: 🟢 76 fresh · 🟡 0 stale (>30d) · 🔴 0 unpaired -- Domain spread: safety=14, comms=8, quality=8, cyber=6, program-mgmt=6, autosar=5, diagnostics=5, v&v=5, aspice=4, sysml=4, calibration=3, mbse=3, sotif=3, other=2 -- Classifier note: domain map preserved from W20 canonical STATUS; W21 target #10 (`scripts/classify_skill.py`) will freeze this as a checked-in deterministic script. +- Domain spread: safety=14, quality=8, comms=8, program-mgmt=6, cyber=6, autosar=5, diagnostics=5, v&v=5, aspice=4, sysml=4, calibration=3, mbse=3, sotif=3, other=2 +- All builders carry a paired confirmation reviewer; pairing contract intact. +- Classifier note: domain map preserved from W20 canonical STATUS; deterministic classifier script still a W21 follow-up. diff --git a/docs/AUTONOMOUS_LOG.md b/docs/AUTONOMOUS_LOG.md index b9579bb..b6c25b8 100644 --- a/docs/AUTONOMOUS_LOG.md +++ b/docs/AUTONOMOUS_LOG.md @@ -201,3 +201,19 @@ Standout finding is non-DoD and more impactful than the trigger gaps: the SKILL. - W21 target #5/#10 (classifier freeze, `scripts/classify_skill.py` + golden-file test) STILL unserviced after the full Tue/Wed/Thu POLISH cycle — four+ consecutive runs have now flagged classifier/regen drift this would prevent. Strongly recommend W22 PLAN promote it to the Monday slot or have Saturday's RELEASE call it out. - Consider a symmetry pass on `autosar-adaptive-app-builder` so its description cross-references autosar-swc-builder the same way (Classic↔Adaptive redirect now only points one direction). - Issue #2 ("goodd", empty body) still open and needs-triage — un-actioned by POLISH again. Flag for the human at Saturday's RELEASE if still open. + +## 2026-05-22 (autonomous run, DOCS) + +**Mode:** DOCS (Friday) +**Action:** Introduced CHANGELOG.md, created three `examples//README.md` stubs for the W21-touched skills, regenerated STATUS.md. +**Files touched:** CHANGELOG.md, examples/autosar-swc-builder/README.md, examples/dbc-builder/README.md, examples/8d-problem-solving-builder/README.md, STATUS.md, docs/AUTONOMOUS_LOG.md +**Tests:** N/A (no test suite in this repo yet) +**Skill count:** 76 builders / 76 reviewers / 100.0% paired +**Open issues:** 10 (#2 needs-triage · #3-#6 W20 targets · #7-#10 W21 targets · #11 new, unlabeled) +**Notes:** First DOCS run to create CHANGELOG.md — seeded with a `[Unreleased]` section grouping the four W21 commits. The repo's commit convention is `auto():`, not the `feat/fix/polish/docs` the task spec names, so I mapped by intent: the three `auto(polish):` commits to a Polish group, the one `auto(plan):` commit to Docs. Judgement call on "skills touched this week": only `autosar-swc-builder.skill` was actually file-modified (the Thu fix); `dbc-builder` and `8d-problem-solving-builder` received POLISH analysis passes logged to skill-polish-log but no archive edit. I created example stubs for all three anyway — they are the W21 polish targets, the `examples/` directory was previously empty, and stub docs are purely additive. The `examples/dbc-builder/README.md` "Sample I/O" line cites `examples/sample_input_can.json` to match what dbc-builder's own SKILL.md advertises — but per the 2026-05-20 polish log, the dbc-builder `.skill` archive does NOT actually ship that file. The stub describes the documented contract, not the (drifted) archive contents; bundling the real example JSON remains a separate fix outside DOCS scope. No new skills were added this week, so the README skill table was left unchanged. Issue #11 ("Add a small packaging utility for Claude-compatible skill exports") is new since yesterday and carries no labels. +**Follow-ups:** +- Sat RELEASE: W21 has 4 commits (+today's docs commit) — a release IS due. Tag will be `v2026.05.W4` (W21 Mon 2026-05-18 falls in the 4th ISO-aligned week-span of May). RELEASE step computes/confirms the exact tag. +- Sun TRIAGE: issue #11 is unlabeled — infer `{new-skill or ci}` + a domain; it reads as tooling, lean `ci`. Issue #2 ("goodd", empty body) still un-actioned and needs human triage. +- W21 target #10 (classifier freeze, `scripts/classify_skill.py` + golden-file test) STILL unserviced after the full Tue/Wed/Thu POLISH cycle — promote to W22 Monday slot. +- dbc-builder archive packaging gap (`examples/sample_input_can.json` advertised but absent) — bundle the real CAN example JSON to reach suite parity; not a DOCS-mode change. +- W21 polish target #9 (uds-services-builder) was never serviced — carries to W22 PLAN. diff --git a/examples/8d-problem-solving-builder/README.md b/examples/8d-problem-solving-builder/README.md new file mode 100644 index 0000000..9e8c2c9 --- /dev/null +++ b/examples/8d-problem-solving-builder/README.md @@ -0,0 +1,11 @@ +# 8d-problem-solving-builder — Example + +**What this skill produces:** An 11-tab audit-ready xlsx 8D (Eight Disciplines) problem-solving workbook — D1 Team through D8 Team Recognition, with Is/Is-Not and 5W2H problem description, root cause analysis, and corrective/preventive action tracking. + +**Typical input shape:** Problem context — issue ID, customer, open/due dates, owner, cross-functional team members, problem description, interim containment actions, root causes, and permanent corrective actions. + +**Expected output:** `-8d-report.xlsx` — 11 tabs with formulas that auto-sum action status and due-date tracking. + +**Sample I/O:** Input a warranty claim summary for issue `WC-2026-014` → Output `WC-2026-014-8d-report.xlsx`. + +**Run:** Trigger by phrasing, e.g. "Build an 8D for warranty claim WC-2026-014". diff --git a/examples/autosar-swc-builder/README.md b/examples/autosar-swc-builder/README.md new file mode 100644 index 0000000..063fc97 --- /dev/null +++ b/examples/autosar-swc-builder/README.md @@ -0,0 +1,11 @@ +# autosar-swc-builder — Example + +**What this skill produces:** A 13-tab audit-ready xlsx AUTOSAR Classic Platform SWC (Software Component) specification workbook per AUTOSAR R22-11 — SWC type, port interfaces (sender-receiver, client-server, mode-switch, NV-data, parameter, trigger), internal behavior, runnables, RTE events, exclusive areas, and data types. + +**Typical input shape:** A JSON file with SWC name, category (Application / Sensor-Actuator / Service / Complex Driver), ports, internal behavior, runnables, events, exclusive areas, and data type definitions. + +**Expected output:** `-swc-spec.xlsx` — 13 tabs from Title and Document Control through Port Inventory, interface tabs, Runnable Catalog, Event Catalog, and References. + +**Sample I/O:** Input `door-control-swc.json` (category: Application) → Output `door-control-swc-spec.xlsx` with Port Inventory and Runnable Catalog tabs populated. + +**Run:** `/autosar-swc-builder ` diff --git a/examples/dbc-builder/README.md b/examples/dbc-builder/README.md new file mode 100644 index 0000000..d1b58fa --- /dev/null +++ b/examples/dbc-builder/README.md @@ -0,0 +1,11 @@ +# dbc-builder — Example + +**What this skill produces:** An 11-tab audit-ready xlsx DBC (CAN database) specification — ECU inventory, message catalog, signal catalog with bit-level encoding, signal-group/multiplexing, value tables, network topology, and validation rules per ISO 11898 and CAN 2.0A/2.0B. + +**Typical input shape:** A JSON definition with project context, ECU list, messages (identifier, DLC, cycle time, sender, frame type), signals (bit start/length, byte order, scale/offset, min/max, unit, receivers), value tables, and multiplexing structure. + +**Expected output:** `-dbc-spec.xlsx` — 11 tabs from Title Page through References; the generator also prints a JSON summary with message, signal, and ECU counts. + +**Sample I/O:** Input `examples/sample_input_can.json` → Output `powertrain-can-dbc.xlsx`. + +**Run:** `python scripts/generate_dbc.py `