Skip to content

feat(skills): executive technical explainer capability (3 skills + technical-explainer profile) - #329

Open
wz-gsa wants to merge 1 commit into
mainfrom
feat/executive-technical-explainer-319
Open

feat(skills): executive technical explainer capability (3 skills + technical-explainer profile)#329
wz-gsa wants to merge 1 commit into
mainfrom
feat/executive-technical-explainer-319

Conversation

@wz-gsa

@wz-gsa wz-gsa commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Implements the core of epic #319 — an evidence-grounded capability for explaining software development, agentic coding, and security controls to executive / non-engineering audiences.

Quality bar: hand an agent a concept, process, or value question and it produces an explanation an executive understands without making an engineer wince at the inaccuracies.

What's in this PR

Skills (communications collection)

Reference material (not skills) (#324, #325)

  • concept-library.md — 24 concepts, each with a "what it is not" and ground-truth source: citations to the playbook/quickstart.
  • audience-profiles.md — CIO/CTO, CISO, CAIO, program exec, COO, acquisition.
  • measurement-guidance.md — evidence classes, good vs. misleading metrics, cost/value framing.

Workflow / profile (#323)

  • Implemented the previously-reserved technical-explainer profile in design-artifact by composing the three skills (no new renderer). Added technical-explainer to schemas/taxonomy.yaml.

Honesty properties (pinned by deterministic test-cases)

  • Sandbox = isolation, not a perfect guarantee (image-provenance/SI-7 caveat; egress ≠ repo authority). Test asserts "not a perfect security guarantee" present, "completely secure" absent.
  • Secrets — precise caveat: host store; msb swap-on-wire (never enters guest); on sbx the USAi key is a custom unproxied secret visible to the agent, protected by isolation not proxying. Test asserts "custom, unproxied secret" present and "secrets never enter the sandbox" absent.
  • Agent autonomy — cannot self-approve/self-merge; humans review/approve. Test asserts those overclaims are absent and "author is not the approver" present.
  • Value — "does AI make devs 50% faster?" answered qualified/ranged with an evidence class; lines-of-code flagged misleading.
  • Anti-fabrication — an ungrounded concept is flagged ("will not invent"), not fabricated.

Process

  • Architecture (extend design-artifact, don't build parallel) chosen via nexus 7/7 higher-order consensus.
  • Adversarial accuracy/security/over-triggering review: 7/7 approve; the two hardening suggestions (anti-fabrication test + explicit differentiation from plain-language-review/narrative-architect/renderers) applied.

Validation

  • make validate ✓ · make generate-check ✓ (INDEX/CATALOG regenerated) · run_test_cases.py 73/73 ✓ · markdownlint ✓

Follow-on

Refs #319 #320 #321 #322 #323 #324 #325

AI-assisted (OpenCode).

…chnical-explainer profile)

Add an evidence-grounded capability for explaining software development, agentic
coding, and security controls to executive / non-engineering audiences —
accurately, without hype, and without overclaiming agent autonomy, sandbox
security, or secret handling.

Skills (communications collection):
- technical-concept-translator: one concept -> accurate executive mental model
  (what it is / plain language / why it matters / what it is NOT / where it fits
  / controls), backed by an executive concept library.
- software-delivery-explainer: the delivery pipeline + where agents act and where
  the human control points are; thesis "more work between the controls, not
  fewer controls."
- agentic-value-analyst: capability -> value without hype; five evidence classes;
  defensible metrics over vanity metrics; honest handling of conflicting research.

Reference material (not skills): executive concept library (24 concepts, each
with a "what it is not" and ground-truth citations to the playbook/quickstart),
six audience profiles, and evidence/measurement guidance.

Workflow: implement the previously-reserved `technical-explainer` profile in the
design-artifact workflow by composing the three skills (no new renderer); add
`technical-explainer` to schemas/taxonomy.yaml.

Honesty properties are pinned by deterministic test-cases: the sandbox is stated
as isolation not a perfect guarantee (image-provenance/SI-7 caveat); the secrets
caveat is precise (host store; msb swap-on-wire; on sbx the USAi key is a custom
unproxied secret visible to the agent, protected by isolation not proxying — so
"secrets never enter the sandbox" is not asserted); the agent cannot self-approve
or self-merge; the "50% faster" question is answered qualified/ranged with an
evidence class; vanity metrics are flagged. Anti-fabrication: an ungrounded
concept is flagged, not invented.

Architecture (extend design-artifact, don't build parallel) chosen via nexus 7/7
higher-order consensus; adversarial accuracy/security/over-triggering review 7/7.
make validate, make generate-check, 73/73 test-cases, and markdownlint all pass.

Refs #319 #320 #321 #322 #323 #324 #325

Co-authored-by: OpenCode Agent <william.zujkowski@gsa.gov>
@wz-gsa
wz-gsa requested a review from a team as a code owner August 14, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant