# Week 2026-W24 — Plan _Auto-generated 2026-06-08 by automotive-skills-daily-standup (PLAN run)._ ## Recap — past 7 days ``` d8b19ef auto(triage): label refresh, #12 typed, #17 delta confirmed, STATUS regen 8e826bb auto(release): v2026.06.W23 weekly snapshot, RELEASES.md, CHANGELOG roll, STATUS regen c21a84a auto(docs): W23 changelog roll, 3 example stubs, STATUS regen d6afa26 auto(polish): W23 #3 fmeda-builder pass, regen STATUS, journal 22d6409 auto(polish): W23 #2 tara-builder pass, regen STATUS, journal 5b4b006 auto(polish): W23 #1 cs-concept-builder pass, regen STATUS, journal f8e940f auto(monthly): KPI report for May 2026 3af1f6b auto(plan): W23 targets — cs-concept, aspice-assessment, classifier, fmeda, tara ``` W23 closed clean: tag `v2026.06.W23` pushed, RELEASES.md drafted for manual Publish, 100% paired ratio (76/76) held. Three W23 polish passes landed (cs-concept, tara, fmeda) plus 3 example stubs and the May monthly KPI. **Tracker reset.** Sunday's TRIAGE recorded 12 open issues. As of this PLAN run the GitHub API reports `open_issues_count = 0` — **a maintainer closed every open issue** (#3–#12, #15, #16) between Sun and Mon. This clears the entire backlog the prior PLAN/POLISH cadence was anchored on, including the four-week carryovers #4 (cs-concept) and #5 (aspice-assessment) and the tooling debt #10 (classifier) and #11 (packaging utility). The standup priority order therefore falls through (a) "skills referenced by open issues" → none → to (c) least-recently-touched builders, with the standing journal mandates (SOTIF coverage, classifier extraction) folded in. ## W24 targets Suite is 100% paired (76/76), zero orphan builders. With the issue tracker emptied, targets are drawn from the stale 🟡 cohort (74 builders untouched since 2026-05-01/02) for maximum domain spread, plus one tooling slot to finally retire the long-running inline-classifier debt. Fresh issues created this run; the human-closed carryovers (#4/#5) are deliberately **not** re-enqueued as polish loops (see Notes). | # | Target | Domain | Tracking issue | Definition of done | |---|---|---|---|---| | 1 | scripts/classify_skill.py extraction | tooling | #19 (successor to closed #10) | Extract inline STATUS-regen logic (domain inference + alias map + flag rules + 9-entry explicit override) into `scripts/classify_skill.py`; standup regenerates via `python scripts/classify_skill.py > STATUS.md`. DoD: output byte-matches current canonical spread; STATUS section of standup shrinks to one shell line. | | 2 | sotif-analysis-builder.skill | sotif | #20 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Satisfies the standing SOTIF-coverage mandate (only zero-touch domain in May KPI). | | 3 | safety-case-builder.skill | safety | #21 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. ISO 26262-2 capstone integrator, densest domain, never polished. | | 4 | control-plan-builder.skill | quality | #22 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Quality-domain anchor (AIAG Control Plan), stale since 2026-05-01. | | 5 | communication-matrix-builder.skill | comms | #23 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Central comms artifact, stale since 2026-05-02. | All five tracking issues were created fresh this run (#19–#23); the issue tracker had jumped past #13/#14/#17/#18 from external activity, consistent with prior journal notes. ## Domain-spread check Targets span 4 distinct skill domains plus tooling: sotif (×1), safety (×1), quality (×1), comms (×1), tooling (×1). No domain is doubled — a deliberate spread across the stale cohort. Polish passes land Tue/Wed/Thu, so expect ~3 of the 4 skill targets to execute in-week; the tooling slot (#19) is the priority Tuesday pick. Carryover lands on the W25 backlog. ## Notes / judgement calls - **Do not re-enqueue #4/#5.** The four-week carryovers cs-concept (#4) and aspice-assessment (#5) were closed by the maintainer this weekend along with the rest of the backlog. Prior journals recommended converting them to maintainer-PR targets; the human closing them is read here as a decision to stop the polish loop, not an invitation to reopen it. Their ready-to-apply rewrites remain in `docs/skill-polish-log/` for any future maintainer PR. W24 picks fresh stale targets instead. - **Classifier extraction is now its own fresh issue (#19).** Closed #10 is its predecessor. This is the 10th run the inline map would otherwise be hand-maintained; the explicit override is stable at 9 entries and ready to freeze into `scripts/classify_skill.py`. Prioritized as the Tuesday slot. - **SOTIF mandate honored** via #20 (sotif-analysis-builder). May was the only zero-touch SOTIF month per the monthly KPI; landing one SOTIF polish in W24 prevents a second. - **Tag scheme** (a RELEASE concern, flagged four times in W23 journals) resolved by default to ISO-absolute (`v2026.06.W23` shipped Saturday). W24's Saturday RELEASE, if commits warrant, continues the ISO-absolute series as `v2026.06.W24`. No further PLAN action.