different-ai · jcllobet · Mar 25, 2026 · Mar 26, 2026 · Mar 27, 2026 · Mar 28, 2026
diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md
@@ -440,10 +440,12 @@ This is intentional for now: predictable scoping beats clever cross-root auto-ro
 ## Cloud Worker Connect Flow (Canonical)
 
 1. Authenticate in OpenWork Cloud control surface.
-2. Launch worker (with checkout/paywall when needed).
-3. Wait for provisioning and health.
-4. Generate/retrieve connect credentials.
-5. Connect in OpenWork app via deep link or manual URL + token.
+2. Create or join the target organization.
+3. Complete checkout when hosted onboarding or worker launch requires billing.
+4. Resume the cloud flow with any saved org draft restored.
+5. Launch worker and wait for provisioning/health.
+6. Generate/retrieve connect credentials.
+7. Connect in OpenWork app via deep link or manual URL + token.
 
 Technical note:
 

diff --git a/PRODUCT.md b/PRODUCT.md
@@ -37,12 +37,13 @@ Where are workflow hosted:
 
 - Users can sign in with the standard web auth providers or accept an org invite through the hosted join flow.
 - Invite signup keeps the invited email fixed, verifies the user by email code, and then drops them into the org join path.
-- Cloud workers are a paid flow: users complete checkout before they can launch hosted workers.
+- First-org setup and hosted workers are paid flows when billing is required: users can be sent to checkout during org creation, then returned to the app with their draft organization restored.
 - After a worker is ready, the user connects from the OpenWork app with `Add a worker` -> `Connect remote`, or opens the generated deep link directly.
 
 ## Team distribution
 
 - Organizations can publish shared skill hubs so members discover approved skills from one managed place instead of collecting local-only installs by hand.
+- Skill hub entries are stored as full `SKILL.md` documents, and the shared title/summary come from YAML frontmatter such as `name` and `description`.
 
 ## Actors
 Bob IT guy makes the config.

diff --git a/ee/apps/den-web/README.md b/ee/apps/den-web/README.md
@@ -7,17 +7,24 @@ Frontend for `app.openworklabs.com`.
 - Signs up / signs in users against Den service auth.
 - Handles invited-org signup flows where the invited email stays locked and the user verifies access before joining.
 - Launches cloud workers via `POST /v1/workers`.
-- Handles paywall responses (`402 payment_required`), routes users through Polar checkout, and only enables worker launch after purchase.
+- Handles paywall responses (`402 payment_required`), routes users through Polar checkout during org setup or worker launch, and resumes the flow after purchase.
 - Offers desktop handoff actions so users can open the generated worker directly in OpenWork or copy the connect credentials manually.
 - Uses a Next.js proxy route (`/api/den/*`) to reach `api.openworklabs.com` without browser CORS issues.
 - Uses a same-origin auth proxy (`/api/auth/*`) so GitHub OAuth callbacks can land on `app.openworklabs.com`.
 
 ## Current hosted user flow
 
 1. Sign in with a standard provider or accept an org invite.
-2. If the org requires billing, complete checkout before launching a worker.
-3. Launch the worker from the cloud dashboard.
-4. Open the worker in the desktop app with the provided deep link, or copy the URL/token into `Connect remote` manually.
+2. Create or join an organization.
+3. If billing is required, complete checkout and return to the app with the saved org draft restored.
+4. Launch the worker from the cloud dashboard.
+5. Open the worker in the desktop app with the provided deep link, or copy the URL/token into `Connect remote` manually.
+
+## Skill authoring
+
+- Uploaded and saved skills should remain valid `SKILL.md` documents.
+- Include YAML frontmatter with at least `name` at the top of the file.
+- When present, `description` in the frontmatter becomes the summary shown in Den.
 
 ## Local development
 

diff --git a/packages/docs/introduction.mdx b/packages/docs/introduction.mdx
@@ -7,10 +7,12 @@ OpenWork Cloud enables team to move faster by making it easy to share your setup
 [https://app.openworklabs.com/](https://app.openworklabs.com/)
 
 - \*\*Team Templates: \*\*make it easy to share your setup across your team so they spend less time copy and pasting configs.
-- \*\*Members: \*\*Makes it easy to invite members to your org.
+- \*\*Members: \*\*Makes it easy to invite members to your org and keep onboarding aligned with your billing plan.
 - \*\*Shared Workspace: \*\*Are cloud instances you can use to perform long-running tasks or connect permanent connection to messaging channels like Slack or Telegram.
 - \*\*Custom LLMs: \*\*(coming soon)
 
+Hosted onboarding can include checkout before the first org or worker is fully provisioned. After payment, OpenWork Cloud brings you back to the same setup flow so you can finish creating the org and connect from the desktop app.
+
 <Frame>
   ![Image](/images/image-6.png)
-</Frame>
+</Frame>
diff --git a/packages/docs/sharing-ow-setup.mdx b/packages/docs/sharing-ow-setup.mdx
@@ -19,6 +19,8 @@ Click on the `...` next to the workspace name, then `Share ...` , then `Share a
 
 You can share a `SKILL.md` by clicking under `Your_Workspace` \> `Skills`
 
+Make sure the skill file starts with YAML frontmatter. At minimum it should include `name`, and `description` is used as the shared summary when present.
+
 <Frame>
   ![Skills management page showing installed skills](/images/sharing-skills-list.png)
 </Frame>
@@ -33,4 +35,4 @@ This creates a url that you can share with other people so they can `copy the sk
 
 <Frame>
   ![Shared skill page with Copy and Open in OpenWork buttons](/images/sharing-skill-share-page.png)
-</Frame>
+</Frame>
diff --git a/packages/docs/team-provisioning.mdx b/packages/docs/team-provisioning.mdx
@@ -6,4 +6,8 @@ OpenWork Cloud enables team to move faster by making it easy to share your setup
 
 When your team starts with OpenWork they'll have the option to pick from one of the templates that is uniquely provisioned to them.
 
-Creating a template is easy: simply create a setup as you would usually. Create your skills, connect your MCPs, and simply click on Share.
+Creating a template is easy: simply create a setup as you would usually. Create your skills, connect your MCPs, and simply click on Share.
+
+Invites now count against the member limit before they are accepted, so plan your seat count around both active members and pending invites.
+
+If your organization needs billing before the first shared workspace can be launched, OpenWork Cloud sends you through checkout and then resumes the org setup flow with your draft organization details restored.