Check And Next
Generated from workflows/modes/check.md, the mode contract the HELIX skill loads. Edit that file, not this page.
Use when the safe next action is ambiguous, when the user asks “what’s next” / “what’s blocked” / “plan the change”, or when a single ask straddles two or more flows declared in the marker (e.g. the prompt names a data-pipeline artifact whose blocker is an infra prerequisite).
- Inspect the requested scope, relevant governing artifacts, and known
engineering blockers. Apply
workflows/principles.md§Product goals and delivery gates. Consult work tracking only when it informs the question. - Decide conservatively among design, alignment, backfill, polish, runtime handoff, wait, guidance, or stop.
- Do not dispatch another workflow silently.
- Explain the recommended next step and its evidence; never prescribe a CLI command.
Flow disambiguation
Applies at activation (SKILL.md §Activation Discipline step 3) before any routing:
- Several distinct flows and an ambiguous verb (for example
helixandhelix-infra, prompt “plan the rollout”): resolve cwd-under-root →defaults.flow→ single entry. If none resolves, emit the disambiguation banner naming both candidate flows with their roots and ask which applies. Do not silently pick one, and do not route to the infra lane underhelixbecause the prompt contains an infra-adjacent noun. - Flows with different profiles (for example
helixassoftware-deliveryandatlasastechnology-atlas): the same chain applies. Once a flow is chosen, its profile bounds the artifact types, link kinds, and authority model; do not apply one profile’s types or authority rules to the other flow’s documents. - Several helix instances (
instance:values with different roots): if cwd lies inside exactly one root, choose it and say so; otherwise emit the banner listing instances and roots, then stop until the operator chooses.
Cross-flow ask — owner-flow first, then prerequisite fan-out
A cross-flow ask is any prompt whose answer requires consulting more than one flow in the marker. Three shapes recur:
- Single-artifact ask whose blocker lives in another flow. Example:
“The monitoring dashboard needs a DNS record. Set this up.” The
monitoring-setup artifact is owned by
helix-data(it lives underpipelines/<scope>/per the marker); the DNS record is owned byhelix-infra. The data flow is the owner-flow because it owns the artifact named in the prompt. Infra is a prerequisite-flow that must satisfy a precondition before the data-flow item ships. - Multi-flow status query. Example: “What’s blocked across the project?” / “What’s next?” against a marker with two or more flows. Every active flow in the marker is a candidate owner — none can be silently dropped.
- PRD-needs-infra ask. Example: “The PRD needs new infra — plan it.” Product owns the PRD (owner-flow); infra owns the provisioning artifact downstream. The PRD edit and the infra plan are TWO artifacts in TWO flows, linked by a cross-flow edge.
Cross-flow contract (every cross-flow ask):
- Resolve the owner flow first. Identify the flow whose
root:owns the named artifact (or the artifact the prompt’s noun phrase most directly names). Do not jump straight to the prerequisite flow because its verb (DNS, deploy, provision) appears in the prompt. The artifact’s home flow wins. - Read the owner-flow’s named upstream artifacts. From the
marker’s
root:for the owner-flow, locate and Read the artifact the prompt references (e.g.monitoring-setup.md,data-product-brief.md,prd-*.md) BEFORE proposing any action. For each upstream named inddx.links:orinformsedges that the answer depends on, Read it too. Identify the relevant intent and any unavailable content that materially changes the recommendation. Do not inventory lifecycle labels or treat missing graph edges as blockers. Treat a link with agraph:key or outside the flow as advisory unless the flow’s profile grantsgoverning; list anycontradictslinks as items for review. - Read relevant prerequisite flows. When a governing artifact identifies a prerequisite in another flow, read that flow’s scoped artifact before recommending work there. Give a next step for each flow that owns part of the requested outcome.
- For a multi-flow status query (“what’s blocked across the project?”, “what’s next?”), inspect every relevant flow listed in the marker before reporting per-flow status. Answering from generic prose alone without reading the scoped artifacts is the failure mode this rule prevents.
Answer concisely by naming the owner flow, relevant evidence, any prerequisite flow that affects the result, and the recommended next action. Mention artifact domain state when it changes that recommendation. Document lifecycle labels and stale review stamps alone never determine readiness. Recommend closing a material user-outcome gap, not normalizing status or link metadata.
Do not skip owner-flow resolution because the prompt is short or the prerequisite verb is loud. Do not collapse multiple flows into a single undifferentiated answer.
Source-Code Boundaries
Check the modularity-and-encapsulation source-code baseline in workflows/references/concern-resolution.md. Missing selection, map, or checker evidence blocks source feature readiness; recommend explicit adoption/design work. Legacy artifact validity remains separate. Check does not silently re-select concerns or edit existing adoption decisions.
UX coverage
For affected interactive UI work, apply ux-interaction-patterns and the selected component owner. Use workflows/references/ux-evidence.md: a missing STP UX Coverage map is an adoption/readiness gap, not retroactive invalidity. Require populated AC mappings and review exclusion reasons. For planning/readiness, check named planned tests, commands, component gaps and evidence capture; do not demand future passing results. For implementation/completion claims, check actual test source and observed runtime results; SDK audit evidence cannot prove interaction flows.
Innsigle seal: model-primary by HELIX
The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.
- Composition
- model-primary
- Issuer
- HELIX
helix - Signing key
ed25519:b0865d76d834a52c48506414d16f4e5a(build key)- Signed source
reference/workflow-modes/check.md- Signed
- 2026-11-16T15:52:45Z
- Content digest
sha256:9ee21802…05fc3e51
This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-11-16T15:52:45Z",
"issuer": {
"id": "helix",
"name": "HELIX",
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/helix/reference/workflow-modes/check/",
"digest": {
"alg": "sha256",
"value": "9ee218025734bee16d7ad8a11a8d245a036f6c998f16674e5fcb4fe205fc3e51"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "model-primary",
"ingredients": [
{
"kind": "model",
"name": "Claude",
"role": "draft"
},
{
"kind": "tool",
"name": "sloptimizer",
"role": "rewrite"
},
{
"kind": "human",
"name": "operator",
"role": "structure-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"alg": "ed25519",
"sig": "0HNM-FNSvOhrz3JvUFz3qAf5MdQSNEgnxCgHEv-9VbtzV2ZAtYiVZHIu2Y0OcLk7NBBLn4uq5c3dZs9bVt5qCg",
"signed_at": "2026-11-16T15:52:45Z"
}
]
}