Method Commitment

Use this skill to run a Method Commitment Workflow: normalize exactly one Source Method against exactly one Method Commitment Source Problem, review inherited local context, reconstruct the method anatomy, attack high-risk design assumptions with the user, record structure-changing decisions, assign a status, and write status-aligned artifacts.

This is a convergence workflow. It does not run broad method search, invent a full method from nothing, automatically choose the best Candidate Method, or write full experiment plans.

Only committed output is downstream-ready. provisionally-committed, needs-redesign, and reject-current-method must not be routed as normal sources for downstream workflows.

Output Root

Set {workspace-root} before creating, scanning, or updating artifacts:

• Default {workspace-root} to workspace (the repo-local workspace/ directory).
• If the user specifies a workspace root, use that path exactly and do not add another workspace/ layer.
• If the user provides an existing artifact or workflow path, infer {workspace-root} from that path and keep related artifacts under the same root.
• Do not create generated workflow directories directly at the repository root.

Create or resume one method commitment folder at: