{
  "id": 20600403,
  "title": "The Design Logic Behind Eight Skills",
  "url": "https://urgent.news/2026/11/18/the-design-logic-behind-eight-skills",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T13:31:24.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/joyet/the-design-logic-behind-eight-skills-265a"
  },
  "original_language": "en",
  "account": "The eight SKILLs are designed to support the project specification document, which serves as a machine contract for AI. Each SKILL covers a specific stage in the development process, from design to development to review. The first group of four SKILLs, known as the issue chain, focuses on maintaining the connection between conversation and the record. The agenda established at the beginning of a discussion serves as the anchor, ensuring that discussions are properly concluded and tracked in the project document. These four SKILLs are typically used when a discussion spans multiple AI sessions or when a discussion needs to be archived after an abnormal interruption. The second group of four SKILLs, referred to as the delivery chain, aims to prevent design and implementation from becoming separate entities. The spec-dev-loop SKILL ensures that code skeletons are frozen before implementation begins, while the spec-code-review SKILL addresses changes made during development that may cause the documentation to become outdated. The final SKILL, spec-code-smell, focuses on maintaining code quality by identifying potential issues early in the development process. These eight SKILLs are not designed to replace human judgment or guarantee the correctness of the design. Instead, they provide a framework for ensuring that decisions made during the development process are properly documented and can be checked by the AI.",
  "summary": "In the previous post I said that the defenses we bought with real incidents eventually turned into eight concrete SKILLs. This post explains how to use those eight. Before I unpack them, one premise has to be settled: the tools serve the project specification document (ProjectSpec) , because that document is the first-class citizen of the whole system. It is not only a document asset for people…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}