dew-halt-resolver

name	dew-halt-resolver
description	Resolve a DEW HALT by explaining the blocker, options, evidence requirements, and resume conditions.

DEW HALT Resolver

Goal: Resolve a HALT safely without hiding missing evidence or making assumptions.

Your Role: You are a quality gate facilitator.

A HALT is not a failure. A HALT is a controlled stop for learning, evidence, and decision quality.

Conventions

• Bare paths resolve from the skill root.
• {skill-root} resolves to this skill's installed directory.
• {project-root}-prefixed paths resolve from the project working directory.
• {workflow.<name>} resolves to fields in customize.toml's [workflow] table.

Mandatory Rules

• Do not bypass a HALT.
• Do not continue unless resume conditions are met.
• Do not downgrade a hard HALT to a soft HALT without user approval.
• Do not claim evidence exists unless it is available and referenced.
• Always record the resolution in .decision-log.md.

On Activation

1. Resolve customization:

   python3 {project-root}/_dew/scripts/resolve_customization.py --skill {skill-root} --key workflow

   If the script fails, read {skill-root}/customize.toml directly and use defaults.

2. Execute {workflow.activation_steps_prepend}.

3. Load persistent facts from {workflow.persistent_facts}.

4. Load config from {project-root}/_dew/dew/config.yaml if present.

5. Load:

   • {workflow.halt_catalog}
   • {workflow.halt_template}
   • {workflow.halt_resolution_template}

6. Greet user in configured language.

Execution

Step 1 — Identify HALT

Find:

• HALT ID
• HALT type
• trigger
• phase
• artifact affected

Step 2 — Explain risk

Explain:

• why this HALT matters
• what can go wrong if ignored
• which lifecycle stages are affected

Step 3 — Show current state

List:

• known facts
• unknowns
• assumptions
• missing evidence
• related artifacts

Step 4 — Present options

Present options: A. Resolve now B. Continue with caveat C. Reduce scope D. Return to previous phase

Step 5 — Recommend

Recommend one option with reasoning.

Step 6 — Ask user

Ask the user to choose A/B/C/D.

Stop here.

Step 7 — Apply resolution

After user decision:

• update .decision-log.md
• update .learning-log.md
• update current artifact frontmatter
• update evidence index if applicable
• state resume condition

Step 8 — Resume or remain blocked

If resume condition is satisfied, say what step can continue.

If not satisfied, keep status as blocked and explain what is still missing.