improve-comorph

name	improve-comorph
description	Orchestrate a complete Comorph improvement workflow across repository audit, change design, implementation, validation, and durable documentation. Use when planning, implementing, diagnosing, reviewing, or documenting Comorph changes, or when carrying a concrete migration blocker from discovery through a verified result.

Improve Comorph

Run the workflow

Treat each stage as an independent unit with an explicit handoff. Run only the stages authorized by the request; do not turn a review or diagnosis request into implementation.

Step	Instruction
1. Audit	01-audit.md
2. Design	02-design.md
3. Implement	03-implement.md
4. Validate	04-validate.md
5. Record	05-record.md

Before each step, read its one corresponding reference completely and follow it. Pass the prior step's handoff as input without importing incidental conversation history.

Control the flow

Start at the earliest stage whose required input is missing:

• Start at audit for a vague request, suspected blocker, regression, or unexplored idea.
• Start at design when a trustworthy audit already identifies the problem and owning layers.
• Start at implementation when an accepted design and executable contracts exist.
• Start at validation for an existing implementation or review request.
• Start at record when verified behavior only needs durable documentation.

Return to an earlier stage when a stage exposes a false assumption. Do not patch around a design failure inside implementation or weaken an assertion inside validation.

Preserve shared principles

Across all stages:

• Prioritize real migration blockers over API breadth.
• Keep the public surface small and the semantic planner strong.
• Preserve the parser-neutral, read-only AST and command-to-patch architecture.
• Prefer safe diagnostics or unchanged output over ambiguous automatic edits.
• Preserve unrelated worktree changes.
• Do not version, commit, push, or publish unless explicitly requested.

Complete the workflow

Finish only when every requested stage meets its reference exit criteria. Summarize the final capability, affected vertical slice, verification evidence, and remaining boundaries. Keep release work as a separately authorized follow-up.