CtrlK
BlogDocsLog inGet started
Tessl Logo

emerge/state-manager

Manages architecture project state in .arch/state.json and .arch/decisions.md. Activates when reading or updating project phase state, tracking component acceptance, logging decisions, or validating phase transitions.

74

1.01x
Quality

85%

Does it follow best practices?

Impact

59%

1.01x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-3/

{
  "context": "Tests whether the agent correctly reads Phase 2 sub-phase flags and blocks a jump from pattern (accepted) to cross_cutting, enforcing that components_overview must be accepted first.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "sub_phase NOT changed to cross_cutting",
      "description": "Output .arch/state.json does NOT have `sub_phase` set to `\"cross_cutting\"` — the skip was blocked",
      "max_score": 30
    },
    {
      "name": "state.json otherwise unchanged",
      "description": "Output .arch/state.json has the same `current_phase`, `pattern_accepted`, `components_overview_accepted`, and `cross_cutting_accepted` values as the input",
      "max_score": 20
    },
    {
      "name": "components_overview referenced",
      "description": "response.md or output explicitly references `components_overview` (or 'component map') as the sub-phase that must be completed next",
      "max_score": 25
    },
    {
      "name": "Sequential ordering explained",
      "description": "response.md or output explains that Phase 2 sub-phases must be accepted in order, or that cross_cutting cannot begin until components_overview is accepted",
      "max_score": 25
    }
  ]
}

evals

SKILL.md

tile.json