Docs

Captures a new requirement, opens a dedicated REQ folder, and triages whether the work follows the lightweight Mode A path or the full five-role Mode B pipeline. Every feature, fix, or enhancement enters the eng-org system through this command.

/eng-org:em-intake

Runs impact analysis with the assigned Tech Lead(s), surfaces blast radius, and produces a structured task decomposition before any development begins. Multiple TLs run in parallel when a requirement spans more than one domain.

/eng-org:tl-analyze

Authors the Technical Requirements Document — the binding contract every developer works from. The TRD is linted automatically for completeness and must carry EM approval before any developer can be dispatched. Developers may not be dispatched without an approved TRD.

/eng-org:trd

Dispatches domain developer agents against the approved plan. Tasks that have no dependencies on each other are spawned in parallel; tasks that depend on prior results are sequenced automatically. Each developer delivers a dev-report on completion.

/eng-org:tl-assign

Spawns five independent test agents in parallel — unit, integration, end-to-end, regression, and load — against the implemented tasks. Each agent is independent of the developer who wrote the code and writes its own verdict report. Any RED verdict blocks the pipeline until a fix iteration is complete.

/eng-org:run-tests

Triggers independent multi-axis review across seven specialist reviewer agents — governance, domain-validator, architecture, performance, standards, observability, and security — plus an independent GR deep-review engine. Each reviewer is independent of the developer and of each other. A BLOCK from any confirmed finding halts the pipeline.

/eng-org:run-reviews

Composites all signals from tests and reviews into a single merge-readiness verdict. The TL reads every dev-report, test report, and review report, applies all nine guardrails, and produces merge-readiness.md with a READY-FOR-MERGE, BLOCKED, or NEEDS-CHANGES status.

/eng-org:merge-readiness

Produces the one-page brief that the human approver reads before authorising merge. The summary condenses the goal, scope, file count, test signal, review signal, risk, and rollback plan into a single concise document addressed directly to the approver.

/eng-org:em-summary

Runs a dedicated architecture pass against a structured brief for a new subsystem or a batch of requirements, producing a versioned Architecture Decision Record that is independently reviewed before any code is written.

/eng-org:architect

Snapshots the pipeline board and renders a table showing every active REQ, its current pipeline stage, its program and milestone, and the single next action needed to advance it. This command is strictly read-only — it never writes or mutates any artifact.

/eng-org:status

Runs the end-to-end Mode B pipeline in sequence for one requirement, halting automatically on the first red signal and printing the exact fix command needed to unblock it. Ship orchestrates the eight existing pipeline commands — it does not reimplement any of their logic. Merge is always human-gated and is never performed by this command.

/eng-org:ship

Identifies the first missing or incomplete pipeline stage for a requirement and prints the exact command needed to unblock it. One diagnostic block, one fix command — nothing more. This command is strictly read-only.

/eng-org:why

Opens the human-gated blocker inbox and surfaces every open item in HUMAN-BLOCKERS.md that requires a person to act. This command never resolves, flips, or removes a blocker entry — that is exclusively the human approver's action.

/eng-org:blockers

Reviews a base..HEAD diff with the full reviewer discipline plus independent verification, emitting the review and a merge-readiness verdict — no pipeline required.

/eng-org:review-diff

Audits the eng-org installation in the current project — confirms every framework file is present, all agents are registered, and configuration matches what is actually on disk. Read-only.

/eng-org:doctor

Dry-runs the whole five-role pipeline on a tiny canned change to prove the wiring works end-to-end before you commit your first real requirement.

/eng-org:pilot-check

Drops the full five-role engineering framework into the current project — detects the stack and domains, then writes tailored agents, slash commands, and governance files ready to use.

/eng-org:init

Scaffolds a fresh, portable project under the eng-org registry — PRD, architecture, system-design, tech-doc, task-list, and test-plan docs, plus source and test folders and a dated decision log — and registers it so every machine can see it.

/eng-org:new-project

Pushes governance and context changes to the shared context repo so every machine stays in step. Self-skips silently when no shared repo is configured.

/eng-org:sync

Opens the fast Mode C bug-fix lane — captures a production bug, runs a safety check, writes a focused spec, and assigns a single tech lead. A lightweight path for fixes that do not need the full feature pipeline.

/eng-org:bug-intake

Runs the tech-lead-to-dev phase of the bug flow — a short root-cause analysis, one dev dispatched, and a fix delivered with a regression test that locks the bug out for good.

/eng-org:bug-fix

Runs the verification phase of the bug flow — regression and unit checks plus an independent cold review — then writes a one-page merge-readiness brief.

/eng-org:bug-verify

Draws the project's linking as living Mermaid diagrams — module and layer dependencies, domain and data-model relationships, the requirement-to-task map, and the role pipeline — so any engineer or fresh AI can see how everything connects at a glance. Idempotent: it creates the graphs if missing and refreshes them in place if present.

/eng-org:graphyfy

Starts an autonomous build-until-done program (Mode L) from a plain-language brief. Before launching, it runs a clarity scorecard to verify the brief is well-specified, interviews the user to fill any gaps, previews the milestone plan, and asks for explicit approval. The loop then drives the full pipeline autonomously across multiple milestones until all acceptance criteria are met.

/eng-org:autopilot

Executes exactly one unit of work for a running autonomous program, updates program state, and stops. Each invocation processes one pipeline stage for one requirement, so context stays fresh and goal drift is prevented. The external driver script calls this command repeatedly until the program reaches DONE, HALTED, or CHECKPOINT-WAIT.

/eng-org:autopilot-iterate

eng-org structures every engineering change through five distinct roles: EM, Tech Lead, Dev, Test, and Reviewer.

eng-org offers three modes of operation.

eng-org ships with nine binding guardrails that protect every requirement from the most common failure modes in agent-driven engineering.

The Technical Requirements Document is the contract that gates Dev dispatch.

The eng-org bench is a capability for measuring whether the framework delivers production-ready pull requests across a representative set of requirements.