project-workflow

Refresh project conventions by comparing AGENTS.md and explicitly selected host-specific rules with objective repository state, then applying authorized drift fixes.

Close READY features by merging durable conclusions into current truth and moving approved feature directories into archive with history preserved.

Run the end-of-feature gate across checks, project conventions, change-spec compliance, current truth, and the delivery receipt.

Understand a proposed change, resolve consequential unknowns, and create or reuse only the feature record needed for acceptance or handoff. Keep ordinary questions and diagnosis in conversation; tiny local fixes need no record.

Initialize the neutral six-file project-workflow baseline when its destinations are absent and existing content, if any, does not require personalization. Preserve incidental files; route project evidence or baseline conflicts to project-personalize.

Adapt a target whose project evidence or partial/custom baseline must shape the working agreement, using repository evidence and explicit user decisions.

Run the canonical pre-implementation requirements-reconciliation and quality gate for a proposed or accepted feature record. Do not use for a material correction to an accepted contract; use spec-revise first.

Reconcile objective contradictions among accumulated specs, current truth, ADRs, and optional implementation evidence.

Revise a materially wrong accepted or delivered-but-unarchived contract, including when the user corrects, rejects, removes, or replaces accepted behavior, while updating affected decisions, acceptance, optional work notes, and any conditional ADR.