ijfw-team

# 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 propose...