forge-microsoft

Microsoft 365 integration — Outlook email, Teams, SharePoint, OneDrive, Planner via the m365 CLI. Scaffold only, not yet implemented.

CLAUDE.md and AGENTS.md are autogenerated by /Init (forge-init.sh). Do not edit directly — run /Update (forge-update.sh) to regenerate.

Status

Scaffold. Module structure exists but no code, hooks, or skills are implemented. All provides: capabilities are false.

Capability	Status	Planned tool
Outlook email	Not started	m365 CLI
Teams chat	Not started	m365 CLI
SharePoint/OneDrive	Not started	m365 CLI
Planner tasks	Not started	m365 CLI
Calendar	Not started	m365 CLI

Layer

Behaviour — part of forge-core's three-layer architecture (Identity / Behaviour / Knowledge). No active hooks (events: []).

Layout

forge-microsoft/
├── .claude-plugin/plugin.json    # Claude Code plugin registration
├── hooks/
│   └── hooks.json                # Empty — no active hooks
├── skills/                       # Empty — no skills yet
├── module.yaml                   # Module metadata
├── INSTALL.md                    # Installation guide
└── VERIFY.md                     # Post-install verification

Planned tool

m365 CLI — cross-platform CLI for Microsoft 365. Install via npm install -g @pnp/cli-microsoft365. Authentication uses device code flow with an Azure Entra app registration.

Path Resolution

Use Core/bin/paths.sh as the shared cross-platform path contract.

From the repository root:

eval "$(bash Core/bin/paths.sh)"

Then use the exported values (FORGE_ROOT, FORGE_USER_ROOT, SAFE_READ_CMD, SAFE_WRITE_CMD, memory paths, journal path, backlog path) instead of re-implementing path/env resolution inside skills.