Automotive Skills Autonomous
3af1f6b181
Autonomous daily run. - Published docs/weekly/WEEK-2026-W23.md (3 polish + 1 tooling + 1 polish) - Opened tracking issues #15 (fmeda-builder) and #16 (tara-builder) - Promoted #10 (extract scripts/classify_skill.py) as W23 tooling slot - Regen STATUS.md, journal entry Generated by automotive-skills-daily-standup scheduled task.
3.9 KiB
Week 2026-W23 — Plan
Auto-generated 2026-06-01 by automotive-skills-daily-standup (PLAN run).
Recap — past 7 days
f54a710 auto(triage): regen STATUS with alias-aware pairing, journal day
3ec50a0 auto(release): v2026.05.W22 weekly snapshot, RELEASES.md, CHANGELOG roll, STATUS regen
f9e63f9 auto(docs): W22 changelog roll-up, 3 example stubs, STATUS regen
ef78172 auto(polish): W22 #2 hara-builder pass, regen STATUS, journal
04482aa auto(polish): W22 #5 dfmea-builder pass, regen STATUS, journal
9850780 auto(polish): W22 #1 uds-services-builder pass, regen STATUS
973c075 auto(plan): W22 targets — uds, hara, cs-concept, aspice-assessment, dfmea
W22 closed clean: tag v2026.05.W22 is pushed, RELEASES.md drafted for
manual Publish, 100% paired ratio held. Three of five W22 polish targets
landed in-week (uds, hara, dfmea); cs-concept (#4) and aspice-assessment (#5)
slipped per the W22 docs/release journal entries. Both are W20-originated
issues now in their fourth consecutive week of carryover — they MUST lead
W23 to stop the bleed.
W23 targets
Suite remains 100% paired (76 / 76), no orphan builders to chase. Priority order applied: (a) skills referenced by oldest open issues, (b) one tooling slot to retire the longest-open infra debt (#10 classifier freeze), (c) a fresh stale-cohort pick to keep the polish wheel turning.
| # | Target | Domain | Tracking issue | Definition of done |
|---|---|---|---|---|
| 1 | cs-concept-builder.skill | cyber | #4 (4-week carryover) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited against current archive; small obvious fixes applied in-place; severity logged. |
| 2 | aspice-assessment-builder.skill | aspice | #5 (4-week carryover) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. |
| 3 | scripts/classify_skill.py extraction | tooling | #10 (6-run carryover) | Extract the inline STATUS-regen Python (domain inference + alias map + flag rules) into scripts/classify_skill.py; daily standup invokes it via python scripts/classify_skill.py > STATUS.md. DoD: standup STATUS section shrinks to one shell line. |
| 4 | fmeda-builder.skill | safety | #15 (new) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Picked from stale 🟡 cohort (untouched since 2026-05-01) — densest safety-domain builder still un-polished. |
| 5 | tara-builder.skill | cyber | #16 (new) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Cyber-domain anchor skill, stale since 2026-05-01. |
Two existing issues (#4, #5) are referenced in place rather than duplicated — consistent with W22 plan precedent. Two fresh issues (#15, #16) created for the new polish targets (issue tracker had jumped past #13/#14 between W22 close and this PLAN run). One existing issue (#10) elevated as the W23 tooling slot.
Domain-spread check
Targets span 4 distinct domains plus tooling: cyber (×2), aspice (×1), safety (×1), tooling (×1). Polish runs land Tue/Wed/Thu so expect ~3 of these 5 to execute this week; carryover lands on W24 backlog.
Notes / judgement calls
- The standup spec literally reads
vYYYY.MM.W<n>with W = "ISO week within current month". Prior tags (W20/W21/W22) used ISO-absolute week numbers for continuity. June 1 starts a new month — if W23 RELEASE keeps the ISO-absolute scheme the tag isv2026.06.W23; if it switches it becomesv2026.06.W1. Flagged for human direction; PLAN does not decide. - W22 RELEASE journal flagged that the alias map for ppap-package and item-definition pairing is now data-driven inside the inline helper. Target #3 (scripts/classify_skill.py) will lift it into a real repo-versioned tool so future runs do not silently drift.