Technical literacy
Source-grounded pack with Architecture and System Risk Scan, Technical Credibility Practice, and Technical Decision Brief, plus 1 more.
Use this pack when
Choose this pack when the work touches Technical literacy and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Included workflows
Choose the job in front of you.
4 source-grounded skills. Load one workflow at a time.
Architecture and System Risk Scan
Use this workflow when an operator needs to trace a software-shaped workflow or architecture, understand data and dependency ownership, debug a symptom with competing hypotheses, and identify failure, detection, recovery, support, migration, and organizational risks without designing the system alone.
Output Return an architecture and system risk scan with observation, systemtrace, dependenciesandseams, hypotheses, discriminatingchecks, riskandoperability, and findingsandnextevidence.
Technical Credibility Practice
Use this workflow when a non-engineer operator or leader wants to become more technically useful, develop operational fluency and analytical judgment, build selective hands-on execution, improve developer empathy, and earn trust with engineers through precise and reliable behavior.
Output Return a technical credibility plan with capabilitygoal, baseline, fluencypractice, judgmentcases, handsonexperiment, trustbehaviors, and feedbackandevidence.
Technical Decision Brief
Use this workflow when a non-engineer operator or leader must participate responsibly in an architecture, vendor, integration, data, platform, automation, build-versus-buy, migration, or systems decision by making goals, constraints, options, consequences, ownership, reversibility, and evidence legible.
Output Return a technical decision brief with decisionframe, systemcontext, optioncomparison, assumptionsandstress, riskandevidence, expertandoperatorcontext, and decisionrecord.
Technical Taste Review
Use this workflow when a proposed product, process, vendor, integration, data model, automation, abstraction, or architecture feels clever or feature-rich but needs review of complexity, dependencies, operability, reversibility, team fit, failure behavior, maintenance, and simpler alternatives.
Output Return a technical taste review with problemcontract, complexityinventory, abstractiontest, consequencemodel, humansystemfit, simpleroptions, and recommendation.
Human review
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.
Source and files
Grounded in the complete Technical literacy series.
10 source essays · 4 usable skills · reviewed Jul 2026