capability-assess-methodology

Score each methodology on requirements stability, change tolerance, team size, time to market, and predictability needs using the comparison matrix. Kanban fits small teams with changing requirements; Scrum fits teams needing fixed iteration cadence and predictability.

Run the assessment to load methodology guidelines and project context like the PRD and architecture docs. It applies a weighted scoring matrix and decision tree, then presents a recommendation with rationale, ceremonies, and trade-offs for approval.

Yes, pass a choice argument such as kanban or scrum to override the assessment. The skill confirms the choice, checks for conflicts with existing adoption, and proceeds directly to writing the adoption file.

The skill detects the existing methodology in way-of-working.md, confirms it is still valid, and exits without changes. If the decision record is missing, it backfills one by composing the decision-recording skill.

Yes, hybrid approaches are documented explicitly: which elements come from which methodology and how they combine. If two methodologies score within 10 percent, both are presented with a trade-off analysis.

The skill degrades gracefully by falling back to a minimal assessment that asks the developer for a preference based on team size and requirements stability. It also warns if the decision-recording skill is not installed and skips recording.