{
  "context": "Tests whether the agent correctly classifies mixed content (procedures vs facts vs suggestions) and follows the copy-then-edit workflow when converting existing documentation into a tile.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "DB guide is a skill",
      "description": "The database-setup-guide content is categorized as a skill (in a skills/ directory), not as docs, because it contains numbered steps and imperative verbs describing a procedure",
      "max_score": 12
    },
    {
      "name": "Service catalog is docs",
      "description": "The service-catalog content is placed in a docs/ directory, since it is purely factual reference material",
      "max_score": 10
    },
    {
      "name": "Standards not a rule",
      "description": "The coding-standards content is NOT placed as a rule (not in rules/ or steering), since the source says they are 'general guidelines' and 'suggestions' — not critical MUST/NEVER constraints",
      "max_score": 12
    },
    {
      "name": "Copy-first approach",
      "description": "The conversion-log.md mentions copying or moving files first before editing them (not rewriting from scratch)",
      "max_score": 10
    },
    {
      "name": "Docs have index.md",
      "description": "The docs directory contains an index.md that links to other doc files",
      "max_score": 8
    },
    {
      "name": "Skill has SKILL.md",
      "description": "The skill directory contains a SKILL.md file (not skill.md or README.md)",
      "max_score": 8
    },
    {
      "name": "SKILL.md has frontmatter",
      "description": "SKILL.md has YAML frontmatter with name and description fields",
      "max_score": 8
    },
    {
      "name": "tile.json has steering or not",
      "description": "If coding standards ARE included as rules, they are under a 'steering' key (not 'rules' key) in tile.json. If not included as rules (correct), this passes automatically.",
      "max_score": 8
    },
    {
      "name": "Tile name format",
      "description": "tile.json name follows workspace/tile-name format: platform-eng/platform-ops",
      "max_score": 8
    },
    {
      "name": "Content type reasoning",
      "description": "conversion-log.md explains the classification rationale, mentioning that procedural/step-by-step content belongs in skills, not docs",
      "max_score": 8
    },
    {
      "name": "Lowercase hyphen files",
      "description": "All markdown files in the tile use lowercase names with hyphens (no uppercase, no underscores)",
      "max_score": 8
    }
  ]
}