Fix print CSS bug and fold in real-world findings from the first live invocation
First test run (Oshkosh GO Transit internal kickoff, via the actual
installed skill, not Claude manually walking the SKILL.md) surfaced real,
fixable gaps. All fixed here:
1. Print CSS bug (root cause, found by Bryan): section{break-inside:
avoid-page} plus whole-table break-inside:avoid caused a 14-page,
mostly-blank PDF. Fixed: sections can split across pages now; only
cards/table-rows avoid splitting, with repeating table headers.
2. SO/PO lookup was wrongly scoped out of this brief type by default.
Wrong -- an internal kickoff about a real sale needs the SO/PO as much
as any external brief would. Scope is now by topic nature (commercial
vs. purely internal), not by brief-type name.
3. Contact-info lookup (not just name resolution) is now an explicit
standing step in attendee capture, starting from a linked SO/PO's own
Odoo contacts when one exists.
4. Added the MPM Technical Reference System (a 131-file Drive registry:
brand, platform, display tech, products, engineering, concepts, proof)
as a standing reference for part-number/product verification --
previously unknown to this skill.
5. Pulled the real run's improved _topic-state.md schema back into the
spec: confidence tags (verified/stated/open), a folder-layout header,
numbered-vs-proposed open items, a Findings/flags section. These
emerged from real use and are now documented, not one-off.
6. Meeting transcript archival (a Meeting Transcripts/ subfolder) is now
a standing step, not something that has to be asked for.
7. section-structure.md: flow and specbar are now marked validated (real
examples: Oshkosh deployment sequence, billing milestones). Added the
meeting-vs-proposed open-items badge pattern and a standard
confidentiality footer note for this brief type.
None of this was a failure of judgment in the moment -- these are gaps
between what the file said and what real use needed, now closed.
This commit is contained in:
1 parent
2c6fa0da03
commit
2209a19eb7
3 files changed
+168
-35
No files matched your search
@@ -228,9 +228,10 @@ footer{padding:22px 6vw; color:var(--muted); font-size:11.5px; text-align:center
|
||||
.theme-toggle, nav.toc{display:none !important;}
|
||||
body{background:#FAF8F4 !important; color:#272326 !important;}
|
||||
header{background:#79640E !important; -webkit-print-color-adjust:exact; print-color-adjust:exact;}
|
||||
.card, .quadcard, .layerbox, .filepill, table.unitgrid, table.actions, .note, .colcard, .spec{
|
||||
.card, .quadcard, .layerbox, .filepill, .note, .colcard, .spec{
|
||||
break-inside:avoid;
|
||||
}
|
||||
section{break-inside:avoid-page;}
|
||||
table.unitgrid tr, table.actions tr{break-inside:avoid;}
|
||||
table.unitgrid thead, table.actions thead{display:table-header-group;}
|
||||
a{color:inherit; text-decoration:none;}
|
||||
}
|
||||
Reference in new issue
Block a user