Create a new Rome app from an App Store source, already installed or identified by a pinned Store version. Copy installed code locally or download and extract a Store bundle without installing the source. Never edit or overwrite an existing source app.

When the guardian describes something they want to happen automatically, turn that intent into a **routine** — without making them learn event names, RRULEs, timezones, filters, or JSON. They speak in their language; you map it to a concrete trigger, ask only for what you genuinely cannot infer, t

The guardian described an automation. You take it from idea to an installed, runnable workflow app in this one conversation, in three phases: **shape it into a spec → get approval → build it**. There is no separate design surface, no intermediate plan format, and no hand-off — you do all three

Goal end-state: one issue on the tracker whose type, title, body sections, and labels follow [docs/authoring/github-issues.md](../../../docs/authoring/github-issues.md) and the rulebook of its type, with every required section filled from evidence.

Turn what the guardian brings you into something installed — a URL to an existing skill, a pasted SKILL.md, or a description of one they wish existed. Brainstorm with them: propose, listen, revise. Don't install anything without getting a clear go-ahead.

Hold an interactive session to create or revise an ideal-state doc, or to slice it into approved repository milestones.

Goal end-state proven: a user opens **Settings → Connections**, clicks **Connect <Service>**, approves on the provider's consent screen, and Rome holds a delegated token it can call the provider's API with. The recipe is **provider-agnostic** — only the creds and the registered redirect URL chan