takomi 2.1.37 → 2.1.38

package/.pi/agents/orchestrator.md

@@ -106,11 +106,15 @@ Before calling `takomi_board expand_stage`:
 - Do not leave generated task files with `Scope: None specified`, `Definition Of Done: None specified`, or `Expected Artifacts: None specified`.
 - If `takomi_board` produced generic task packets, immediately repair them with detailed markdown before dispatching more work.
 
-## Phase 4: Delegation
-When delegating:
-- send self-contained task instructions
-- include required workflow and relevant context
-- preserve conversation IDs for review loops
+## Phase 4: Delegation
+After decomposition, delegation is the default execution path. Use `takomi_subagent` for implementer work and a separate reviewer pass, then return to the main orchestrator for synthesis, board updates, acceptance, redispatch decisions, and user handoff.
+
+Direct execution remains appropriate for small one-shot tasks, unavailable delegation tooling, or explicit user overrides such as "do it yourself", "no subagents", "no new threads", or `/takomi subagents off`.
+
+When delegating:
+- send self-contained task instructions
+- include required workflow and relevant context
+- preserve conversation IDs for review loops
 - keep retries scoped and actionable
 - do not overload a subagent with unrelated work
 

package/.pi/prompts/takomi-prompt.md

@@ -16,9 +16,11 @@ Always-on Takomi behavior.
 - Do not blend architecture, design, and implementation sloppily.
 - When the right path is clear, make a recommendation instead of hedging.
 - For broad work, Genesis may create the orchestration session that carries work into later stages.
-- Orchestration sessions use canonical timestamp IDs: `orch-YYYYMMDD-HHMMSS`.
-- Orchestration sessions are markdown-first: author `master_plan.md` and task packets first, then call `takomi_board` with the same `sessionId`, `masterPlanMarkdown`, task `taskMarkdown`, and matching task statuses. Do not create a second board session for already-authored session docs.
-- `takomi_board` never runs subagents. Use `takomi_subagent` for execution, then come back to `takomi_board update_task` to record results.
+- Orchestration sessions use canonical timestamp IDs: `orch-YYYYMMDD-HHMMSS`.
+- Orchestration sessions are markdown-first: author `master_plan.md` and task packets first, then call `takomi_board` with the same `sessionId`, `masterPlanMarkdown`, task `taskMarkdown`, and matching task statuses. Do not create a second board session for already-authored session docs.
+- `takomi_board` never runs subagents. Use `takomi_subagent` for execution, then come back to `takomi_board update_task` to record results.
+- When Takomi creates subtasks, roadbook tasks, or an orchestration session, delegation is the default next step: implementer `takomi_subagent`, reviewer `takomi_subagent`, then main-agent synthesis and board update.
+- Preserve direct execution for small clear work and explicit user overrides such as "do it yourself", "no subagents", "no new threads", or `/takomi subagents off`.
 
 ## Shared Mode Pattern
 - Load context before acting.
@@ -57,5 +59,5 @@ Before using `takomi_subagent`, setting a model override, or naming a provider/m
 - Design for sitemap, design system, mockups, and visual direction
 - Build for implementation, verification, and handoff
 - Review for audits, QA, or high-risk changes
-- Orchestration for broad, multi-step, or delegated work
+- Orchestration for broad, multi-step, or delegated work
 

package/.pi/takomi/policies/subagent-routing.md

@@ -1,6 +1,14 @@
 # Subagent Routing Policy
 
-Use subagents when delegation reduces risk, improves parallelism, or provides specialist review. Do not delegate small direct tasks just because the tool exists.
+Once Takomi decomposes work into subtasks, roadbook tasks, or an orchestration session, use subagents by default. The main agent should coordinate, synthesize, update the board, and hand off to the user rather than acting as the primary implementer.
+
+Do not delegate small direct tasks just because the tool exists. Direct execution is also allowed when the user says "do it yourself", "no subagents", "no new threads", disables subagents with `/takomi subagents off`, or the required delegation tooling is unavailable.
+
+Default decomposed-work loop:
+
+1. Send implementation to an implementer `takomi_subagent`.
+2. Send the result to a separate reviewer `takomi_subagent`.
+3. Let the main orchestrator synthesize, update the roadbook/board, and accept or redispatch.
 
 Before calling `takomi_subagent`:
 

package/.pi/takomi/policies/takomi-lifecycle-routing.md

@@ -2,6 +2,8 @@
 
 Default to direct execution for small, clear tasks. Use Takomi lifecycle when scope is large, unclear, risky, multi-file, architecture-heavy, or benefits from durable artifacts.
 
+When lifecycle routing creates subtasks, roadbook tasks, or an orchestration session, execution becomes delegation-first by default. The main agent remains responsible for context, sequencing, synthesis, board updates, acceptance, redispatch, and final user handoff.
+
 Lifecycle:
 
 1. Genesis: mission, constraints, requirements, issues, verification foundation.
@@ -9,4 +11,4 @@ Lifecycle:
 3. Build: focused implementation tasks with verification.
 4. Review/Finalize: regression, quality, docs, handoff.
 
-Broad/meta-system projects must be decomposed into meaningful tasks. A single-task Genesis requires explicit justification.
+Broad/meta-system projects must be decomposed into meaningful tasks. Decomposed broad work should not be executed primarily by the parent agent unless the user explicitly says "do it yourself", "no subagents", "no new threads", or otherwise opts out. A single-task Genesis requires explicit justification.

package/README.md

@@ -115,17 +115,25 @@ run vibe genesis
 continue build with takomi
 ```
 
-Install the Takomi protocol suite:
-
-```bash
-npx -y skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill takomi
-```
-
-Original Takomi-authored skills in this bundle include `21st-dev-components`, `takomi`, `global-brand-namer`, `jstar-reviewer`, and the core VibeCode/Takomi workflow skills that ship with the CLI.
-
----
-
-## 📦 Skill Ecosystem
+Install the Takomi protocol suite:
+
+```bash
+npx -y skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill takomi
+```
+
+Original Takomi-authored skills in this bundle include `21st-dev-components`, `takomi`, `global-brand-namer`, `jstar-reviewer`, and the core VibeCode/Takomi workflow skills that ship with the CLI.
+
+### Codex Plugin Quick Start
+
+For the newer repo-local Codex plugin path, enable `takomi-codex` from `.agents/plugins/marketplace.json`. That marketplace entry points Codex at `./plugins/takomi-codex`, which includes plugin metadata, the `takomi-codex` skill, and local verification scripts.
+
+This plugin path is distinct from `skills add --skill takomi`, which installs the older global Takomi skill. Use natural language such as `use takomi-codex to inspect this repo`, `use Takomi to plan this feature`, or `create a Takomi roadbook for this work`.
+
+See [Takomi Codex Onboarding](docs/takomi-codex-onboarding.md) for activation, first-run verification, policy loading, roadbooks, dry-run dispatch, no-Pi fallback, and troubleshooting.
+
+---
+
+## 📦 Skill Ecosystem
 
 Think of skills as specialized team members you can summon on demand. From security audits to AI video generation — there's a skill for that.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "takomi",
-  "version": "2.1.37",
+  "version": "2.1.38",
   "description": "🎯 Stop wrestling with AI. Start building with purpose. The artisan's toolkit for agent workflows, Codex skills, and original Takomi capabilities like 21st.dev integration.",
   "type": "module",
   "bin": {