assess-methodology

Assessing methodology selection involves evaluating project context against decision frameworks. This Skill analyzes requirements stability, team size, and time-to-market constraints to recommend Scrum, Kanban, or Lean based on predefined guidelines and resolution cascades.

Deciding between Scrum and Kanban requires analyzing project variables. This Skill evaluates your requirements stability, team size, and time-to-market constraints through a resolution cascade, then updates your way-of-working.md file with the formally adopted methodology.

The methodology assessment framework processes existing guidelines via a resolution cascade. It prioritizes argument overrides and existing adoption checks before triggering a full assessment, ensuring the selected methodology respects predefined project constraints.

Yes, you can automatically document methodology selection. This Skill updates the way-of-working.md adoption file with the selected approach and records the decision as an Architecture Decision Log (ADL) entry to maintain project governance.

You should avoid an automated methodology selector when project context or predefined guidelines are undefined. The assessment relies on a resolution cascade involving argument overrides and existing adoption checks, requiring structured project inputs to produce valid recommendations.