/ijfw-team

name: ijfw-team
description: "Use when the user says: 'set up a team', 'create agents for', 'team for this project', 'who should work on this', or after Discovery in a project setup flow."
context: fork
model: sonnet

IJFW Team Assembly

Assembles a project-specific operating team. Team Assembly is project-agnostic: it works for software, books, content, design, research, business strategy, education, operations, and mixed projects.

Do not treat every team as a code-generation swarm. Generate the agents plus the operating contracts that let those agents coordinate around artifacts, claims, reviews, and handoffs.

CLI entry point: `ijfw team init [--archetype <type>] [--name <team-name>] [--brief <text>]`. `ijfw team` is the skill/workflow trigger; `ijfw team init` is the concrete command that writes `.ijfw/team/`, `.ijfw/agents/`, and Codex agent files.

Programmatic entry: `createTeamAssembly(projectRoot, { brief, archetype, teamName })`. When `brief` is provided and contains explicit domain signal (`book`/`novel`/`chapter`, `marketing`/`campaign`/`launch`, `research`/`paper`/`study`, `software`/`app`/`api`, etc.) the brief score outweighs filesystem-only detection. This is the wire that closes the "Receive project brief from Discovery stage" flow below.

---

How It Works

1. Receive project brief from Discovery stage (or ask for context) 2. Infer one or more project archetypes and artifact types 3. Identify the roles needed for creation, review, integration, and verification 4. Generate portable agent markdown files with proper frontmatter 5. Generate Codex custom-agent TOML when the Codex surface is present 6. Generate the team charter and workflow manifest 7. Present the proposed team and operating model for approval 8. Save approved outputs to `.ijfw/agents/`, `.codex/agents/`, and `.ijfw/team/` as applicable

---

Operating Outputs

Team Assembly 2.0 produces three coordinated surfaces:

• `.ijfw/agents/*.md` -- portable human/platform-readable agent definitions
• `.codex/agents/*.toml` -- Codex custom agents generated from the same role contracts when Codex is installed or `ijfw codex sync-agents` is run
• `.ijfw/team/charter.json` -- team roster, role contracts, phase scope, owned artifacts, reviewed artifacts, conflict rules, handoff requirements, verification responsibilities
• `.ijfw/team/workflow.json` -- project work manifest: archetypes, artifacts, owners, dependencies, waves, review graph, verification commands or rubrics

Keep `.ijfw/agents/*.md` lightweight and role-focused. Put machine-readable ownership, dependency, review, and coordination details in the charter and workflow manifest.

Codex TOML agents are platform-native projections, not a separate source of truth. Regenerate them with `ijfw codex sync-agents` after changing the team charter, and check the local Codex install with `ijfw codex doctor`.

---

Project Archetypes

Infer archetypes from the brief, repository signals, existing files, and user corrections. Support mixed projects instead of forcing one label.

Common archetypes:

• **software** -- modules, APIs, tests, config, docs
• **design** -- screens, flows, tokens, components, prototypes
• **content** -- briefs, articles, landing copy, scripts, social posts
• **book** -- chapters, outline, continuity bible, timeline, notes
• **research** -- questions, corpus, methods, evidence table, synthesis
• **business** -- strategy docs, operating plans, models, risk register
• **education** -- curriculum, lessons, assessments, rubrics
• **operations** -- SOPs, workflows, runbooks, checklists
• **mixed** -- any project-specific combination

---

Domain Templates (starting points -- always customize to the project)

Software Development

• **product-lead** (sonnet) -- requirements, user stories, acceptance criteria
• **architect** (opus, high effort) -- system design, security, data model, API design
• **senior-dev** (sonnet) -- complex implementation, patterns, code review
• **dev** (sonnet) -- feature implementation, tests, bug fixes
• **qa** (sonnet) -- test strategy, edge cases, regression testing
• **security** (opus, high effort) -- threat model, auth, data protection, pen testing
• **devops** (haiku) -- CI/CD, deployment, infrastructure, monitoring
• **docs** (haiku) -- documentation, API docs, READMEs, guides

Book / Long-Form Writing

• **story-architect** (opus, high effort) -- plot structure, pacing, arcs, tension
• **world-builder** (sonnet) -- settings, environments, atmosphere, sensory detail
• **lore-master** (haiku) -- continuity bible, rules, history, faction tracking
• **prose-stylist** (sonnet) -- voice, tone, sentence craft, genre conventions
• **continuity-editor** (haiku) -- cross-chapter consistency, timeline, character tracking
• **beta-reader** (sonnet) -- fresh-eyes review, plot holes, reader experience

Content / Marketing

• **strategist** (opus, high effort) -- campaign strategy, audience, positioning
• **copywriter** (sonnet) -- headlines, body copy, CTAs, tone of voice
• **seo-specialist** (haiku) -- keywords, structure, meta, search intent
• **editor** (sonnet) -- clarity, grammar, consistency, brand voice
• **social-media** (haiku) -- platform adaptation, hooks, engagement

Business / Strategy

• **ceo** (opus, high effort) -- vision, strategy, decision-making, priorities
• **cto** (opus, high effort) -- technical strategy, architecture, build-vs-buy
• **analyst** (sonnet) -- research, data analysis, market assessment
• **operations** (sonnet) -- process design, workflows, efficiency
• **finance** (haiku) -- budgets, projections, cost analysis

Design / Creative

• **creative-director** (opus, high effort) -- vision, aesthetic direction, brand
• **ux-designer** (sonnet) -- user flows, wireframes, usability, accessibility
• **ui-designer** (sonnet) -- visual design, components, responsive layout
• **researcher** (haiku) -- user research, competitive analysis, testing

Any Other Domain

If t