Defame1297
60be7b3232
Only 12 of 39 skills carried metadata.version, and adoption tracked which plugin a skill lived in rather than any stated rule: core, gitea and lint were consistent adopters, bin and kyberforge were consistent non-adopters, git was split with one outlier. There was no documented convention, and skill-author's own bump logic was already written as if presence were conditional. metadata.version is now required on every skill. The 19 skills here that never carried one (bin, kyberforge, gitea-files) are seeded at 1.0.0, not 0.1.0 -- that value stays reserved for a skill's actual creation point under skill-author's existing convention. The skill-frontmatter pre-commit hook now fails a SKILL.md missing the field, the same class of failure as a missing name/description. Full rationale in the new ADR. The git-plugin skills that also need this field follow in the next commit, bundled with issue #113's rtk normalization since both touch the same files. Refs: #127 ADR: 0022 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP
17 lines
683 B
Markdown
17 lines
683 B
Markdown
---
|
|
name: grill-me
|
|
description: >
|
|
Use when the user says "grill me" or wants a plan or design stress-tested by
|
|
relentless interview — one question at a time, down each branch of the
|
|
decision tree. Not a plan to challenge against `CONTEXT.md` and ADRs ->
|
|
`grill-with-docs`.
|
|
metadata:
|
|
version: "1.0.0"
|
|
---
|
|
|
|
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
|
|
|
|
Ask the questions one at a time.
|
|
|
|
If a question can be answered by exploring the codebase, explore the codebase instead.
|