From trillo
Drives building a Trillo AOS app step by step (Input → SoftwareSpec → EntityModel → Functions → Agents → UIScenario → deploy). Use whenever the user wants to build, continue, or resume a Trillo app, asks "what do I do next", or right after an app is selected. Checks app_status, runs the current step, and asks before advancing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/trillo:building-an-appThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You guide the user through a **stepwise refinement** — the same process the
You guide the user through a stepwise refinement — the same process the Trillo AI UI follows. The generation knowledge (prompts, schemas, the toolkit API) is served live by Trillo AI; your job is to orchestrate the steps and write each result back. Keep the user in the loop — this is a conversation, not a batch job.
requirements (Input) → SoftwareSpec → { EntityModel, UIScenario } → Functions → Agents → deploy
Strict rules — follow them, don't guess:
EntityModel requires SoftwareSpec; Functions require EntityModel;
Agents require Functions. Never create entities, functions, or agents
before SoftwareSpec is COMPLETED.UIScenario depends only on SoftwareSpec — generate it any time after
the spec; it neither blocks nor is blocked by EntityModel/Functions/Agents.The server also gates each step (a step stays NOT_READY until its predecessor
has output), so always call app_status first and run nextActivity — it
is the source of truth for what comes next. If the user asks for a step that
app_status shows NOT_READY, tell them what must come first instead of
forcing it.
app_list / app_select / app_create + .trillo/session.json). On first
work on an app, pull its artifacts to the local workspace; on returning,
resync — see the workspace skill.app_status → {activities:[{name, status, statusInfo}], nextActivity, deployStatus}.COMPLETED ✓ · READY (do next) · NOT_READY (blocked — statusInfo says on what) —
and what nextActivity is.For the current step (nextActivity) or a step the user names:
step_guide({step}) → the live prompt
(modelRole/objective/instructions/constraints) + expectedOutputSchema.
Generate exactly to that schema — do not invent fields.
Steps: SoftwareSpec, EntityModel, Functions, Agents, UIScenario;
add-one variants: EntityModel.add, Functions.add, Agents.add.
(Input has no step_guide — use the requirements skill.)SoftwareSpec / UIScenario → md_update (one activity_output per app)ClassM (EntityModel) / FunctionM (Functions) / AgentM (Agents) →
md_create per item, md_update to edit oneWhen a focused skill exists for the step, follow it: requirements (Input),
software-spec, entity-model, functions, agents,
ui-scenario, deploy. (They ship incrementally; if one isn't present,
fall back to this skill + step_guide.)
The user can go back to a completed step to regenerate or refine it, or add a
single item — use the .add step_guide variant (EntityModel.add, etc.) for
one entity/function/agent. After any write, re-check app_status; the server
re-derives downstream readiness.
If a requirement needs something AOS doesn't support yet, ground yourself with
aos_capabilities (the coverage map: In place / Partial / Gap), tell the user
plainly rather than faking it, and — with their OK — file it via
request_aos_capability. See the request-aos-capability skill.
deployStatus == "deployed"); do those after deploy.npx claudepluginhub trillo/tcs-claude-plugin --plugin trilloProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.