initialize-workspace

Bootstrap per-project agent context across a VS Code multi-root workspace.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill initialize-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: initialize-workspace
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/initialize-workspace
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill initialize-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap per-project agent context across a VS Code multi-root workspace, enabling workspace-wide coordination and cross-project workflows.

Core Features & Use Cases

  • Locate the .code-workspace file and parse project folders
  • Run initialize-repo (or upgrade-repo) for each project and generate per-project context
  • Create a workspace-level overview at the workspace root
  • Ensure isolation: each project initialized independently and branch guard applied

Quick Start

Open a multi-root workspace in VS Code and run initialize-workspace to bootstrap all projects.

Frequently Asked Questions about initialize-workspace

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

FAQPage Schema
How do I bootstrap agent context across a VS Code multi-root workspace?

Bootstrapping context across a VS Code multi-root workspace involves discovering the .code-workspace file, classifying folders as projects or resources, and generating per-project agent context plus a workspace-wide overview.

What is the best way to generate a workspace-wide overview for multi-project repos?

Generating a workspace-wide overview requires classifying multi-project folders as projects or resources, initializing each independently with branch guards, and creating workspace-level documentation at the workspace root.

Can I initialize multiple projects in a multi-root workspace independently?

Yes, you can initialize multiple projects independently in a multi-root workspace. Each folder is processed individually with a branch guard applied to ensure isolation and generate specific per-project context.

Does multi-project workspace bootstrap work with existing repository upgrades?

Multi-project workspace bootstrap works with existing repository upgrades by classifying folders and running initialize-repo or upgrade-repo for each project to generate or update their respective contexts.

Why do I need a .code-workspace file to set up cross-project context?

You need a .code-workspace file to set up cross-project context because the bootstrap process discovers this file to parse multi-root workspace folders, classify them, and generate the required workspace-wide overview.