takomi 2.1.29 → 2.1.30

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

@@ -11,6 +11,21 @@ Follow the blueprints precisely. Verify constantly.
 
 ---
 
+## Build Orchestration Readiness
+
+If Build is being run through an orchestration session, do not start with bare board placeholders.
+Before dispatching Build subagents, each Build task packet must include:
+- exact FR IDs and mockup files covered
+- objective and concrete scope boundaries
+- dependencies and handoff assumptions
+- expected files/artifacts
+- definition of done and verification commands
+- privacy/payment/security constraints that apply
+
+If existing Build task packets say `Scope: None specified`, `Definition Of Done: None specified`, or `Expected Artifacts: None specified`, pause and repair the task packet before launching or continuing subagents.
+
+---
+
 ## Steps
 
 ### 1. Context Loading (MANDATORY)

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

@@ -138,3 +138,11 @@ Usually recommend:
 - make decisive recommendations when the evidence is clear
 - make the output strong enough that design/build can follow without guessing
 - keep FRs and issue files aligned 1:1
+
+## Tool-Use Safety for Genesis Artifacts
+- Do not generate PRDs, coding guidelines, builder prompts, issue packs, or session docs by embedding huge markdown strings inside a single `bash` command.
+- Prefer `write` for large markdown artifacts.
+- For many repeated issue files, `write` a compact generator script first, then run that script with `bash`.
+- Use `bash` for short filesystem commands, script execution, and verification only.
+- Avoid massive inline heredocs because they can hit command-length limits and fail before writing anything.
+- If `ENAMETOOLONG` appears, immediately switch to file-based writes or a written generator script; do not retry the same oversized inline command.

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

@@ -27,6 +27,22 @@ Always-on Takomi behavior.
 - For implementation, verify before claiming completion.
 - For planning/review, produce actionable handoffs rather than vague commentary.
 
+## Large Generated Content / Bash Safety
+- Do not place large generated documents or long scripts directly inside a `bash` command.
+- If generating large content, use `write` for individual markdown/text files.
+- If many files need generated content, first `write` a small generator script to disk, then run it with a short `bash` command.
+- Keep `bash` commands short and focused on shell work: directory creation, running scripts, inspections, and verification.
+- Never use massive inline heredocs for multi-file generation; they can fail with OS command-length limits such as `ENAMETOOLONG`, especially on Windows.
+- If a command fails with `ENAMETOOLONG`, do not retry the same inline approach. Switch immediately to file-based writes or a written generator script.
+
+## Launch-Ready Orchestration Tasks
+- Never use `takomi_board` as a placeholder task generator for Design or Build stage work.
+- Before `takomi_board init_session` or `takomi_board expand_stage`, author launch-ready task packets or provide full `taskMarkdown` for every non-trivial task.
+- A launch-ready task packet must have non-empty Objective, Scope, Context, Definition of Done, Expected Artifacts, Dependencies, Verification/Review checkpoint, and exact prime-agent files to read.
+- JSON task fields are tracking metadata only; they must not replace the human-readable task packet.
+- If the subagent launch prompt is more detailed than the task packet, copy that launch prompt back into the task packet before or immediately after launch.
+- Do not move to the next lifecycle stage with `Scope: None specified`, `Definition Of Done: None specified`, or `Expected Artifacts: None specified` task files.
+
 ## Provider / Model Selection
 Before using `takomi_subagent`, setting a model override, or naming a provider/model:
 - use the injected Pi model-registry context and active Takomi routing policy

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "takomi",
-  "version": "2.1.29",
+  "version": "2.1.30",
   "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": {