メニュー
Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | source-command-pipeline-work |
| description | Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default. |
Use this skill when the user asks to run the migrated source command work.
/work is the native Codex entry point for the Business-driven
methodology (BIZ-0001 / WF-0036). Use it to START an operation the right way —
classify the request, then create the Operation/Business work context and its
nested workflow — instead of improvising.
⚠️ Do NOT call
node ctx.mjs ...ornode cdx.mjs ...here. Those are the Antigravity (ctx) and Codex (cdx) runners — they may not even exist in a Claude-only install. From Codex always invoke the host-neutral script directly:node contextkit/tools/scripts/work.mjs <verb>.
intake first to get the Work Nature
(business vs operation), Tier, Execution Ceremony and business match. This is the
standing intake obligation from AGENTS.md.--actor human).Dry-run by default (constitution §8). A mutator (operation, approve, …)
writes nothing until you pass --apply. intake is read-only — its receipt IS
the output. Always read the receipt and act on it; never assume a write happened.
# 1. Classify the objective (read-only — returns nature/tier/ceremony/business match)
node contextkit/tools/scripts/work.mjs intake "<your objective>"
# 2a. Operation work (direct/batch): create the OP-#### context
node contextkit/tools/scripts/work.mjs operation "<title>" --intent IMPROVE # dry-run
node contextkit/tools/scripts/work.mjs operation "<title>" --intent IMPROVE --apply # write
# 2b. A workflow nests UNDER its owner (BIZ/OP) — never central [[workflow-must-nest-under-owner]]:
node contextkit/tools/scripts/workflow.mjs new <slug> --owner OP-####
# 3. Inspect / advance a Business work context
node contextkit/tools/scripts/work.mjs status --id BIZ-0001
node contextkit/tools/scripts/work.mjs approve --id BIZ-0001 --actor human --apply
intake · operation · status · approve · revise · reject · render ·
link · unlink · promote · reconcile · start · close · validate
Run node contextkit/tools/scripts/work.mjs <verb> --help style by invoking the
verb; the receipt names the next corrective step on any refusal.
intake with the user's objective; report nature / tier / ceremony / business match.OP-#### with operation (dry-run, show
the plan, then --apply once confirmed).workflow.mjs new <slug> --owner <id>./new-adr.Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
Workflow Navigator — shows the current phase, deliverables, and next commands for an ADR-0057 workflow. Read-only; never mutates state.
Start a focused session on one objective — locks scope, blocks opportunistic refactors.
Deterministic QA gate (ADR-0055) — run the project suite; green + complete acceptance criteria ⇒ qa-approve testing cards into conclusion; red ⇒ report (and qa-reject only attributable failures).
L6 — autonomous feature pipeline. Drives the full squad: design → implement → review → test → log. Checkpoints can be manual or automatic.
Swarm coordinator (ADR-0051) — pull N disjoint backlog tasks and run them as parallel, governed workstreams in isolated worktrees. Finishes at testing/; humans merge via `/swarm review`.