# Week of 2026-05-11 → 2026-05-17 (ISO 2026-W20) _Autonomous PLAN entry — generated by the daily-standup task on 2026-05-11._ ## Recap (past 7 days) ``` (no commits in the last 7 days — the suite is at its initial 152-skill baseline) ``` Total commits to date: 3 (seed + skill expansion + README). Open issues: 1 (#2, an untriaged test issue with no labels — handled in Sunday's TRIAGE pass). ## Targets for this week (4) Each target gets a paired GitHub issue (`weekly-target` + domain label). Definition of Done is the one-sentence check below — keep edits surgical; if a target balloons, defer it to next week and record the why. ### 1. `hara-builder.skill` — domain: **safety** - **Why:** flagship ISO 26262-3 concept-phase doc and the input for FSC; every downstream safety builder depends on its xlsx shape, so polish here pays out across 16 other skills. - **DoD:** description ≤ 1024 chars, frontmatter has all required fields, and the trigger list mentions at least HARA + hazard analysis + ASIL + safety goal + item definition within the first 400 chars. ### 2. `cs-concept-builder.skill` — domain: **cyber** - **Why:** ISO/SAE 21434 cybersecurity concept derivation; counterpart to FSC on the security side. Currently last-touched 2026-05-01, never polished after seed. - **DoD:** description reviewed for accuracy of the six security properties (AAICAN), and trigger phrases include both formal terms (CSR derivation, CAL allocation) and casual framings ("derive cyber controls from goals"). ### 3. `aspice-assessment-builder.skill` — domain: **aspice** - **Why:** ASPICE PAM v3.1/v4.0 anchor; consumed by gap-analysis and improvement-plan builders, so the I/O contract here gates the whole ASPICE cluster. - **DoD:** confirm the 13-tab output list in the description matches the actual builder schema, and trigger list mentions both v3.1 and v4.0. ### 4. `8d-problem-solving-builder.skill` — domain: **quality** - **Why:** warranty / customer-complaint workhorse; first-line skill for field-failure response. Last-touched 2026-05-01. - **DoD:** description names all 8 disciplines (D1–D8) and triggers include "warranty response," "customer complaint," and "corrective action tracking." ## Domain spread check | Domain | Count | |---|---| | safety | 1 | | cyber | 1 | | aspice | 1 | | quality | 1 | Spread looks healthy — 4 distinct domains, no concentration. Notable gaps this week: no v&v, comms, autosar, diagnostics, calibration, mbse, sysml, sotif, or program-mgmt target. Acceptable for W20 because the LRT bucket (last-touched 2026-05-01) is itself concentrated in safety/cyber/aspice/quality; next week's PLAN should explicitly pull from the comms / autosar / diagnostics / calibration clusters to keep rotation balanced. ## Issue links _Filled in by the create-issue step of this same run; if any cell is blank the API call failed and the follow-up is captured in the journal._ | Target | Issue | |---|---| | hara-builder | [#3](https://github.com/jherrodthomas/automotive-skills-suite/issues/3) | | cs-concept-builder | [#4](https://github.com/jherrodthomas/automotive-skills-suite/issues/4) | | aspice-assessment-builder | [#5](https://github.com/jherrodthomas/automotive-skills-suite/issues/5) | | 8d-problem-solving-builder | [#6](https://github.com/jherrodthomas/automotive-skills-suite/issues/6) |