technical-essay-study-workflow

name	technical-essay-study-workflow
description	Create or review structured study notes from technical essay collections, engineering blogs, opinionated practice books, industry criticism, and experience-based software or engineering writing where the learning unit is claim → reasoning → anecdote/context → practice or applicability limit. Do not use for systematic textbook taxonomies or for problem-framing sources whose lesson depends on misframing → reframing → consequence.
metadata	{"short-description":"Technical essay study-note workflow"}

Purpose

Create or review privacy-safe study notes from technical essay collections, engineering blogs, opinionated practice writing, industry criticism, and experience reports.

The output is a paraphrased learning artifact, not a transcript. Do not copy long passages from the source. Prefer paraphrased explanation, compact references, and original learning structure. Use short quotations only when necessary and only within applicable copyright limits.

When to use

Use this skill when:

• the source is made of essays, blog posts, columns, criticism, experience reports, or opinionated practice writing
• learning depends on author claim, reasoning path, anecdote/example, practice advice, historical context, or applicability limit
• the user asks to separate timeless advice from time-bound technology, market, or organizational assumptions
• the user asks for principle/practice/checklist extraction from essays

Do not use when:

• the source is stable textbook taxonomy; route to textbook-structured-content-workflow
• the source primarily teaches through misframing/reframing cases; route to problem-framing-narrative-study-workflow
• the task is final mechanical publish/sync gate; route to in mode