workflow trained

A workflow routes an authorized goal through discovery, decision, implementation, and proof. It never resets the user's authority.

Read the owning guide, inspect the live path, and run the smallest check that proves the changed boundary.

• Use the existing project spec, plan, issue, and report owner.
• Diagnose concrete failures before repair.
• Use an optional mode only when it serves the actual requested outcome.

The guide map can route broad development requests without imposing a single heavy pipeline.

Optional CLI workflows depend on installed tools and project ownership. Check both before invoking one.

A named mode is not permission to make a worktree, publish, or demand repeated approval. User and project instructions remain authoritative.

This layer synthesizes the workflow guide map under local law, with the skills fleet's AGENTS.md as its contract. The command procedures are not verified in this runtime, so the layer makes no claim about external CLI behavior: check the specific tool in the execution environment before use.

No version-specific workflow CLI defect has been verified here.

• A pipeline that demands a review agent for a small fix gets a proportionate review plus the required project gates.
• When a suggested report path conflicts with project ownership, write to the owning project document instead.