# App Investigation Prompt

Use this prompt template to investigate cplace apps and document their capabilities.

---

## Workspace Naming Convention

All investigation workspaces use this uniform naming pattern:

```
[App Investigation] <qualified.name>
```

**Examples:**
- `[App Investigation] cf.cplace.meeting`
- `[App Investigation] cf.cplace.gantt`
- `[App Investigation] cf.cplace.okr`

This makes investigation workspaces:
- Easy to identify in the workspace list
- Easy to clean up later
- Clearly distinguishable from production workspaces

---

## Prerequisites

Before investigating, you need to know the app's qualified name. To discover available apps:

```
Use mcp__cplace__cplace_list_workspace_apps with:
- workspaceId: <any existing workspace>
- category: "all"
- responseFormat: "minimal"

This returns all apps (installed and available) with their qualified names.
```

---

## Generic Investigation Prompt

Replace `<APP_NAME>` and `<APP_QUALIFIED_NAME>` with the target app:

```
I'm investigating cplace apps to build a catalog for the /building-blocks skill. Read the context in the apps catalog (use cplace_list_apps_catalog MCP tool)

Now investigate the **<APP_NAME>** app (`<APP_QUALIFIED_NAME>`) following this process:

## Step 1: Create Investigation Workspace

Use mcp__cplace__cplace_create_workspace:
- name: "[App Investigation] <APP_QUALIFIED_NAME>"
- (no apps - we want a minimal workspace)

Record the workspace ID for subsequent steps.

## Step 2: Check Pre-Installation State

Before installing, document the baseline:

1. Use mcp__cplace__cplace_list_workspace_apps with category="installed" to see what's already there (should be minimal/platform only)
2. Use mcp__cplace__cplace_list_types to see baseline types

## Step 3: Install the App

Use mcp__cplace__cplace_install_workspace_app:
- workspaceId: <from step 1>
- appQualifiedName: "<APP_QUALIFIED_NAME>"

Note: Dependencies auto-install.

## Step 4: Document What Changed

After installation, gather:

1. **Installed Apps** (including dependencies):
   Use mcp__cplace__cplace_list_workspace_apps with category="installed"
   → Compare to Step 2 to identify what got auto-installed

2. **Types Provided**:
   Use mcp__cplace__cplace_list_types
   → For each NEW type (not in Step 2), get details with:
   mcp__cplace__cplace_get_type_datamodel with responseFormat="minimal"

3. **Widgets Provided**:
   Use mcp__cplace__cplace_list_widget_definitions
   → Filter results where requiredApp matches "<APP_QUALIFIED_NAME>"

## Step 5: Create Documentation

Create folder and README:
   ai-builder/apps/<APP_QUALIFIED_NAME>/
   └── README.md

Follow the template structure from ai-builder/apps/README.md

## Step 6: Update Tracking

Update ai-builder/apps/README.md to mark <APP_NAME> as complete.

## Step 7: Cleanup (Optional)

The investigation workspace can be kept for reference or deleted.
The `[App Investigation]` prefix makes these workspaces easy to find and clean up later.
```

---

## Example: Investigating the Meeting App

```
I'm investigating cplace apps to build a catalog for the /building-blocks skill. Read the context in the apps catalog (use cplace_list_apps_catalog MCP tool)

Now investigate the **Meeting** app (`cf.cplace.meeting`) following this process:

## Step 1: Create Investigation Workspace

Use mcp__cplace__cplace_create_workspace:
- name: "[App Investigation] cf.cplace.meeting"

Record the workspace ID for subsequent steps.

## Step 2: Check Pre-Installation State
...
(continue with steps 2-7 as above)
```

---

## Apps Pending Investigation

See [README.md](./README.md) for the full categorized list of 70+ available apps.

**Recommended investigation order:**

1. **Start with `cf.cplace.platform`** - understand the baseline (always installed)
2. **Core building blocks** - Board, Meetings, Forms Wizard, Item List
3. **Project planning family** - Basic → Extended → Schedule Mgmt → New Gantt
4. **UI/Navigation** - Tile Navigation, Breadcrumbs, Landing Page
5. **Specialized** - as needed for specific use cases

---

## Tips for Investigation

1. **Run Steps 2-4 in parallel where possible** - use sub-agents for concurrent API calls

2. **Platform types are always present** - focus on types that are NEW after app installation

3. **Widget filtering** - the `cplace_list_widget_definitions` returns ALL widgets; filter by `requiredApp` to find app-specific widgets

4. **Dependencies matter** - document what auto-installs, as this affects workspace complexity

5. **Keep investigation workspaces** - they're useful for verifying documentation accuracy later

6. **Bulk cleanup** - search for workspaces starting with `[App Investigation]` to find all investigation workspaces