os-welcome

Routes users to the correct OS-Intelligence flow and configures permissions.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/simonconway1979/os-intelligence --skill os-welcome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-welcome
Source: https://github.com/simonconway1979/os-intelligence/tree/main/.claude/skills/os-welcome
Command: npx skills add https://github.com/simonconway1979/os-intelligence --skill os-welcome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OS-Intelligence can feel like a cold start after install because you must configure access, choose a useful starter workflow, and begin loading context before synthesis can work.

Core Features & Use Cases

  • First-run routing: Detects fresh vs returning installs and routes you to the right next step (welcome flow vs quick start).
  • Permissions setup guidance: Checks .claude/settings.local.json and offers to add missing auto-approve permission rules for OS-Intelligence-managed paths.
  • Guided context capture loop: Creates a new project via /os-new-project, then walks you through adding documents, transcripts, chats, and notes, ending with a synthesis handoff.

Use case: After installing OS-Intelligence, you want to create your first private project and produce a cross-cut synthesis using your own meetings and documents, without getting blocked by repetitive permission prompts.

Quick Start

Run the os-welcome skill to route you through permissions, create a first project, then guide you to add documents and trigger /ctx-synthesise for your first synthesis.

Frequently Asked Questions about os-welcome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up project initialization in Claude Code for product management workflows?

Project initialization in Claude Code for product management workflows is routed by detecting fresh versus returning installs, guiding you through permissions and context capture before producing a synthesis. It ensures your workspace is ready for cross-cutting document analysis.

How do I stop repetitive permission prompts when capturing project context?

To stop repetitive permission prompts during context capture, you can configure workspace access by validating and adding missing auto-approve rules to your local settings file. This allows OS-Intelligence to read and write managed project files without interruption.

What is the first-run setup process for a new project context synthesis?

The first-run setup process for a new project context synthesis involves checking your installation state, establishing workspace permissions, creating a project, and walking you through adding documents and notes before handing off to the synthesis engine.

Can I use Claude Code to add meeting transcripts and notes for product management synthesis?

Yes, you can use Claude Code to add meeting transcripts, chats, and notes for product management synthesis. The guided context capture loop ingests these documents into your private project before triggering the cross-cutting synthesis generation.

Does the guided context setup work for both new and returning installs?

The guided context setup works for both new and returning installs by detecting the installation state. Fresh installs are routed to a welcome flow while returning users are directed to a quick start for faster project initialization.

Why do I need to configure workspace permissions before starting a project synthesis?

You need to configure workspace permissions before starting a project synthesis so the system can autonomously read and write managed project files. Without these auto-approve rules, the context capture and synthesis process would be blocked by manual permission prompts.