Skip to content

FCC for Teams

Welcome to the For Teams section of the FCC Agent Team Framework documentation. This area is written for the people who decide how a team uses FCC together: team leads, engineering managers, tech leads, staff engineers, program managers, and anyone running a multi-person workflow that needs persona-aware orchestration, shared governance, and collective knowledge.

If you are here as an individual contributor, you may want to start with the For Beginners section or the Getting Started guide instead. If you are evaluating FCC for your organization, see For Decision Makers first.

Who This Section Is For

Your role

This section assumes you are responsible for one of the following:

  • Defining how 3-30 engineers collaborate around FCC-driven workflows
  • Standing up shared governance (quality gates, constitutions, compliance review)
  • Managing persona coverage across multiple squads, chapters, or tribes
  • Coordinating documentation, release management, or cross-team handoffs
  • Running incident response, architecture review, or sprint rituals that benefit from persona orchestration

If any of those fit, the eight guides in this section will help you move from "I installed FCC" to "our team uses FCC as a first-class collaboration substrate."

Overview of Team-Specific Content

The For Teams section covers the team-centric concerns that do not fit neatly into per-persona documentation or individual tutorials. You will find workflow templates, governance patterns, scaling advice, and shared-knowledge strategies.

Guide Primary Audience When to Read
Downstream Adoption Guide Senior engineers, architects Integrating FCC into an existing codebase
Team Workflow Templates Tech leads, scrum masters Designing repeatable multi-persona workflows
Multi-Team Governance Engineering managers, staff engineers Coordinating across 2+ teams
Team Scaling Guide Engineering directors, VPs Growing a team from seed to 50+ engineers
Shared Knowledge Base Knowledge managers, tech leads Building team-level RAG and KG systems

Each guide assumes you have already read the Getting Started guide and have a working FCC installation. If you have not yet installed the package, begin with the Quick Start before returning here.

Quick-Start for Team Adoption

Adopting FCC as a team is a five-step process. Most teams complete it in one or two working weeks.

Step 1: Identify Your Team Archetype

Look at your team's primary output. Is it software features? Documentation? Research deliverables? Compliance artifacts? A mix? Your archetype determines which personas you need and which workflows you will run most often.

Common team archetypes

  • Product team (6-12 people): builds customer-facing features
  • Platform team (4-8 people): provides shared infrastructure
  • Research team (3-6 people): produces analyses, white papers, models
  • Governance team (2-4 people): compliance, audit, policy
  • Documentation team (2-5 people): guides, API docs, books
  • Hybrid team (8-20 people): spans multiple archetypes

Step 2: Select Your Starter Persona Roster

Every team needs a core roster of 5-8 personas that cover the recurring responsibilities in your day-to-day work. You can always add more later, but starting small prevents overwhelm.

from fcc.api import PersonaRegistry

registry = PersonaRegistry.load_default()

# Example starter roster for a product team
roster = [
    registry.get("RC"),   # Research Crafter - requirements analysis
    registry.get("BC"),   # Blueprint Crafter - design and architecture
    registry.get("BV"),   # Blueprint Validator - design review
    registry.get("DE"),   # Documentation Evangelist - team docs
    registry.get("CO"),   # Collaboration Orchestrator - handoffs
    registry.get("GCA"),  # Governance Compliance Auditor - gates
]

for persona in roster:
    print(f"{persona.persona_id}: {persona.role_title}")

Step 3: Pick Your First Workflow Template

Do not try to boil the ocean. Pick one recurring team ritual, template it with FCC, and run it for two weeks before adding a second. See Team Workflow Templates for 7 ready-to-use patterns.

Step 4: Establish Lightweight Governance

You need at least three governance decisions before your team workflows generate useful output:

  1. Quality gate thresholds -- what scores mean "approved" vs "needs revision"
  2. Handoff protocol -- how personas/humans pass work between stages
  3. Escalation path -- who resolves disagreement between personas

Multi-Team Governance provides RACI templates and decision frameworks.

Step 5: Instrument and Iterate

Turn on the event bus, capture traces of your first few workflow runs, and hold a team retrospective. The observability layer gives you metrics on stage duration, handoff quality, and score distributions so you can tune the workflow before scaling it.

Decision Tree: If Your Team Is X, Start With Y

Use this tree to pick your first guide to read after this index page.

flowchart TD
    Start([What does your team need most?]) --> Adopt{Adopting FCC<br/>for the first time?}
    Adopt -->|Yes| Size{Team size?}
    Adopt -->|No, already using FCC| Need{What is missing?}

    Size -->|1-5 people| Small[Team Workflow Templates<br/>pick 1-2 patterns]
    Size -->|6-15 people| Mid[Downstream Adoption Guide<br/>then Workflow Templates]
    Size -->|16+ people| Large[Team Scaling Guide<br/>then Multi-Team Governance]

    Need -->|Coordination across teams| Gov[Multi-Team Governance]
    Need -->|Shared docs and search| KB[Shared Knowledge Base]
    Need -->|Growing fast| Scale[Team Scaling Guide]
    Need -->|New integration| Adopt2[Downstream Adoption Guide]

    classDef start fill:#e1f5ff,stroke:#0277bd,stroke-width:2px;
    classDef decision fill:#fff9c4,stroke:#f57f17,stroke-width:2px;
    classDef result fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px;
    class Start start;
    class Adopt,Size,Need decision;
    class Small,Mid,Large,Gov,KB,Scale,Adopt2 result;

Team Maturity Model

As your team adopts FCC, you will progress through four maturity stages. Use this model to set expectations and plan investment.

Stage Signals Typical Duration Next Investment
Exploring 1-2 engineers running demos, no shared workflow 1-4 weeks Pick a starter workflow template
Piloting 1 workflow running for 1 team, manual oversight 4-12 weeks Add event bus instrumentation
Operating 3+ workflows, automated gates, runbooks exist 3-9 months Standardize governance, add RAG
Scaling Multi-team adoption, federation, cross-team KG 9+ months Multi-team governance, scaling guide

Do not skip stages

Teams that jump from "Exploring" to "Scaling" in under six months usually end up with brittle workflows, inconsistent governance, and persona rosters nobody remembers. Take each stage seriously.

Common Team Questions

How do we pick which personas our team owns vs shares?

A persona is owned by your team if you run it more than once a week and adapt its constitution to your domain. A persona is shared (used but not owned) if you invoke it occasionally with default configuration. See Multi-Team Governance for the shared responsibility matrix.

Should every engineer be able to run every persona?

For small teams (under 10), yes -- the overhead of gating access is not worth it. For larger teams, scope access by role and workflow stage. The collaboration engine supports participant roles with scoped permissions.

How do we keep workflow templates from drifting between squads?

Store templates in a shared repository under version control, reference them by git SHA in per-squad configs, and run Blueprint Validator (BV) on template changes. The Multi-Team Governance guide has concrete patterns.

Do we need the compliance module if we are a small team?

If you handle personal data, healthcare data, financial data, or deploy models in the EU, yes. Otherwise, defer it until you have over 10 engineers or your first formal customer audit. See For Professionals: AI Compliance for the decision criteria.

How does FCC fit with our existing Scrum / Kanban / SAFe process?

FCC does not replace your agile framework -- it augments the artifacts produced within it. Use persona-driven workflows to generate the inputs (backlogs, design docs, retros) that your existing ceremonies consume. See the Scrum Master persona and SAFe Metrics Crafter for framework-aware personas.

Next Steps

Pick one of the following based on your immediate need:

  1. Starting fresh? Read Downstream Adoption Guide end-to-end.
  2. Need workflow patterns? Jump to Team Workflow Templates.
  3. Coordinating multiple teams? Go to Multi-Team Governance.
  4. Growing quickly? Read Team Scaling Guide.
  5. Building a team knowledge hub? See Shared Knowledge Base.

After you finish your chosen guide, return here to pick a second. Most teams read 3-4 guides in their first month of FCC adoption.