Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Playbook GuideNew to Visual Studio Code? Get it now.
Playbook Guide

Playbook Guide

Anusha Meka

|
7 installs
| (0) | Free
Initialize and maintain Modern AI Playbook files in any repository.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Playbook Guide VS Code Extension

Playbook Guide helps engineers bootstrap and validate a Modern AI Playbook setup in any repository.

Quick Start

After installing from the VS Code Marketplace:

  1. Open a repository folder in VS Code.
  2. Open Command Palette (Ctrl+Shift+P).
  3. Run Playbook Guide: Daily Start.
  4. Run Playbook Guide: Validate Agent Setup.
  5. Run Playbook Guide: Run Full Setup Sequence (optional, executes tool/setup commands).

Playbook Guide: Initialize Project is optional and available as a manual fallback.

The extension creates and maintains:

  • .github/agents/playbook-guide.agent.md
  • AGENTS.md
  • memory-bridge.md

Use Playbook Guide: Update Memory Bridge at the end of each session to capture decisions and next steps.

Command Output (Actual Extension Behavior)

This extension manages workspace files and guidance. It can also execute a full setup sequence when you run Playbook Guide: Run Full Setup Sequence.

Typical outputs users will see:

  • Playbook Guide auto-setup completed for this workspace.
  • Playbook Guide initialized. Created: X, Updated: Y.
  • Daily start ready: review memory bridge, define a plan, then start implementation.
  • Playbook Guide setup looks good.

Validate Agent Setup checks these files:

  • .github/agents/playbook-guide.agent.md
  • AGENTS.md
  • memory-bridge.md

If checks fail, details are shown in the Playbook Guide output channel.

Run Full Setup Sequence executes setup flow steps and prints a status table in the Playbook Guide output channel. It checks and/or attempts:

  1. Prerequisites (git, node, npm, code)
  2. Optional repository clone (or use current workspace)
  3. Copilot CLI check and install attempt
  4. Dependency install (npm install) when package.json exists
  5. Test run (npm test) when package.json exists
  6. Starts Copilot CLI and sends /login

Automation boundaries:

  • Browser-based authentication still requires user confirmation.
  • External installs may fail due to org policy, admin permissions, or restricted shell access.
  • Opening the cloned repository in a new VS Code window is prompted for confirmation.
  • Agency CLI installation is intentionally excluded from the public marketplace extension.

Commands

  • Playbook Guide: Initialize Project
  • Playbook Guide: Daily Start
  • Playbook Guide: Update Memory Bridge
  • Playbook Guide: Validate Agent Setup
  • Playbook Guide: Run Full Setup Sequence

What it creates

  • .github/agents/playbook-guide.agent.md
  • AGENTS.md
  • memory-bridge.md

The extension is idempotent and avoids destructive overwrites.

Development

npm install
npm run compile

Press F5 in VS Code to launch an Extension Development Host.

Package

npm run package:vsix

Publish

npx vsce login <publisher-name>
npm run publish:patch

You need a VS Code Marketplace publisher and PAT.

Local Install

In VS Code:

  1. Open Extensions view
  2. Select the menu in the top-right corner
  3. Choose Install from VSIX...
  4. Pick the generated .vsix file
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft