Technical literacy
Source-grounded pack with Architecture and System Risk Scan, Technical Credibility Practice, and Technical Decision Brief, plus 1 more.
Get this packGrounded in the complete Technical literacy series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 4 usable skills · reviewed Jul 2026
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.
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 specification
Return an architecture and system risk scan with observation, system_trace, dependencies_and_seams, hypotheses, discriminating_checks, risk_and_operability, and findings_and_next_evidence.
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 specification
Return a technical credibility plan with capability_goal, baseline, fluency_practice, judgment_cases, hands_on_experiment, trust_behaviors, and feedback_and_evidence.
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 specification
Return a technical decision brief with decision_frame, system_context, option_comparison, assumptions_and_stress, risk_and_evidence, expert_and_operator_context, and decision_record.
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 specification
Return a technical taste review with problem_contract, complexity_inventory, abstraction_test, consequence_model, human_system_fit, simpler_options, and recommendation.
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.