{
  "exampleUrl": "https://jasminejames.dev/leading-deeper/assess-workflow-value-example.json",
  "schemaVersion": 1,
  "version": 1,
  "author": "Jasmine James",
  "id": "assess-workflow-value",
  "title": "Check whether the workflow is helping",
  "summary": "Check whether the workflow reduces human effort after review, correction and maintenance, then decide whether to keep, revise or stop it.",
  "inputs": [
    "Workflow step, intended outcome, owner, people involved and protected judgment or development",
    "Definition of a comparable completed case, acceptance checks and reporting period",
    "Manual baseline and assisted human effort, including remaining preparation, review, correction, interventions and handoffs",
    "Recurring maintenance and one-time setup effort, with case counts or an explicit amortization horizon where known",
    "Known tool costs, quality findings and evidence of what available attention was used for",
    "Source, date, unit, coverage and measured or estimated status for each input; unknowns may remain unknown"
  ],
  "prompt": "Assess one AI-assisted workflow and return a decision draft. This is a new companion exercise, not evidence that the talk's examples produced any particular saving.\n\nINPUTS\nWorkflow, intended outcome and owner: [fill in]\nPeople involved and judgment or growth to protect: [fill in]\nCompleted-case definition and acceptance checks: [fill in]\nReporting period and comparable manual/assisted cases: [fill in]\nActive human effort and its components: [supply measurements or bounded estimates]\nMaintenance, setup, supported case counts and any proposed amortization horizon: [fill in or mark unknown]\nKnown costs, quality findings and use of attention: [fill in or mark unknown]\nApproved evidence and its provenance: [supply records, excerpts or scoped read locations]\n\nCOMPARE\nCompare like-for-like completed cases with similar scope, complexity and quality requirements. Make volume, staffing and case-mix differences visible. Label each input measured, recalled, estimated or assumed, with its source, date, unit and coverage. Missing evidence remains unknown; it is never zero by default.\n\nUse active person-minutes, including preparation, review, correction, interventions and relevant handoffs. Count each person's effort once. If a review total already includes corrections, do not add them again. Do not infer effort from message counts, assistance percentages, scheduled calendar duration, generated outputs or elapsed agent runtime. Include unsuccessful attempts and rework within the effort window. Do not compare only successful assisted cases with the full manual baseline; show unfinished or excluded cases and limit conclusions when a fair completed-case comparison is unavailable.\n\nAllocate recurring maintenance across the cases it supports. Amortize setup only when its effort and an explicit supported or proposed case horizon are known; distinguish projection from observation. Never charge setup twice. If setup is unknown or excluded, label the result a recurring-effort comparison before setup, not an all-in saving.\n\nIn minutes: baseline effort/case = baseline case effort + allocated baseline overhead; assisted effort/case = assisted human effort + allocated assisted overhead. Net recurring reduction/case = baseline effort/case minus assisted effort/case. All-in reduction/case also subtracts allocated setup. A period total multiplies the relevant per-case result by a supported comparable case count. Preserve negative results. Use actual totals or suitable summaries when case sizes differ. If inputs are bounded estimates, calculate conservative bounds and state their provenance. Convert minutes to hours only after computing the scoped total. Do not extrapolate beyond the supplied frequency and period without labeling the assumptions.\n\nVALUE\nKeep effort, monetary cost, quality and use of attention separate. Known API/tool/hosting charges are not human time. Do not monetize effort without a supplied rate and stated assumptions. Review acceptance checks, errors, coverage and rework; AI's self-assessment is not independent quality evidence. Reduced effort does not establish customer value, growth or wellbeing. Distinguish what the owner intended to make room for from what actually happened. Routine work for one person may be useful practice for another; protect judgment, relationships, learning, ownership and reviewer capacity.\n\nOUTPUT\nReturn a concise conclusion, calculation or comparison, provenance, quality/cost findings and observed use of attention. Separate supported observations, bounded estimates and unknowns; state setup treatment and material exclusions. Propose keep, revise or stop against the intended outcome and acceptance conditions. When evidence is insufficient, propose a bounded revision or measurement rather than declaring success. Name one small next measurement, owner, scope and review point.\n\nSTOP\nWork with supplied data; no MCP is compulsory. Optional external evidence needs scoped read access to the agreed accounts, measures and period. Return the draft here unless a private destination is authorized. Do not change workflows, assign people, publish results, contact colleagues or create tracking or scheduled automation.",
  "review": [
    "Are the cases and quality requirements comparable, and are every input, exclusion and estimate traceable?",
    "Does human effort include preparation, review, correction and overhead exactly once, with unknown setup kept distinct?",
    "Does the conclusion separate effort, cost, quality and actual use of attention while protecting judgment and person-relative growth?",
    "Is the proposed keep, revise or stop decision proportionate to the evidence?"
  ],
  "evidence": [
    "Use active human effort for comparable completed cases; retain unsuccessful attempts, rework and case-mix or coverage limits.",
    "Check maintenance allocation and setup treatment; a before-setup comparison does not establish an all-in benefit.",
    "Compare quality and known costs for the same scope. Record what available attention supported without assuming a customer, growth or wellbeing result.",
    "If evidence is missing, take one small prospective measurement rather than deriving hours from messages, assistance rates or calendar time."
  ],
  "status": "New companion exercise for the talk resources; not a historical result or the original internal prompt",
  "tooling": {
    "summary": "No MCP is needed with supplied measurements and workflow context. Optional scoped read access can help establish case counts, dates and effort evidence.",
    "noMcpFallback": "Provide an approved aggregate table, timing notes or excerpts with dates, units, scope and provenance. Keep missing values unknown and propose one small manual measurement.",
    "requirements": [
      {
        "capability": "Read optional effort and case evidence",
        "requiredWhen": "Only when approved measurements or records must be retrieved rather than supplied.",
        "providers": [
          "Approved local CSV, spreadsheet or timing-log tools",
          "An approved reporting or issue-tracker connector or MCP",
          "An approved calendar connector or export for context only"
        ],
        "operations": [
          "Read the selected timing measures, completed-case records and quality findings",
          "Check definitions, case counts, dates and coverage",
          "Record provenance and distinguish active effort from calendar or system elapsed time"
        ],
        "access": "Read access to the named records and reporting window. Calendar duration or task state alone is not an effort measure; no edits, messaging, administration or tracking setup is required.",
        "manualAlternative": "Supply selected timing notes, case outcomes and known overhead in a small table, or leave unknowns explicit and plan the next measurement.",
        "sourceUrls": []
      }
    ]
  },
  "updated": "2026-11-04",
  "value": {
    "id": "assess-workflow-value",
    "cardSummary": "Compare preparation, review, corrections and upkeep before deciding whether to keep an automation.",
    "outcome": "Compare preparation, review, corrections and upkeep before deciding whether to keep an automation.",
    "bridge": {
      "practice": "Use a repeatable Softball IQ task, such as a debrief or content review, as a proposed measurement exercise.",
      "work": "Apply the same comparison to a workplace workflow, including preparation, review, correction and the outcome people need.",
      "relationship": "new-companion"
    },
    "humanDecision": "You decide whether the evidence supports keeping, changing or stopping the automation, and where any released capacity should go.",
    "valueToCheck": "Compare similar tasks and periods, count all human effort, record quality tradeoffs and label estimates separately from observed results."
  },
  "firstRun": {
    "id": "assess-workflow-value",
    "goal": "Check the effort behind one workflow.",
    "supplied": [
      {
        "label": "Comparable work | Fictional week",
        "text": "Five completed drafts per approach, with the same acceptance requirements assumed. No failed or unfinished cases in this illustration. Effort is active person-minutes, not agent runtime or elapsed time."
      },
      {
        "label": "Effort records | Invented measurements",
        "text": "Manual work: 25 minutes per draft including preparation and checks, with zero separate baseline maintenance explicitly assumed. Assisted work: 7 minutes per draft including preparation, review and corrections, plus 10 minutes of maintenance for the week."
      },
      {
        "label": "Unknowns and request",
        "text": "Setup effort, monetary cost and use of attention are unknown. Equal quality is assumed for the example, not independently verified. Return a decision draft and one next measurement; make no workflow or staffing changes."
      }
    ],
    "steps": [
      {
        "actor": "human",
        "label": "Supply a fair comparison",
        "description": "Name the completed task, period and quality requirements. Provide human effort for both approaches and label assumptions, estimates and missing values."
      },
      {
        "actor": "ai",
        "label": "Prepare a decision draft",
        "description": "Explain what the effort comparison can establish, showing a traceable calculation. Separate the recurring difference from unknown setup, cost, quality and impact."
      },
      {
        "actor": "human",
        "label": "Choose the next measurement",
        "description": "Check comparability and arithmetic, then decide whether the evidence supports keeping, revising or stopping. Unknown effort stays unknown rather than becoming zero."
      }
    ],
    "output": {
      "title": "Workflow assessment | Five comparable drafts",
      "sections": [
        {
          "label": "Recurring human effort",
          "text": "Manual: 125 active person-minutes. Assisted: 45 active person-minutes including maintenance. Difference: 80 minutes before setup. [Supplied fictional effort records]"
        },
        {
          "label": "Quality and unknowns",
          "text": "Equal acceptance requirements are assumed for the illustration, not independently validated evidence. Setup effort and monetary cost are unknown."
        },
        {
          "label": "Recommendation",
          "text": "Revise the assessment: collect setup effort and real comparable case measurements before claiming an all-in benefit."
        },
        {
          "label": "Next evidence",
          "text": "Have the workflow owner record active preparation, review, corrections and maintenance for the next comparable completed cases; retain failures and exclusions."
        }
      ]
    },
    "exampleUrl": "/leading-deeper/assess-workflow-value-example.json",
    "outputRequirements": [
      "Comparable cases, units and a traceable calculation",
      "Assumptions, missing evidence and setup treatment",
      "Quality, monetary cost and use of attention kept distinct from effort",
      "A reviewed keep, revise or stop proposal and one next measurement"
    ],
    "review": [
      "Were the cases comparable, and did you count all human effort once, including unsuccessful attempts in your real comparison?",
      "Do the known results support the decision, or do you first need setup, quality or other missing evidence?"
    ],
    "updated": "2026-11-04",
    "notice": "All examples use invented sources and results. They are illustrations, not reports from Jasmine’s workplace or measured outcomes.",
    "modelAgnosticNote": "Use the AI tool approved for your work with supplied material. Wording and layout will vary by model; look for the evidence, uncertainty and review decisions shown here. Connections and recurring runs depend on your setup."
  },
  "modelGuidance": {
    "reviewedOn": "2026-11-02",
    "basis": "Suggested fit based on official provider documentation, not our own speed or quality benchmarks. Test on representative examples before relying on a model.",
    "pricingBasis": "USD per one million input and output tokens, using standard first-party API pricing. These are not subscription prices or total workflow costs. Tool calls, reasoning, retries, caching and different tokenizers affect the final bill.",
    "runtimeNote": "A model does not connect your tools or grant access. MCP support, available tools and model selection depend on the agent host and your organization's approved setup.",
    "catalogUrl": "https://jasminejames.dev/leading-deeper/model-guidance.json",
    "reviewedLabel": "November 2, 2026",
    "start": {
      "modelId": "gpt-6-luna",
      "effort": "low",
      "why": "A starting point for organizing a small supplied evidence table and explaining deterministic calculations. Check the arithmetic with a calculator or code and review the assumptions."
    },
    "escalate": {
      "modelId": "gpt-6.1-sol",
      "when": "The cases are hard to compare, records conflict or the decision needs a deeper examination. A stronger model cannot recover unmeasured effort."
    },
    "alternatives": [
      {
        "modelId": "claude-haiku-5-5",
        "when": "An alternative for structuring supplied evidence in an approved Claude host. Compare review effort and complete workflow cost on your own cases."
      }
    ],
    "humanBoundary": "The owner decides whether to keep, revise or stop. A model cannot establish savings from missing measurements or infer that released effort produced customer value or growth.",
    "models": {
      "gpt-6-luna": {
        "name": "GPT-6 Luna",
        "provider": "OpenAI",
        "apiId": "gpt-6-luna",
        "context": "1.05 million tokens",
        "providerPositioning": "Focused, cost-sensitive, high-volume work.",
        "prices": [
          {
            "label": "Standard API",
            "inputUsdPerMillion": 0.1,
            "outputUsdPerMillion": 0.5,
            "condition": ""
          }
        ],
        "modelSourceUrl": "https://developers.openai.com/api/docs/models/gpt-6-luna",
        "pricingSourceUrl": "https://developers.openai.com/api/docs/pricing"
      },
      "gpt-6.1-sol": {
        "name": "GPT-6.1 Sol",
        "provider": "OpenAI",
        "apiId": "gpt-6.1-sol",
        "context": "1.05 million tokens",
        "providerPositioning": "Complex coding and professional work with a balance of intelligence and cost.",
        "prices": [
          {
            "label": "Standard API",
            "inputUsdPerMillion": 2,
            "outputUsdPerMillion": 10,
            "condition": ""
          }
        ],
        "modelSourceUrl": "https://developers.openai.com/api/docs/models/gpt-6.1-sol",
        "pricingSourceUrl": "https://developers.openai.com/api/docs/pricing"
      },
      "claude-haiku-5-5": {
        "name": "Claude Haiku 5.5",
        "provider": "Anthropic",
        "apiId": "claude-haiku-5-5",
        "context": "1 million tokens",
        "providerPositioning": "High-volume, latency-sensitive classification, extraction and routing.",
        "prices": [
          {
            "label": "Standard API",
            "inputUsdPerMillion": 0.1,
            "outputUsdPerMillion": 0.5,
            "condition": "For requests with prompts up to 100,000 tokens."
          },
          {
            "label": "Standard API",
            "inputUsdPerMillion": 0.5,
            "outputUsdPerMillion": 2.5,
            "condition": "For requests with prompts over 100,000 tokens; the higher rates apply to that request."
          }
        ],
        "modelSourceUrl": "https://platform.claude.com/docs/en/models/haiku-5-5/overview",
        "pricingSourceUrl": "https://platform.claude.com/docs/en/about-claude/pricing"
      }
    }
  },
  "skillUrl": "https://jasminejames.dev/leading-deeper/skills/assess-workflow-value/SKILL.md",
  "repositorySourceUrl": "https://github.com/jasminelsjames/leading-deeper-ai-skills/blob/e1d2e65d3922c5e376fc0c6e8cfbb2f85722b1a7/skills/assess-workflow-value/SKILL.md",
  "repositoryRawUrl": "https://raw.githubusercontent.com/jasminelsjames/leading-deeper-ai-skills/e1d2e65d3922c5e376fc0c6e8cfbb2f85722b1a7/skills/assess-workflow-value/SKILL.md",
  "skillRequest": "Read this GitHub agent skill and use it to assess whether one workflow is helping:\nhttps://raw.githubusercontent.com/jasminelsjames/leading-deeper-ai-skills/e1d2e65d3922c5e376fc0c6e8cfbb2f85722b1a7/skills/assess-workflow-value/SKILL.md\n\nTask and period: [what you compared]\nCases: [comparable completed work, including failures]\nHuman effort: [preparation, review, corrections and upkeep]\nQuality and setup: [measured results and costs]\nUnknowns: [anything not measured]\n\nUse comparable cases and the measurements I provide. Include human preparation, review, correction and maintenance. Keep unknowns and setup costs visible. Separate effort from quality, cost and what the attention enabled. Return a decision draft and one next measurement.",
  "sampleRequest": "Read this GitHub agent skill and use it to assess whether one workflow is helping:\nhttps://raw.githubusercontent.com/jasminelsjames/leading-deeper-ai-skills/e1d2e65d3922c5e376fc0c6e8cfbb2f85722b1a7/skills/assess-workflow-value/SKILL.md\n\nTry this fictional example. All people, records and measurements below are invented. Use only the supplied context; no connectors, account access or additional records are available.\n\nGoal: An effort comparison and a keep, revise or stop recommendation.\nYou prepare the draft; I review it. Keep any named decision owner in the supplied material responsible for their decision.\n\nSupplied context:\nComparable work | Fictional week\nFive completed drafts per approach, with the same acceptance requirements assumed. No failed or unfinished cases in this illustration. Effort is active person-minutes, not agent runtime or elapsed time.\n\nEffort records | Invented measurements\nManual work: 25 minutes per draft including preparation and checks, with zero separate baseline maintenance explicitly assumed. Assisted work: 7 minutes per draft including preparation, review and corrections, plus 10 minutes of maintenance for the week.\n\nUnknowns and request\nSetup effort, monetary cost and use of attention are unknown. Equal quality is assumed for the example, not independently verified. Return a decision draft and one next measurement; make no workflow or staffing changes.\n\nReturn:\n- Comparable cases, units and a traceable calculation\n- Assumptions, missing evidence and setup treatment\n- Quality, monetary cost and use of attention kept distinct from effort\n- A reviewed keep, revise or stop proposal and one next measurement\n\nStop after returning the private draft in this chat. Keep source labels, assumptions and unknowns visible. Do not send messages, change files or tasks, publish, connect tools or create a schedule. If you cannot read the linked skill, say so rather than claiming to have used it.",
  "feedbackUrl": "https://github.com/jasminelsjames/leading-deeper-ai-skills/issues/new?template=skill-feedback.md&title=Feedback%3A+Check+whether+the+automation+is+helping&body=**Which+skill+did+you+try%3F**%0A%0ACheck+whether+the+automation+is+helping+%28assess-workflow-value%29%0A%0A**What+did+you+use+it+for%2C+and+what+result+did+you+get%3F**%0A%0A**What+did+you+have+to+correct%2C+and+what+would+make+the+next+run+better%3F**%0A%0A**Agent+and+model%2C+if+known%3A**%0A%0AOptional%3A+a+short+fictional+or+sanitized+example.+Do+not+include+private+workplace+content%2C+credentials+or+personal+information+about+others.",
  "htmlUrl": "https://jasminejames.dev/leading-deeper/assess-workflow-value",
  "markdownUrl": "https://jasminejames.dev/leading-deeper/assess-workflow-value.md",
  "jsonUrl": "https://jasminejames.dev/leading-deeper/assess-workflow-value.json",
  "textUrl": "https://jasminejames.dev/leading-deeper/prompts/assess-workflow-value.txt",
  "requiresHumanReview": true
}
