biz-ops-setup · git:20261028.2e43893 · 2026-10-28 · sha256 6250951939e62d2f
biz-ops-setup git:20261028.2e43893A
Immutable. This exact content never changes and is served at /api/v1/blob/6250951939e62d2f.
---
name: biz-ops-setup
description: "Set up or operate a business operations workspace for activity reports, tasks, and customer routing; workIQ is optional. Use when initializing BizOps, processing ongoing business updates, reviewing reports or tasks, tracking upcoming-event reminders and post-event follow-ups, or preparing an operations handoff. Triggers: business-operations-workspace, BizOps, 業務管理ワークスペース, レポート管理, タスク管理, リマインド, 業務引き継ぎ."
argument-hint: "作りたい業務ワークスペース、必要機能、管理したい対象"
user-invocable: true
license: CC BY-NC-SA 4.0
metadata:
author: yamapan (https://github.com/aktsmm)
---
# Biz-Ops Workspace
Set up or operate a business operations workspace with reporting and task management.
## When to Use
- Creating a new business operations workspace with optional workIQ integration.
- Operating an existing workspace: classifying updates, maintaining tasks, and generating reports.
- Reviewing current activity, missing reports, open tasks, or a handoff.
## Choose a Mode
Inspect the target before acting. `DASHBOARD.md` together with `Tasks/` or `ActivityReport/` identifies an existing BizOps workspace. Other managed content or partial structure requires confirmation; never initialize over a different workspace or infer BizOps from a single shared folder.
| Mode | Use when | First action |
| ---------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Setup | A new, explicitly chosen target has no managed structure | Interview and initialize the workspace. |
| Operate | New activity, task, or report request in an existing workspace | Read the relevant records and source evidence before updating. |
| Review / Handoff | Status, missing work, or continuity is requested | Read the dashboard, active tasks, report index, and relevant customer records. |
Never rerun the initialization or template deployment scripts during Operate or Review. Template deployment can rewrite customer mappings in an existing agent file even when other files are skipped. Add missing assets only when requested and after checking existing content.
## Prerequisites
| Item | Required | Description |
| ------------------------ | -------- | ----------------------- |
| VS Code + GitHub Copilot | Yes | Agent execution |
| Git + PowerShell 7+ | Yes | Version control/scripts |
| workIQ MCP Server | Optional | M365 integration |
## Setup Flow (New Workspace Only)
```
Interview → Folder Structure → Deploy Agents → Customer Workspaces → Config → Done
```
## Phase 1: Interview (MANDATORY)
Collect the following information:
1. **Customer list**: Name, ID, primary contact
2. **External folders**: Tech QA, Blog, OneDrive paths (optional)
3. **Holiday config**: japan / us / other
4. **workIQ availability**: Yes (M365 auto) / No (manual input)
> Run `Get-Date` before generating reports; do not infer today's date.
## Phase 2-5: Setup Execution
**Recommended: Use scripts**
```powershell
# Phase 2: Create folder structure
.\scripts\Initialize-BizOpsWorkspace.ps1 -WorkspacePath "<workspace-path>" -Customers @("contoso")
# Phase 3: Deploy agents and report skills
.\scripts\Deploy-BizOpsTemplates.ps1 -WorkspacePath "<workspace-path>"
```
**Manual setup** → [references/setup-phases.md](references/setup-phases.md)
## Deployed Components
| Type | Count | Examples |
| ------- | ----- | ----------------------------------------------------------------- |
| Agents | 9 | orchestrator, report-generator, task-manager, availability-finder |
| Skills | 4 | daily-report, weekly-report, monthly-report, review-report |
| Folders | 7 | ActivityReport/, Customers/, Tasks/, \_inbox/ |
## Operate an Existing Workspace
| Input | Canonical record and action |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New activity | Store the source once: confirmed customer items in `Customers/{id}/_inbox/`, confirmed internal items in `_internal/_inbox/`, and unresolved items in `_inbox/`; link from summaries instead of copying it. |
| Task update | Keep `Tasks/active.md` or `Tasks/completed.md` as the overall index; link to details in `Customers/{id}/tasks.md` for confirmed customer tasks, and sync both task records and `DASHBOARD.md` together. |
| Daily, weekly, or monthly report | Invoke the matching deployed report skill; it dispatches the complete report contract and user arguments to the configured report-generator, preserving evidence gates and independent review. |
| Ambiguous customer or project association | Keep the original input unclassified and ask for confirmation before creating a customer or project folder. |
| Meeting transcript, VTT, or AI note; a manager's goal or evaluation guidance | Verify the file belongs to the target meeting and mark AI-note-only items provisional; record goal axes once as a workspace instruction and store the official role definition verbatim. Details: [references/meeting-and-goal-inputs.md](references/meeting-and-goal-inputs.md). |
| Dated future event (meeting, visit, deadline), or a request for reminders or "how did it go" checks | Register it in the upcoming-events ledger without waiting to be asked; a scheduled read-only run reminds before and researches results after. Details: [references/upcoming-events.md](references/upcoming-events.md). |
Use the deployed task-manager, data-collector, and report-generator for their respective workflows. Keep original evidence authoritative; reports and indexes summarize or link instead of copying source content. workIQ is optional and missing data is not evidence of no activity. `Customers/{id}/` is a lightweight BizOps record, not a full per-customer workspace; do not run any other workspace initializer (such as a dedicated customer workspace setup) inside it. Link to a separately managed customer workspace when one exists. Do not treat a customer project thread as a separate project workspace unless the user explicitly requests one.
- Select external rechecks from current owner-relevant actions, due dates, and changed evidence or restart conditions. Do not reopen completed details or expand unchanged blocked items into queries; count candidates and actual calls separately.
- Retain original query/response evidence and its acquisition time. Saving or copying evidence is not a new query; unknown acquisition time must stay explicit.
- Derived views (summaries, dashboards, status tables) go stale silently. When a source record changes, including a new ledger row or a decision stated in chat, update every derived view in the same turn. Before answering from a view, compare the sources' modification times with the view's last-updated stamp, and reconcile the sources first when they are newer.
- Where independent review is required, retain a separate reviewer's original verdict against the exact artifact version. Producer self-assessment or validation PASS is not approval; quality approval does not make incomplete data complete. Substantive post-review changes require another review.
## Review / Handoff
Read `DASHBOARD.md`, `Tasks/active.md`, recent `ActivityReport/` entries, and only relevant `Customers/` records. Report the source of the current status, owner, next action, and any unavailable or unconfirmed information; do not fill gaps by rerunning setup.
## Done Criteria
- Setup: folders, agents, four report skills with contracts/licenses, mappings, daily activity roots, and report preflight are verified without replacing existing records (see [agent list](references/agent-list.md)).
- Operate: the owning task or activity record and relevant index reflect the input; reports identify their evidence and any unavailable sources.
- Review / Handoff: the current status, owner, next action, and unresolved questions are traceable to existing records.
## Key References
| Topic | Reference |
| ---------------- | ---------------------------------------------------------------------------------- |
| Setup Phases | [references/setup-phases.md](references/setup-phases.md) |
| Folder Structure | [references/folder-structure.md](references/folder-structure.md) |
| Agent List | [references/agent-list.md](references/agent-list.md) |
| Holidays | [references/holidays.md](references/holidays.md) |
| Daily Evidence | [references/daily-activity-collection.md](references/daily-activity-collection.md) |
| Data Sources | [references/external-datasources.md](references/external-datasources.md) |
| Meeting / Goal | [references/meeting-and-goal-inputs.md](references/meeting-and-goal-inputs.md) |
| Upcoming Events | [references/upcoming-events.md](references/upcoming-events.md) |