From 7b05d07af6c1d38a1f707dab9b43ae2e143a9d7b Mon Sep 17 00:00:00 2001
From: Jay Patel
- Build the right Codex agent team for this repository and goal. + Turn your project and goal into the smallest useful Codex agent team.
- Codesemble audits bounded project evidence, generates only the specialists - your work needs, and shows every project-local change before applying it. + Codesemble audits your project, proposes the specialists it needs, and gives + you an exact preview, human approval, and rollback.
Quick start · How it works · - Safety · + Safety · Documentation
@@ -26,190 +26,153 @@ ## Why Codesemble? -- **Project-specific** — agents are derived from your repository and intended outcome. -- **Small by design** — every proposed role must cover justified project work. -- **Native and reversible** — Codesemble configures Codex project files with exact preview, Doctor, and rollback support. +- **Understands the project** — recommendations come from repository evidence and your goal. +- **Builds only justified roles** — no fixed team, no role padding, no team to design by hand. +- **Keeps changes reviewable** — project-local setup is previewed before apply and can be rolled back. -Codesemble is an open-source, repository-aware team builder for native Codex -multi-agent orchestration. It configures Codex; it does not replace the Codex -runtime. +Codesemble is for builders and teams who want useful specialists without +maintaining a multi-agent framework. It configures native Codex project files; +it does not replace Codex. ## Quick start -### Install the v0.2 candidate +### 1. Install, then restart Codex ```bash codex plugin marketplace add VAMFI/codsemble --ref fc247152961c25e79b525a969806991f499a2bac codex plugin add codsemble@codsemble ``` -The pinned commit is the merged, validated v0.2 candidate. Start a fresh Codex -session after installation so the plugin skills are discovered. +Open a fresh Codex session so its four Codesemble skills are discovered. The +pinned commit is the merged, validated v0.2 candidate. -### Build your team +### 2. Audit, choose, and approve ```text -$codsemble:initialize-team Build the recommended Codex team for this workspace. +$codsemble:initialize-team Audit this workspace and help me choose the smallest useful team. ``` -Codesemble audits the workspace and presents Focused, Recommended, and Extended -options. It prepares a side-effect-free exact plan before writing any project -file. +Codesemble presents Focused, Recommended, and Extended options, then shows the +exact project files and configuration diff. Choose an apply-capable mode if you +want changes: a preview-only plan is read-only and cannot later be applied. -### Use your agents +Nothing is written until you approve the exact current plan with its +confirmation ID or complete six-word voice challenge. -After you approve and apply the team, work normally in the primary Codex thread: +### 3. Restart and give the team a goal + +After apply, open another fresh Codex session so the generated agents are +discovered. You continue working through the primary thread: ```text -Review the checkout flow, fix the highest-risk issue, and validate the result. +You → primary Codex thread → bounded specialists → primary integrates and reports ``` -Start another fresh Codex session after apply or configuration changes so the -generated project agents are discovered. - -The primary agent remains user-facing and accountable. Project-local -orchestration guidance delegates bounded, separable work to installed -specialists when useful, reconciles their evidence, and keeps final decisions -with the primary thread. - -Installed roles are available capabilities, not always-running processes. The -project worker ceiling limits simultaneous spawned workers, excludes the primary -thread, and is independent of installed role count. - -### Keep the team healthy - ```text -$codsemble:update-team Re-audit this workspace and preview team changes. -$codsemble:team-doctor Check this project's generated team and configuration. -$codsemble:rollback-team Preview rollback of the latest Codesemble transaction. +Use the installed specialists where useful to review the checkout flow, fix the +highest-risk issue, and validate the result. ``` -[Open the step-by-step guide →](docs/USAGE.md) +Specialists run only when the primary delegates separable work; they are not +always running. The primary remains accountable for decisions and final claims. -> **You stay in control.** Audit and preview are read-only. Codesemble writes -> project files only after you approve the exact current plan, refuses stale or -> changed plans, preserves transaction history, and previews rollback before -> restoring managed files. It does not change personal Codex settings or -> publish anything. +Maintain the team with +[`$codsemble:update-team`](docs/USAGE.md#update-a-team), +[`$codsemble:team-doctor`](docs/USAGE.md#diagnose), and +[`$codsemble:rollback-team`](docs/USAGE.md#roll-back). ## How it works ```text -Repository evidence + your goal → Work Packages → Project team → Preview → Apply +Project evidence + your goal → required work → project team → preview → apply ``` -1. **Audit** bounded, typed project signals locally. -2. **Compile** the capabilities and separable work the goal requires. -3. **Generate** evidence-backed Focused, Recommended, and Extended teams. -4. **Preview** every role, sandbox, instruction, and configuration change. -5. **Apply** only the exact fresh plan you confirm, with Doctor and rollback support. +1. **Audit** project signals locally. +2. **Compile** required work into evidence-backed team options. +3. **Preview and apply** only the exact fresh plan you confirm. -### Example output +For example: ```text -Repository evidence +Project evidence GitHub Actions + delivery goal + security requirement Recommended Codex team - Delivery specialist owns the delivery Work Package + Delivery specialist owns the delivery work Security specialist reviews the security boundary - Independent validator verifies the high-risk delivery path + Independent validator verifies the high-risk path Spawned-worker ceiling: 4 ``` -The names and number of agents change with the repository evidence and confirmed -goal. Codesemble explains the evidence and Work Package behind every generated -role before apply. - -[Read the compiler contract →](docs/PROJECT_CAPABILITY_COMPILER.md) · -[See the architecture →](docs/ARCHITECTURE.md) - -## Dynamic teams, not 111 installed agents +The names and number of agents change with the project and goal. Codesemble +explains why every role is present before apply. -Codesemble does not install a fixed team of 111 agents. +### Why 111 does not mean 111 agents -The current 111-entry catalog is a reusable primitive library—not a roster, -recommendation ceiling, team-size target, or concurrency limit. For each -workspace, the compiler derives Work Packages from bounded evidence and explicit -goals, then generates only justified project-specific roles. +The 111-entry catalog is a library of reusable capability primitives—not a team +size, recommendation ceiling, or concurrency limit. Codesemble generates only +the roles justified by the current project: **Focused** covers required work, +**Recommended** adds independent verification only for high-risk required work, +and **Extended** adds only closed-rule optional lifecycle work; it may equal +Recommended. -- **Focused** is the smallest complete team covering required Work Packages. -- **Recommended** adds independent verification only for evidenced high-risk work. -- **Extended** adds only closed-rule, evidence-backed optional lifecycle work and may equal Recommended. +Installed roles and concurrent workers are separate. A project can install 12 +useful specialists while allowing only 4 workers to run at once; the primary +thread is not counted in that worker ceiling. -Catalog size, installed roles, and active workers remain separate. A project may -install 12 useful specialists while allowing only 4 workers to run concurrently. - -[Explore the primitive library →](docs/ROLE_CATALOG.md) · -[See the bounded comparison →](docs/USEFULNESS_COMPARISON.md) - -## Who is it for? - -- **Solo builders** who want useful specialists without designing a team by hand. -- **Maintainers** who need reviewable, reversible project configuration. -- **Product teams** whose work spans engineering, testing, design, docs, growth, or operations. -- **Organizations** that want project-local defaults without silently changing personal Codex settings. +[Read the compiler contract →](docs/PROJECT_CAPABILITY_COMPILER.md) · +[Explore the primitive library →](docs/ROLE_CATALOG.md) -## What can it create? +## What it creates ```text AGENTS.md bounded orchestration guidance .codex/agents/