engineering-os

# Engineering OS This skill invokes an organization defined by `os.json`. It is not the OS itself and does not install a scheduler, grant tools, or create a second backlog. Resolve this skill's real directory (follow an installation symlink). The package root is three levels above it. Run the adjacent `scripts/context.py --role <role-id>` to obtain the exact method, output schema, and host contract. Read only those files plus the issue's relevant contracts and source. 1. **Bind the mission.** Resolve the workspace, user outcome, repository/revision, canonical backlog, allowed files, budget, and existing authorization. Read applicable repository instructions. Distinguish `project-challenge` (read-only) from `bounded-issue-delivery` (an accepted issue). 2. **Select useful roles.** Start with the Engineering Director. For a project challenge, evidence research and outcome challenge can run independently; contract and issue planning consume their findings. For delivery, assign one implementer per overlapping file scope and use separate contexts/principals for review. Delegate bounded tasks to available host agents when running the requested engineering team; do not spawn all 11 roles automatically. If delegation is unavailable, label the single-host fallback and do not claim independent review. 3. **Use the real host.** If an authenticated Agentik MCP exposes this installed package and its pinned version, inspect its actual tools and use the supported workflow. Do not invent tool names, claims of installation, or successful dispatch. Otherwise use the native coding host to execute the selected role methods directly, recording that this is manual host orchestration rather than MCP execution. 4. **Preserve authority.** The host owns identity, capability grants, file isolation, tool execution, secrets, scheduling, and recovery. A role, package edge, or Markdown instruction grants none of these. Propose architecture changes to the designated human. Continue routine work within accepted contracts; do not ask again for an unchanged, already authorized action. 5. **Separate work from proof.** Emit the role's typed artifact and cite actual observations. Source, tests, deployment, reopened journey, and release are different states. A Jev judgment is advisory and cannot replace readback. Compare agentic complexity against a simpler matched baseline before recommending it as the default. 6. **Return a decision packet.** Report the result, evidence, gaps, dependency-ordered next work, and any concrete decision needed. Never merge, publish, deploy, change pricing, or perform production-destructive actions solely because this skill was invoked. For engineering-team execution, the delegating host must provide each agent a task, allowed files, revision, required artifact schema, and stop condition. Tell writers they share the codebase and must preserve others' work. Record role identities and provenance in the mission's private artifacts. Reviews of an implementation must be independent; synthesis can be performed by the coordinating host. If Jev is requested, use the user's configured TypeSafe System One connection, check it with a real typed request, and never expose its credential. Record unavailable access or exhausted credits honestly. Jev does not hold approval authority. Consult the package's `docs/JEV.md` only for this optional path.