MCP serverorg.agile-today/agile-today

Evaluates gate g.g0 … g.g10 against your evidence. Outcome precedence: Stop > Recycle > Hold > Conditional go > Go, with the rule that fired (outcome_reason). Critical evidence mis

For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.g. seven estimation methods), items to avoid or not applicable here, risks, mi

One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite. Filter with link_types, direction and limit.

Call first. Returns the context dimensions and flags (with defaults and how many rules each flag drives), stages, gates, evidence states and levels, the gate outcome precedence and

Route from presale to closure for a project context. Default is compact (ids by strength + a names dictionary, core items and gate evidence for all stages, about 6–10k characters).

Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.

Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts). Errors: empty plan, unknown ids, non-step types, stage order (analysis and des

For one event, practice, technique, notation, tool, artifact or antipattern: does it fit this context (fits / avoid / not_applicable / antipattern), its strength and why, alternati