Gsd plan phase

• ◦Ask one question at a timein 51 of 1099
• ◦Break plans into vertical slicesin 29 of 1099, across 11 files
• ◦Publish issues in dependency orderin 27 of 1099, across 9 files
• ◦Iterate until user approves the breakdownin 25 of 1099, across 7 files
• ◦Explore the repository to understand the codebase statein 24 of 1099, across 7 files
• ◦Use domain glossary vocabularyin 23 of 1099, across 5 files
• ◦Apply correct triage labels to published issuesin 23 of 1099, across 5 files
• ◦Prefer AFK slices over HITLin 22 of 1099, across 7 files
• ◦Write a specification before writing any codein 22 of 1099, across 14 files
• ◦Write failing tests before implementation codein 22 of 1099, across 20 files
• ◦Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
• ◦Respect existing architecture decision recordsin 20 of 1099, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.