docs: add team and enterprise guides

docs/index.md

@@ -35,6 +35,13 @@ The modules site owns all bundle-specific deep guidance. Core CLI platform docs
 - [Project DevOps Flow](bundles/project/devops-flow/)
 - [DevOps Adapter Integration](integrations/devops-adapter-overview/)
 
+## Team And Enterprise
+
+- [Team Collaboration Setup](team-and-enterprise/team-collaboration/)
+- [Agile And Scrum Team Setup](team-and-enterprise/agile-scrum-setup/)
+- [Multi-Repo Setup](team-and-enterprise/multi-repo/)
+- [Enterprise Configuration](team-and-enterprise/enterprise-config/)
+
 ## Authoring
 
 - [Module Development](authoring/module-development/)

docs/team-and-enterprise/agile-scrum-setup.md

@@ -0,0 +1,65 @@
+---
+layout: default
+title: Agile And Scrum Team Setup
+permalink: /team-and-enterprise/agile-scrum-setup/
+redirect_from:
+  - /guides/agile-scrum-workflows/
+---
+
+# Agile And Scrum Team Setup
+
+This playbook translates the backlog and project-bundle commands into team onboarding steps for Scrum and Kanban groups.
+
+## 1. Choose the team bootstrap profile
+
+```bash
+specfact init --profile backlog-team
+specfact init ide --repo . --ide cursor
+```
+
+For API-heavy teams that also own contract workflows, move to `api-first-team` instead.
+
+## 2. Configure the team’s backlog operating model
+
+Primary ceremony commands:
+
+```bash
+specfact backlog ceremony standup github
+specfact backlog ceremony refinement github --preview --labels feature
+specfact backlog verify-readiness --adapter github --project-id owner/repo --target-items 123
+```
+
+Use standup for daily visibility, refinement for standardization, and verify-readiness before sprint commitment or release planning.
+
+## 3. Scrum setup
+
+Use Scrum when the team commits to iterations and wants readiness checks before sprint planning:
+
+- Run standup against the active sprint or iteration
+- Refine backlog items before they enter sprint planning
+- Validate readiness before commitment
+- Export persona-owned plan views when product, architecture, and development need separate edit streams
+
+## 4. Kanban setup
+
+Use Kanban when the team works from a continuous queue:
+
+- Run standup without sprint filters
+- Use refinement continuously on incoming work
+- Use readiness checks on pull-ready or release-candidate items
+- Keep unassigned work visible for pull-based planning
+
+## 5. Shared team rollout for prompts and templates
+
+Backlog refinement and standup support bundle-owned prompts and templates. Keep them aligned through installed module versions and re-bootstrap the IDE exports after upgrades:
+
+```bash
+specfact module upgrade
+specfact init ide --repo . --ide cursor --force
+```
+
+## Related
+
+- [Team Collaboration Setup](/team-and-enterprise/team-collaboration/)
+- [Backlog bundle overview](/bundles/backlog/overview/)
+- [Workflows](/workflows/)

docs/team-and-enterprise/enterprise-config.md

@@ -0,0 +1,58 @@
+---
+layout: default
+title: Enterprise Configuration
+permalink: /team-and-enterprise/enterprise-config/
+---
+
+# Enterprise Configuration
+
+This guide covers the configuration levers most relevant to enterprise rollouts: profiles, central registry policy, project-scoped bootstrap, and domain-specific overlays managed in repository configuration.
+
+## 1. Start from an enterprise profile
+
+```bash
+specfact init --profile enterprise-full-stack
+specfact init ide --repo . --ide cursor
+```
+
+This profile installs the broadest official command surface for teams that need project, backlog, code, spec, and govern flows together.
+
+## 2. Manage registries centrally
+
+Use custom registries when teams consume an internal mirror or approved company modules:
+
+```bash
+specfact module add-registry https://company.example.com/specfact/registry/index.json --id company --priority 10 --trust always
+specfact module list-registries
+```
+
+Combine this with project or workstation provisioning so teams see the same registry ordering and trust policy.
+
+## 3. Use project-scoped bootstrap for domain overlays
+
+Enterprise teams often need repository-local overlays on top of the shared company baseline. The supported approach is to keep shared module versions central while letting individual repositories bootstrap their own module root and IDE exports:
+
+```bash
+specfact module init --scope project --repo .
+specfact init ide --repo . --ide cursor --force
+```
+
+Treat those repo-local artifacts as the domain overlay layer for a given service or business unit.
+
+## 4. Keep bundle-owned resources versioned
+
+Prompts and workspace templates ship from installed bundles. Enterprise rollout should therefore version the bundles, not copied prompt files:
+
+- approve bundle versions centrally
+- upgrade with `specfact module upgrade`
+- refresh project-facing exports with `specfact init ide --force`
+
+## 5. Non-official publisher policy
+
+If the enterprise uses private or third-party registries, make the trust model explicit in automation and workstation setup. For non-official publishers, use the documented trust controls rather than bypassing the module lifecycle.
+
+## Related
+
+- [Multi-Repo Setup](/team-and-enterprise/multi-repo/)
+- [Custom registries](/authoring/custom-registries/)
+- [Module marketplace](/guides/module-marketplace/)

docs/team-and-enterprise/multi-repo.md

@@ -0,0 +1,55 @@
+---
+layout: default
+title: Multi-Repo Setup
+permalink: /team-and-enterprise/multi-repo/
+---
+
+# Multi-Repo Setup
+
+Use this guide when one team manages several repositories that share the same module stack or bundle rollout policy.
+
+## 1. Standardize the bootstrap across repos
+
+Use the same profile in each repository:
+
+```bash
+specfact init --profile enterprise-full-stack
+specfact init ide --repo . --ide cursor
+specfact module init --scope project --repo .
+```
+
+This gives each repo the same baseline while still allowing repository-local artifacts.
+
+## 2. Use `--repo` explicitly for repository-specific actions
+
+Commands that support `--repo` should point to the active repository when automation runs across several working copies:
+
+```bash
+specfact project export --repo /workspace/service-a --bundle service-a --persona architect --stdout
+specfact project import --repo /workspace/service-b --bundle service-b --persona developer --input docs/project-plans/developer.md --dry-run
+specfact project sync bridge --adapter github --mode export-only --repo /workspace/service-a --bundle service-a
+```
+
+## 3. Keep shared module rollout predictable
+
+Prompts and templates come from installed bundles, so multi-repo teams should align on:
+
+- the profile used for first bootstrap
+- the module versions promoted across repositories
+- when `specfact init ide --force` is re-run after upgrades
+
+## 4. Use repo-local overrides where needed
+
+Project-scope module bootstrap is the safe place for repo-specific behavior:
+
+```bash
+specfact module init --scope project --repo /workspace/service-a
+```
+
+Use that when one repository needs additional local artifacts without changing the user-scoped defaults for every repo on a developer workstation.
+
+## Related
+
+- [Enterprise Configuration](/team-and-enterprise/enterprise-config/)
+- [Team Collaboration Setup](/team-and-enterprise/team-collaboration/)
+- [Project bundle overview](/bundles/project/overview/)

docs/team-and-enterprise/team-collaboration.md

@@ -0,0 +1,94 @@
+---
+layout: default
+title: Team Collaboration Setup
+permalink: /team-and-enterprise/team-collaboration/
+redirect_from:
+  - /guides/team-collaboration-workflow/
+---
+
+# Team Collaboration Setup
+
+This guide is for team leads who are rolling out SpecFact across a shared repository or a small set of team-owned repositories.
+
+## 1. Bootstrap the team profile
+
+Start from a team-oriented profile instead of a solo-developer bootstrap:
+
+```bash
+specfact init --profile backlog-team
+specfact init ide --repo . --ide cursor
+```
+
+Use `backlog-team` for shared backlog and project-bundle workflows. Re-run `specfact init ide` after bundle upgrades so every developer gets the same prompt and template set from the installed modules.
+
+## 2. Initialize project-scoped module artifacts
+
+```bash
+specfact module init --scope project --repo .
+specfact project init-personas --bundle legacy-api --no-interactive
+```
+
+Use project scope when the team wants repository-local bootstrap artifacts instead of per-user defaults. `init-personas` ensures the shared bundle has the expected persona mappings before collaboration begins.
+
+## 3. Establish shared role workflows
+
+Typical role ownership:
+
+- Product Owner: backlog content, readiness, prioritization
+- Architect: constraints, contracts, deployment and risk
+- Developer: implementation details, task mapping, definition of done
+
+Export and import flows for each role:
+
+```bash
+specfact project export --bundle legacy-api --persona product-owner --output-dir docs/project-plans
+specfact project import --bundle legacy-api --persona product-owner --input docs/project-plans/product-owner.md --dry-run
+```
+
+Repeat the same pattern for `architect` and `developer`.
+
+## 4. Protect concurrent edits with locks
+
+```bash
+specfact project locks --bundle legacy-api
+specfact project lock --bundle legacy-api --section idea --persona product-owner
+```
+
+Lock high-contention sections before edits, then unlock after import. This prevents overlapping changes when several personas work in parallel.
+
+## 5. Merge branch-level bundle edits safely
+
+```bash
+specfact project merge \
+  --bundle legacy-api \
+  --base main \
+  --ours feature/product-owner-updates \
+  --theirs feature/architect-updates \
+  --persona-ours product-owner \
+  --persona-theirs architect
+```
+
+Use persona-aware merge when branches diverged on the same bundle but the changes came from different owners.
+
+## 6. Keep bundle-owned prompts and templates aligned
+
+Prompts and workspace templates are bundle-owned resources, not core-owned files. Team rollout should use installed module versions plus the supported bootstrap commands:
+
+```bash
+specfact module upgrade
+specfact init ide --repo . --ide cursor --force
+```
+
+## Recommended team cadence
+
+1. Bootstrap one repo with `backlog-team`.
+2. Initialize personas and project-scope module artifacts.
+3. Export persona views into a shared docs or planning directory.
+4. Require locks for high-contention sections.
+5. Refresh IDE resources whenever module versions change.
+
+## Related
+
+- [Agile/Scrum Team Setup](/team-and-enterprise/agile-scrum-setup/)
+- [Multi-Repo Setup](/team-and-enterprise/multi-repo/)
+- [Project bundle overview](/bundles/project/overview/)