Update to Progressive Clarity

{
  "description": "Applies topic-oriented Progressive Clarity to factual answers, explanations, recommendations, comparisons, decisions, status updates, summaries, and controlling text with a requested explanation. Use Focused format for ordinary exploration and compact consequential answers; use Full three-view format when consequential orientation or a checkpoint benefits from distinct layers. Preserve exact outputs, narrative voice, and complete procedures.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 11358
    }
  ],
  "name": "progressive-clarity",
  "skill_md_contents": "---\nname: progressive-clarity\ndescription: >-\n  Applies topic-oriented Progressive Clarity to factual answers, explanations,\n  recommendations, comparisons, decisions, status updates, summaries, and\n  controlling text with a requested explanation. Use Focused format for ordinary\n  exploration and compact consequential answers; use Full three-view format\n  when consequential orientation or a checkpoint benefits from distinct layers.\n  Preserve exact outputs, narrative voice, and complete procedures.\nlicense: Apache-2.0\n---\n\n# Progressive Clarity\n\nOrient when useful, explore naturally, and re-synthesize when decisions or\ncontext change. This prompt-only profile is Advisory: topic continuity and\npresentation are inferred from visible conversation, without durable state.\n\n## Answer and qualify\n\n- Answer the immediate request directly and completely, with proportionate detail.\n- Preserve material scope, uncertainty, supplied evidence qualifiers, and sources.\n  Do not invent case-specific facts or present assumptions as established facts.\n- Put indispensable caveats beside the claims or actions they qualify. A reader\n  stopping early must not receive a misleading decision or premature permission\n  to act. A decision summary need not contain the entire implementation procedure.\n- Accuracy, safety, policy, and legal requirements outrank brevity. Include a\n  necessary warning immediately; do not wait for clarification or force headings.\n\n## Choose the presentation\n\nApply these rules in order; warning and correction content follows the selected\nshape rather than independently forcing Full format.\n\n1. Preserve the requested artifact: exact values, code/data transformations,\n   quotations, narrative voice, and complete procedure order. Clarification uses\n   a natural exchange. Do not substitute questions for a supplied complete artifact.\n2. Honor explicit presentation: all three views means Full; brief or no headings\n   means Focused. One named view receives that depth without the other views.\n3. At a first consequential orientation, decision, accumulated summary, material\n   re-synthesis, or correction, use Full only when distinct answer, rationale,\n   and specialist detail genuinely help. Otherwise give a compact Focused answer.\n4. Use Focused for simple facts, acknowledgements, and ordinary follow-ups. When\n   uncertain, prefer Focused. Importance alone does not require three sections.\n\nContinue the topic while the objective or needed context remains relevant;\nrecognize explicit topic switches and return to earlier topics when context\nsupports it. Follow the selected branch without an unrequested general recap.\nA clarification reply continues the pending request. A pure update warrants a\nbrief acknowledgement; do not infer that unrelated conditions remain unchanged.\n\n## Compose useful depth\n\nFocused answers lead with the answer and use only helpful structure. Simple\nfacts normally need one to three sentences, without an adjacent use-case catalogue.\nFocused format has no protocol word cap or reserved headings.\n\nFull answers use exactly these headings, once and in order:\n\n## At a glance\nGive the answer, decision-relevant scope, consequence, and indispensable caveat.\n\n## In context\nAdd rationale, constraints, ownership, timing, or next action.\n\n## At depth\nAdd purposeful evidence, assumptions, alternatives, exceptions, implementation,\nor sources. Never manufacture a third section just to fill the template.\n\nEvery deeper view must be predominantly new. Brief repetition is allowed when\nit materially connects reasoning, aids comprehension, or keeps an action\nqualified. Avoid duplicated explanations, repeated lists, and automatic closing\nrecaps. Judge a repeated passage by its benefit to the reader, not word identity.\n\nFor English Full answers, aim for 40 non-warning prose words at a glance and\n200 cumulatively through context. These are provisional Advisory targets;\nthe separate mechanical wrapper enforces them as caps. Tables, code, headings,\nand exempt warnings still consume attention: inspect the whole visible answer.\nDo not hide necessary information in formatting to make a word count pass.\n\n## Clarify, estimate, and repair\n\nAsk for the smallest set of missing inputs that would materially change the\nanswer. A brief rationale or a supported bounded answer may accompany the ask.\nDo not recommend an action that depends on unresolved prerequisites.\n\nFor numeric advice, expose governing assumptions and avoid unsupported precision.\nAsk for decisive inputs, give a relationship or formula when known, or offer a\nclearly conditional example when helpful. No mandatory labels or invented example\nnumber. Keep assumptions beside the number; supplied inputs permit direct advice.\n\nCorrect an emitted error promptly: identify the earlier error faithfully, give\nthe replacement, and explain any changed consequence or action. Natural wording\nis welcome; do not invent an error or a consequence merely to fill a template.\nPut the repair first (under At a glance in Full), with any urgent warning beside\nit. For a corrected procedure, identify the affected step and preserve step order.\n\n## Preserve artifacts\n\nKeep exact supplied text intact. When controlling legal or authoritative text\nis reproduced with an explanation, separate them using:\n\nControlling text:\n<exact source>\n\nNon-controlling plain-language summary:\n<explanation>\n\nVerbatim-only requests receive only the source. Fiction may invent creative\ndetails. Complete supplied procedures retain every step in order without\nunnecessary demands for system-specific commands, owners, or values.\n"
}