Generated from smart-base/skills/content/authoring-who-smart-guidelines/l4-application-brief.md — do not edit here.

✎ Edit this page’s source

l4-application-brief

Skill id: l4-application-brief · Package: authoring-who-smart-guidelines · Stage 7 of smart-guideline-end-to-end, task Task_DescribeApp of smart-guideline-end-to-end.bpmn, in the requester’s (user) lane.

The application is the requester’s, not the agent’s — the same rule as stage 0 (guideline-use-case).

Input and output

The contract is input.schema.json and output.schema.json.

  • In: what the requester said (request), the useCase, the stage-4 l2Assets the options are drawn from, and the stage-6 ig build.
  • Out: the applicationBrief (topic, kind, users, devices, l2Processes, l3Resources, operations, connectivity, systems); and the wireframeRequest, which is cat-harness wireframe-design-review’s input for design use, so stage 8a is called with it unchanged.

Steps

  1. If the request does not describe the application, ask a numbered question. Use the requester’s own words where they gave any, and offer options drawn from the L2 personas and processes already found:

    Which application are we building?

    1. A point-of-care app for the DAK’s main persona, covering its business processes (recommended when stage 4 found one dominant persona).
    2. A reporting / indicator dashboard over the DAK’s indicators.
    3. A decision-support service (CDS Hooks / $apply) that an existing EMR calls.
    4. Tell me more.
  2. Fill the brief. users are L2 persona ids, l2Processes L2 business-process ids, l3Resources canonicals from the stage-6 build: the brief names what the guideline already has, and a need it does not have goes back to stage 4 or 6 as a finding.
  3. Write the wireframeRequest: use: design, the brief’s topic, the application’s screens as surface, and as intent who the screens are for, what they need to do and what they must show.

Adjudication

None: the requester is the source. The brief is checked when the wireframes and the application are adjudicated.

Processes that run this skill

processstep(s) that name it
SMART Guideline end to end7 · L4: describe the consuming application

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed b08c961 · 2026-10-23T23:11:09Z