メニュー
The DevPipeline manager - production board for bugs, increments, chores and roadmap tasks (backlog -> testing -> conclusion).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
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.
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.
| name | source-command-pipeline-pipeline |
| description | The DevPipeline manager - production board for bugs, increments, chores and roadmap tasks (backlog -> testing -> conclusion). |
Use this skill when the user asks to run the migrated source command pipeline.
The execution control panel, distinct from the product roadmap. The roadmap
(contextkit/memory/roadmap.md) is the product/business plan. The DevPipeline is
how work actually flows: bugs, increments, chores, and roadmap items broken into
tasks, each with priority + SLA, moving through backlog -> working -> testing -> conclusion. Tasks are files under contextkit/pipeline/<stage>/;
devpipeline.md is the generated dashboard.
Act as the manager of this board based on $ARGUMENTS:
node contextkit/tools/scripts/pipeline.mjs board --digest. Open the full
contextkit/pipeline/devpipeline.md only when the digest is not enough.node contextkit/tools/scripts/pipeline.mjs add --type <bug|feature|increment|chore> \
--priority <P0-P3> --title "..." [--sla YYYY-MM-DD] [--roadmap P2.3] \
[--workflow <slug>] [--spec contextkit/memory/workflows/<slug>/spec.md]
node contextkit/tools/scripts/complexity-rubric.mjs classify "<objective>"
and pass --complexity only when the automatic classification needs an
explicit override.
Then open the new file in contextkit/pipeline/backlog/ and fill the context
and acceptance criteria. For non-trivial workflow work (ADR-0057), pass
--workflow and --spec; the card will include spec references,
implementation report, diff summary, and verification sections.node contextkit/tools/scripts/pipeline.mjs move <id> <backlog|working|testing|conclusion>.
Moving a card to testing stamps implemented: YYYY-MM-DD. Moving to
conclusion stamps concluded: YYYY-MM-DD; QA closure should still prefer
qa-approve through /pipetest.contextkit/memory/roadmap.md, pick the next milestone,
and break it into concrete backlog tasks with --roadmap <P-ID>.Always run sync after changes so devpipeline.md reflects reality. Treat
P0/SLA items as the priority. The workflow spec pack references this board; it
does not replace it.