Project Workspace Skill

Use this skill when the user asks to create, open, prepare, or organize a topic-specific project workspace, or to record a meeting in an existing project. Use a customer-specific workflow for customer account operations, and a transcription workflow when the source media still needs transcription.

Default location

• When an active VS Code workspace is provided and the user is adding or organizing assets for the current task, use that workspace as the default target even without repo markers. Do not redirect it to an external project root.
• When that workspace already manages a customer's ongoing work, add requested validation evidence under the confirmed topic and link to its existing status and actions. Do not create a second project workspace or parallel task ledger unless a separate workspace is explicitly requested.
• Use the configured project root only when the user requests a separate project workspace or no active workspace target is available.
• In CLI / Scout without active-workspace context, ask for a target folder when CWD does not identify a workspace. Do not infer an external project location.
• Use Windows-style paths with backslashes.

Folder naming